From: Herbert Poetzl <herbert@13thfloor.at>
To: Terry Barnaby <terry1@beam.ltd.uk>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Inherited Filesystem for Linux
Date: Fri, 16 Apr 2004 19:49:29 +0200 [thread overview]
Message-ID: <20040416174929.GA18647@MAIL.13thfloor.at> (raw)
In-Reply-To: <40800BDB.3060104@beam.ltd.uk>
On Fri, Apr 16, 2004 at 05:37:47PM +0100, Terry Barnaby wrote:
> Hi,
>
> Is there or is anyone working on an Inherited file sustem for Linux
> (2.6.x kernels) ?
> I have seen very old postings on this issue but nothing recent.
>
> If not is there any good documentation on how to implement a kernel
> filesystem ?
>
> My application is a number of diskless nodes that I would like to share
> a basic file system, but allowing each node to have differing files
> for configuration differences etc. So any writes made to the
> Inherited file system would result in a file copy from the underlying file
> system and a write to the newly copied file.
maybe this provides a good starting point:
http://vserver.13thfloor.at/TBVFS/
best,
Herbert
> Cheers
>
> Terry
> --
> Dr Terry Barnaby BEAM Ltd
> Phone: +44 1454 324512 Northavon Business Center, Dean Rd
> Fax: +44 1454 313172 Yate, Bristol, BS37 5NH, UK
> Email: terry@beam.ltd.uk Web: www.beam.ltd.uk
> BEAM for: Visually Impaired X-Terminals, Parallel Processing, Software
> "Tandems are twice the fun !"
> -
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-04-16 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 16:37 Inherited Filesystem for Linux Terry Barnaby
2004-04-16 17:49 ` Herbert Poetzl [this message]
2004-04-16 18:39 ` Szakacsits Szabolcs
2004-04-23 9:22 ` Terry Barnaby
2004-04-23 13:25 ` Herbert Poetzl
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=20040416174929.GA18647@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=linux-fsdevel@vger.kernel.org \
--cc=terry1@beam.ltd.uk \
/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).