From: Jamie Lokier <jamie@shareable.org>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: unionfs
Date: Fri, 19 Mar 2004 09:11:48 +0000 [thread overview]
Message-ID: <20040319091148.GC2650@mail.shareable.org> (raw)
In-Reply-To: <20040316171038.GA27046@wohnheim.fh-wedel.de>
Jörn Engel wrote:
> And version control is something I actually want to be done inside the
> kernel, at least to some degree. People already use kernel support,
> although it sucks (cp -lr anyone?). Looks like the alternatives suck
> even more, so your point is void.
Fwiw, I much prefer your COW hard links to something where I have to
mount a new filesystem every time I "copy" a tree, and have to redo
those mounts each time I reboot, have a big ugly mess in "df" output,
what "du" get confused, and "rsync" has no hope of dealing with them
sensibly.
I also don't mind if copying isn't implemented in the kernel. I'm ok
with programs reporting an error that they couldn't write to a file
because it was linked readonly. At least that removes the danger of
accidental overwriting, and I can either fix it by hand or use an
LD_PRELOAD library which detects that error code from open() and
copies the file.
Even if vi and Emacs, which make it temptingly easy to ignore normal
read-only protection, were changed to be aware of and bypass the
read-only link attribute, they'd do the right thing: the attribute
expresses the _intent_ that removing it should always be done by
copying the file, whereas with hard links that intent isn't clear.
(Emacs has backup-by-copying-when-linked, but that isn't too helpful
because sometimes you want writing to a linked file to change both places).
So my vote is for the very simple COW hard link attribute, and leave
the rest to userspace.
Thanks!
-- Jamie
next prev parent reply other threads:[~2004-03-19 9:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 11:35 unionfs Carsten Otte
2004-03-15 12:19 ` unionfs Jörn Engel
2004-03-15 12:47 ` unionfs Ian Kent
2004-03-15 13:16 ` unionfs Jörn Engel
2004-03-15 14:35 ` unionfs Ian Kent
2004-03-15 16:13 ` unionfs Jörn Engel
2004-03-15 17:09 ` unionfs Claudio Martins
2004-03-15 19:22 ` unionfs Horst von Brand
2004-03-15 23:20 ` unionfs Chris Friesen
2004-03-16 16:04 ` unionfs Horst von Brand
2004-03-16 17:31 ` unionfs Jörn Engel
2004-03-16 18:04 ` unionfs Jörn Engel
2004-03-16 19:40 ` unionfs Horst von Brand
2004-03-16 20:45 ` unionfs Jörn Engel
2004-03-16 19:19 ` unionfs Horst von Brand
2004-03-16 20:00 ` unionfs Chris Friesen
2004-03-23 2:38 ` unionfs Robert White
2004-03-15 23:52 ` unionfs Jörn Engel
2004-03-16 16:18 ` unionfs Horst von Brand
2004-03-16 17:10 ` unionfs Jörn Engel
2004-03-19 9:11 ` Jamie Lokier [this message]
2004-03-19 9:42 ` unionfs Jörn Engel
2004-03-19 9:04 ` unionfs Jamie Lokier
2004-03-16 19:03 ` unionfs Andy Isaacson
2004-03-15 14:37 ` unionfs Ian Kent
2004-03-15 16:15 ` unionfs Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2004-03-08 9:52 unionfs Miklos Szeredi
2004-03-08 16:10 ` unionfs Bernd Schubert
2004-03-09 9:38 ` unionfs Miklos Szeredi
[not found] ` <20040311151343.GA943@escher.cs.wm.edu>
2004-03-11 15:44 ` unionfs Miklos Szeredi
2004-03-14 2:33 ` unionfs Ian Kent
2004-03-14 4:20 ` unionfs Horst von Brand
2004-03-16 12:42 ` unionfs Miklos Szeredi
[not found] ` <20040315214207.GA26615@escher.cs.wm.edu>
2004-03-16 13:43 ` unionfs Miklos Szeredi
2004-03-12 23:37 ` unionfs 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=20040319091148.GC2650@mail.shareable.org \
--to=jamie@shareable.org \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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).