git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: enforcing DB immutability

From
EMErik Mouw <erik@harddisk-recovery.com>
Date
Apr 20, 2005, 15:57 UTC
Message-ID
<20050420155723.GC27307@harddisk-recovery.com>
In-Reply-To
<20050420084115.2699.qmail@science.horizon.com>
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
Previous: linux@horizon.comNext: Bill Davidsen
Message 2 of 3 in “Re: enforcing DB immutability”
  1. linux@horizon.comApr 20, 2005
  2. Erik MouwApr 20, 2005
  3. Bill DavidsenApr 22, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.