From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] puzzling 9P server / 9pcon interaction
Date: Wed, 1 Apr 2015 11:37:07 -0700 [thread overview]
Message-ID: <CAJSxfmKGnY2mw4vpGbo2OZkvFxGBviwyZuGRa2VQ0AhrMU1cyg@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5hdXU3eLpvG0jbMB3K2ofeLfpZ0T=QzW_4PNzWez-+aRA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
Thanks Charles. i had looked at /sys/src/9/port/sysfile.c, but couldn't
quite connect the dots.
On Wed, Apr 1, 2015 at 7:03 AM, Charles Forsyth <charles.forsyth@gmail.com>
wrote:
>
> On 1 April 2015 at 00:23, Skip Tavakkolian <skip.tavakkolian@gmail.com>
> wrote:
>
>> trying 9pcon on the same fd (e.g. aux/9pcon /srv/foo) results in
>> "inappropriate use of fd".
>
>
> You aren't allowed to read or write an fd directly once it has been used
> for 9P traffic by mount (devmnt).
>
[-- Attachment #2: Type: text/html, Size: 1107 bytes --]
prev parent reply other threads:[~2015-04-01 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 23:23 Skip Tavakkolian
2015-04-01 14:03 ` Charles Forsyth
2015-04-01 18:37 ` Skip Tavakkolian [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJSxfmKGnY2mw4vpGbo2OZkvFxGBviwyZuGRa2VQ0AhrMU1cyg@mail.gmail.com \
--to=skip.tavakkolian@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).