Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
I notice that on versions 22237 and 20140415 (amd64) you can't properly "Skip" the /home/part assignement and have the target drive image just get stored back onto the USB jump drive that we booted from (always get an Unkown Partition error). What I really need to do always is to clone a drive image right the the same USB stick I booted up from. Trying to start "Ram" mode and having to unplug / replug in the same USB stick is kind of lame (choosing Local Device), and the machine operators are always fouling it up not waiting long enough for the USB stick to get re-started after plugging in. I also did try partitioning the USB stick into two partitions, but that's a hassle trying to read out the second partition in Windows.
Did I miss something?
Can we please have Clonezilla work like it did on 22125 and 21125 (amd64) for instance? On those its really easy to just store the drive image right back on the same USB stick it booted up from. You just "Skip" and the /hom/part directory is assigned correctly right on the USB boot drive. It seems like thats the easieast and most intuitive way.
But again, maybe I missed something?
OH - I see in another post there is a way to preset the system to go toram, and then to mount /dev/sdb1 in the boot imnage.
I wish this just worked as it did in the other versions. I realize there was a possibility of a USB crash doing it the easy way, but seriously - we've used it thousands of times without error.
" we've used it thousands of times without error." -> It's risky, for FAT it might be OK, however, for some other file system, it might be not. Therefore we can not continue using that way.
If you really want to do that, you can put boot parameter
ocs_live_prerun="mount -o remount,rw /lib/live/mount/medium"
to force to do that.