>>100146059
>Sockets appear in /dev/fd/n where n is the process's file descriptor (in linux).
That's just a symlink to /proc/self/fd. All FDs appear there, but that doesn't really make them a filesystem accessible thing. For example, you can't open a TCP socket by opening a device-like file on the socket. You can do that with other things, like terminals and block devices. /proc/self/ is just for introspection and debugging. Other Unixes don't necessarily have that.
You are right that opened sockets can be called files because you can access them normally with the write/read syscalls.
>But I don't know how it gets from the file descriptor to /dev/eth0.
Again, network devices aren't files. They don't appear on the filesystem. Unlike sockets, you can't even get FDs to them. Linux uses the netlink API to access them from userspace. The filesystem isn't involved. You can check with "strace ip link".
> Is the kernel packet scheduler and stuff before or after eth0?
What? Packet scheduler could mean anything.

Back | Go to board

Board:

/g/

Thread:

Why are devices in windows not files like in gano/launux?