--- trunk/www/2doc/README.txt 2010/05/25 13:31:38 59 +++ trunk/www/2doc/README.txt 2010/05/26 10:24:27 60 @@ -342,7 +342,7 @@ SystemRescueCD boot parameters **************************************** [[ info.png ]] -The following info applies to SystemRescueCD v. 1.3.5. In case +The following info applies to SystemRescueCD v. 1.5.4. 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 {{ http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM }}" @@ -357,19 +357,15 @@ Available kernels (boot images): -* rescuecd This is the default choice for 32bits systems, with Framebuffer -disabled, best choice. -* altker32 This is an alternative kernel for 32bits systems. Boot with -this kernel in case you have problems with rescuecd. altker32 was named -vmlinuz2 in versions prior to SystemRescueCd-1.0.0. -* rescue64 This is the default 64 bits kernel. Use it if you want to chroot -to a 64bits linux system installed on your hard disk, or if you have to run -64 bits programs. This kernel is able to boot SystemRescueCd from the cdrom -with 32bits programs, and it required a processor with 64bits instructions -(amd64 / em64t). -* altker64 This is an alternative kernel for 64bits systems. Boot with -this kernel in case you have problems with rescue64. Only available from -SystemRescueCd-1.0.0 and newer. +* rescuecd Default for 32bit systems, with Framebuffer disabled, best choice. +* rescue64 Default 64 bit kernel. Use it if you want to chroot to a 64bit +linux system installed on your hard disk, or if you have to run 64 bits +programs. This kernel is able to boot with 32bit programs, and it requires +a processor with 64bit instructions (amd64 / em64t). +* altker32 an alternative kernel for 32bit systems. Boot with this kernel +if you have problems with rescuecd +* altker64 an alternative kernel for 64bit systems. Boot with this kernel +in case you have problems with rescue64. The boot parameters you can use are: @@ -388,33 +384,31 @@ * setkmap=kk: which defines the keymap to load where kk (example: setkmap=de for German keyboards) -* root=/dev/xdnp: the root= option {{ -http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/ -}} boots an existing linux system. For example, if you have linux -Gentoo installed on /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=/dev/xdnp: the root= option boots an existing linux +system. For example, if you have linux Gentoo installed on /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=service:action: This options allows start/stop a service at boot time. For instance if you need the samba service to be started, you can boot with: 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=xxx: SystemRescueCd comes with support for the backing-stores {{ -http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/ -}}. A backing-store saves all the changes you can make. so that you -keep these changes the next time you boot it. By default, sysresccd -automatically scan removable devices (eg: USB sticks) at boot time and -uses the first backing-store it finds. A backing-store is not mandatory -and it the scan fails it will store the files which change in memory. To -disable the disks scan at boot time specify backstore=off on the boot command +* backstore=xxx: SystemRescueCd comes with support for the backing-stores. A +backing-store saves all the changes you can make. so that you keep these +changes the next time you boot it. By default, sysresccd automatically +scan removable devices (eg: USB sticks) at boot time and uses the first +backing-store it finds. A backing-store is not mandatory and it the +scan fails it will store the files which change in memory. To disable +the disks scan at boot time specify 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 @@ -432,16 +426,14 @@ 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 {{ -http://www.sysresccd.org/Sysresccd-manual-en_Easy_install_SystemRescueCd_on_harddisk#Boot_the_ISO_image_from_the_disk_using_Grub2 -}} for more details. +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 * dodebug: Enables verbose messages in linuxrc @@ -516,32 +508,28 @@ * rootpass=123456: Sets the root password of the system running on the livecd to 1234. That way you can connect from the network and ssh on the livecd and give 123456 password as the root password. -* vncserver=x:123456: The vncserver boot option {{ -http://www.sysresccd.org/news/2008/04/12/use-systemrescuecd-remotely-with-vnc-server/ -}} has been introduced in SystemRescueCd-1.0.2. This options forces the -system to configure the VNC-server and to start it automatically at boot -time. You have to replace 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=xxx: You can can specify what interface name to give {{ -http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/ -}} to a particular interface using the mac address. You need -SystemRescueCd-1.1.0 or newer to do that. Here is how you can specify -which interface is using which mac address on a machine with two network -interfaces: 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). +* vncserver=x:123456: The vncserver boot option has been introduced in +SystemRescueCd-1.0.2. This options forces the system to configure the +VNC-server and to start it automatically at boot time. You have to replace +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=xxx: You can can specify what interface name to give to a +particular interface using the mac address. You need SystemRescueCd-1.1.0 +or newer to do that. Here is how you can specify which interface +is using which mac address on a machine with two network interfaces: +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). Network boot using PXE SystemRescueCd provides several options for booting from the network using PXE. -These options can be combined with other network boot options -such as ethx (cf previous section). See PXE network booting {{ -http://www.sysresccd.org/Sysresccd-manual-en_PXE_network_booting }} to -get a global overview of SystemRescueCd and PXE and Manage remote servers -using PXE. +These options can be combined with other network boot options such as ethx +(cf previous section). See PXE network booting to get a global overview +of SystemRescueCd and PXE and Manage remote servers using PXE. The second stage downloads the kernel + initramfs using DHCP/TFTP. The third stage of the PXE boot process acquires the root files system. Several protocols are available. @@ -565,8 +553,7 @@ the network. After the boot process, the connection is required the access to the root system. -For information on activating speakup, see the speakup info page {{ -http://www.sysresccd.org/Speakup-info }}. +For information on activating speakup, see the speakup info page. Options provided for autorun * ar_source=xxx: place where the autorun are stored. It may @@ -589,7 +576,7 @@ Clonezilla Live boot parameters **************************************** [[ info.png ]] -The following info applies to Clonezilla Live v. 1.2.3-27 +The following info applies to Clonezilla Live v. 1.2.5-17 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 {{ http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc @@ -611,8 +598,8 @@ http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc }}. -Clonezilla live is based on Debian live {{ http://wiki.debian.org/DebianLive/ -}} with clonezilla installed. Therefore there are 2 kinds of boot parameters: +Clonezilla live is based on Debian live with clonezilla installed. Therefore +there are 2 kinds of boot parameters: * Boot parameters from live-initramfs. You can refer to this manual of live-initramfs. @@ -811,9 +798,10 @@ You probably do not want to install this package onto a non-live system, although it will do no harm. -live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper]. -casper was originally written by Tollef Fog Heen -and Matt Zimmerman . +live-initramfs is a fork of casper. +casper was originally written by Tollef Fog Heen +<tfheen@canonical.com&gt; +and Matt Zimmerman <mdz@canonical.com&gt;. Boot options ------------ @@ -859,8 +847,10 @@ compared to the value found in md5sum.txt found in the root directory of the live media. - ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF] - [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]]***:: + ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]: + [DEVICE]:[AUTOCONF] + [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]: + [DEVICE]:[AUTOCONF]]***:: Let you specify the name(s) and the options of the interface(s) that should be @@ -880,7 +870,8 @@ {keyb|kbd-chooser/method}=**KEYBOARD**, {klayout|console-setup/layoutcode}=**LAYOUT**, {kvariant|console-setup/variantcode}=**VARIANT**, - {kmodel|console-setup/modelcode}=**CODE**, koptions=**OPTIONS**:: + {kmodel|console-setup/modelcode}= + **CODE**, koptions=**OPTIONS**:: Configure the running keyboard as specified, if this one misses live-initramfs @@ -1123,7 +1114,7 @@ this file, any images in the "/live" directory are loaded in alphanumeric order. -/etc/live-persistence.binds + /etc/live-persistence.binds This optional file (which resides in the rootfs system, not in the live media) @@ -1146,25 +1137,25 @@ ---- Report bugs against live-initramfs -link:http://packages.qa.debian.org/live-initramfs[http://packages.qa.debian.org/live-initramfs]. +http://packages.qa.debian.org/live-initramfs. Homepage -------- More information about the Debian Live project can be found at -link:http://debian-live.alioth.debian.org/[http://debian-live.alioth.debian.org/] -and -link:http://wiki.debian.org/DebianLive/[http://wiki.debian.org/DebianLive/]. +http://debian-live.alioth.debian.org/ and +http://wiki.debian.org/DebianLive/. Authors ------- -live-initramfs is maintained by Daniel Baumann +live-initramfs is maintained by Daniel Baumann <daniel@debian.org&gt; for the Debian project. -live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper]. -casper was originally written by Tollef Fog Heen -and Matt Zimmerman . +live-initramfs is a fork of casper. +casper was originally written by Tollef Fog Heen +<tfheen@canonical.com&gt; +and Matt Zimmerman <mdz@canonical.com&gt;.