Re: enforcing DB immutability
From: Erik Mouw <hidden>
Date: 2005-04-20 15:57:28
Also in:
lkml
From: Erik Mouw <hidden>
Date: 2005-04-20 15:57:28
Also in:
lkml
On Wed, Apr 20, 2005 at 08:41:15AM -0000, linux@horizon.com wrote:
[A discussion on the git list about how to provide a hardlinked file that *cannot* me modified by an editor, but must be replaced by a new copy.]
Some time ago there was somebody working on copy-on-write links: once you modify a cow-linked file, the file contents are copied, the file is unlinked and you can safely work on the new file. It has some horrible semantics in that the inode number of the opened file changes, I don't know if applications are or should be aware of that. Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands