/[clonezilla-sysresccd]/trunk/www/boot-params.html
ViewVC logotype

Diff of /trunk/www/boot-params.html

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

revision 37 by sng, Tue Mar 23 10:28:53 2010 UTC revision 77 by sng, Thu Jun 17 22:25:06 2010 UTC
# Line 78  Line 78 
78  <H2>Clonezilla-SysRescCD</H2>  <H2>Clonezilla-SysRescCD</H2>
79  <H3>Documentation: Boot parameters</H3>  <H3>Documentation: Boot parameters</H3>
80    <div style="margin:0; padding: 3px; width: 980; position relative;">    <div style="margin:0; padding: 3px; width: 980; position relative;">
81      <div style="position: absolute; left: 0px;"><H4>25/02/2010 - v 3.1.0</H4></div>      <div style="position: absolute; left: 0px;"><H4>25/05/2010 - v 3.1.0</H4></div>
82      <div style="position: absolute; right: 0px;"><H4>Last update: 23/03/2010</H4></div>      <div style="position: absolute; right: 0px;"><H4>Last update: 18/06/2010</H4></div>
83    </div>    </div>
84  </div>  </div>
85  <div id="linkline">  <div id="linkline">
# Line 120  While in the splash screen of <b>Clonezi Line 120  While in the splash screen of <b>Clonezi
120  <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>  <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>
121  <!-- note -->  <!-- note -->
122  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>
123  The following info applies to <b>SystemRescueCD v. 1.3.5</b>. In case<br>  The following info applies to <b>SystemRescueCD v. 1.5.5</b>. In case<br>
124   you need to get info for a more recent version of <b>SystemRescueCD</b><br>   you need to get info for a more recent version of <b>SystemRescueCD</b><br>
125  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>"  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>"
126  </td></tr></table></div>  </td></tr></table></div>
# Line 134  append initrd=initram.igz video=ofonly</ Line 134  append initrd=initram.igz video=ofonly</
134  Available kernels (boot images):</p>  Available kernels (boot images):</p>
135    
136  <ul class="otherpage" style="padding: 0px 10px 20px 40px">  <ul class="otherpage" style="padding: 0px 10px 20px 40px">
137  <li><b>rescuecd</b> This is the default choice for 32bits systems, with Framebuffer disabled, best choice.</li>  <!-- Please do not delete these comented lines-->
138  <li><b>altker32</b> 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.</li>  <!-- SysRescCD documentation section. Please use "update-boot-params" script to update -->
139  <li><b>rescue64</b> 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).</li>  <!--kernels-Documentation-->
140  <li><b>altker64</b> 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.</li>  <li><b>rescuecd</b> Default for 32bit systems, with Framebuffer disabled, best choice.
141    </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).
142    </li><li><b>altker32</b> an alternative kernel for 32bit systems. Boot with this kernel if you have problems with <b>rescuecd</b>
143    </li><li><b>altker64</b> an alternative kernel for 64bit systems. Boot with this kernel in case you have problems with <b>rescue64</b>.
144    </li>
145  </ul>  </ul>
146    
   
