* Russ Cox <[EMAIL PROTECTED]> wrote:
> you can run
>
> verbose9pserve=2 vacfs ...
>
> and you will get a lot of debugging messages on standard error.
thx, I'll have a try.
> among other things, you'll get a trace of all the 9p traffic,
> and you can check whether this is true. i doubt v
>>
>> if dial strings are written with / and not !
>>/net/tcp/bell-labs.com/http,
>> an appropriately constructed namespace could
>> allow the "correct" fileserver to pass judgement.
>>
>
> Why include the tcp path element? Name resolution should be able to
> determine the best network pa
On Sun, Jun 1, 2008 at 10:41 AM, erik quanstrom <[EMAIL PROTECTED]> wrote:
>
> if dial strings are written with / and not !
>/net/tcp/bell-labs.com/http,
> an appropriately constructed namespace could
> allow the "correct" fileserver to pass judgement.
>
Why include the tcp path element?
the fact that dial strings live in their own parallel
universe has always seemed un-plan 9-ish to me.
> network addresses and files are different kinds of names.
> mixing them would introduce ambiguities, like what
> if i have a file name 'tcp!bell-labs.com!http'.
we don't have this problem with
> BTW: I've now mounted an vacfs from Midnight Command :)
> But when trying to overwrite, it causes mc to hang. Could it be
> that vacfs drops certain messages instead of returning an
> appropriate error ?
you can run
verbose9pserve=2 vacfs ...
and you will get a lot of debugging messa
* Russ Cox <[EMAIL PROTECTED]> wrote:
> > seems like dial() doesn't accept socket path names.
> > I'll have a look if I can fix this ...
>
> sorry, that should be
>
> 9pserve -c unix!`namespace`/acme tcp!*!12345
yep, already found it out.
Seems to work fine.
BTW: I've now mounted an vacfs
> seems like dial() doesn't accept socket path names.
> I'll have a look if I can fix this ...
sorry, that should be
9pserve -c unix!`namespace`/acme tcp!*!12345
i had considered not requiring the unix! once,
but i decided against it.
russ
* Russ Cox <[EMAIL PROTECTED]> wrote:
Hi,
> If you were to add a -c option to 9pserve
> to make it connect to a network address instead of
> using stdin/stdout, then you could use 9pserve
> to redirect the Unix postings onto TCP.
>
> ARGBEGIN{
> ...
> case 'c':
>
