From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] puzzling 9P server / 9pcon interaction
Date: Tue, 31 Mar 2015 23:23:16 +0000 [thread overview]
Message-ID: <CAJSxfmJVcfHb+TUzpTyieGLAKFyAM5ocdES7GZR4Twh7ZVRWoA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
i'm trying to test a new 9P fs with 9pcon. after posting the file server's
fd to /srv, it can be mounted (e.g. mount /srv/foo /n/foo) and walked
correctly. trying 9pcon on the same fd (e.g. aux/9pcon /srv/foo) results
in "inappropriate use of fd".
any ideas? fyi, the 9p code is from scartch based on re-re-reading of
0intro(5) docs, so it is entirely possible i missed something subtle that
9pcon doesn't tolerate.
[-- Attachment #2: Type: text/html, Size: 530 bytes --]
next reply other threads:[~2015-03-31 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 23:23 Skip Tavakkolian [this message]
2015-04-01 14:03 ` Charles Forsyth
2015-04-01 18:37 ` Skip Tavakkolian
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=CAJSxfmJVcfHb+TUzpTyieGLAKFyAM5ocdES7GZR4Twh7ZVRWoA@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).