147  <p><br>The boot parameters you can use are:</p>  <p><br>The boot parameters you can use are:</p>
   
   
148  <div class="otherpage">  <div class="otherpage">
149  <p><b>General boot options</b></p>  <!-- Please do not delete these comented lines-->
150    <!-- SysRescCD documentation section. Please use "update-boot-params" script to update -->
151  <ul><li><b>setkmap=xx</b>: if you don't want to be asked for the keymap, you can choose which keymap to load automatically. Replace <code>xx</code> with your keymap (for example: <code>setkmap=de</code> for german keyboards)  <!--SysRescCD-Documentation-->
152  </li><li><b>docache</b>: this option is very useful if you need to insert another disc in the CD drive after booting. The CD-ROM will be fully loaded into memory, and you will be able to remove the disc from the drive. The <code>docache</code> option requires 400MB of memory if you want to cache everything (including the <code>bootdisks</code> and <code>isolinux</code> directories). You can add the <code>lowmem</code> option if you have less that 400MB of memory of to prevent these directories to be copied into memory.  <a name="General_boot_options" id="General_boot_options"></a><p><b> General boot options</b></p>
153  </li><li><b>root=xxx</b>: the <a 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> lets you boot an existing linux system. For example, if you have a linux gentoo installed on <code>/dev/sda6</code>, you can type <code>rescuecd root=/dev/sda6</code> and Gentoo Linux will be started instead of the system that is on the CD-ROM. Keep in mind that you must use a 64bits kernel if your system is made of 64bits programs. For instance, you can boot a 64bits linux system installed on /dev/sda6 with <code>rescue64 root=/dev/sda6</code>. From SystemRescueCd-1.0.4, this option works with LVM disks, so you can write something like <code>rescuecd root=/dev/VolGroup00/LogVol00</code>. SystemRescueCd-1.0.4 and newer versions also supports <code>root=auto</code>, that will scan all the block devices of the computer to find a linux system. The first linux system found on the disks 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 with your kernel for instance. You can have <a 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> about that option.  <p>Press &lt;TAB&gt; to add additional options (in SystemRescueCd-1.5 and more recent)
154  </li><li><b>initscript=service:action</b>: This options allows you to automatically start/stop a service at boot time. For instance if you need the samba service to be started, you can boot with the following option: <code>initscript=samba:start</code>. This does the same thing as <code>/etc/init.d/samba start</code>. You can use this option several times with different services. All the action that are supported by an initscript can be used. This option is available with SystemRescueCd-1.0.2 and newer.  </p>
155  </li><li><b>backstore=xxx</b>: SystemRescueCd-1.1.x comes with support for the <a 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>. Basically, a backing-store is a loopback filesystem which saves all the changes you can make in SystemRescueCd when you use it. In other words it allows you to save all the files which changes in SystemRescueCd while you use it, so that you keep these changes the next time you boot it. By default, sysresccd automatically scan all your removable devices (eg: usb sticks) at boot time and uses the first backing-store it finds if there is one. A backing-store is not mandatory and it the scan fails it will just store the files which change in memory. To disable the disks scan at boot time you can specify <code>backstore=off</code> on the boot command line. If you want to save your backing-store file on an harddisk, you will have to boot with <code>backstore=alldev</code> so that it scans all devices not just removable devices. The default place for backing-stores file is any file named <code>sysrcd.bs</code> located at the root of a disk which is often an USB key. You can change the path by using an option such as <code>backstore=/sysrcd/mybackstore.bs</code> and then sysresccd will try to find a file named <code>mybackstore.bs</code> located in <code>/sysrcd</code> in any block-device (partition, USB-stick, ...). You can find more information about on the page about <a 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>.  <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.
156  </li></ul>  </li><li><b>setkmap=kk</b>:  which defines the keymap to load  where <code>kk</code>  (example: <code>setkmap=de</code> for German keyboards). This way you won't be prompted for the keyboard configuration during the boot.
157    </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>.
158  <p><b><BR>Hardware, drivers and troubleshooting options</b></p>  </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.
159    </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>.
160  <ul><li><b>nonet</b>: this will disable the network auto detection at startup  </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.
161  </li><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>
162  </li><li><b>doxdetect</b>: Since version 0.3.5 the auto-configuration is done in X.Org itself, and then mkxf86config is disabled by default. This option forces the system to run the mkxf86config startup script 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.  <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>
163  </li><li><b>nodetect</b>: prevents the generic hardware auto-detection. Use this option if you have problems with the hardware auto-detection.  <ul><li><b>dodebug</b>: Enables verbose messages in linuxrc
164  </li><li><b>doload=xxx</b>: forces to load one/several modules at startup (example: <code>doload=3c59x</code>)  </li></ul>
165  </li><li><b>noload=xxx</b>: prevents the system to load one/several modules at startup (example: <code>noload=3c59x</code>). Use this option if you have a problem when the system loads a particular module at boot time.  <ul><li><b>doload=xxx</b>: loads needed kernel modules, multiple comma separated occurrences are permitted (example: <code>doload=3c59x,e1000</code>)
166  </li><li><b>dostartx</b>: This option will force the system to load the X.Org graphical environment at boot time. You won't have to type <code>startx</code> by hand to get it.  </li><li><b>noload=xxx</b>: prevents loading kernel modules, multiple comma separated occurrences are permitted (example: <code>noload=3c59x,e1000</code>). Use this option if you have a problem when the system loads a particular module.
167  </li><li><b>forcevesa</b>: Forces X.Org to work with 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>nonet</b>: this will disable the network auto detection at startup
168  </li><li><b>forcevesa=xxx</b>: The <code>startx</code> command will load the <code>Xvesa</code> server instead of <code>Xorg</code>, and Xvesa will use the screen resolution given as parameter (eg: <code>1024x768</code>, <code>1280x1024x32</code>). The <code>forcevesa</code> option can take a parameter from SystemRescueCd-1.0.0 and more recent.  </li></ul>
169  </li><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>)  <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.
170  </li><li><b>acpi-off</b> / <b>noapic</b> / <b>irqpool</b>: use these options if you have any problem when the kernel boots: if it hangs on a driver or if it crashes, ...  </li></ul>
171  </li><li><b>dodebug</b>: Enables verbose messages in the linuxrc script.  <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.
172  </li><li><b>lowmem</b>: Prevents non critical things to be loaded into memory (like the sshd and nfsd services)  </li><li><b>nodetect</b>: prevents generic hardware auto-detection. Use this option if you have problems with the hardware auto-detection.
173  </li><li><b>skipmount=/dev/xxx</b>: The system mounts all the storage devices at boot time to find the sysrcd.dat file. You may not want it to mount a device, for instance if your hard disk is broken because it would crash the system. You can just boot with <code>skipmount=/dev/sda1 skipmount=/dev/sda2</code> if you want SystemRescueCd to ignore these two partitions. This boot option requires SystemRescueCd-1.0.1 or more recent.  </li></ul>
174  </li><li><b>nodmraid</b>: Disable dmraid, which is the program that drives RAID disks based on cheap RAID controller built-in motherboards.  <ul><li><b>dostartx</b>:   load the X.Org graphical environment.
175  </li><li><b>nomdadm</b>: Disable mdadm, which is the program that drives software RAID.  </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.
176  </li></ul>  </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>).
177    </li></ul>
178  <p><b><BR>Network auto-configuration and remote access</b></p>  <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>)
179    </li><li><b>nodmraid</b>: Disable dmraid,  for some motherboards with built-in RAID controller.
180  <ul><li><b>dodhcp</b>: Use <code>dodhcp</code> if you have a DHCP server on your network and you want the system to get a dynamic IP address at boot time.  </li><li><b>nomdadm</b>: Disable mdadm,  for software RAID.
181  </li><li><b>ethx=ipaddr/cidr</b>: Sets the static IP address of all the ethernet interfaces found 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 also write something like <code>ethx=10.0.0.1/24</code> (using the cidr notation) if you don't use the default netmask.  </li></ul>
182  </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. Of course, you can use <a href="http://www.sysresccd.org/news/2008/04/13/new-boot-options-for-advanced-ethernet-ip-configuration/" class="external text" title="http://www.sysresccd.org/news/2008/04/13/new-boot-options-for-advanced-ethernet-ip-configuration/" rel="nofollow">the eth0=ipaddr/cidr option</a> it for all the ethernet interfaces, not just eth0. For instance if you want to configure the network on a server that has two interfaces, you can write something like this: <code>eth0=192.168.10.1/24 eth1=192.168.20.1</code>. This option requires SystemRescueCd-1.0.2 or newer.  <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, ...
183    </li></ul>
184    <ul><li><b>lowmem</b>: For systems with smaller memory, some daemons are not started including sshd and nfsd.
185    </li></ul>
186    <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.
187    </li></ul>
188    <a name="Network_configuration_and_remote_access" id="Network_configuration_and_remote_access"></a><p><b><br> Network configuration and remote access</b></p>
189    <ul><li><b>nonm</b>: to disable the Network-Manager service that conflicts with the standard network command line tools such as <code>ifconfig</code> and <code>ip</code>. 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.
190    </li><li><b>dodhcp</b>: to request a DHCP server provide network attributes including an IP address, gateway...
191    </li><li><b>nodhcp</b>: never run the dhcp client in the initramfs boot script. May be useful if you use PXE boot on a computer with several ethernet interfaces. Support for this option is available in SystemRescueCd-1.5.5-beta2 and more recent
192    </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.
193    </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>.
194  </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>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.
195  </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>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>.
196  </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>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.
197  </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>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.
198  </li><li><b>vncserver=x:123456</b>: The <a 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>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.
199  </li><li><b>nameif=xxx</b>: You can can <a 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><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). You can also use the magic keyword <a target="_blank" href="http://www.sysresccd.org/forums/viewtopic.php?f=7&amp;t=2538&amp;start=0" class="external text" title="http://www.sysresccd.org/forums/viewtopic.php?f=7&amp;t=2538&amp;start=0" rel="nofollow">BOOTIF</a> 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 <code>nameif=eth0!BOOTIF</code> if you want the boot interface to be called <code>eth0</code> on a computer with several Ethernet interfaces.
200  </li></ul>  </li></ul>
201    <a name="Network_boot_using_PXE" id="Network_boot_using_PXE"></a><p><b><br> Network boot using PXE</b></p>
202  <p><b><BR>Options provided by the autorun</b></p>  <p>SystemRescueCd provides several options for booting from the network using PXE.
203    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>.
204  <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 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>).  </p><p>The second stage downloads the kernel + initramfs using DHCP/TFTP.
205  </li><li><b>autoruns=[0-9]</b>: comma separated list of the autorun script that have to be run. For instance if you use <code>autoruns=0,2,7</code> then the following autorun scripts will be executed: <code>autorun0</code>, <code>autorun2</code>, <code>autorun7</code>. Use <code>autoruns=no</code> to disable all the autorun scripts with a number.  </p><p>The third stage of the PXE boot process acquires the root files system.
206    </p><p>Several protocols are available.
207    </p>
208    <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.
209    </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.
210    </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.
211    </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.
212    </li></ul>
213    <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>.
214    </p>
215    <a name="Options_provided_for_autorun" id="Options_provided_for_autorun"></a><p><b><br> Options provided for autorun</b></p>
216    <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>).
217    </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.
218  </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_ignorefail</b>: continue to execute the scripts chain even if a script failed (returned a non-zero status)
219  </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_nodel</b>: do not delete the temporary copy of the autorun scripts located in <code>/var/autorun/tmp</code> after execution
220  </li><li><b>ar_disable</b>: completely disable autorun, the simple <code>autorun</code> script will not be executed  </li><li><b>ar_disable</b>: completely disable autorun, the simple <code>autorun</code> script will not be executed
221  </li><li><b>ar_nowait</b>: do not wait for a keypress after the autorun script have been executed.  </li><li><b>ar_nowait</b>: do not wait for a keypress after the autorun script have been executed.
222  </li></ul>  </li></ul>
223    </p>
224  </div>  </div>
225    
226    
# Line 203  Available kernels (boot images):</p> Line 228  Available kernels (boot images):</p>
228  <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>  <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>
229  <!-- note -->  <!-- note -->
230  <div align="center"><table class="note" border="0" cellpadding="20"><tr valign="top"><td><img src="images/info.png"></td><td>  <div align="center"><table class="note" border="0" cellpadding="20"><tr valign="top"><td><img src="images/info.png"></td><td>
231  The following info applies to <b>Clonezilla Live v. 1.2.3-27</b><br>  The following info applies to <b>Clonezilla Live v. 1.2.5-17</b><br>
232  In case you need to get info for a more recent version of  <b>Clonezilla Live</b><br>  In case you need to get info for a more recent version of  <b>Clonezilla Live</b><br>
233  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>"  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>"
234  </td></tr></table></div>  </td></tr></table></div>
# Line 220  please see the page "<a href="http://www Line 245  please see the page "<a href="http://www
245    
246  <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>  <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>
247    
248  <!-- Start of copy/paste 3 -->  <!-- Please do not delete these comented lines-->
249  <div class="otherpage">Clonezilla live is based on <a href="http://wiki.debian.org/DebianLive/" target=_blank>Debian live</a> with clonezilla installed. Therefore there are 2 kinds of boot parameters:  <!-- Clonezilla documentation section. Please use "update-boot-params" script to update -->
250    <!--Clonezilla-Documentation-->
251    <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:
252  <ol>  <ol>
253  <li>Boot parameters from live-initramfs. You can refer to this <a href="#live-initramfs">manual of live-initramfs</a>.  <li>Boot parameters from live-initramfs. You can refer to this <a href="#live-initramfs">manual of live-initramfs</a>.
254  <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.  <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.
255    <ul>    <ul>
256    <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>    <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>
257        e.g. ocs_live_run="ocs-live-general"        e.g. ocs_live_run="ocs-live-general"<br>
258          <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>
259    <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>    <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>
260        e.g. ocs_live_extra_param="-b -c restoredisk sarge-r5 hda"        e.g. ocs_live_extra_param="-b -c restoredisk sarge-r5 hda"
261    <li>ocs_live_keymap is for keymap used in Clonezilla live. Man install-keymap for more details.<br>    <li>ocs_live_keymap is for keymap used in Clonezilla live. Man install-keymap for more details.<br>
# Line 241  please see the page "<a href="http://www Line 269  please see the page "<a href="http://www
269    <li>ocs_daemonon, ocs_daemonoff, ocs_numlk, ocs_capslk.<br>    <li>ocs_daemonon, ocs_daemonoff, ocs_numlk, ocs_capslk.<br>
270  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.  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.
271    <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_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.
272    <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.    <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>
273      <font color=red>//NOTE//</font><br>
274      <ul>
275      <li>This parameter was added in Clonezilla live 1.2.3-22 or later.
276      <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.
277      <li>It's recommended to assign ocs_lang and ocs_live_keymap in the boot parameters too.
278      </ul>
279      <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>
280    ip=eth0,10.0.100.1,255.255.255.0,10.0.100.254,8.8.8.8<br>
281    If more than one network card, you can use ":" to separate them, e.g.:<br>
282    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>
283    <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.    <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.
284  </ul>  </ul>
285  </ol>  </ol>
# Line 337  fi Line 375  fi
375  <BR>  <BR>
376  </p>  </p>
377    
378  <div class="otherpage"><pre>  <!-- Please do not delete these comented lines-->
379    <!-- SysRescCD documentation section. Please use "update-boot-params" script to update -->
380    <!--initramfs-Documentation-->
381    <a name="live-initramfs"></a><div class="otherpage" style="overflow: auto;"><pre>
382  live-initramfs(7)  live-initramfs(7)
383  =================  =================
384    
# Line 366  aufs, for Debian like systems to boot fr Line 407  aufs, for Debian like systems to boot fr
407  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,
408  although it will do no harm.  although it will do no harm.
409    
410  live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper].  live-initramfs is a fork of <a href="http://packages.ubuntu.com/casper/" target="_blank">casper</a>.
411  casper was originally written by Tollef Fog Heen &lt;tfheen@canonical.com&gt;  casper was originally written by Tollef Fog Heen &amp;lt;tfheen@canonical.com&amp;gt;
412  and Matt Zimmerman &lt;mdz@canonical.com&gt;.  and Matt Zimmerman &amp;lt;mdz@canonical.com&amp;gt;.
413    
414  Boot options  Boot options
415  ------------  ------------
416    
417  Here is the complete list of recognized boot parameters by live-initramfs.  Here is the complete list of recognized boot parameters by live-initramfs.
418    
419   access=*ACCESS*::    access=*ACCESS*::
420    
421  Set the accessibility level for physically or visually impared users. ACCESS  Set the accessibility level for physically or visually impared users. ACCESS
422  must be one of v1, v2, v3, m1, or m2. v1=lesser visual impairment, v2=moderate  must be one of v1, v2, v3, m1, or m2. v1=lesser visual impairment, v2=moderate
423  visual impairment, v3=blindness, m1=minor motor difficulties, m2=moderate motor  visual impairment, v3=blindness, m1=minor motor difficulties, m2=moderate motor
424  difficulties.  difficulties.
425    
426   console=*TTY,SPEED*::    console=*TTY,SPEED*::
427    
428  Set the default console to be used with the "live-getty" option. Example:  Set the default console to be used with the "live-getty" option. Example:
429  "console=ttyS0,115200"  "console=ttyS0,115200"
430    
431   debug::    debug::
432    
433  Makes initramfs boot process more verbose.  Makes initramfs boot process more verbose.
434    
435   fetch=*URL*::    fetch=*URL*::
436    
437  Another form of netboot by downloading a squashfs image from a given url,  Another form of netboot by downloading a squashfs image from a given url,
438  copying to ram and booting it.  copying to ram and booting it.
439    
440   hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*::    hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*::
441    
442  Those parameters lets you override values read from the config file.  Those parameters lets you override values read from the config file.
443    
444   ignore_uuid    ignore_uuid
445    
446  Do not check that any UUID embedded in the initramfs matches the discovered  Do not check that any UUID embedded in the initramfs matches the discovered
447  medium. live-initramfs may be told to generate a UUID by setting  medium. live-initramfs may be told to generate a UUID by setting
448  LIVE_GENERATE_UUID=1 when building the initramfs.  LIVE_GENERATE_UUID=1 when building the initramfs.
449    
450   integrity-check::    integrity-check::
451    
452  If specified, an MD5 sum is calculated on the live media during boot and  If specified, an MD5 sum is calculated on the live media during boot and
453  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
454  live media.  live media.
455    
456   ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]    ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:
457      [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]]***::       [DEVICE]:[AUTOCONF] [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:
458         [DEVICE]:[AUTOCONF]]***::
459    
460  Let you specify the name(s) and the options of the interface(s) that should be  Let you specify the name(s) and the options of the interface(s) that should be
461  configured at boot time. Do not specify this if you want to use dhcp (default).  configured at boot time. Do not specify this if you want to use dhcp (default).
462  It will be changed in a future release to mimick official kernel boot param  It will be changed in a future release to mimick official kernel boot param
463  specification (e.g. ip=10.0.0.1::10.0.0.254:255.255.255.0::eth0,:::::eth1:dhcp).  specification (e.g. ip=10.0.0.1::10.0.0.254:255.255.255.0::eth0,:::::eth1:dhcp).
464    
465   ip[=**frommedia**]::    ip[=**frommedia**]::
466    
467  If this variable is set, dhcp and static configuration are just skipped and the  If this variable is set, dhcp and static configuration are just skipped and the
468  system will use the (must be) media-preconfigured /etc/network/interfaces  system will use the (must be) media-preconfigured /etc/network/interfaces
469  instead.  instead.
470    
471   {keyb|kbd-chooser/method}=**KEYBOARD**, {klayout|console-setup/layoutcode}=**LAYOUT**,    {keyb|kbd-chooser/method}=**KEYBOARD**, {klayout|console-setup/layoutcode}=**LAYOUT**,
472      {kvariant|console-setup/variantcode}=**VARIANT**,      {kvariant|console-setup/variantcode}=**VARIANT**, {kmodel|console-setup/modelcode}=
473      {kmodel|console-setup/modelcode}=**CODE**, koptions=**OPTIONS**::      **CODE**, koptions=**OPTIONS**::
474    
475  Configure the running keyboard as specified, if this one misses live-initramfs  Configure the running keyboard as specified, if this one misses live-initramfs
476  behaves as if "keyb=us" was specified. It will be interfered from "locale=" if  behaves as if "keyb=us" was specified. It will be interfered from "locale=" if
477  locale is only 2 lowecase letters as a special case. You could also specify  locale is only 2 lowecase letters as a special case. You could also specify
478  console layout, variant, code, and options (no defaults).  console layout, variant, code, and options (no defaults).
479    
480   live-getty::    live-getty::
481    
482  This changes the auto-login on virtual terminals to use the (experimental)  This changes the auto-login on virtual terminals to use the (experimental)
483  live-getty code. With this option set the standard kernel argument "console=" is  live-getty code. With this option set the standard kernel argument "console=" is
484  parsed and if a serial console is specified then live-getty is used to autologin  parsed and if a serial console is specified then live-getty is used to autologin
485  on the serial console.  on the serial console.
486    
487   {live-media|bootfrom}=**DEVICE**::    {live-media|bootfrom}=**DEVICE**::
488    
489  If you specify one of this two equivalent forms, live-initramfs will first try  If you specify one of this two equivalent forms, live-initramfs will first try
490  to find this device for the "/live" directory where the read-only root  to find this device for the "/live" directory where the read-only root
491  filesystem should reside. If it did not find something usable, the normal scan  filesystem should reside. If it did not find something usable, the normal scan
492  for block devices is performed.  for block devices is performed.
493    
494   {live-media-encryption|encryption}=**TYPE**::    {live-media-encryption|encryption}=**TYPE**::
495    
496  live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase,  live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase,
497  useful to build paranoid live systems :-). TYPE supported so far are "aes" for  useful to build paranoid live systems :-). TYPE supported so far are "aes" for
498  loop-aes encryption type.  loop-aes encryption type.
499    
500   live-media-offset=**BYTES**::    live-media-offset=**BYTES**::
501    
502  This way you could tell live-initramfs that your image starts at offset BYTES in  This way you could tell live-initramfs that your image starts at offset BYTES in
503  the above specified or autodiscovered device, this could be useful to hide the  the above specified or autodiscovered device, this could be useful to hide the
504  Debian Live iso or image inside another iso or image, to create "clean" images.  Debian Live iso or image inside another iso or image, to create "clean" images.
505    
506   live-media-path=**PATH**::    live-media-path=**PATH**::
507    
508  Sets the path to the live filesystem on the medium. By default, it is set to  Sets the path to the live filesystem on the medium. By default, it is set to
509  '/live' and you should not change that unless you have customized your media  '/live' and you should not change that unless you have customized your media
510  accordingly.  accordingly.
511    
512   live-media-timeout=**SECONDS**::    live-media-timeout=**SECONDS**::
513    
514  Set the timeout in seconds for the device specified by "live-media=" to become  Set the timeout in seconds for the device specified by "live-media=" to become
515  ready before giving up.  ready before giving up.
516    
517   {locale|debian-installer/locale}=**LOCALE**::    {locale|debian-installer/locale}=**LOCALE**::
518    
519  Configure the running locale as specified, if not present the live-media rootfs  Configure the running locale as specified, if not present the live-media rootfs
520  configured locale will be used and if also this one misses live-initramfs behave  configured locale will be used and if also this one misses live-initramfs behave
# Line 482  case if also "keyb=" is unspecified is s Line 524  case if also "keyb=" is unspecified is s
524  (keyb=us). Beside that facility, only UTF8 locales are supported by  (keyb=us). Beside that facility, only UTF8 locales are supported by
525  live-initramfs.  live-initramfs.
526    
527   module=**NAME**::    module=**NAME**::
528    
529  Instead of using the default optional file "filesystem.module" (see below)  Instead of using the default optional file "filesystem.module" (see below)
530  another file could be specified without the extension ".module"; it should be  another file could be specified without the extension ".module"; it should be
531  placed on "/live" directory of the live medium.  placed on "/live" directory of the live medium.
532    
533   netboot[=**nfs**|**cifs**]::    netboot[=**nfs**|**cifs**]::
534    
535  This tells live-initramfs to perform a network mount. The parameter "nfsroot="  This tells live-initramfs to perform a network mount. The parameter "nfsroot="
536  (with optional "nfsopts="), should specify where is the location of the root  (with optional "nfsopts="), should specify where is the location of the root
537  filesystem.  With no args, will try cifs first, and if it fails nfs.  filesystem.  With no args, will try cifs first, and if it fails nfs.
538    
539   nfsopts=::    nfsopts=::
540    
541  This lets you specify custom nfs options.  This lets you specify custom nfs options.
542    
543   noautologin::    noautologin::
544    
545  This parameter disables the automatic terminal login only, not touching gdk/kdm.  This parameter disables the automatic terminal login only, not touching gdk/kdm.
546    
547   noxautologin::    noxautologin::
548    
549  This parameter disables the automatic login of gdm/kdm only, not touching  This parameter disables the automatic login of gdm/kdm only, not touching
550  terminals.  terminals.
551    
552   nofastboot::    nofastboot::
553    
554  This parameter disables the default disabling of filesystem checks in  This parameter disables the default disabling of filesystem checks in
555  /etc/fstab. If you have static filesystems on your harddisk and you want them to  /etc/fstab. If you have static filesystems on your harddisk and you want them to
556  be checked at boot time, use this parameter, otherwise they are skipped.  be checked at boot time, use this parameter, otherwise they are skipped.
557    
558   nopersistent::    nopersistent::
559    
560  disables the "persistent" feature, useful if the bootloader (like syslinux) has  disables the "persistent" feature, useful if the bootloader (like syslinux) has
561  been installed with persistent enabled.  been installed with persistent enabled.
562    
563   noprompt    noprompt
564    
565  Do not prompt to eject the CD on reboot.  Do not prompt to eject the CD on reboot.
566    
567   nosudo::    nosudo::
568    
569  This parameter disables the automatic configuration of sudo.  This parameter disables the automatic configuration of sudo.
570    
571   swapon::    swapon::
572    
573  This parameter enables usage of local swap partitions.  This parameter enables usage of local swap partitions.
574    
575   nouser::    nouser::
576    
577  This parameter disables the creation of the default user completely.  This parameter disables the creation of the default user completely.
578    
579   noxautoconfig::    noxautoconfig::
580    
581  This parameter disables Xorg auto-reconfiguration at boot time. This is valuable  This parameter disables Xorg auto-reconfiguration at boot time. This is valuable
582  if you either do the detection on your own, or, if you want to ship a custom,  if you either do the detection on your own, or, if you want to ship a custom,
583  premade xorg.conf in your live system.  premade xorg.conf in your live system.
584    
585   persistent[=nofiles]::    persistent[=nofiles]::
586    
587  live-initramfs will look for persistent and snapshot partitions or files labeled  live-initramfs will look for persistent and snapshot partitions or files labeled
588  "live-rw", "home-rw", and files called "live-sn*", "home-sn*" and will try to,  "live-rw", "home-rw", and files called "live-sn*", "home-sn*" and will try to,
# Line 551  informations. If "nofiles" is specified, Line 593  informations. If "nofiles" is specified,
593  will be searched; no filesystems will be traversed looking for archives or image  will be searched; no filesystems will be traversed looking for archives or image
594  files. This results in shorter boot times.  files. This results in shorter boot times.
595    
596   {preseed/file|file}=**FILE**::    {preseed/file|file}=**FILE**::
597    
598  A path to a file present on the rootfs could be used to preseed debconf  A path to a file present on the rootfs could be used to preseed debconf
599  database.  database.
600    
601   package/question=**VALUE**::    package/question=**VALUE**::
602    
603  All debian installed packages could be preseeded from command-line that way,  All debian installed packages could be preseeded from command-line that way,
604  beware of blanks spaces, they will interfere with parsing, use a preseed file in  beware of blanks spaces, they will interfere with parsing, use a preseed file in
605  this case.  this case.
606    
607   quickreboot::    quickreboot::
608    
609  This option causes live-initramfs to reboot without attempting to eject the  This option causes live-initramfs to reboot without attempting to eject the
610  media and without asking the user to remove the boot media.  media and without asking the user to remove the boot media.
611    
612   showmounts::    showmounts::
613    
614  This parameter will make live-initramfs to show on "/" the ro filesystems  This parameter will make live-initramfs to show on "/" the ro filesystems
615  (mostly compressed) on "/live". This is not enabled by default because could  (mostly compressed) on "/live". This is not enabled by default because could
616  lead to problems by applications like "mono" which store binary paths on  lead to problems by applications like "mono" which store binary paths on
617  installation.  installation.
618    
619   textonly    textonly
620    
621  Start up to text-mode shell prompts, disabling the graphical user interface.  Start up to text-mode shell prompts, disabling the graphical user interface.
622    
623   timezone=**TIMEZONE**::    timezone=**TIMEZONE**::
624    
625  By default, timezone is set to UTC. Using the timezone parameter, you can set it  By default, timezone is set to UTC. Using the timezone parameter, you can set it
626  to your local zone, e.g. Europe/Zurich.  to your local zone, e.g. Europe/Zurich.
627    
628   todisk=**DEVICE**::    todisk=**DEVICE**::
629    
630  Adding this parameter, live-initramfs will try to copy the entire read-only  Adding this parameter, live-initramfs will try to copy the entire read-only
631  media to the specified device before mounting the root filesystem. It probably  media to the specified device before mounting the root filesystem. It probably
# Line 591  needs a lot of free space. Subsequent bo Line 633  needs a lot of free space. Subsequent bo
633  specify the "live-media=DEVICE" boot parameter with the same DEVICE used this  specify the "live-media=DEVICE" boot parameter with the same DEVICE used this
634  time.  time.
635    
636   toram::    toram::
637    
638  Adding this parameter, live-initramfs will try to copy the whole read-only media  Adding this parameter, live-initramfs will try to copy the whole read-only media
639  to the computer's RAM before mounting the root filesystem. This could need a lot  to the computer's RAM before mounting the root filesystem. This could need a lot
640  of ram, according to the space used by the read-only media.  of ram, according to the space used by the read-only media.
641    
642   union=**aufs**|**unionfs**::    union=**aufs**|**unionfs**::
643    
644  By default, live-initramfs uses aufs. With this parameter, you can switch to  By default, live-initramfs uses aufs. With this parameter, you can switch to
645  unionfs.  unionfs.
646    
647   utc=**yes**|**no**::    utc=**yes**|**no**::
648    
649  By default, Debian systems do assume that the hardware clock is set to UTC. You  By default, Debian systems do assume that the hardware clock is set to UTC. You
650  can change or explicitly set it with this parameter.  can change or explicitly set it with this parameter.
651    
652   xdebconf::    xdebconf::
653    
654  Uses xdebconfigurator, if present on the rootfs, to configure X instead of the  Uses xdebconfigurator, if present on the rootfs, to configure X instead of the
655  standard procedure (experimental).  standard procedure (experimental).
656    
657   xvideomode=**RESOLUTION**::    xvideomode=**RESOLUTION**::
658    
659  Doesn't do xorg autodetection, but enforces a given resolution.  Doesn't do xorg autodetection, but enforces a given resolution.
660    
661  Files  Files
662  -----  -----
663    
664   /etc/live.conf    /etc/live.conf
665    
666  Some variables can be configured via this config file (inside the live system).  Some variables can be configured via this config file (inside the live system).
667    
668    /live/filesystem.module     /live/filesystem.module
669    
670  This optional file (inside the live media) contains a list of white-space or  This optional file (inside the live media) contains a list of white-space or
671  carriage-return-separated file names corresponding to disk images in the "/live"  carriage-return-separated file names corresponding to disk images in the "/live"
# Line 633  in this file will be the "lowest" point Line 675  in this file will be the "lowest" point
675  this list will be on the "top" of the aufs, directly below /cow.  Without  this list will be on the "top" of the aufs, directly below /cow.  Without
676  this file, any images in the "/live" directory are loaded in alphanumeric order.  this file, any images in the "/live" directory are loaded in alphanumeric order.
677    
678  /etc/live-persistence.binds   /etc/live-persistence.binds
679    
680  This optional file (which resides in the rootfs system, not in the live media)  This optional file (which resides in the rootfs system, not in the live media)
681  is used as a list of directories which not need be persistent: ie. their  is used as a list of directories which not need be persistent: ie. their
# Line 655  Bugs Line 697  Bugs
697  ----  ----
698    
699  Report bugs against live-initramfs  Report bugs against live-initramfs
700  link:http://packages.qa.debian.org/live-initramfs[http://packages.qa.debian.org/live-initramfs].  <a href="http://packages.qa.debian.org/live-initramfs" target="_blank">http://packages.qa.debian.org/live-initramfs</a>.
701    
702  Homepage  Homepage
703  --------  --------
704    
705  More information about the Debian Live project can be found at  More information about the Debian Live project can be found at
706  link:http://debian-live.alioth.debian.org/[http://debian-live.alioth.debian.org/] and  <a href="http://debian-live.alioth.debian.org/" target="_blank">http://debian-live.alioth.debian.org/</a> and
707  link:http://wiki.debian.org/DebianLive/[http://wiki.debian.org/DebianLive/].  <a href="http://wiki.debian.org/DebianLive/" target="_blank">http://wiki.debian.org/DebianLive/</a>.
708    
709  Authors  Authors
710  -------  -------
711    
712  live-initramfs is maintained by Daniel Baumann &lt;daniel@debian.org&gt;  live-initramfs is maintained by Daniel Baumann &amp;lt;daniel@debian.org&amp;gt;
713  for the Debian project.  for the Debian project.
714    
715  live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper].  live-initramfs is a fork of <a href="http://packages.ubuntu.com/casper/" target="_blank">casper</a>.
716  casper was originally written by Tollef Fog Heen &lt;tfheen@canonical.com&gt;  casper was originally written by Tollef Fog Heen &amp;lt;tfheen@canonical.com&amp;gt;
717  and Matt Zimmerman &lt;mdz@canonical.com&gt;.</pre>  and Matt Zimmerman &amp;lt;mdz@canonical.com&amp;gt;.
718    </pre>
719  </div>  </div>
720    
721    

Legend:
Removed from v.37  
changed lines
  Added in v.77

webmaster@linux.gr
ViewVC Help
Powered by ViewVC 1.1.26