2doc/doc/boot-params.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<link rel="alternate" type="application/rss+xml" title="RSS" href="http://clonezilla-sysresccd.hellug.gr/clonezilla-sysresccd.rss">
<link rel="shortcut icon" href="favicon.ico">
<title>Clonezilla-SysRescCD - Offline Documentation: Boot parameters</title>
  <style type="text/css">
    body { font-family: Arial, 'sans serif';  color: black;  font-size: 12pt; background : url(null) fixed no-repeat; background-color: #333333; padding: 0; margin: 0; margin-top: 5px;  margin-bottom: 5px; }

  
    #header {position:relative; display: block; width: 980px; height: 121px;margin: auto; padding: auto; background-color: #D37624; background-image: url('images/header.png');clear:both;}
    #header h2{ color: #FFE6BC; font-weight: bold; font-size: 2.2em; margin:0; padding:0; padding-left: 10px; padding-top: 7px; text-shadow: #333333 2px 2px 4px;}
    #header h3{ color: #FFE6BC; font-weight: bold; font-size: 1.8em; margin:0; padding: 0; padding-left: 10px; text-shadow: #333333 2px 2px 4px;}
    #header h4{ color: #FFE6BC; font-weight: bold; font-size: 1.2em; margin:0; padding: 0; padding-left: 10px; padding-right: 10px; text-shadow: #333333 2px 2px 4px;}
    #header a {text-decoration:none;}

    #contarea {display: block; width: 980px; margin: auto; padding: auto; background-color: #FFF2DD; clear:both;}
  
    #linkline { width: 980px; height: 29px;margin: auto; padding: auto; background-color: #D37624; background-image: url('images/linkline.png');clear:both; }
    #linkline a{float: left; color: #FFE6BC; font-weight: bold; font-size: 0.8em; text-decoration: none; text-shadow: #333333 2px 2px 4px; padding-left: 10px; padding-right: 10px; padding-top: 5px;}
    #linkline a:visited{color: #FFE6BC;}
    #linkline a:hover{color: #333333;}
    #linkline a.here {color: #333333; text-decoration: none;}

    #lastupdate {float: right; display: block; text-align: right; margin: 0; margin-top: -1.2em; padding: 0; padding-right: 15px;}

    #rss { float: right; text-align: right; padding-top: 3px;}
    
          #docline-top { float: right; padding-right: 40px; text-align: right; }
          #docline-bottom { float: right; padding-right: 40px; text-align: right; font-size: 0.8em; padding-top: 15px; }
          #docline-bottom a{ padding-left: 10px; padding-right: 10px; }
  
    #menu { float: right; display: block; width: 170px; margin: auto; padding: 15px; font-size: 0.8em; font-weight: bold; background-color: #FFE6BC;}
    #menu h1 {color: #990000; font-size: 1.8em;text-shadow: gray 2px 2px 4px;}
    #menu a,a:visited{ color: black; text-decoration: none; font-weight: normal;}
    #menu a:hover{ text-decoration: underline;}
    #menu p{ margin-bottom: 10px;}
  
    #content { float: left; display: block; width: 950px; margin: auto; padding: 15px;}
  
  
    #footer {display: block; width: 980px; height: 100px;margin: auto; padding: auto; background-color: #D37624; background-image: url('images/footer.png');clear:both;text-shadow: #333333 2px 2px 4px;}
    #footer p{color: #FFE6BC; font-weight: bold; padding:15px; padding-left: 10px;}
    #footer a,a:visited{color: #FFE6BC; font-weight: bold; text-decoration:none;}
    #footer a:hover{ color: #333333; text-decoration: none;}
  
  
    #content H1,H2,H3,H4{color: #990000; text-align: left;}
    #content H2{margin-top: 2em;}
    #content H3{margin-top: 1.5em}
    #content H4{margin-top: 1em}
    #content li { margin-top: 1em;}
    #content a,a:active,a:visited{text-decoration: none; color: #4075CA; font-weight: normal;}
    #content a:hover{text-decoration: underline; font-weight: normal;}
    #content .hidden{ display:none; }
    #content p,td,table,tr,li { font-family: Arial, 'sans serif'; }
    #content .nav{margin-left: 0pt;}
    #content .newcode{font-family : "Courier New", Courier, monospace; font-weight: bold; background-color: #F2F2F2; border: solid 1px #DEDEDE;padding: 20pt;}
    #content .note{margin-top: 30pt; margin-bottom: 30pt; text-align: left; background-color: #FFEFEF; border: double 3px; border-color: #FFD5D5;}
    #content hr{color: Black; background-color: Black; height: 1px; border: none;}
    #content .header-news{margin-top: 2em; margin-left: 25pt; font-weight: bold; color: #990000;}
    #content .item-news{margin-left: 45pt; margin-right: 45pt;}
    #content .otherpage{border: solid 1px darkgoldenrod; padding: 20pt; background-color: lemonchiffon;}
    #content IMG {display: block; margin-left: auto; margin-right: auto; }
    #content .red{color: white; background-color: Red; font-weight: bold;}
    #lphp{text-align: right; padding-left: 10px; padding-right: 10px; padding-top: 50px; float: right;}
    #lphp a{padding-left: 5px;}
  </style>
<META NAME="Keywords" CONTENT="multiboot Multi Boot bootable cd rescue clonezilla sysresccd backup restore samba">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

</head>

<body>
<div id="header">
<H2>Clonezilla-SysRescCD</H2>
<H3>Offline Documentation: Boot parameters</H3>
  <div style="margin:0; padding: 3px; width: 980; position relative;">
    <div style="position: absolute; left: 0px;"><H4>26/03/2010 - v 3.1.0</H4></div>
    <div style="position: absolute; right: 0px;"><H4>Last update: 21/05/2010</H4></div>
  </div>
</div>
<div id="linkline">

  
<!--  <a href="features.html">Features</a>-->
  <a class="here" href="../README.html">Offline Documentation</a>


  <!-- docline-top-->
<div id="docline-top">  <a href="usb.html">&lt; PREV</a>  <a href="../README.html">UP</a>  <a href="clonezilla.html">NEXT &gt;</a>  </div>
</div>
<div id="contarea">
  <div id="content">
<a name="boot-top"></a>


<!--   Intro   -->

<H2 style="margin-top: 0;"><a name="boot-intro"></a>Intro <span class="hideprint">[<a href="#boot-top" title="go to top of the page">^</a>]</span></H2>
<p>Booting a linux system means loading a kernel, which is actually the operating system. Well, this is not exactly true, and it is not the only thing that happens during boot up phase, but it is not my intension to explain it here.
<br><br>
The kernel is loaded by Isolinux (the CD boot manager), which is able to pass a number of parameters to it, through its configuration file <b>isolinux.cfg</b>.
<br><br>
These parameters, called boot parameters, are documented by the kernel itself, and can differentiate its behavior dramatically. In our case, each CD (SystemRescueCD and Clonezilla Live) accept a different set of parameters, because they are based on <a href="http://www.gentoo.org/" target="_blank">gentoo</a> and <a href="http://www.debian.org/" target="_blank">debian</a>, respectively.
<br><br>
While in the splash screen of <b>Clonezilla-SysRescCD</b>, you can edit the boot parameters by pressing TAB. They will be presented to you, and you can add or remove what you want. You must be careful not to change or remove the parameters that are dedicated to the CD itself, as altering them will certainty make it unbootable. When you are done, just press ENTER to boot.
</p>


<!--   sysresccd   -->
<H2><a name="sysresccd"></a>SystemRescueCD boot parameters <span class="hideprint">[<a href="#boot-top" title="go to top of the page">^</a>]</span></H2>
<!-- note -->
<div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>
The following info applies to <b>SystemRescueCD v. 1.3.5</b>. In case<br>
 you need to get info for a more recent version of <b>SystemRescueCD</b><br>
please see the page "<a href="http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM" target="_blank">Sysresccd-manual-en Booting the CD-ROM</a>"
</td></tr></table></div>
<p>A typical sysresccd isolinux entry is:</p>

<p class="newcode">kernel rescuecd<br>
append initrd=initram.igz video=ofonly</p>
<!--empty-line-->
<p>The kernel used is <b>rescuecd</b>, and anything after the word <b>append</b> is a boot parameter.<br><br>
<!--empty-line-->
Available kernels (boot images):</p>

<ul class="otherpage" style="padding: 0px 10px 20px 40px">
<!-- Please do not delete these comented lines-->
<!-- SysRescCD documentation section. Please use "update-boot-params" script to update -->
<!--kernels-Documentation-->
<li><b>rescuecd</b> Default for 32bit systems, with Framebuffer disabled, best choice.
</li><li><b>rescue64</b> 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).
</li><li><b>altker32</b> an alternative kernel for 32bit systems. Boot with this kernel if you have problems with <b>rescuecd</b>
</li><li><b>altker64</b> an alternative kernel for 64bit systems. Boot with this kernel in case you have problems with <b>rescue64</b>.
</li>
</ul>

