/[clonezilla-sysresccd]/trunk/www/2doc/README.txt
ViewVC logotype

Diff of /trunk/www/2doc/README.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 43 by sng, Tue May 18 17:41:12 2010 UTC revision 60 by sng, Wed May 26 10:24:27 2010 UTC
# Line 342  certainty make it unbootable. When you a Line 342  certainty make it unbootable. When you a
342  SystemRescueCD boot parameters  SystemRescueCD boot parameters
343  ****************************************  ****************************************
344  [[ info.png ]]  [[ info.png ]]
345  The following info applies to SystemRescueCD v. 1.3.5. In case  The following info applies to SystemRescueCD v. 1.5.4. In case
346   you need to get info for a more recent version of SystemRescueCD   you need to get info for a more recent version of SystemRescueCD
347  please see the page "Sysresccd-manual-en Booting the CD-ROM {{  please see the page "Sysresccd-manual-en Booting the CD-ROM {{
348  http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM }}"  http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM }}"
# Line 357  boot parameter. Line 357  boot parameter.
357    
358  Available kernels (boot images):  Available kernels (boot images):
359    
360  * rescuecd This is the default choice for 32bits systems, with Framebuffer  * rescuecd Default for 32bit systems, with Framebuffer disabled, best choice.
361  disabled, best choice.  * rescue64 Default 64 bit kernel. Use it if you want to chroot to a 64bit
362  * altker32 This is an alternative kernel for 32bits systems. Boot with  linux system installed on your hard disk, or if you have to run 64 bits
363  this kernel in case you have problems with rescuecd. altker32 was named  programs. This kernel is able to boot with 32bit programs, and it requires
364  vmlinuz2 in versions prior to SystemRescueCd-1.0.0.  a processor with 64bit instructions (amd64 / em64t).
365  * rescue64 This is the default 64 bits kernel. Use it if you want to chroot  * altker32 an alternative kernel for 32bit systems. Boot with this kernel
366  to a 64bits linux system installed on your hard disk, or if you have to run  if you have problems with rescuecd
367  64 bits programs. This kernel is able to boot SystemRescueCd from the cdrom  * altker64 an alternative kernel for 64bit systems. Boot with this kernel
368  with 32bits programs, and it required a processor with 64bits instructions  in case you have problems with rescue64.
 (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.  
369    
370  The boot parameters you can use are:  The boot parameters you can use are:
371    
# Line 388  this by using Line 384  this by using
384    
385  * setkmap=kk: which defines the keymap to load where kk (example: setkmap=de  * setkmap=kk: which defines the keymap to load where kk (example: setkmap=de
386  for German keyboards)  for German keyboards)
387  * root=/dev/xdnp: the root=<device> option {{  * root=/dev/xdnp: the root=<device> option boots an existing linux
388  http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/  system. For example, if you have linux Gentoo installed on /dev/sda6,
389  }} boots an existing linux system. For example, if you have linux  use rescuecd root=/dev/sda6 to start it. Keep in mind that you must use a
390  Gentoo installed on /dev/sda6, use rescuecd root=/dev/sda6 to start  64bit kernel if your system is made of 64bit programs. This option works
391  it. Keep in mind that you must use a 64bit kernel if your system is  with LVM volumes. Use rescuecd root=/dev/VolGroup00/LogVol00. Support
392  made of 64bit programs. This option works with LVM volumes. Use rescuecd  is also provided for root=auto, which scans all the block devices tfor
393  root=/dev/VolGroup00/LogVol00. Support is also provided for root=auto,  a linux system. The first linux system found will be started. So with
394  which scans all the block devices tfor a linux system. The first linux  root=auto let you start the system installed from the CD-ROM in case
395  system found will be started. So with root=auto let you start the system  you have problem with your boot loader or kernel. It's also possible
396  installed from the CD-ROM in case you have problem with your boot loader or  to specify a partition using its filesystem label or filesystem
397  kernel. It's also possible to specify a partition using its filesystem label  uuid. If the label of the partition where linux is installed is
398  or filesystem uuid. If the label of the partition where linux is installed  mylinux, then boot it using rescuecd root=LABEL=mylinux. Similarly
 is mylinux, then boot it using rescuecd root=LABEL=mylinux. Similarly  
399  root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7. See more details.  root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7. See more details.
400  * initscript=service:action: This options allows start/stop a service  * initscript=service:action: This options allows start/stop a service
401  at boot time. For instance if you need the samba service to be started,  at boot time. For instance if you need the samba service to be started,
402  you can boot with: initscript=samba:start. This does the same thing as  you can boot with: initscript=samba:start. This does the same thing as
403  /etc/init.d/samba start. Use this option multiple times for different  /etc/init.d/samba start. Use this option multiple times for different
404  services. All the actions that are supported by an initscript can be used.  services. All the actions that are supported by an initscript can be used.
405  * backstore=xxx: SystemRescueCd comes with support for the backing-stores {{  * backstore=xxx: SystemRescueCd comes with support for the backing-stores. A
406  http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/  backing-store saves all the changes you can make. so that you keep these
407  }}. A backing-store saves all the changes you can make. so that you  changes the next time you boot it. By default, sysresccd automatically
408  keep these changes the next time you boot it. By default, sysresccd  scan removable devices (eg: USB sticks) at boot time and uses the first
409  automatically scan removable devices (eg: USB sticks) at boot time and  backing-store it finds. A backing-store is not mandatory and it the
410  uses the first backing-store it finds. A backing-store is not mandatory  scan fails it will store the files which change in memory. To disable
411  and it the scan fails it will store the files which change in memory. To  the disks scan at boot time specify backstore=off on the boot command
 disable the disks scan at boot time specify backstore=off on the boot command  
412  line. If you want to save your backing-store file on an harddisk, boot with  line. If you want to save your backing-store file on an harddisk, boot with
413  backstore=alldev to scan all devices (not just removable devices). The  backstore=alldev to scan all devices (not just removable devices). The
414  default location for backing-stores file is any file named sysrcd.bs  default location for backing-stores file is any file named sysrcd.bs
# Line 432  execute the kernel. The SystemRescueCd i Line 426  execute the kernel. The SystemRescueCd i
426  its sysrcd.dat file is in an ISO and not directly on the partition. For that  its sysrcd.dat file is in an ISO and not directly on the partition. For that
427  reason, this isoloop=xxx boot option is required so you must use it in your  reason, this isoloop=xxx boot option is required so you must use it in your
428  grub.cfg. This option is only supported in SystemRescueCd-1.4.0 and more  grub.cfg. This option is only supported in SystemRescueCd-1.4.0 and more
429  recent. This option specifies the path of the ISO image in the partition  recent. This option specifies the path of the ISO image in the partition that
430  that grub considers as its root partition. It's important to understand  grub considers as its root partition. It's important to understand that the
431  that the path of the ISO image may be different from the path on your  path of the ISO image may be different from the path on your linux system. If
432  linux system. If you have a separate boot partition mounted on /boot and if  you have a separate boot partition mounted on /boot and if you copy this
433  you copy this ISO image to /boot/sysrcd/systemrescuecd-x86-x.y.z.iso then  ISO image to /boot/sysrcd/systemrescuecd-x86-x.y.z.iso then the option has
434  the option has to be isoloop=/sysrcd/systemrescuecd-x86-x.y.z.iso. This  to be isoloop=/sysrcd/systemrescuecd-x86-x.y.z.iso. This is because the
435  is because the boot partition is what Grub2 will consider as its root  boot partition is what Grub2 will consider as its root partition during
436  partition during the boot process. Please read the section about isoloop {{  the boot process. Please read the section about isoloop for more details.
 http://www.sysresccd.org/Sysresccd-manual-en_Easy_install_SystemRescueCd_on_harddisk#Boot_the_ISO_image_from_the_disk_using_Grub2  
 }} for more details.  
437    
438   Hardware, drivers and troubleshooting options   Hardware, drivers and troubleshooting options
439  * dodebug: Enables verbose messages in linuxrc  * dodebug: Enables verbose messages in linuxrc
# Line 516  in SystemRescueCd-1.3.5. Line 508  in SystemRescueCd-1.3.5.
508  * rootpass=123456: Sets the root password of the system running on the  * rootpass=123456: Sets the root password of the system running on the
509  livecd to 1234. That way you can connect from the network and ssh on the  livecd to 1234. That way you can connect from the network and ssh on the
510  livecd and give 123456 password as the root password.  livecd and give 123456 password as the root password.
511  * vncserver=x:123456: The vncserver boot option {{  * vncserver=x:123456: The vncserver boot option has been introduced in
512  http://www.sysresccd.org/news/2008/04/12/use-systemrescuecd-remotely-with-vnc-server/  SystemRescueCd-1.0.2. This options forces the system to configure the
513  }} has been introduced in SystemRescueCd-1.0.2. This options forces the  VNC-server and to start it automatically at boot time. You have to replace
514  system to configure the VNC-server and to start it automatically at boot  x with the number of displays you want, and 123456 with your password The
515  time. You have to replace x with the number of displays you want, and 123456  password must be between 5 and 8 characters, else the boot option will be
516  with your password The password must be between 5 and 8 characters, else the  ignored. In other words the vncserver=2:MyPaSsWd option will give you access
517  boot option will be ignored. In other words the vncserver=2:MyPaSsWd option  to two displays (display=1 on tcp/5901 and display=2 on tcp/5902). Display
518  will give you access to two displays (display=1 on tcp/5901 and display=2  0 is reserved for X.Org since SystemRescueCd-1.1.0.
519  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
520  * nameif=xxx: You can can specify what interface name to give {{  particular interface using the mac address. You need SystemRescueCd-1.1.0
521  http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/  or newer to do that. Here is how you can specify which interface
522  }} to a particular interface using the mac address. You need  is using which mac address on a machine with two network interfaces:
523  SystemRescueCd-1.1.0 or newer to do that. Here is how you can specify  nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64. Be careful, you have
524  which interface is using which mac address on a machine with two network  to respect the separator (comma between the interfaces and exclamation
525  interfaces: nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64. Be  marks between the name and the mac address).
 careful, you have to respect the separator (comma between the interfaces  
 and exclamation marks between the name and the mac address).  
526    
527   Network boot using PXE   Network boot using PXE
528  SystemRescueCd provides several options for booting from the network  SystemRescueCd provides several options for booting from the network
529  using PXE.  using PXE.
530  These options can be combined with other network boot options  These options can be combined with other network boot options such as ethx
531  such as ethx (cf previous section). See PXE network booting {{  (cf previous section). See PXE network booting to get a global overview
532  http://www.sysresccd.org/Sysresccd-manual-en_PXE_network_booting }} to  of SystemRescueCd and PXE and Manage remote servers using PXE.
 get a global overview of SystemRescueCd and PXE and Manage remote servers  
 using PXE.  
533  The second stage downloads the kernel + initramfs using DHCP/TFTP.  The second stage downloads the kernel + initramfs using DHCP/TFTP.
534  The third stage of the PXE boot process acquires the root files system.  The third stage of the PXE boot process acquires the root files system.
535  Several protocols are available.  Several protocols are available.
# Line 565  and it allows computers with smaller mem Line 553  and it allows computers with smaller mem
553  the network. After the boot process, the connection is required the access  the network. After the boot process, the connection is required the access
554  to the root system.  to the root system.
555    
556  For information on activating speakup, see the speakup info page {{  For information on activating speakup, see the speakup info page.
 http://www.sysresccd.org/Speakup-info }}.  
557    
558   Options provided for autorun   Options provided for autorun
559  * ar_source=xxx: place where the autorun are stored. It may  * ar_source=xxx: place where the autorun are stored. It may
# Line 589  been executed. Line 576  been executed.
576  Clonezilla Live boot parameters  Clonezilla Live boot parameters
577  ****************************************  ****************************************
578  [[ info.png ]]  [[ info.png ]]
579  The following info applies to Clonezilla Live v. 1.2.3-27  The following info applies to Clonezilla Live v. 1.2.5-17
580  In case you need to get info for a more recent version of Clonezilla Live  In case you need to get info for a more recent version of Clonezilla Live
581  please see the page "The boot parameters for Clonezilla live {{  please see the page "The boot parameters for Clonezilla live {{
582  http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc  http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc
# Line 611  page titled The boot parameters for Clon Line 598  page titled The boot parameters for Clon
598  http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc  http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc
599  }}.  }}.
600    
601  Clonezilla live is based on Debian live {{ http://wiki.debian.org/DebianLive/  Clonezilla live is based on Debian live with clonezilla installed. Therefore
602  }} with clonezilla installed. Therefore there are 2 kinds of boot parameters:  there are 2 kinds of boot parameters:
603    
604  * Boot parameters from live-initramfs. You can refer to this manual of  * Boot parameters from live-initramfs. You can refer to this manual of
605  live-initramfs.  live-initramfs.
# Line 811  aufs, for Debian like systems to boot fr Line 798  aufs, for Debian like systems to boot fr
798  You probably do not want to install this package onto a non-live system,  You probably do not want to install this package onto a non-live system,
799  although it will do no harm.  although it will do no harm.
800    
801  live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper].  live-initramfs is a fork of casper.
802  casper was originally written by Tollef Fog Heen <tfheen@canonical.com>  casper was originally written by Tollef Fog Heen
803  and Matt Zimmerman <mdz@canonical.com>.  &lt;tfheen@canonical.com&amp;gt;
804    and Matt Zimmerman &lt;mdz@canonical.com&amp;gt;.
805    
806  Boot options  Boot options
807  ------------  ------------
# Line 859  If specified, an MD5 sum is calculated o Line 847  If specified, an MD5 sum is calculated o
847  compared to the value found in md5sum.txt found in the root directory of the  compared to the value found in md5sum.txt found in the root directory of the
848  live media.  live media.
849    
850   ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]   ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:
851   [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]]***::   [DEVICE]:[AUTOCONF]
852     [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:
853     [DEVICE]:[AUTOCONF]]***::
854    
855  Let you specify the name(s) and the options of the interface(s) that  Let you specify the name(s) and the options of the interface(s) that
856  should be  should be
# Line 880  instead. Line 870  instead.
870   {keyb|kbd-chooser/method}=**KEYBOARD**,   {keyb|kbd-chooser/method}=**KEYBOARD**,
871   {klayout|console-setup/layoutcode}=**LAYOUT**,   {klayout|console-setup/layoutcode}=**LAYOUT**,
872   {kvariant|console-setup/variantcode}=**VARIANT**,   {kvariant|console-setup/variantcode}=**VARIANT**,
873   {kmodel|console-setup/modelcode}=**CODE**, koptions=**OPTIONS**::   {kmodel|console-setup/modelcode}=
874     **CODE**, koptions=**OPTIONS**::
875    
876  Configure the running keyboard as specified, if this one misses  Configure the running keyboard as specified, if this one misses
877  live-initramfs  live-initramfs
# Line 1123  this list will be on the "top" of the au Line 1114  this list will be on the "top" of the au
1114  this file, any images in the "/live" directory are loaded in alphanumeric  this file, any images in the "/live" directory are loaded in alphanumeric
1115  order.  order.
1116    
1117  /etc/live-persistence.binds   /etc/live-persistence.binds
1118    
1119  This optional file (which resides in the rootfs system, not in the live  This optional file (which resides in the rootfs system, not in the live
1120  media)  media)
# Line 1146  Bugs Line 1137  Bugs
1137  ----  ----
1138    
1139  Report bugs against live-initramfs  Report bugs against live-initramfs
1140  link:http://packages.qa.debian.org/live-initramfs[http://packages.qa.debian.org/live-initramfs].  http://packages.qa.debian.org/live-initramfs.
1141    
1142  Homepage  Homepage
1143  --------  --------
1144    
1145  More information about the Debian Live project can be found at  More information about the Debian Live project can be found at
1146  link:http://debian-live.alioth.debian.org/[http://debian-live.alioth.debian.org/]  http://debian-live.alioth.debian.org/ and
1147  and  http://wiki.debian.org/DebianLive/.
 link:http://wiki.debian.org/DebianLive/[http://wiki.debian.org/DebianLive/].  
1148    
1149  Authors  Authors
1150  -------  -------
1151    
1152  live-initramfs is maintained by Daniel Baumann <daniel@debian.org>  live-initramfs is maintained by Daniel Baumann &lt;daniel@debian.org&amp;gt;
1153  for the Debian project.  for the Debian project.
1154    
1155  live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper].  live-initramfs is a fork of casper.
1156  casper was originally written by Tollef Fog Heen <tfheen@canonical.com>  casper was originally written by Tollef Fog Heen
1157  and Matt Zimmerman <mdz@canonical.com>.  &lt;tfheen@canonical.com&amp;gt;
1158    and Matt Zimmerman &lt;mdz@canonical.com&amp;gt;.
1159    
1160    
1161    

Legend:
Removed from v.43  
changed lines
  Added in v.60

webmaster@linux.gr
ViewVC Help
Powered by ViewVC 1.1.26