From: Padraig Brady <Padraig@AnteFacto.com>
To: Larry McVoy <lm@bitmover.com>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
linux-kernel@vger.kernel.org, linux-fsdev@vger.kernel.org
Subject: Re: Yet another linux filesytem: with version control
Date: Tue, 24 Jul 2001 10:30:12 +0100 [thread overview]
Message-ID: <3B5D4024.2080109@AnteFacto.com> (raw)
In-Reply-To: <20010723141751.W6820@work.bitmover.com> <200107240524.f6O5OwX286884@saturn.cs.uml.edu> <20010723223413.G15284@work.bitmover.com>
Larry McVoy wrote:
>
> Useful stuff would be the copy on write file system, that's good for SCM
> and other things
Ooh ooh! are there any filesystems @ present that support copy on write?
Seems like a very useful feature that would be relatively easy to
implement (just
store a hash for each file in it's inode). With the ammount of duplicate
files on my
system (see freshmeat.net/projects/fslint) it would be very useful.
write() already
supports ENOSPC because of holes in files etc. There would be large
overhead
though as the hash for a file would have to be generated on each write()
? For a
"revision control" filesystem it would probably be more appropriate to
work @ the
block level instead? Hmm snapFS be appropriate for this ?
http://uwsg.iu.edu/hypermail/linux/kernel/0103.0/0436.html
Sorry just thinking out load..
Padraig.
next prev parent reply other threads:[~2001-07-24 9:32 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
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 [this message]
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=3B5D4024.2080109@AnteFacto.com \
--to=padraig@antefacto.com \
--cc=acahalan@cs.uml.edu \
--cc=linux-fsdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/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