<p><br>The boot parameters you can use are:</p>
<div class="otherpage">
<!-- Please do not delete these comented lines-->
<!-- SysRescCD documentation section. Please use "update-boot-params" script to update -->
<!--SysRescCD-Documentation-->
<a name="General_boot_options" id="General_boot_options"></a><p><b> General boot options</b></p>
<p>Press &lt;TAB&gt; to add additional options.
</p>
<ul><li><b>docache</b>: causes the CD-ROM will be fully loaded into memory. A slower start but once complete, programs start faster and the CD drive will be released allowing normal access to other CDs.   This requires 400MB of memory to cache everything (including the <code>bootdisks</code> and <code>isolinux</code> directories). Add <code>lowmem</code> if you have less that 400MB of memory of to prevent these directories to be copied.
</li></ul>
<p>During boot you will be prompted for the keyboard configuration, avoid this by using
</p>
<ul><li><b>setkmap=kk</b>:  which defines the keymap to load  where <code>kk</code>  (example: <code>setkmap=de</code> for German keyboards)
</li><li><b>root=/dev/xdnp</b>: the <a target="_blank" href="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" class="external text" title="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" rel="nofollow">root=&lt;device&gt; option</a>  boots an existing linux system. For example, if you have linux Gentoo installed on <code>/dev/sda6</code>,  use <code>rescuecd root=/dev/sda6</code> 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 <code>rescuecd root=/dev/VolGroup00/LogVol00</code>. Support is also provided for <code>root=auto</code>, which scans all the block devices tfor a linux system. The first linux system found will be started. So with <code>root=auto</code> 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 <code>filesystem label</code> or <code>filesystem uuid</code>. If the label of the partition where linux is installed is <code>mylinux</code>, then boot it using <code>rescuecd root=LABEL=mylinux</code>. Similarly <code>root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7</code>. See <a target="_blank" href="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" class="external text" title="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" rel="nofollow">more details</a>.
</li><li><b>initscript=service:action</b>: 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: <code>initscript=samba:start</code>. This does the same thing as <code>/etc/init.d/samba start</code>. Use this option multiple times for different services. All the actions that are supported by an initscript can be used.
</li><li><b>backstore=xxx</b>: SystemRescueCd comes with support for the <a target="_blank" href="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" class="external text" title="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" rel="nofollow">backing-stores</a>. 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 <code>backstore=off</code> on the boot command line. If you want to save your backing-store file on an harddisk,  boot with <code>backstore=alldev</code> to scan all devices (not just removable devices). The default location for backing-stores file is any file named <code>sysrcd.bs</code> located at the root of a disk which is often an USB stick. Change the path by using  <code>backstore=/sysrcd/mybackstore.bs</code>. See <a target="_blank" href="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" class="external text" title="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" rel="nofollow">backing-stores</a>.
</li><li><b>isoloop=xxx</b>: Grub2 (currently in development: grub-1.98) provides a new feature to boot from an ISO image which is stored from the hard disk. If you put a copy of <code>systemrescuecd-x86-x.y.z.iso</code> 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 <code>sysrcd.dat</code> file is in an ISO and not directly on the partition. For that reason, this <code>isoloop=xxx</code> boot option is required so you must use it in your <code>grub.cfg</code>. 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 <code>/boot</code> and if you copy this ISO image to <code>/boot/sysrcd/systemrescuecd-x86-x.y.z.iso</code> then the option has to be <code>isoloop=/sysrcd/systemrescuecd-x86-x.y.z.iso</code>. This is because the boot partition is what Grub2 will consider as its root partition during the boot process. Please read <a target="_blank" href="http://www.sysresccd.org/Sysresccd-manual-en_Easy_install_SystemRescueCd_on_harddisk#Boot_the_ISO_image_from_the_disk_using_Grub2" title="Sysresccd-manual-en Easy install SystemRescueCd on harddisk">the section about isoloop</a> for more details.
</li></ul>
<a name="Hardware.2C_drivers_and_troubleshooting_options" id="Hardware.2C_drivers_and_troubleshooting_options"></a><p><b><br> Hardware, drivers and troubleshooting options</b></p>
<ul><li><b>dodebug</b>: Enables verbose messages in linuxrc
</li></ul>
<ul><li><b>doload=xxx</b>: loads needed modules, multiple occurrences are permitted (example: <code>doload=3c59x</code>)
</li><li><b>noload=xxx</b>: prevents loading modules, multiple occurrences are permitted (example: <code>noload=3c59x</code>). Use this option if you have a problem when the system loads a particular module.
</li><li><b>nonet</b>: this will disable the network auto detection at startup
</li></ul>
<ul><li><b>scandelay=x</b>: pauses x seconds during the startup to allow slow devices to initialize. This is required when you boot an USB device. A delay of only few seconds should be enough.
</li></ul>
<ul><li><b>doxdetect</b>: 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 <code>noxdetect</code> that was useful in previous versions.
</li><li><b>nodetect</b>: prevents generic hardware auto-detection. Use this option if you have problems with the hardware auto-detection.
</li></ul>
<ul><li><b>dostartx</b>:   load the X.Org graphical environment.
</li><li><b>forcevesa</b>: 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.
</li><li><b>forcevesa=xxx</b>: The <code>startx</code> command will load the <code>Xvesa</code> server instead of <code>Xorg</code>, and  use the screen resolution given as parameter (eg: <code>1024x768</code>, <code>1280x1024x32</code>).
</li></ul>
<ul><li><b>all-generic-ide</b>: In case of problems related to your hard disk, try to enable this option (eg <code>rescuecd all-generic-ide</code>)
</li><li><b>nodmraid</b>: Disable dmraid,  for some motherboards with built-in RAID controller.
</li><li><b>nomdadm</b>: Disable mdadm,  for software RAID.
</li></ul>
<ul><li><b>acpi-off</b> / <b>noapic</b> / <b>irqpool</b>: use these options if you have problem when the kernel boots: if it hangs on a driver or if it crashes, ...
</li></ul>
<ul><li><b>lowmem</b>: For systems with smaller memory, some daemons are not started including sshd and nfsd.
</li></ul>
<ul><li><b>skipmount=/dev/xxx</b>: The system mounts all the storage devices at boot time to find the sysrcd.dat file.  If your hard disk is broken it should be mounted. Boot with <code>skipmount=/dev/sda1 skipmount=/dev/sda2</code> to ignore these two partitions.
</li></ul>
<a name="Network_configuration_and_remote_access" id="Network_configuration_and_remote_access"></a><p><b><br> Network configuration and remote access</b></p>
<ul><li><b>dodhcp</b>:  to request a DHCP server provide network attributes including an IP address, gateway... .  otherwise,
</li><li><b>ethx=ipaddr/cidr</b>: Sets the static IP address of all the ethernet interfaces on the system. The <code>/cidr</code> extension is optional. For instance, if you use option <code>ethx=192.168.0.1</code> on a machine with two ethernet adapters, both <code>eth0</code> and <code>eth1</code> will be configured with <code>192.168.0.1</code>. You can use the format <code>ethx=10.0.0.1/24</code> (using the cidr notation) if you don't use the default netmask.
</li><li><b>eth0=ipaddr/cidr</b>: This option is similar to <code>ethx=ipaddr/cidr</code> but it configures only one interface at a time.  To configure the network on a server that has two interfaces, use: <code>eth0=192.168.10.1/24 eth1=192.168.20.1</code>.
</li><li><b>dns=ipaddr</b>: Sets the static IP address of the DNS nameserver you want to use to resolve the names. For instance <code>dns=192.168.0.254</code> means that you want to use <code>192.168.0.254</code> as the DNS server.
</li><li><b>gateway=ipaddr</b>: Sets the static IP address of the default route on your network. For instance <code>gateway=192.168.0.254</code> means that the computer can connect to a computer outside of the local network via <code>192.168.0.254</code>.
</li><li><b>dhcphostname=myhost</b>: Sets the hostname that the DHCP client will send to the DHCP server. This may be required if the default hostname cannot be used with your DHCP configuration. This option has been introduced in SystemRescueCd-1.3.5.
</li><li><b>rootpass=123456</b>: Sets the root password of the system running on the livecd to <code>1234</code>. That way you can connect from the network and ssh on the livecd and give <code>123456</code> password as the root password.
</li><li><b>vncserver=x:123456</b>: The <a target="_blank" href="http://www.sysresccd.org/news/2008/04/12/use-systemrescuecd-remotely-with-vnc-server/" class="external text" title="http://www.sysresccd.org/news/2008/04/12/use-systemrescuecd-remotely-with-vnc-server/" rel="nofollow">vncserver boot option</a> 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 <code>x</code> with the number of displays you want, and <code>123456</code> with your password The password must be between 5 and 8 characters, else the boot option will be ignored. In other words the <code>vncserver=2:MyPaSsWd</code> 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.
</li><li><b>nameif=xxx</b>: You can can <a target="_blank" href="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" class="external text" title="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" rel="nofollow">specify what interface name to give</a> 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: <code>nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64</code>. Be careful, you have to respect the separator (comma between the interfaces and exclamation marks between the name and the mac address).
</li></ul>
<a name="Network_boot_using_PXE" id="Network_boot_using_PXE"></a><p><b><br> Network boot using PXE</b></p>
<p>SystemRescueCd provides several options for booting from the network using PXE.
These options can be combined with other network boot options such as <code>ethx</code> (cf previous section). See <a target="_blank" href="http://www.sysresccd.org/Sysresccd-manual-en_PXE_network_booting" class="external text" title="http://www.sysresccd.org/Sysresccd-manual-en_PXE_network_booting" rel="nofollow">PXE network booting</a> to get a global overview of SystemRescueCd and PXE and <a target="_blank" href="http://www.sysresccd.org/Sysresccd-manual-en_Manage_remote_windows_linux_servers_using_SystemRescueCd" class="external text" title="http://www.sysresccd.org/Sysresccd-manual-en_Manage_remote_windows_linux_servers_using_SystemRescueCd" rel="nofollow">Manage remote servers using PXE</a>.
</p><p>The second stage downloads the kernel + initramfs using DHCP/TFTP.
</p><p>The third stage of the PXE boot process acquires the root files system.
</p><p>Several protocols are available.
</p>
<ul><li><b>netboot=</b>tftp<b>://ip/path/sysrcd.dat</b>: from a TFTP server. The filesystem is loaded into memory. As a consequence computers with less than 400MB of memory won't be able to boot this way. The system will continue to work if the network is disconnected after the boot process.
</li><li><b>netboot=</b>http<b>://ip:port/path/sysrcd.dat</b>:  from a Web server. The file system is loaded into memory. Computers with smaller memory won't be able to boot this way. The the system continues to work if the network is disconnected after the boot process.
</li><li><b>netboot=</b>nfs<b>://ip:/path</b>:  mount an NFSv3 directory. The NFS url must be the path of the directory that contains <code>sysrcd.dat</code>. 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.
</li><li><b>netboot=</b>nbd<b>://ip:port</b>:  connect to an NBD server  configured with <code>sysrcd.dat</code> 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.
</li></ul>
<p>For information on activating <b>speakup</b>, see the <a target="_blank" href="http://www.sysresccd.org/Speakup-info" title="Speakup-info">speakup info page</a>.
</p>
<a name="Options_provided_for_autorun" id="Options_provided_for_autorun"></a><p><b><br> Options provided for autorun</b></p>
<ul><li><b>ar_source=xxx</b>: place where the autorun are stored. It may be the root directory of a partition (<code>/dev/sda1</code>), an nfs share (<code>nfs://192.168.1.1:/path/to/scripts</code>), a samba share (<code>smb://192.168.1.1/path/to/scripts</code>), or an http directory (<code><a target="_blank" href="http://192.168.1.1/path/to/scripts" class="external free" title="http://192.168.1.1/path/to/scripts" rel="nofollow">http://192.168.1.1/path/to/scripts</a></code>).
</li><li><b>autoruns=[0-9]</b>: comma separated list of the autorun scrip to be run. For example <code>autoruns=0,2,7</code> the autorun sc <code>autorun0</code>, <code>autorun2</code>, <code>autorun7</code> are run. Use <code>autoruns=no</code> to disable all the autorun scripts with a number.
</li><li><b>ar_ignorefail</b>: continue to execute the scripts chain even if a script failed (returned a non-zero status)
</li><li><b>ar_nodel</b>: do not delete the temporary copy of the autorun scripts located in <code>/var/autorun/tmp</code> after execution
</li><li><b>ar_disable</b>: completely disable autorun, the simple <code>autorun</code> script will not be executed
</li><li><b>ar_nowait</b>: do not wait for a keypress after the autorun script have been executed.
</li></ul>
</p>
</div>


<!--   Clonezilla   -->
<H2><a name="clonezilla"></a>Clonezilla Live boot parameters <span class="hideprint">[<a href="#boot-top" title="go to top of the page">^</a>]</span></H2>
<!-- note -->
<div align="center"><table class="note" border="0" cellpadding="20"><tr valign="top"><td><img src="images/info.png"></td><td>
The following info applies to <b>Clonezilla Live v. 1.2.3-27</b><br>
In case you need to get info for a more recent version of  <b>Clonezilla Live</b><br>
please see the page "<a href="http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc" target="_blank">The boot parameters for Clonezilla live</a>"
</td></tr></table></div>

<p>A typical Clonezilla Live isolinux entry is:</p>

<p class="newcode">  kernel /live/vmlinuz1<br>
  append initrd=/live/initrd1.img boot=live union=aufs    ocs_live_run="ocs-live-general"<br>
  ocs_live_extra_param="" ocs_live_keymap="" ocs_live_batch="no" ocs_lang="" vga=791 nolocales</p>
<!--empty-line-->
<p>The kernel used is <b>vmlinuz</b>, and anything after the word <b>append</b> is a boot parameter.</p>
<!--empty-line-->


<p>The following info comes from the page titled <a href="http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc" target="_blank">The boot parameters for Clonezilla live</a>.</p>

<!-- Please do not delete these comented lines-->
<!-- Clonezilla documentation section. Please use "update-boot-params" script to update -->
<!--Clonezilla-Documentation-->
<div class="otherpage">Clonezilla live is based on <a target="_blank" href="http://wiki.debian.org/DebianLive/" >Debian live</a> with clonezilla installed. Therefore there are 2 kinds of boot parameters:
<ol>
<li>Boot parameters from live-initramfs. You can refer to this <a href="#live-initramfs">manual of live-initramfs</a>.
<li>Boot parameters specially for Clonezilla. All of them are named as "ocs_*", e.g. ocs_live_run, ocs_live_extra_param, ocs_live_batch, ocs_lang.
  <ul>
  <li>ocs_live_run is the main program to run in Clonezilla live to save or restore. or other command. Available program: ocs-live-general, ocs-live-restore or any command you write. Use the Absolute path in Clonezilla live.<br>
      e.g. ocs_live_run="ocs-live-general"<br>
      <font color="red">//NOTE// You might have to use "sudo" command inside your own script, or you can assign it like: ocs_live_run="sudo bash /my-clonezilla"</font><br>
  <li>ocs_live_extra_param will be used only when ocs_live_run=ocs-live-restore (not for ocs-live-general or any other), then it will be passed to ocs-sr. Therefore these parameters are actually those of ocs-sr.<br>
      e.g. ocs_live_extra_param="-b -c restoredisk sarge-r5 hda"
  <li>ocs_live_keymap is for keymap used in Clonezilla live. Man install-keymap for more details.<br>
      e.g. ocs_live_keymap="NONE" (won't change the default layout)<br>
           ocs_live_keymap="/usr/share/keymaps/i386/azerty/fr-latin9.kmap.gz" (French keyboard)
  <li>batch mode or not (yes/no), if no, will run interactively.<br>
      e.g. ocs_live_batch="no"
  <li>ocs_lang is the language used in Clonezilla live. Available value: en_US.UTF-8, zh_TW.UTF-8... (see $DRBL_SCRIPT_PATH/lang/bash/)
      e.g. ocs_lang="en_US.UTF-8"
  <li>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.
  <li>ocs_daemonon, ocs_daemonoff, ocs_numlk, ocs_capslk.<br>
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.
  <li>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.
  <li>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.<br>
  <font color=red>//NOTE//</font><br>
  <ul>
  <li>This parameter was added in Clonezilla live 1.2.3-22 or later.
  <li>If "live-getty console=$tty,38400n81" are assigned in the boot parameters, ocs_live_run_tty will honor $tty, even other value is assigned to ocs_live_run_tty in boot parameter.
  <li>It's recommended to assign ocs_lang and ocs_live_keymap in the boot parameters too.
  </ul>
  <li>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:<br>
ip=eth0,10.0.100.1,255.255.255.0,10.0.100.254,8.8.8.8<br>
If more than one network card, you can use ":" to separate them, e.g.:<br>
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,,<br>
  <li>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.
</ul>
</ol>
<hr>

With the above options, we have the following examples:
<ol>
<li>A PXE config example for you to boot Clonezilla live via PXE, and ssh service is on, the password of account "user" is assigned:<br>
----------------------------------------<br>
label Clonezilla Live<br>
  MENU LABEL Clonezilla Live<br>
  MENU DEFAULT<br>
  kernel vmlinuz1<br>
  append initrd=initrd1.img boot=live union=aufs noswap noprompt vga=788 fetch=tftp://192.168.120.254/filesystem.squashfs usercrypted=bkuQxLqLRuDW6 ocs_numlk="on" ocs_daemonon="ssh"<br>
----------------------------------------<br>

The usercrypted password is created by:<br>
echo YOUR_PASSWORD | mkpasswd -s<br>
("mkpasswd" is from package "whois" in Debian or Ubuntu. Check your GNU/Linux to see which package provides this command if you are not using Debian or Ubuntu. Replace YOUR_PASSWORD with your plain text password, and remember do not put any " in the boot parameters of live-initramfs (while it's ok for those ocs_* boot parameters), i.e.  do NOT use something like usercrypted="bkuQxLqLRuDW6").<br>
//NOTE// If you do not assign salt to mkpasswd, the encrypted password will not be the same every time you create it.<br>
For more about usercrypted discussion, please check the <a href="http://lists.debian.org/debian-live/2008/10/msg00020.html" target=_blank>here</a>.
<br><br>
<li>How to put your own binary driver in Clonezilla live without modifying /live/filesystem.squashfs:
<ul>
<li>Boot clonezilla live
<li>Become root by running "sudo su -"
<li>Copy the dir lsi, which contains a precompiled kernel module matching the running kernel in Clonezilla live and a script to run it, to a working dir, e.g.: <br>
    cp -r /live/image/lsi /home/partimag
<li>cd /home/partimag
<li>/opt/drbl/sbin/ocs-live-dev -c -s -i lsi -u lsi -x "ocs_prerun=/live/image/lsi/prep-lsi.sh"
<li>/opt/drbl/sbin/ocs-iso -s -i lsi -u lsi -x "ocs_prerun=/live/image/lsi/prep-lsi.sh"
<li>///NOTE/// In this example, the 2 files in dir lsi are: megasr.ko (the binary driver) and prep-lsi.sh. The contents of prep-lsi.sh:
<pre>
------------------------
#!/bin/bash
cp -f /live/image/lsi/megasr.ko /lib/modules/`uname -r`/kernel/drivers/block/
chown root.root /lib/modules/`uname -r`/kernel/drivers/block/megasr.ko
depmod -a modprobe megasr
sleep 1
------------------------
</pre>
</ul>

<li>To put your customized script with a PXE version of Clonezilla live (You have to use Clonezilla live version 1.2.2-2 or later):<br>
In this example, we assume (1) The IP address of your PXE server is 192.168.120.254, (2) the customized script (custom-ocs-2) is put on your PXE server's tftpd root dir (E.g. On DRBL server, the path is /tftpboot/nbi_img/. It might be different in your case if you are not use DRBL server as a PXE server).<br>
Therefor your pxelinux.cfg/default file is like:
<p>------------------------<br>
label Clonezilla Live<br>
  MENU DEFAULT<br>
  # MENU HIDE<br>
  MENU LABEL Clonezilla Live<br>
  # MENU PASSWD<br>
  kernel vmlinuz1<br>
  append initrd=initrd1.img boot=live union=aufs noswap noprompt vga=788 ip=frommedia fetch=tftp://192.168.120.254/filesystem.squashfs ocs_prerun="busybox tftp -g -b 10240 -r custom-ocs-2 -l /tmp/custom-ocs-2 192.168.120.254" ocs_live_run="bash /tmp/custom-ocs-2" ocs_live_keymap="NONE" ocs_live_batch="no" ocs_lang="en_US.UTF-8" nolocales<br>
  TEXT HELP<br>
  Boot Clonezilla live via network<br>
  ENDTEXT<br>
<p>------------------------<br>
The content of custom-ocs-2 can be like:
<pre>
------------------------
#!/bin/bash
. /opt/drbl/sbin/drbl-conf-functions
. /opt/drbl/sbin/ocs-functions
. /etc/ocs/ocs-live.conf

# Load language file
ask_and_load_lang_set en_US.UTF-8

# 1. Mount the clonezilla image home.
# Types: local_dev, ssh_server, samba_server, nfs_server
prep-ocsroot -t nfs_server

# 2. Restore the image
if mountpoint /home/partimag/ &>/dev/null; then
  ocs-sr -l en_US.UTF-8 -c -p choose restoredisk ask_user ask_user
else
  [ "$BOOTUP" = "color" ] && $SETCOLOR_FAILURE
  echo "Fail to find the Clonezilla image home /home/partimag!"
  echo "Program terminated!"
  [ "$BOOTUP" = "color" ] && $SETCOLOR_NORMAL
fi
------------------------
</pre>
</li>
</ol>
</div>
<!-- End of copy/paste 3 -->

<H3><a name="live-initramfs"></a>live-initramfs manual <span class="hideprint">[<a href="#boot-top" title="go to top of the page">^</a>]</span></H3>

<p>This is the manual of <a href="http://www.clonezilla.org/clonezilla-live/live-initramfs-param.php" target=_blank>live-initramfs</a>
<BR>
</p>

<!-- Please do not delete these comented lines-->
<!-- SysRescCD documentation section. Please use "update-boot-params" script to update -->
<!--initramfs-Documentation-->
<a name="live-initramfs"></a><div class="otherpage" style="overflow: auto;"><pre>
live-initramfs(7)
=================

Name
----
live-initramfs - Debian Live initramfs hook

Synopsis
--------
BOOT=live

as kernel parameter at boot prompt.

Description
-----------

live-initramfs is a hook for the initramfs-tools, used to generate a initramfs
capable to boot live systems, such as those created by *live-helper*(7).
This includes the Debian Live isos, netboot tarballs, and usb stick images.

At boot time it will look for a (read-only) media containing a "/live"
directory where a root filesystems (often a compressed filesystem image like
squashfs) is stored. If found, it will create a writable environment, using
aufs, for Debian like systems to boot from.

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 <a href="http://packages.ubuntu.com/casper/" target="_blank">casper</a>.
casper was originally written by Tollef Fog Heen &amp;lt;tfheen@canonical.com&amp;gt;
and Matt Zimmerman &amp;lt;mdz@canonical.com&amp;gt;.

Boot options
------------

Here is the complete list of recognized boot parameters by live-initramfs.

  access=*ACCESS*::

Set the accessibility level for physically or visually impared users. ACCESS
must be one of v1, v2, v3, m1, or m2. v1=lesser visual impairment, v2=moderate
visual impairment, v3=blindness, m1=minor motor difficulties, m2=moderate motor
difficulties.

  console=*TTY,SPEED*::

Set the default console to be used with the "live-getty" option. Example:
"console=ttyS0,115200"

  debug::

Makes initramfs boot process more verbose.

  fetch=*URL*::

Another form of netboot by downloading a squashfs image from a given url,
copying to ram and booting it.

  hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*::

Those parameters lets you override values read from the config file.

  ignore_uuid

Do not check that any UUID embedded in the initramfs matches the discovered
medium. live-initramfs may be told to generate a UUID by setting
LIVE_GENERATE_UUID=1 when building the initramfs.

  integrity-check::

If specified, an MD5 sum is calculated on the live media during boot and
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]]***::

Let you specify the name(s) and the options of the interface(s) that should be
configured at boot time. Do not specify this if you want to use dhcp (default).
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**]::

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
instead.

  {keyb|kbd-chooser/method}=**KEYBOARD**, {klayout|console-setup/layoutcode}=**LAYOUT**,
    {kvariant|console-setup/variantcode}=**VARIANT**, {kmodel|console-setup/modelcode}=
    **CODE**, koptions=**OPTIONS**::

