General boot options
Press <TAB> to add additional options (in SystemRescueCd-1.5 and more recent)
-bootdisks and isolinux directories). Add lowmem if you have less that 400MB of memory of to prevent these directories to be copied.
+bootdisks and isolinux directories). Add lowmem if you have less that 400MB of memory of to prevent these directories from being copied.
kk (example: setkmap=de for German keyboards). This way you won't be prompted for the keyboard configuration during the boot.
-/dev/sda6, use rescuecd root=/dev/sda6 to start it. Keep in mind that you must use a 64bit kernel if your system is made of 64bit programs. This option works with LVM volumes. Use rescuecd root=/dev/VolGroup00/LogVol00. Support is also provided for root=auto, which scans all the block devices tfor a linux system. The first linux system found will be started. So with root=auto let you start the system installed from the CD-ROM in case you have problem with your boot loader or kernel. It's also possible to specify a partition using its filesystem label or filesystem uuid. If the label of the partition where linux is installed is mylinux, then boot it using rescuecd root=LABEL=mylinux. Similarly root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7. See more details.
-initscript=samba:start. This does the same thing as /etc/init.d/samba start. Use this option multiple times for different services. All the actions that are supported by an initscript can be used.
-backstore=off on the boot command line. If you want to save your backing-store file on an harddisk, boot with backstore=alldev to scan all devices (not just removable devices). The default location for backing-stores file is any file named sysrcd.bs located at the root of a disk which is often an USB stick. Change the path by using backstore=/sysrcd/mybackstore.bs. See backing-stores.
-systemrescuecd-x86-x.y.z.iso on a partition that Grub2 can read then you can boot SystemRescueCd directly from the ISO image stored on your hard drive. This is very convenient if you frequently update SystemRescueCd and you want to boot it directly from Grub2. Grub2 knows what an ISO image is and it will load the kernel image (rescuecd/rescue64) and the initramfs (initram.igz) from the ISO into memory. It will then do its normal job and execute the kernel. The SystemRescueCd init script must then be aware that its sysrcd.dat file is in an ISO and not directly on the partition. For that reason, this isoloop=xxx boot option is required so you must use it in your grub.cfg. This option is only supported in SystemRescueCd-1.4.0 and more recent. This option specifies the path of the ISO image in the partition that grub considers as its root partition. It's important to understand that the path of the ISO image may be different from the path on your linux system. If you have a separate boot partition mounted on /boot and if you copy this ISO image to /boot/sysrcd/systemrescuecd-x86-x.y.z.iso then the option has to be isoloop=/sysrcd/systemrescuecd-x86-x.y.z.iso. This is because the boot partition is what Grub2 will consider as its root partition during the boot process. Please read the section about isoloop for more details.
+/dev/sda6, use rescuecd root=/dev/sda6 to start it. Keep in mind that you must use a 64bit kernel if your system is made of 64bit programs. This option works with LVM volumes. Use rescuecd root=/dev/VolGroup00/LogVol00. Support is also provided for root=auto, which scans all the block devices for a linux system. The first linux system found will be started. So root=auto lets you start the system installed from the CD-ROM in case you have problem with your boot loader or kernel. It's also possible to specify a partition using its filesystem label or filesystem uuid. If the label of the partition where linux is installed is mylinux, then boot it using rescuecd root=LABEL=mylinux. Similarly root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7. See more details.
+initscript=samba:start. This does the same thing as /etc/init.d/samba start. Use this option a multiple of times for different services. All the actions that are supported by an initscript can be used.
+backstore=off on the boot command line. If you want to save your backing-store file on a harddisk, boot with backstore=alldev to scan all devices (not just removable devices). The default location for a backing-stores file is any file named sysrcd.bs located at the root of a disk which is often a USB stick. Change the path by using backstore=/sysrcd/mybackstore.bs. See backing-stores.
+systemrescuecd-x86-x.y.z.iso on a partition that Grub2 can read then you can boot SystemRescueCd directly from the ISO image stored on your hard drive. This is very convenient if you frequently update SystemRescueCd and you want to boot it directly from Grub2. Grub2 knows what an ISO image is and it will load the kernel image (rescuecd/rescue64) and the initramfs (initram.igz) from the ISO into memory. It will then do its normal job and execute the kernel. The SystemRescueCd init script must then be aware that its sysrcd.dat file is in an ISO and not directly on the partition. For that reason, this isoloop=xxx boot option is required so you must use it in your grub.cfg. This option is only supported in SystemRescueCd-1.4.0 and more recent. This option specifies the path of the ISO image in the partition that grub considers as its root partition. It's important to understand that the path of the ISO image may be different from the path on your linux system. If you have a separate boot partition mounted on /boot and if you copy this ISO image to /boot/sysrcd/systemrescuecd-x86-x.y.z.iso then the option has to be isoloop=/sysrcd/systemrescuecd-x86-x.y.z.iso. This is because the boot partition is what Grub2 will consider as its root partition during the boot process. Please read the section about isoloop for more details.
Hardware, drivers and troubleshooting options
noload=3c59x,e1000). Use this option if you have a problem when the system loads a particular module.
noxdetect that was useful in previous versions.
skipmount=/dev/sda1 skipmount=/dev/sda2 to ignore these two partitions.
+skipmount=/dev/sda1 skipmount=/dev/sda2 to ignore these two partitions.
Network configuration and remote access
ifconfig and ip. 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.
/cidr extension is optional. For instance, if you use option ethx=192.168.0.1 on a machine with two ethernet adapters, both eth0 and eth1 will be configured with 192.168.0.1. You can use the format ethx=10.0.0.1/24 (using the cidr notation) if you don't use the default netmask.
-ethx=ipaddr/cidr but it configures only one interface at a time. To configure the network on a server that has two interfaces, use: eth0=192.168.10.1/24 eth1=192.168.20.1.
+ethx=ipaddr/cidr but 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.
dns=192.168.0.254 means that you want to use 192.168.0.254 as the DNS server.
gateway=192.168.0.254 means that the computer can connect to a computer outside of the local network via 192.168.0.254.
1234. That way you can connect from the network and ssh on the livecd and give 123456 password as the root password.
-x with the number of displays you want, and 123456 with your password The password must be between 5 and 8 characters, else the boot option will be ignored. In other words the vncserver=2:MyPaSsWd option will give you access to two displays (display=1 on tcp/5901 and display=2 on tcp/5902). Display 0 is reserved for X.Org since SystemRescueCd-1.1.0.
-nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64. Be careful, you have to respect the separator (comma between the interfaces and exclamation marks between the name and the mac address). You can also use the magic keyword BOOTIF with SystemRescueCd-1.5.4 and more recent when you boot from pxelinux. The pxeboot loader will set BOOTIF to the name of the interface used to boot. You can then use something like nameif=eth0!BOOTIF if you want the boot interface to be called eth0 on a computer with several Ethernet interfaces.
+123456. That way you can connect from the network and ssh on the livecd and give 123456 password as the root password.
+x with the number of displays you want, and 123456 with your password. The password must be between 6 and 8 characters, else the boot option will be ignored. In other words the vncserver=2:MyPaSsWd option will give you access to two displays (display=1 on tcp/5901 and display=2 on tcp/5902). Display 0 is reserved for X.Org since SystemRescueCd-1.1.0. SystemRescueCd-1.5.7 and more recent accept a password longer than 8 chars (between 5 and 12 chars)
+nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64. Be careful, you have to respect the separator (comma between the interfaces and exclamation marks between the name and the mac address). You can also use the magic keyword BOOTIF with SystemRescueCd-1.5.4 and more recent when you boot from pxelinux. The pxeboot loader will set BOOTIF to the name of the interface used to boot. You can then use something like nameif=eth0!BOOTIF if you want the boot interface to be called eth0 on a computer with several Ethernet interfaces.
Network boot using PXE
SystemRescueCd provides several options for booting from the network using PXE. @@ -207,8 +207,8 @@
sysrcd.dat. Only NFSv3 can be used, NFSv4 is not supported. NFS it allows computers with smaller memory to boot SystemRescueCd from the network. After the boot process, the connection is required or you will loose the access to the root file system.
-sysrcd.dat on ip:port. NBD is easier to configure than NFS (only one TCP port involved) and it allows computers with smaller memort to boot SystemRescueCd from the network. After the boot process, the connection is required the access to the root system.
+sysrcd.dat. Only NFSv3 can be used, NFSv4 is not supported. NFS allows computers with smaller memory to boot SystemRescueCd from the network. After the boot process, continued network connection is required or you will loose access to the root file system.
+sysrcd.dat on ip:port. NBD is easier to configure than NFS (only one TCP port involved) and it allows computers with smaller memory to boot SystemRescueCd from the network. After the boot process, the network connection continues to be required to access the root file system.
For information on activating speakup, see the speakup info page.
@@ -257,7 +257,7 @@ e.g. ocs_live_run="ocs-live-general"
live-initramfs(7)
=================
+:man source: 1.157.3
+:man manual: Debian Live
Name
----
@@ -435,7 +437,15 @@
fetch=*URL*::
Another form of netboot by downloading a squashfs image from a given url,
-copying to ram and booting it.
+copying to ram and booting it. Due to current limitations in busyboxs wget
+and DNS resolution, an URL can not contain a hostname but an IP only.
+
+Not working: http://example.com/path/to/your_filesystem.squashfs
+Working: http://1.2.3.4/path/to/your_filesystem.squashfs
+
+Also note that therefore it's currently not possible to fetch an image from a
+namebased virtualhost of an httpd if it is sharing the ip with the main httpd
+instance.
hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*::
@@ -462,7 +472,7 @@
It will be changed in a future release to mimick official kernel boot param
specification (e.g. ip=10.0.0.1::10.0.0.254:255.255.255.0::eth0,:::::eth1:dhcp).
- ip[=**frommedia**]::
+ ip=[**frommedia**]::
If this variable is set, dhcp and static configuration are just skipped and the
system will use the (must be) media-preconfigured /etc/network/interfaces
@@ -491,6 +501,11 @@
filesystem should reside. If it did not find something usable, the normal scan
for block devices is performed.
+Instead of specifing an actual device name, the keyword 'removable' can be used
+to limit the search of acceptable live media to removable type only. Note that
+if you want to further restrict the media to usb mass storage only, you can use
+the 'removable-usb' keyword.
+
{live-media-encryption|encryption}=**TYPE**::
live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase,
@@ -562,7 +577,7 @@
noprompt
-Do not prompt to eject the CD on reboot.
+Do not prompt to eject the CD or remove the USB flash drive on reboot.
nosudo::
@@ -593,6 +608,12 @@
will be searched; no filesystems will be traversed looking for archives or image
files. This results in shorter boot times.
+ persistent-path=PATH
+
+live-initramfs will look for persistency files in the root directory of a partition,
+with this parameter, the path can be configured so that you can have multiple
+directories on the same partition to store persistency files.
+
{preseed/file|file}=**FILE**::
A path to a file present on the rootfs could be used to preseed debconf
@@ -616,6 +637,11 @@
lead to problems by applications like "mono" which store binary paths on
installation.
+ silent
+
+If you boot with the normal quiet parameter, live-initramfs hides most messages
+of its own. When adding silent, it hides all.
+
textonly
Start up to text-mode shell prompts, disabling the graphical user interface.