[9fans] #a

[9fans] #a

[quanstro]

why is #a references directly and not part of the standard namespace?

- erik

Re: [9fans] #a

[C H Forsyth]

[-- Attachment #1: Type: text/plain, Size: 94 bytes --]

like #D it can't be exported or imported so you must always use one
that's known to be local.

[-- Attachment #2: Type: message/rfc822, Size: 2434 bytes --]

From: quanstro@quanstro.net
To: 9fans@cse.psu.edu
Subject: [9fans] #a
Date: Fri, 7 Jul 2006 22:44:04 -0500
Message-ID: <76ccd76a4e207d6e2fdce387f428c3ad@quanstro.net>

why is #a references directly and not part of the standard namespace?

- erik

Re: [9fans] #a

[erik quanstrom]

that's a bit pedantic, isn't it?   i would like to mount #a from a linux machine
so i can get upas working with imaps.

- erik

On Sat Jul  8 03:40:22 CDT 2006, forsyth@vitanuova.com wrote:

> like #D it can't be exported or imported so you must always use one
> that's known to be local.

>>From: quanstro@quanstro.net
>> why is #a references directly and not part of the standard namespace?

- erik

Re: [9fans] #a

[Charles Forsyth]

> that's a bit pedantic, isn't it?   i would like to mount #a from a linux machine
> so i can get upas working with imaps.

i'm afraid i'm not being pedantic. it will only work locally, because
its interface (like #D's) is peculiar: the file descriptor number
for the connection to protect is included in the "fd" ctl request,
and that is not going to be correct at the remote end.
it works locally because the kernel device of course has
access to the correct file descriptor table to index by the number
to find the right Chan for the connection.