From: "Anthony Sorace" <anothy@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] pipefs or cmdfs
Date: Sat, 21 Apr 2007 07:54:19 -0400 [thread overview]
Message-ID: <509071940704210454j4d4f36b9v767ddabbffc74b5d@mail.gmail.com> (raw)
In-Reply-To: <1BD003CD-1E32-4366-87CA-A1FBD3D59757@ar.aichi-u.ac.jp>
execnet(4) seems close to what you want, but not quite right - it
provides arbitrary command access, rather than a single command (which
could make sharing it awkward).
i think closer to what you want is' geoff's cmdfs (in his contrib
dir). it's only advertised to run on third edition, but if it doesn't
run on current it could be a good starting point. the comment at the
head matches what you want pretty well:
/*
* cmdfs mntpt cmd - mount this file server, writes into which become
* writes to a pipe to cmd. a new cmd is started for each open
* of mntpt/pipe, but only one is permitted at a time.
*/
next prev parent reply other threads:[~2007-04-21 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-21 10:59 arisawa
2007-04-21 11:54 ` Anthony Sorace [this message]
2007-04-21 17:09 ` Francisco J Ballesteros
2007-04-21 21:19 ` arisawa
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=509071940704210454j4d4f36b9v767ddabbffc74b5d@mail.gmail.com \
--to=anothy@gmail.com \
--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).