From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Hardlink Pitfalls (was: Patches for REALLY TINY 386 kernels)
Date: Tue, 17 Jul 2007 13:43:43 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707171341420.10600@anakin> (raw)
In-Reply-To: <200707161722.53203.a1426z@gawab.com>
On Mon, 16 Jul 2007, Al Boldi wrote:
> Satyam Sharma wrote:
> > Or just "cp -al" to create multiple trees at (almost) no disk cost
> > that won't interfere with each other in any way, and makes the
> > development process / generating patchsets trifle easier as well ...
>
> That would be correct if hardlinks would actually do a CoW on modify, instead
> of misleading the user into thinking he is modifying an independent file.
>
> Moral of the story: try to avoid hardlinks as much as possible!
Or use a different user account.
I used to have `all' Linux kernel source trees hardlinked where possible, as
special user `src'. So I could create a `cp -rl' copy under my own account and
get an error when trying to modify a file.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2007-07-17 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 14:22 Hardlink Pitfalls (was: Patches for REALLY TINY 386 kernels) Al Boldi
2007-07-16 16:44 ` Satyam Sharma
2007-07-16 16:53 ` Jörn Engel
2007-07-16 17:23 ` Al Boldi
2007-07-16 21:10 ` Jörn Engel
2007-07-17 11:43 ` Geert Uytterhoeven [this message]
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=Pine.LNX.4.64.0707171341420.10600@anakin \
--to=geert@linux-m68k.org \
--cc=a1426z@gawab.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).