linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Barker <jbarker@ebi.ac.uk>
To: linux-kernel@vger.kernel.org
Subject: VFS mediator?
Date: Thu, 14 Mar 2002 14:52:04 +0000	[thread overview]
Message-ID: <200203141351.NAA257264@alpha1.ebi.ac.uk> (raw)

Dear all

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. 

Clearly, an application-specific module could do the job - cf NFS. But I am 
not (yet) skilled enough in kernel development to know how, and it seems to 
me that a "VFS mediator" module could simplify development of many 
VFS-related applications (eg mounting ftp sites). Is there a kind soul out 
there who has already done this, or is willing to undertake such a task? 

Thanks for any input

Jonathan

Dr Jonathan Barker
EMBL-EBI Hinxton
jbarker@ebi.ac.uk

 

             reply	other threads:[~2002-03-14 13:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14 14:52 Jonathan Barker [this message]
2002-03-14 23:09 ` VFS mediator? 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
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=200203141351.NAA257264@alpha1.ebi.ac.uk \
    --to=jbarker@ebi.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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).