From: Larry McVoy <lm@bitmover.com>
To: Jerome de Vivie <jerome.de-vivie@wanadoo.fr>
Cc: linux-kernel@vger.kernel.org, linux-fsdev@vger.kernel.org,
martizab@libertsurf.fr, rusty@rustcorp.com.au
Subject: Re: Yet another linux filesytem: with version control
Date: Mon, 23 Jul 2001 14:17:51 -0700 [thread overview]
Message-ID: <20010723141751.W6820@work.bitmover.com> (raw)
In-Reply-To: <3B5C91DA.3C8073AC@wanadoo.fr>
In-Reply-To: <3B5C91DA.3C8073AC@wanadoo.fr>; from jerome.de-vivie@wanadoo.fr on Mon, Jul 23, 2001 at 11:06:34PM +0200
> The multiple version filesystem (mvfs) of ClearCase gives a
> transparent acces to the data. I found this feature cool, but the
> overall system is too complex. I would like to write an extension
> module for the linux kernel to handle version control in a simply way.
Having been through this a time or two, a few points to consider:
a) This is a hard area to get right. I've done it twice, I told Linus that
I could do it the second time in 6 months, and that was 3 years ago and
we're up to 6 full time people working on this. Your mileage may vary.
b) Filesystem support for SCM is really a flawed approach. No matter how
much you hate all SCM systems out there, shoving the problem into the
kernel isn't the answer. All that means is that you have an ongoing
battle to keep your VFS up to date with the kernel. Ask Rational
how much fun that is...
c) If you have to do a file system, may I suggest that you clone the SunOS
4.x TFS (translucent file system)? It's a useful model, you "stack" a
directory on top of a directory and you can see through to the underlying
directory. When you write to a file, the file is copied forward to the
top directory. So a hack attack is
mount -t TFS my_linux /usr/src/linux
cd my_linux
hack hack hack
... many hours later
cd ..
umount my_linux
find . -type f -print # this is your list of modified files
It's a cool thing but only semi needed - most serious programmers already
know how to do the same thing with hard links.
More brains are better than less brains, so welcome to the SCM mess...
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2001-07-23 21:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 21:06 Yet another linux filesytem: with version control Jerome de Vivie
2001-07-23 21:17 ` Larry McVoy [this message]
2001-07-23 21:51 ` Rik van Riel
2001-07-23 22:19 ` Jerome de Vivie
2001-07-23 22:29 ` Rik van Riel
2001-07-23 23:05 ` Jerome de Vivie
2001-07-23 23:30 ` Rik van Riel
2001-07-24 13:30 ` Olivier Galibert
2001-07-24 16:42 ` Jerome de Vivie
2001-07-23 23:14 ` Larry McVoy
2001-07-24 23:57 ` Peter A. Castro
2001-07-23 22:00 ` Jerome de Vivie
2001-07-23 22:14 ` Larry McVoy
2001-07-23 22:27 ` Jerome de Vivie
2001-07-24 5:24 ` Albert D. Cahalan
2001-07-24 5:34 ` Larry McVoy
2001-07-24 6:06 ` Alexander Viro
2001-07-24 9:30 ` Padraig Brady
2001-07-24 19:07 ` Jan Harkes
2001-07-24 2:13 ` Keith Owens
2001-07-24 13:07 ` Andrew Pimlott
2001-07-24 17:14 ` Jerome de Vivie
2001-07-24 19:05 ` Andrew Pimlott
2001-07-24 23:14 ` Jerome de Vivie
2001-07-25 0:39 ` Andrew Pimlott
-- strict thread matches above, loose matches on Subject: below --
2001-07-23 22:50 Florin Iucha
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=20010723141751.W6820@work.bitmover.com \
--to=lm@bitmover.com \
--cc=jerome.de-vivie@wanadoo.fr \
--cc=linux-fsdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martizab@libertsurf.fr \
--cc=rusty@rustcorp.com.au \
/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