From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?B?SsO2cm4=?= Engel Subject: Re: Hardlink Pitfalls (was: Patches for REALLY TINY 386 kernels) Date: Mon, 16 Jul 2007 18:53:12 +0200 Message-ID: <20070716165312.GA32647@lazybastard.org> References: <200707161722.53203.a1426z@gawab.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Al Boldi , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Satyam Sharma Return-path: Received: from lazybastard.de ([212.112.238.170]:49562 "EHLO longford.lazybastard.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757985AbXGPQ4s (ORCPT ); Mon, 16 Jul 2007 12:56:48 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, 16 July 2007 22:14:41 +0530, Satyam Sharma wrote: > On 7/16/07, 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 .= =2E. > > > >That would be correct if hardlinks would actually do a CoW on modify= ,=20 > >instead > >of misleading the user into thinking he is modifying an independent = file. >=20 > "patch" already handles this correctly ... and backupcopy=3Dauto,brea= khardlink > 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 year= s back. The still need a lot of love to be merge-ready. But I do use them on a daily basis. J=C3=B6rn --=20 Joern's library part 2: http://www.art.net/~hopkins/Don/unix-haters/tirix/embarrassing-memo.htm= l - 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