From: "Jörn Engel" <joern@logfs.org>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Rob Landley <rob@landley.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Copy on write hard links?
Date: Fri, 13 Dec 2013 17:58:02 -0500 [thread overview]
Message-ID: <20131213225802.GA21911@logfs.org> (raw)
In-Reply-To: <1380119333.7453.4.camel@localhost.localdomain>
On Wed, 25 September 2013 16:28:53 +0200, Thomas Meyer wrote:
>
> I wonder how hard it would be to implement this on vfs layer?
As an ugly hack: a few weeks maybe. Did it back in 2005 or so. If
you have higher standards, you will need support from the underlying
filesystem. Especially in order to make copying a large file on slow
storage anything but a nightmare.
Jörn
--
When in doubt, use brute force.
-- Ken Thompson
prev parent reply other threads:[~2013-12-14 0:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 18:36 Copy on write hard links? Thomas Meyer
2013-09-25 1:40 ` Adam Borowski
2013-09-25 13:59 ` Rob Landley
2013-09-25 14:28 ` Thomas Meyer
2013-09-25 14:37 ` richard -rw- weinberger
2013-09-29 5:22 ` Pádraig Brady
2013-09-29 7:14 ` Richard Weinberger
2013-09-29 17:19 ` Pádraig Brady
2013-12-13 22:58 ` Jörn Engel [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=20131213225802.GA21911@logfs.org \
--to=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=thomas@m3y3r.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.