Re: /servers/socket/2 -- why only one inet socket?

[Niels Möller]

Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de> writes:

> For socket servers, the simples thing to do would probably be to allow to
> override _SERVERS_SOCKET (eg "/servers/socket/" in glibc/hurd/hurdsock.c)
> with SOCKETSERVERS for non-suid programs.

I think that's the natural thing to do. Setting up a couple of links
is a lot easier than setting up an entire chroot environment. 

> Having PFINETSERVER, PFLOCALSERVER etc and check them according to
> the protocol family number is a bit more work, but also more
> userfriendly.

If one goes that way, one could just as well change the name "2" to
something more sensible. It's just a lookup from protocol number to a
string. Without having read the glibc code, I guess the point of the
current naming is that glibc doesn't need to know what protocol
families exist, so adding such a lookup into glibc seems to break that
design.

Regards,
/Niels