From: "Jörn Engel" <joern@logfs.org>
To: Satyam Sharma <satyam.sharma@gmail.com>
Cc: Al Boldi <a1426z@gawab.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Hardlink Pitfalls (was: Patches for REALLY TINY 386 kernels)
Date: Mon, 16 Jul 2007 18:53:12 +0200 [thread overview]
Message-ID: <20070716165312.GA32647@lazybastard.org> (raw)
In-Reply-To: <a781481a0707160944h2f991739p69058208cdf13f76@mail.gmail.com>
On Mon, 16 July 2007 22:14:41 +0530, Satyam Sharma wrote:
> On 7/16/07, Al Boldi <a1426z@gawab.com> 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.
>
> "patch" already handles this correctly ... and backupcopy=auto,breakhardlink
> in vim (and something similar in other editors I presume)
Yet even a single program failing to break the link will leave you with
a mess to sort out. The only place that can ensure to always break the
link is the kernel. Which is why I wrote the cowlink patches some years
back.
The still need a lot of love to be merge-ready. But I do use them on a
daily basis.
Jörn
--
Joern's library part 2:
http://www.art.net/~hopkins/Don/unix-haters/tirix/embarrassing-memo.html
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-07-16 16:56 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 [this message]
2007-07-16 17:23 ` Al Boldi
2007-07-16 21:10 ` Jörn Engel
2007-07-17 11:43 ` Geert Uytterhoeven
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=20070716165312.GA32647@lazybastard.org \
--to=joern@logfs.org \
--cc=a1426z@gawab.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=satyam.sharma@gmail.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;
as well as URLs for NNTP newsgroup(s).