Configure the running keyboard as specified, if this one misses live-initramfs
behaves as if "keyb=us" was specified. It will be interfered from "locale=" if
locale is only 2 lowecase letters as a special case. You could also specify
console layout, variant, code, and options (no defaults).

  live-getty::

This changes the auto-login on virtual terminals to use the (experimental)
live-getty code. With this option set the standard kernel argument "console=" is
parsed and if a serial console is specified then live-getty is used to autologin
on the serial console.

  {live-media|bootfrom}=**DEVICE**::

If you specify one of this two equivalent forms, live-initramfs will first try
to find this device for the "/live" directory where the read-only root
filesystem should reside. If it did not find something usable, the normal scan
for block devices is performed.

  {live-media-encryption|encryption}=**TYPE**::

live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase,
useful to build paranoid live systems :-). TYPE supported so far are "aes" for
loop-aes encryption type.

  live-media-offset=**BYTES**::

This way you could tell live-initramfs that your image starts at offset BYTES in
the above specified or autodiscovered device, this could be useful to hide the
Debian Live iso or image inside another iso or image, to create "clean" images.

  live-media-path=**PATH**::

Sets the path to the live filesystem on the medium. By default, it is set to
'/live' and you should not change that unless you have customized your media
accordingly.

  live-media-timeout=**SECONDS**::

