archive mirror
 help / color / mirror / Atom feed
From: Russ Lewis <>
Subject: Has it been done: User Script File System?
Date: Wed, 13 Jun 2001 10:39:19 -0700	[thread overview]
Message-ID: <> (raw)

Is there any filesystem in Linux that uses user scripts/executables to
implement the various function calls?  What I'm thinking of is something
along the lines of a file system module that, when it receives a call
from VFS, passes the information out to a user-mode daemon which could
then run scripts or executables to answer the question.  The daemon
would then return the answer to the module, and the module would answer

The reason I'm wondering is that I have a lot of brainstorms about
things that might be cool to implement as filesystems, but I don't want
to take the time to have to implement a full filesystem for each
(especially considering the number of bugs and kernel panics I'm likely
to encounter in the process).  What I'd really like to do is something
like this:

mount -t userfs   /etc/myfs.conf   /myfs

Where /etc/myfs.conf would have something like this:

lookup:  /usr/bin/myfslookup
open:   /usr/bin/myfsopen

I know that it would be very slow, and might require some modifications
to VFS to make it work (in addition to the module I'd have to write),
but it would be really nice to be able to throw together a very simple
utility filesystem without having to worry about crashing the kernel.

Does Linux have anything even remotely like this?  If not, I might (if I
can spare the time) play around with something like this of my own.

             reply	other threads:[~2001-06-13 17:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13 17:39 Russ Lewis [this message]
2001-06-13 17:12 ` Has it been done: User Script File System? Jeff Dike
2001-06-13 18:54 ` Peter Makholm
2001-06-13 19:43 ` Jeremy Fitzhardinge
2001-06-14 13:01 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).