I'm not sure how important is the sequence of boot parameters when booting to Clonezilla. Is there any meaningful difference between the three versions of menu.lst shown below? I have tested version 1 and 3 with Grub4Dos v0.4.5c-2014-01-17 and Clonezilla v2.2.3-25 installed on the hard drive and both versions boot ok.
title Clonezilla Live (code with Environment Variables)
root (hd0,41)
set BOPT=boot=live live-config noswap nolocales edd=on nomodeset ip=frommedia
set PRERUN=ocs_prerun="sudo su -"
set RUN=ocs_live_run="ocs-live-general" ocs_live_extra_param="" keyboard-layouts=NONE ocs_live_batch="no" locales=en_US.UTF-8 vga=791 nosplash live-media-path=/live-hd bootfrom=/dev/sda42 toram=filesystem.squashfs
kernel /live-hd/vmlinuz %BOPT% %PRERUN% %RUN%
initrd /live-hd/initrd.img
3) As above, but to make the code cleaner, Debian boot parameters are grouped together under BOPT and Clonezilla parameters are placed under PRERUN and RUN environment variables:
title Clonezilla Live (cleaner code with Environment Variables)
root (hd0,41)
set BOPT=boot=live live-config noswap nolocales edd=on nomodeset ip=frommedia live-media-path=/live-hd bootfrom=/dev/sda42 toram=filesystem.squashfs
set PRERUN=ocs_prerun="sudo su -"
set RUN=ocs_live_run="ocs-live-general" ocs_live_extra_param="" keyboard-layouts=NONE locales=en_US.UTF-8 ocs_live_batch="no" vga=791 nosplash
kernel /live-hd/vmlinuz %BOPT% %PRERUN% %RUN%
initrd /live-hd/initrd.img
Last edit: Kirkx 2014-10-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure how important is the sequence of boot parameters when booting to Clonezilla. Is there any meaningful difference between the three versions of menu.lst shown below? I have tested version 1 and 3 with Grub4Dos v0.4.5c-2014-01-17 and Clonezilla v2.2.3-25 installed on the hard drive and both versions boot ok.
1) Version w/o environment variables, based on the code posted on Clonezilla's help page ( http://clonezilla.org/livehd.php ):
title Test: Clonezilla Live (code w/o Environment Variables)
root (hd0,41)
kernel /live-hd/vmlinuz boot=live live-config noswap nolocales edd=on nomodeset ocs_prerun="sudo su -" ocs_live_run="ocs-live-general" ocs_live_extra_param="" keyboard-layouts=NONE ocs_live_batch="no" locales=en_US.UTF-8 vga=791 ip=frommedia nosplash live-media-path=/live-hd bootfrom=/dev/sda42 toram=filesystem.squashfs
initrd /live-hd/initrd.img
2) The same code with environment variables:
title Clonezilla Live (code with Environment Variables)
root (hd0,41)
set BOPT=boot=live live-config noswap nolocales edd=on nomodeset ip=frommedia
set PRERUN=ocs_prerun="sudo su -"
set RUN=ocs_live_run="ocs-live-general" ocs_live_extra_param="" keyboard-layouts=NONE ocs_live_batch="no" locales=en_US.UTF-8 vga=791 nosplash live-media-path=/live-hd bootfrom=/dev/sda42 toram=filesystem.squashfs
kernel /live-hd/vmlinuz %BOPT% %PRERUN% %RUN%
initrd /live-hd/initrd.img
3) As above, but to make the code cleaner, Debian boot parameters are grouped together under BOPT and Clonezilla parameters are placed under PRERUN and RUN environment variables:
title Clonezilla Live (cleaner code with Environment Variables)
root (hd0,41)
set BOPT=boot=live live-config noswap nolocales edd=on nomodeset ip=frommedia live-media-path=/live-hd bootfrom=/dev/sda42 toram=filesystem.squashfs
set PRERUN=ocs_prerun="sudo su -"
set RUN=ocs_live_run="ocs-live-general" ocs_live_extra_param="" keyboard-layouts=NONE locales=en_US.UTF-8 ocs_live_batch="no" vga=791 nosplash
kernel /live-hd/vmlinuz %BOPT% %PRERUN% %RUN%
initrd /live-hd/initrd.img
Last edit: Kirkx 2014-10-03
Basically the order is not important, unless there are duplicated boot parameters. If so, the latter one will overwrite the former one.
Steven.