Set the timeout in seconds for the device specified by "live-media=" to become
ready before giving up.

  {locale|debian-installer/locale}=**LOCALE**::

Configure the running locale as specified, if not present the live-media rootfs
configured locale will be used and if also this one misses live-initramfs behave
as "locale=en_US.UTF-8" was specified. If only 2 lowercase letter are specified
(like "it"), the "maybe wanted" locale is generated (like en:EN.UTF-8), in this
case if also "keyb=" is unspecified is set with those 2 lowercase letters
(keyb=us). Beside that facility, only UTF8 locales are supported by
live-initramfs.

  module=**NAME**::

Instead of using the default optional file "filesystem.module" (see below)
another file could be specified without the extension ".module"; it should be
placed on "/live" directory of the live medium.

  netboot[=**nfs**|**cifs**]::

This tells live-initramfs to perform a network mount. The parameter "nfsroot="
(with optional "nfsopts="), should specify where is the location of the root
filesystem.  With no args, will try cifs first, and if it fails nfs.

  nfsopts=::

This lets you specify custom nfs options.

  noautologin::

This parameter disables the automatic terminal login only, not touching gdk/kdm.

  noxautologin::

This parameter disables the automatic login of gdm/kdm only, not touching
terminals.

  nofastboot::

This parameter disables the default disabling of filesystem checks in
/etc/fstab. If you have static filesystems on your harddisk and you want them to
be checked at boot time, use this parameter, otherwise they are skipped.

  nopersistent::

