From: Ronald G Minnich <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] semi-synthetic file system
Date: Tue, 27 Sep 2005 17:07:40 -0600 [thread overview]
Message-ID: <4339D0BC.8080405@lanl.gov> (raw)
I'd like to make a file system that reflects /proc from a linux node,
but that adds plan9-style proc support, e.g. text commands for ctl, and
so on. (note we're adding plan9 style ctl etc. to linux /proc, here, but
don't know if the linux core will buy it).
What I'm thinking to do is tag /proc in some way, when walk()ing to it,
in the QID, then track children of /proc, and tag them in some way, and
then make it so that walk will allow people to walk to the mythical ctl
file This directory won't exist in linux, only in my semi-synthetic file
server.
I'm wondering if something like this has not already been done, or if
there is some better way to do it. Has anyone done a mixed sort of file
server like this? I would most prefer just to hack u9fs, for a number of
reasons, but I'm open to better ideas.
thanks
ron
next reply other threads:[~2005-09-27 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 23:07 Ronald G Minnich [this message]
2005-09-27 23:18 ` Steve Simon
2005-09-28 16:29 ` rog
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=4339D0BC.8080405@lanl.gov \
--to=rminnich@lanl.gov \
--cc=9fans@cse.psu.edu \
/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).