mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Davies <james_m_davies@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Multiplexing filesystem
Date: Tue, 27 Nov 2001 17:38:42 +1000	[thread overview]
Message-ID: <20011127074333Z282845-17409+17724@vger.kernel.org> (raw)
In-Reply-To: <3C030FB4.C3303BE4@ecf.utoronto.ca>
In-Reply-To: <3C030FB4.C3303BE4@ecf.utoronto.ca>

What about implimenting something like KDE's IOSlaves at kernel level? you 
could then create a symlink to any recognized URL. This would also have 
plenty of other uses. 


On Tue, 27 Nov 2001 13:59, Mark Richards wrote:
> Quick question, which I suspect has a long answer.
>
> I would like to write a multiplexing filesystem.  The idea is as follows:
>
> The filesystem would ideally wrap another filesystem, such as nfs or smbfs
> or ext2.  Most operations would just be passed to the native fs call. 
> However, for some files, selectable at run time by some control singal,
> would actually reside on another file system.  The other filesystem would
> have to be mounted.
>
> The idea is for a version controlling filesystem.  The server would be a
> network server (hence the desire to wrap nfs) which presents a 'view' of
> the source code.  When the user reserves a file for editing, the file is
> copied to the local disk.  From that point on, the local file is referred
> to until the user commits the change or unreserves the file.  Ideally, the
> local copy of the file could be on any file system, not one that is
> necessarily local.  And this has to be totally transparent to the user,
> except for the step where the user 'reserves' the file.
>
> I've thought about two ways to do this.  One is to wrap the 'versioning'
> file system with a multiplexor that checks fs calls to see if they are
> referring to a file that is on a different fs.  The other approach is to
> intercept calls to the VFS to do the same trick.
>
> I'm new to the whole filesystem-coding thing, so bear with me if what i've
> just said makes no sense.  So, my question (I guess it wasn't quick after
> all) is: Can it be done, and are either of my two approaches feasible?  Any
> suggestions or tips?
>
> Thanks,
> Mark Richards
>
> PS please CC me if possible.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


  parent reply	other threads:[~2001-11-27  7:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-27  3:59 Mark Richards
2001-11-27  4:34 ` Jeff V. Merkey
2001-11-27  4:39   ` Jeff V. Merkey
2001-11-27  7:38 ` James Davies [this message]
2001-11-28  0:34   ` Pavel Machek
2001-11-27 10:27 ` Helge Hafting
2001-11-27 14:45   ` Mark Richards
2001-11-27 19:37     ` Mike Fedyk
2001-11-28 11:11     ` Helge Hafting
2001-11-29  1:56       ` Mark Richards
2001-11-27 15:15 ` Eli Carter
2001-11-27 23:39 ` Blake Barnett

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=20011127074333Z282845-17409+17724@vger.kernel.org \
    --to=james_m_davies@yahoo.com \
    --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

all inboxes | Powered by JetHome®