disables the "persistent" feature, useful if the bootloader (like syslinux) has
been installed with persistent enabled.

  noprompt

Do not prompt to eject the CD on reboot.

  nosudo::

This parameter disables the automatic configuration of sudo.

  swapon::

This parameter enables usage of local swap partitions.

  nouser::

This parameter disables the creation of the default user completely.

  noxautoconfig::

This parameter disables Xorg auto-reconfiguration at boot time. This is valuable
if you either do the detection on your own, or, if you want to ship a custom,
premade xorg.conf in your live system.

  persistent[=nofiles]::

live-initramfs will look for persistent and snapshot partitions or files labeled
"live-rw", "home-rw", and files called "live-sn*", "home-sn*" and will try to,
in order: mount as /cow the first, mount the second in /home, and just copy the
contents of the latter in appropriate locations (snapshots). Snapshots will be
tried to be updated on reboot/shutdown. Look at live-snapshot(1) for more
informations. If "nofiles" is specified, only filesystems with matching labels
will be searched; no filesystems will be traversed looking for archives or image
files. This results in shorter boot times.

  {preseed/file|file}=**FILE**::

A path to a file present on the rootfs could be used to preseed debconf
database.

  package/question=**VALUE**::

All debian installed packages could be preseeded from command-line that way,
beware of blanks spaces, they will interfere with parsing, use a preseed file in
this case.

  quickreboot::

