Reason/explanation why the toram parameter changed to toram="live,syslinux"?
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
I've noticed that starting from 2.5.2-2 & 20170529-zesty the "To RAM" boot option's parameter has changed from toram=filesystem.squashfs to toram="live,syslinux". The changelog says that it is to enable Clonezilla Live in RAM to be used as lite server, but to me it seems redundant to copy both directories to RAM when the actual file system is only in filesystem.squashfs, plus the syslinux directory only contains the files required to boot through syslinux.
I've tried changing the parameter back to toram=filesystem.squashfs, and it still booted up fine. Mind you, I have limited experience with Clonezilla SE and don't really have a test environment for the lite server function, so maybe just copying filesystem.squashfs to RAM without the other files break that function? Would love an explanation on why that is though.
Of course you can use "toram=filesystem.squashfs" if you do not need to use Clonezilla lite server. However, in order to make lite server works, toram="live,syslinux" is a must.
Definitely we can improve that by including only vmlinuz and initrd, but this has to patch live-boot and make things more complicated.
The directory syslinux and live do not take too much space. Nowadays the modern machine which you can use "toram" option has big enough RAM to put those files in the RAM disk. Hence we decide to enable that for lite server.
Thanks for your understanding.
Steven