From: Jonathan Barker <jbarker@ebi.ac.uk>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Alexander Viro <viro@math.psu.edu>,
Britt Park <britt@drscience.sciencething.org>,
David Golden <david.golden@unison.ie>,
Dominik Kubla <kubla@sciobyte.de>,
Simon Richter <Simon.Richter@phobos.fachschaften.tu-muenchen.de>
Subject: Re: VFS mediator?
Date: Fri, 15 Mar 2002 14:28:22 +0000 [thread overview]
Message-ID: <200203151327.NAA303879@alpha1.ebi.ac.uk> (raw)
In-Reply-To: <200203141351.NAA257264@alpha1.ebi.ac.uk>
In-Reply-To: <200203141351.NAA257264@alpha1.ebi.ac.uk>
Dear All
On Thursday 14 Mar 2002 2:52 pm, I wrote:
> In brief: a kernel module which "exported" VFS requests to a (specified)
> user-space daemon would be useful. My particular application is a daemon
> which generates files on the fly - I would like to expose this as part of
> the filesystem. Ideally, the kernel module would deal with generation of
> fake inode numbers etc and the user-space daemon would simply be asked to
> create a pipe corresponding to a "filename" and (possibly) supply a
> directory tree.
Many thanks for all your useful suggestions. I'll look at them all and (when
I get time) compile a digest of answers. I'm particularly amused by the very
groovy perlfs (thanks to David Golden for pointing me towards it).
Jonathan
next prev parent reply other threads:[~2002-03-15 13:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 14:52 VFS mediator? Jonathan Barker
2002-03-14 23:09 ` Simon Richter
2002-03-14 23:33 ` Alan Cox
2002-03-15 0:00 ` Alexander Viro
2002-03-15 11:50 ` Simon Richter
2002-03-18 19:25 ` Pavel Machek
2002-03-18 22:18 ` Trond Myklebust
2002-03-18 22:38 ` Pavel Machek
2002-03-18 22:48 ` Trond Myklebust
2002-03-18 22:54 ` Pavel Machek
2002-03-18 23:05 ` Trond Myklebust
2002-03-19 0:15 ` Alan Cox
2002-03-18 22:29 ` Alexander Viro
2002-03-18 22:36 ` Pavel Machek
2002-03-15 14:28 ` Jonathan Barker [this message]
2002-03-19 13:45 Jesse Pollard
2002-03-19 21:24 ` Pavel Machek
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=200203151327.NAA303879@alpha1.ebi.ac.uk \
--to=jbarker@ebi.ac.uk \
--cc=Simon.Richter@phobos.fachschaften.tu-muenchen.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=britt@drscience.sciencething.org \
--cc=david.golden@unison.ie \
--cc=kubla@sciobyte.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.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).