This option causes live-initramfs to reboot without attempting to eject the
media and without asking the user to remove the boot media.

  showmounts::

This parameter will make live-initramfs to show on "/" the ro filesystems
(mostly compressed) on "/live". This is not enabled by default because could
lead to problems by applications like "mono" which store binary paths on
installation.

  textonly

Start up to text-mode shell prompts, disabling the graphical user interface.

  timezone=**TIMEZONE**::

By default, timezone is set to UTC. Using the timezone parameter, you can set it
to your local zone, e.g. Europe/Zurich.

  todisk=**DEVICE**::

Adding this parameter, live-initramfs will try to copy the entire read-only
media to the specified device before mounting the root filesystem. It probably
needs a lot of free space. Subsequent boots should then skip this step and just
specify the "live-media=DEVICE" boot parameter with the same DEVICE used this
time.

  toram::

Adding this parameter, live-initramfs will try to copy the whole read-only media
to the computer's RAM before mounting the root filesystem. This could need a lot
of ram, according to the space used by the read-only media.

  union=**aufs**|**unionfs**::

By default, live-initramfs uses aufs. With this parameter, you can switch to
unionfs.

  utc=**yes**|**no**::

By default, Debian systems do assume that the hardware clock is set to UTC. You
can change or explicitly set it with this parameter.

  xdebconf::

