From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 19 Nov 2008 21:05:15 -0800 From: Roman Shaposhnik In-reply-to: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-id: <9768FEC3-5CF6-4CD6-A1BE-6E33A9705BA6@sun.com> MIME-version: 1.0 Content-type: text/plain; delsp=yes; format=flowed; charset=WINDOWS-1252 Content-transfer-encoding: QUOTED-PRINTABLE References: Subject: Re: [9fans] fd2path and devsrv Topicbox-Message-UUID: 4a6ebfb4-ead4-11e9-9d60-3106f5b1d025 On Nov 19, 2008, at 8:14 PM, erik quanstrom wrote: >> On Nov 19, 2008, at 7:32 PM, erik quanstrom wrote: >>>> Sure it can: >>>> % srv tcp!sources.cs.bell-labs.com!9fs test >>>> % ls /net/tcp >>>> /net/tcp/0 >>>> /net/tcp/1 >>>> /net/tcp/2 >>>> /net/tcp/clone >>>> % mount -n /net/tcp/2/data /n/test >>>> % >>> >>> ; mount /net/il/0/data /n/x >>> mount: mount /n/x: version conversion >> >> Huh? What gives -- of course I ran my example >> in 9vx, but it shouldn't matter -- should it? > > your example does work; mine was a counter example. But now I'm curious -- why didn't it work? > so following fd2path along its merry way down > to the source doesn't help generating such a script. > i could think of cases where it would be a hinderance. Fair enough. It does, invalidate the example given by Rob in his article though: ---------------------------------------------------------------------= ---------- Another program, ns, does this; it reads the /proc/n/ns file, decodes= =20 the information, and interprets it, translating the network addresses and quoting the = =20 names when required: =2E.. mount -a =92#s/dns=92 /net =2E.. mount -c il!135.104.3.100!12884 /mnt/term ---------------------------------------------------------------------= ---------- Thanks, Roman.