"Axel z^ <axeld@xxxxxxxxxxxxxxxx> wrote: >> I remain in the position that there is absolutely no reason whatever >> that sockets need have their own syscalls: the current system works >> quite well and is vastly more extensible. > >Not that I would really object against you, but it has an advantage: >you can easily use networking functions from kernel drivers or file >systems; you can use that API from everywhere. This is a big pro for not using a socket driver approach. Which kernel drivers require to create sockets and send data? I don't know, perhaps a http server in the kernel, or a ftp filesystem. Might be a security problem to implement such things, but why not, allow it! Marcus