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

[Niels Möller]

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

> For this, you could probably use a virtual root filesystem that
> redirects all access to /servers/socket/2 to ~/servers/socket/2
> (such tricks can be done [soon?] with shadowfs for example] Or you
> could try a chroot approach. Or you compile a private glibc with a
> hacked up <hurd/paths.h>.

I think it would be a good thing to have environment variables for
overriding all paths in <hurd/paths.h>. Some of the servers already
have that, right? (Some or all must probably be ignored for setuid
programs).

That would make it a lot easier to try out hacked servers.

> The nice thing about the Hurd is that this has nothing to do with the
> kernel.

Except that one wants some things like an ethernet device driver that
does the Right Thing when several pfinet processes uses it at the same
time.

/Niels