Re: Automated package testing (Re: Is Sid for broken stuff? Is it too much to ask for testing the packages?)
> > > - shareable, copy-on-write block devices (makes repeated testing much more
> > > efficient)
> > How do you do that ? It might improve pbuilder-uml performance,
> > and reliability.
> Check out the HOWTO etc. on user-mode-linux.sf.net. Basically, you just do:
> where file1 is the (possibly read-only) backing file, and file2 is the
> copy-on-write data. The same backing file can be used with any number of
> COW files, and a COW file is invalidated when the backing file is changed.
I just noticed that COW just didn't stand for being BIG and like a cow,
but it was Copy-On-Write....