SystemRescueCD boot parameters [^]
 |
-The following info applies to SystemRescueCD v. 1.5.5. In case +The following info applies to SystemRescueCD v. 2.1.1. In case you need to get info for a more recent version of SystemRescueCD please see the page "Sysresccd-manual-en Booting the CD-ROM" |
- doxdetect: Since version 0.3.5 the auto-configuration is done in X.Org itself, mkxf86config is disabled by default. This option forces the system to run the mkxf86config startup script and to run the hardware auto-detection from this script. Use this option if you have problems with the graphical environment configuration. This option replaces the option
noxdetectthat was useful in previous versions. - nodetect: prevents generic hardware auto-detection. Use this option if you have problems with the hardware auto-detection.
- dostartx: load the X.Org graphical environment.
+
- nomodeset: Do not load the Kernel-Mode-Setting video driver. You can use that option if you are experiencing problems with your screen during the boot process (just after modules are being loaded). +
- dostartx: load the X.Org graphical environment.
- forcevesa: Forces X.Org to use the safe VESA driver instead of the best video driver detected for your video card. Use this option if you cannot get the graphical environment working with the default options.
- forcevesa=xxx: The
startxcommand will load theXvesaserver instead ofXorg, and use the screen resolution given as parameter (eg:1024x768,1280x1024x32).
Network configuration and remote access
- nonm: to disable the Network-Manager service that conflicts with the standard network command line tools such as
ifconfigandip. You can use this option if you want to configure the network using these commands. This option is not necessary when SystemRescueCd is booting from the network since the service is automatically stopped in that case. This option requires SystemRescueCd-1.5.5 or more recent. - - dodhcp: to request a DHCP server provide network attributes including an IP address, gateway... +
- dodhcp: to request a DHCP server provide network attributes including an IP address, gateway... If there are multiple interfaces on the computer it will run the dhcp client on all of them by default, when no argument is specified with this option. Thanks to emiliano SystemRescueCd-1.7.0-beta009 and more recent allows you to optionally specify which interfaces should be configured with dhcp. This way you can combine static and dynamic addresses in the automatic Ethernet configuration. For example you can now use options like that:
dodhcp=eth0,eth2 eth1=192.168.128.1/24
to use dhcp for eth0 and eth2 and a static address on eth1. - nodhcp: never run the dhcp client in the initramfs boot script. May be useful if you use PXE boot on a computer with several ethernet interfaces. Support for this option is available in SystemRescueCd-1.5.5 and more recent
- ethx=ipaddr/cidr: Sets the static IP address of all the ethernet interfaces on the system. The
/cidrextension is optional. For instance, if you use optionethx=192.168.0.1on a machine with two ethernet adapters, botheth0andeth1will be configured with192.168.0.1. You can use the formatethx=10.0.0.1/24(using the cidr notation) if you don't use the default netmask. - eth0=ipaddr/cidr: This option is similar to
ethx=ipaddr/cidrbut it configures only one interface at a time. To configure the network on a server that has two interfaces, use, for example:eth0=192.168.10.1/24 eth1=192.168.20.1. @@ -238,9 +239,9 @@Clonezilla Live boot parameters [^]
-The following info applies to Clonezilla Live v. 1.2.5-17
+The following info applies to Clonezilla Live v. 1.2.8-46
In case you need to get info for a more recent version of Clonezilla Live
-please see the page "The boot parameters for Clonezilla live" +please see the page "The boot parameters for Clonezilla live"A typical Clonezilla Live isolinux entry is:
@@ -278,18 +279,17 @@ - ocs_debug (or ocs-debug) is for you to enter command line prompt before any clonezilla-related action is run. This is easier for you to debug.
- ocs_daemonon, ocs_daemonoff, ocs_numlk, ocs_capslk.
Ex. for the first 2 parameters, ocs_daemonon="ssh", then ssh service will be turned on when booting. For the last 2 parameters, use "on" or "off", e.g. ocs_numlk=on to turn on numberlock when booting. - - ocs_prerun, ocs_prerun1, ocs_prerun2... is for you to run a shell script before Clonezilla is started. E.g. ocs_prerun="/live/image/myscript.sh". If you have more commands to run, you can assign them in the order: ocs_prerun=..., ocs_prerun1=..., ocs_prerun2=.... If more than 10 parameters, remember to use ocs_prerun01, ocs_prerun02..., ocs_prerun11 to make it in order. -
- ocs_live_run_tty. This option allows you to specify the tty where $ocs_live_run is run. By default $ocs_live_run is run on /dev/tty1 only. (It was also on /dev/ttyS0 before, but since Clonezilla live >= 1.2.3-22 no more this due to a problem). If you want to use ttyS0, for example, add live-getty and console=ttyS0,38400n81 in the boot parameter.
+ - ocs_prerun, ocs_prerun1, ocs_prerun2... is for you to run a command before Clonezilla is started. E.g. ocs_prerun="/live/image/myscript.sh". If you have more commands to run, you can assign them in the order: ocs_prerun=..., ocs_prerun1=..., ocs_prerun2=.... If more than 10 parameters, remember to use ocs_prerun01, ocs_prerun02..., ocs_prerun11 to make it in order. +
- ocs_live_run_tty. This option allows you to specify the tty where $ocs_live_run is run. By default $ocs_live_run is run on /dev/tty1 only. If you want to use ttyS0, for example, add live-getty and console=ttyS0,38400n81 in the boot parameter.
//NOTE//
-
-
- This parameter was added in Clonezilla live 1.2.3-22 or later.
- If "live-getty console=ttyS0,38400n81" are assigned in the boot parameters, ocs_live_run_tty will honor ttyS0, even other value is assigned to ocs_live_run_tty in boot parameter.
- It's recommended to assign ocs_lang and ocs_live_keymap in the boot parameters too.
- ip, this option allows you to specify the network parameters for network card. In Clonezilla live a patched live-initramfs is used, which is different from the original live-initramfs so that you can assign DNS server, too. Its format is: ip=ethernet port,IP address, netmask, gateway, DNS. E.g. If you want to assing eth0 with IP address 10.0.100.1, netmask 255.255.255.0, gateway 10.0.100.254, DNS server 8.8.8.8, you can assign the following in the boot parameter:
-ip=eth0,10.0.100.1,255.255.255.0,10.0.100.254,8.8.8.8
-If more than one network card, you can use ":" to separate them, e.g.:
-ip=eth0,10.0.100.1,255.255.255.0,10.0.100.254,8.8.8.8:eth1,192.168.120.1,255.255.255.0,192.168.120.254,,
+ip=eth0:10.0.100.1:255.255.255.0:10.0.100.254:8.8.8.8
+If more than one network card, you can use "," to separate them, e.g.:
+ip=eth0:10.0.100.1:255.255.255.0:10.0.100.254:8.8.8.8,eth1:192.168.120.1:255.255.255.0:192.168.120.254::
- Besides, "live-netdev" (yes, not ocs_live_netdev) can be used when using PXE booting, you can force to assign the network device to get filesystem.squashfs. This is useful when there are two or more NICs are linked. E.g. live-netdev="eth1" allows you to force the live-initramfs to use eth1 to fetch the root file system filesystem.squashfs.