Uses xdebconfigurator, if present on the rootfs, to configure X instead of the
standard procedure (experimental).

  xvideomode=**RESOLUTION**::

Doesn't do xorg autodetection, but enforces a given resolution.

Files
-----

  /etc/live.conf

Some variables can be configured via this config file (inside the live system).

   /live/filesystem.module

This optional file (inside the live media) contains a list of white-space or
carriage-return-separated file names corresponding to disk images in the "/live"
directory. If this file exists, only images listed here will be merged into the
root aufs, and they will be loaded in the order listed here. The first entry
in this file will be the "lowest" point in the aufs, and the last file in
this list will be on the "top" of the aufs, directly below /cow.  Without
this file, any images in the "/live" directory are loaded in alphanumeric order.

 /etc/live-persistence.binds

This optional file (which resides in the rootfs system, not in the live media)
is used as a list of directories which not need be persistent: ie. their
content does not need to survive reboots when using the persistence features.

This saves expensive writes and speeds up operations on volatile data such as
web caches and temporary files (like e.g. /tmp and .mozilla) which are
regenerated each time. This is achieved by bind mounting each listed directory
with a tmpfs on the original path.


See also
--------

live-snapshot(1), initramfs-tools(8), live-helper(7), live-initscripts(7),
live-webhelper(7)

