If I understand casper snapshot correctly, it relies on a dedicated
partition for the persistence.
How difficult is it to make casper write directly to /casper on the main
IMHO it would be more usable.
On 4/12/07, Marco Amadori <firstname.lastname@example.org> wrote:
> Alle 08:12, gioved? 12 aprile 2007, Daniel Baumann ha scritto:
> > Hadar wrote:
> > > Another approach is to manage only one changes module. On boot this
> > > module is extracted to /cow (RAM), so following writes are made to
> > > On shutdown, this /cow is compressed again and saved on casper
> > > In this approach cons are RAM consumption and slow shutdowns because
> > > the big compressions.
> > ...and since it only write once per run on the usb-stick, it doesn't
> > shortcut its life; so I would be in favour of having this.
> This is what casper already supports with it's snapshot feature, the file
> be cpio.gz, squashfs or just a file image (ext2), but it is not saved
> in /casper, just where it was found at boot stage (with names
> like "casper-sn*", and "home-sn*")
> Debian-live-devel mailing list
-------------- next part --------------
An HTML attachment was scrubbed...