All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John P. Looney" <john@antefacto.com>
To: linux-kernel@vger.kernel.org
Subject: Re: COW fs (Re: Editing-in-place of a large file)
Date: Mon, 10 Sep 2001 10:35:49 +0100	[thread overview]
Message-ID: <20010910103549.E6058@antefacto.com> (raw)
In-Reply-To: <20010902152137.L23180@draal.physics.wisc.edu> <318476047.20010903002818@port.imtp.ilyichevsk.odessa.ua> <3B9B80E2.C9D5B947@riohome.com> <8015001541.20010910122851@port.imtp.ilyichevsk.odessa.ua>
In-Reply-To: <8015001541.20010910122851@port.imtp.ilyichevsk.odessa.ua>; from VDA@port.imtp.ilyichevsk.odessa.ua on Mon, Sep 10, 2001 at 12:28:51PM +0300

[-- Attachment #1: Type: text/plain, Size: 714 bytes --]

On Mon, Sep 10, 2001 at 12:28:51PM +0300, VDA mentioned:
> Now, sometimes we use hardlinks as "poor man's COW fs", but
> I bet it's error prone. Every now and then you forget it's a
> hardlinked kernel tree and start happily hacking in it... :-(

 And of course hardlinks don't work on directories...

> A "compressor" which hunts and merges duplicate blocks is a bonus,
> not a primary tool.

 Checkout http://freshmeat.net/projects/fslint/ - it's an excellent tool
for hunting down duplicate files, dangling links etc.

Kate

-- 
_______________________________________
John Looney             Chief Scientist
a n t e f a c t o     t: +353 1 8586004
www.antefacto.com     f: +353 1 8586014


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-09-10  9:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-02 20:21 Editing-in-place of a large file Bob McElrath
2001-09-02 21:28 ` COW fs (Re: Editing-in-place of a large file) VDA
2001-09-09 14:46   ` John Ripley
2001-09-09 16:30     ` John Ripley
2001-09-09 17:41       ` Xavier Bestel
2001-09-10  1:29         ` John Ripley
2001-09-10  6:45           ` Ragnar Kjørstad
2001-09-14 10:06           ` Pavel Machek
2001-09-10 11:11         ` Ihar Filipau
2001-09-10 16:10           ` Kari Hurtta
2001-09-10  2:43       ` Daniel Phillips
2001-09-10  2:58         ` David Lang
2001-09-10  9:28     ` VDA
2001-09-10  9:35       ` John P. Looney [this message]
2001-09-14 10:03     ` Pavel Machek
2001-09-02 21:30 ` Editing-in-place of a large file Ingo Oeser
2001-09-03  0:59   ` Larry McVoy
2001-09-03  1:24     ` Ingo Oeser
2001-09-03  1:31       ` Alan Cox
2001-09-03  1:50         ` Ingo Oeser
2001-09-03 10:48           ` Alan Cox
2001-09-03 14:31             ` Daniel Phillips
2001-09-03 14:46             ` Bob McElrath
2001-09-03 14:54               ` Alan Cox
2001-09-03 15:42                 ` Doug McNaught
2001-09-03 15:11               ` Richard Guenther
2001-09-03 21:19             ` Ben Ford
2001-09-03  4:27       ` Bob McElrath
2001-09-03  1:30     ` Daniel Phillips

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=20010910103549.E6058@antefacto.com \
    --to=john@antefacto.com \
    --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 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.