Bugs
----

Report bugs against live-initramfs
<a href="http://packages.qa.debian.org/live-initramfs" target="_blank">http://packages.qa.debian.org/live-initramfs</a>.

Homepage
--------

More information about the Debian Live project can be found at
<a href="http://debian-live.alioth.debian.org/" target="_blank">http://debian-live.alioth.debian.org/</a> and
<a href="http://wiki.debian.org/DebianLive/" target="_blank">http://wiki.debian.org/DebianLive/</a>.

Authors
-------

live-initramfs is maintained by Daniel Baumann &amp;lt;daniel@debian.org&amp;gt;
for the Debian project.

live-initramfs is a fork of <a href="http://packages.ubuntu.com/casper/" target="_blank">casper</a>.
casper was originally written by Tollef Fog Heen &amp;lt;tfheen@canonical.com&amp;gt;
and Matt Zimmerman &amp;lt;mdz@canonical.com&amp;gt;.
</pre>
</div>


</div>


<!--<a name="template-top"></a>-->

  <div id="footer">
<div id="docline-bottom">  <a href="usb.html">&lt; PREV</a>  <a href="../README.html">UP</a>  <a href="clonezilla.html">NEXT &gt;</a>  </div>
  <p>Copyright: &#169; <a href="mailto:&#115;&#110;&#103;&#064;&#104;&#101;&#108;&#108;&#117;&#103;&#046;&#103;&#114;?subject=About Clonezilla-SysRescCD v 3.1.0">Spiros Georgaras</a>, 2007-2010<br /><br/>
  Hosted by <a href="http://www.hellug.gr" target="_blank" title="Hellenic Linux User Group">HEL.L.U.G.</a></p>
  </div>
</div>
</body>
</html>