Re: Latest Tarball Problems
Your problem is that libc looks at /servers/socket/2 when programs
attempt to use inet domain sockets, *not* /servers/socket/inet.
/servers/socket/inet and /servers/socket/local are not used by
anything, except as little reminders as to which translator is used
for which domain number.
What happened between gnu-0.2 and now is /servers/socket/inet used to
be a hard link to /servers/socket/2, and so your `settrans
/servers/socket/inet ...' was synonymous with `settrans
/servers/socket/2 ...', because they referred to the same inode.
Nowadays, /servers/socket/inet is just a symlink, which makes it a
different inode than /servers/socket/2, hence your difficulties.
Of course, if you woke up pfinet by referencing /servers/socket/inet,
then it would answer pings, but that didn't help programs that were
using /servers/socket/2 to find the running pfinet.
More sense?
--
Gordon Matzigkeit <gord@fig.org> //\ I'm a FIG (http://fig.org/)
Committed to freedom and diversity \// I use GNU (http://gnu.fig.org/)
Reply to: