That's Tungsten
- Posts
- 17
- Comments
- 227
- Joined
- 3 yr. ago
- Posts
- 17
- Comments
- 227
- Joined
- 3 yr. ago
Linux @lemmy.ml Gamepad latency of the XBOX series S controller
Linux @lemmy.ml How to manage configuration files
linuxmemes @lemmy.world Everything is so tiny
Programmer Humor @programming.dev His man.go
linuxmemes @lemmy.world His man.go
Linux @lemmy.ml Why can ffmpeg kmsgrab capture the tty without root permissions?
Linux Gaming @lemmy.ml Shadow of the tomb raider, native or proton-experimental
Linux @lemmy.ml I can now control external display brightness from KDE and I don't know why. Thank you, nameless Linux contributor
Linux Gaming @lemmy.ml PhysX on Batman Arkham Asylum
Linux @lemmy.ml Storing SSH keys on gnome-keyring, kwallet, ibsecret or similar
Linux @lemmy.ml Switching rgb range at monitor plugin
Linux @lemmy.ml Splitting headphones and internal speakers on a thinkpad with fedora
Linux @lemmy.ml Imagine trusting oracle
Memes @lemmy.ml All hail lemmyverse.net
Linux @lemmy.ml Can I apply a shader to the whole screen?
Reddit Migration @kbin.social remember to update your review of the official reddit app
Memes @lemmy.ml No more sad dinners
ISO/OSI is a neatly separated model mostly used on theory.
In practice, actual network stacks are often modeled after a simpler model that is called TCP/IP. Which despite the name is not actually TCP specific.
Here's the general description and correspondence to ISO/OSI:
Or, you can just not care about how the actual software stack is separated, and continue to use the most complete model, knowing that everyone will understand what you when you say "layer 2/3/4" anyway.
Plus, some could say that the TCP/IP model is equally unfit because the Linux network subsystem doesn't care about layers.
Edit: I hope the formatting of that table isn't broken on your client, because it is on mine