On Mon, 2005-05-16 at 12:38 -0600, Benjamin Bytheway wrote: > This 'copy-on-write' behavior is useful in some cases. The Arch can keep > revisions in a library and hard link checkouts instead of copying, increasing > speed of checkouts. To edit that tree without corrupting the library, you > want to break that hard link on write.
You will also notice that the Arch documentation cautions strongly against taking advantage of the this feature without careful consideration. Playing with hard links is becoming increasingly dangerous as meta data, such as se-linux contexts, is being added to files to improve user experience. Heck, even simple stuff like ownership and permissions can bite you. Just a couple days ago here at work we found a bug in gnu sed -i that was changing ownership incorrectly. Not to mention being a less than optimal solution in combination with large file support. You don't want to go around duplicating a > 2 GB file more than absolutely necessary. -- Stuart Jansen e-mail/jabber: [EMAIL PROTECTED] "XML is like violence: if it doesn't solve your problem, you aren't using enough of it." - Chris Maden
signature.asc
Description: This is a digitally signed message part
.===================================. | This has been a P.L.U.G. mailing. | | Don't Fear the Penguin. | | IRC: #utah at irc.freenode.net | `==================================='
