linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Charles P. Wright" <cpwright@cpwright.com>
To: Shaya Potter <spotter@cs.columbia.edu>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: fistgen-0.1.1 released (linux-2.6 support)
Date: Tue, 03 Aug 2004 08:42:31 -0400	[thread overview]
Message-ID: <1091536950.21607.5.camel@polarbear.fsl.cs.sunysb.edu> (raw)
In-Reply-To: <1091498050.7483.8.camel@localhost.localdomain>

On Mon, 2004-08-02 at 21:54, Shaya Potter wrote:
> > One uses it by typing "cp -a dir1 dir2" or "cp -r dir1 dir2".
> > 
> > That's all.  There are no user-visible versions, no branch
> > management, and no other commands.
> 
> I have a "working" (relative term as performance sucks) fs that can do
> that.  It combined a file system based out of fist's templates and a bit
> of hacking on ext3cow.
> 
> basic idea is that ext3cow provided the individual file versioning
> semantic (and directories are just treated as containers) while the
> stackable fs managed the branching (and deciding when to version and the
> like).
> 
> was able to build 4 kernels side by side w/o a problem.
> 
> i.e. it was something along the lines of (from memory)
> 
> # mkfs.ext3cow /dev/loop0
> # mount -t ext3cow /dev/loop0 /mnt
> # mount -o bind /mnt /mnt1
> # mount -o bind /mnt /mnt2
> # mount -o bind /mnt /mnt3
> # (cd /mnt ; tar xzf ~/linux.tar.gz)
> # mount -t branchfs -o new_branch=new,old_branch=,(some fist
> options) /mnt /mnt
> # cd /mnt
> # branch_ioctl new1
> # mount -t branchfs -o new_branch=new2,old_branch=new,(some fist
> options) /mnt1 /mnt1
> # mount -t branchfs -o new_branch=new2,old_branch=new,(some fist
> options) /mnt2 /mnt2
> # mount -t branchfs -o new_branch=new2,old_branch=new,(some fist
> options) /mnt2 /mnt2
> 
> lots of issues w/ it, but it was able to do the above as (well as then
> build the kernels).
> 
Shaya,

What does that sequence of commands actually mean?

Charles


  reply	other threads:[~2004-08-03 12:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 21:05 fistgen-0.1.1 released (linux-2.6 support) Erez Zadok
2004-07-30 21:31 ` Jeff Garzik
2004-07-30 21:41   ` Erez Zadok
2004-07-31 10:54     ` Jamie Lokier
2004-07-31 12:04       ` David Chow
2004-07-31 14:23         ` Erez Zadok
2004-07-31 14:41       ` Erez Zadok
2004-07-31 19:57         ` Jamie Lokier
2004-08-02 18:18           ` Erez Zadok
2004-08-02 19:08             ` Jamie Lokier
2004-08-02 20:34               ` Erez Zadok
2004-08-03  1:54               ` Shaya Potter
2004-08-03 12:42                 ` Charles P. Wright [this message]
2004-08-03 15:05                   ` Shaya Potter

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=1091536950.21607.5.camel@polarbear.fsl.cs.sunysb.edu \
    --to=cpwright@cpwright.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=spotter@cs.columbia.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).