Here's the state of persistence, to the best of my knowledge: live-snapshot (live-sn, home-sn): BROKEN
Cannot be used to make live-sn or home-sn snapshots, e.g. $ sudo live-snapshot -d /dev/hda1 live-snapshot: option requires an argument -- d live-rw: BROKEN If you create an ext2 partition labelled "live-rw" and boot "persistent" it will be detected and a snapshot of the /cow will be saved at shutdown, but it will be corrupted (due to errors during the shutdown?) which forces a fsck on the next reboot and/or kernel panic. Even if you boot without "persistent" to fix the corrupt filesystem and then reboot with "persistent", the kernel still panics. home-rw: works I am told that in etch, live-rw (casper-rw?) works with casper. If you want to be a hero, please help make persistence work. I get several queries about this per week on irc but have not had the time to do anything about it myself. Thanks, Ben -- ,-. nSLUG http://www.nslug.ns.ca [EMAIL PROTECTED] \`' Debian http://www.debian.org [EMAIL PROTECTED] ` [ gpg 395C F3A4 35D3 D247 1387 2D9E 5A94 F3CA 0B27 13C8 ] [ pgp 7F DA 09 4B BA 2C 0D E0 1B B1 31 ED C6 A9 39 4F ] _______________________________________________ debian-live-devel mailing list debian-live-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel