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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 40 - (hide annotations)
Thu May 13 14:01:58 2010 UTC (11 years, 4 months ago) by sng
File MIME type: text/html
File size: 49116 byte(s)
updating site (trunk)

1 sng 28 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
2     <html>
3     <head>
4     <link rel="alternate" type="application/rss+xml" title="RSS" href="http://clonezilla-sysresccd.hellug.gr/clonezilla-sysresccd.rss">
5     <link rel="shortcut icon" href="favicon.ico">
6     <title>Clonezilla-SysRescCD - Documentation: Boot parameters</title>
7     <style type="text/css">
8     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; }
9    
10    
11    
12     #header {position:relative; display: block; width: 980px; height: 121px;margin: auto; padding: auto; background-color: #D37624; background-image: url('images/header.png');clear:both;}
13     #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;}
14     #header h3{ color: #FFE6BC; font-weight: bold; font-size: 1.8em; margin:0; padding: 0; padding-left: 10px; text-shadow: #333333 2px 2px 4px;}
15     #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;}
16     #header a {text-decoration:none;}
17    
18     #contarea {display: block; width: 980px; margin: auto; padding: auto; background-color: #FFF2DD; clear:both;}
19    
20     #linkline { width: 980px; height: 29px;margin: auto; padding: auto; background-color: #D37624; background-image: url('images/linkline.png');clear:both; }
21     #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;}
22     #linkline a:visited{color: #FFE6BC;}
23     #linkline a:hover{color: #333333;}
24     #linkline a.here {color: #333333; text-decoration: none;}
25    
26     #lastupdate {float: right; display: block; text-align: right; margin: 0; margin-top: -1.2em; padding: 0; padding-right: 15px;}
27    
28     #rss { float: right; text-align: right; padding-top: 3px;}
29    
30     #docline-top { float: right; padding-right: 40px; text-align: right; }
31     #docline-bottom { float: right; padding-right: 40px; text-align: right; font-size: 0.8em; padding-top: 15px; }
32     #docline-bottom a{ padding-left: 10px; padding-right: 10px; }
33    
34     #menu { float: right; display: block; width: 170px; margin: auto; padding: 15px; font-size: 0.8em; font-weight: bold; background-color: #FFE6BC;}
35     #menu h1 {color: #990000; font-size: 1.8em;text-shadow: gray 2px 2px 4px;}
36     #menu a,a:visited{ color: black; text-decoration: none; font-weight: normal;}
37     #menu a:hover{ text-decoration: underline;}
38     #menu p{ margin-bottom: 10px;}
39    
40     #content { float: left; display: block; width: 950px; margin: auto; padding: 15px;}
41    
42    
43     #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;}
44     #footer p{color: #FFE6BC; font-weight: bold; padding:15px; padding-left: 10px;}
45     #footer a,a:visited{color: #FFE6BC; font-weight: bold; text-decoration:none;}
46     #footer a:hover{ color: #333333; text-decoration: none;}
47    
48    
49     #content H1,H2,H3,H4{color: #990000; text-align: left;}
50     #content H2{margin-top: 2em;}
51     #content H3{margin-top: 1.5em}
52     #content H4{margin-top: 1em}
53     #content li { margin-top: 1em;}
54     #content a,a:active,a:visited{text-decoration: none; color: #4075CA; font-weight: normal;}
55     #content a:hover{text-decoration: underline; font-weight: normal;}
56     #content .hidden{ display:none; }
57     #content p,td,table,tr,li { font-family: Arial, 'sans serif'; }
58     #content .nav{margin-left: 0pt;}
59     #content .newcode{font-family : "Courier New", Courier, monospace; font-weight: bold; background-color: #F2F2F2; border: solid 1px #DEDEDE;padding: 20pt;}
60     #content .note{margin-top: 30pt; margin-bottom: 30pt; text-align: left; background-color: #FFEFEF; border: double 3px; border-color: #FFD5D5;}
61     #content hr{color: Black; background-color: Black; height: 1px; border: none;}
62     #content .header-news{margin-top: 2em; margin-left: 25pt; font-weight: bold; color: #990000;}
63     #content .item-news{margin-left: 45pt; margin-right: 45pt;}
64     #content .otherpage{border: solid 1px darkgoldenrod; padding: 20pt; background-color: lemonchiffon;}
65     #content IMG {display: block; margin-left: auto; margin-right: auto; }
66     #content .red{color: white; background-color: Red; font-weight: bold;}
67     #lphp{text-align: right; padding-left: 10px; padding-right: 10px; padding-top: 50px; float: right;}
68     #lphp a{padding-left: 5px;}
69     </style>
70     <META NAME="Keywords" CONTENT="multiboot Multi Boot bootable cd rescue clonezilla sysresccd backup restore samba">
71     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
72    
73     </head>
74    
75     <body>
76     <div id="header">
77 sng 37 <div id="lphp" style=""><a target="_blank" href="onepage.html"><img src="images/chain.png" border="0" /></a><a target="_blank" href="printable.php"><img src="images/print_it.png" border="0" /></a></div>
78 sng 28 <H2>Clonezilla-SysRescCD</H2>
79     <H3>Documentation: Boot parameters</H3>
80     <div style="margin:0; padding: 3px; width: 980; position relative;">
81 sng 38 <div style="position: absolute; left: 0px;"><H4>26/03/2010 - v 3.1.0</H4></div>
82 sng 40 <div style="position: absolute; right: 0px;"><H4>Last update: 13/05/2010</H4></div>
83 sng 28 </div>
84     </div>
85     <div id="linkline">
86     <a href="index.html">Home</a>
87     <a href="news.php">News</a>
88     <!-- <a href="features.html">Features</a>-->
89     <a class="here" href="doc.html">Documentation</a>
90     <a href="index.html#download">Download</a>
91     <a href="screenshots.html">Screenshots</a>
92     <a href="index.html#credits">Credits</a>
93     <a href="help.html">Help</a>
94    
95     <div id="rss">
96     <a href="clonezilla-sysresccd.rss"><img src="images/rss-orange-11.png" width="30" height="14" border="0"/></a>
97     </div>
98     <!-- docline-top-->
99     <div id="docline-top"> <a href="usb.html">&lt; PREV</a> <a href="doc.html">UP</a> <a href="clonezilla.html">NEXT &gt;</a> </div>
100     </div>
101     <div id="contarea">
102     <div id="content">
103     <a name="boot-top"></a>
104    
105    
106     <!-- Intro -->
107    
108     <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>
109     <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.
110     <br><br>
111     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>.
112     <br><br>
113     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.
114     <br><br>
115     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.
116     </p>
117    
118    
119     <!-- sysresccd -->
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>
121     <!-- note -->
122     <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>
124     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>"
126     </td></tr></table></div>
127     <p>A typical sysresccd isolinux entry is:</p>
128    
129     <p class="newcode">kernel rescuecd<br>
130     append initrd=initram.igz video=ofonly</p>
131     <!--empty-line-->
132     <p>The kernel used is <b>rescuecd</b>, and anything after the word <b>append</b> is a boot parameter.<br><br>
133     <!--empty-line-->
134     Available kernels (boot images):</p>
135    
136     <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>
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>
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>
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>
141     </ul>
142    
143    
144     <p><br>The boot parameters you can use are:</p>
145    
146    
147     <div class="otherpage">
148 sng 40 <!-- Please do not delete these comented lines-->
149     <!-- SysRescCD documentation section. Please use "update-boot-params" script to update -->
150     <!--SysRescCD-Documentation-->
151     <a name="General_boot_options" id="General_boot_options"></a><p><b> <span class="mw-headline">General boot options</span></b></p>
152     <p>Press &lt;TAB&gt; to add additional options.
153     </p>
154     <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.
155 sng 28 </li></ul>
156 sng 40 <p>During boot you will be prompted for the keyboard configuration, avoid this by using
157     </p>
158     <ul><li><b>setkmap=kk</b>: which defines the keymap to load where <code>kk</code> (example: <code>setkmap=de</code> for German keyboards)
159     </li><li><b>root=/dev/xdnp</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> 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 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>.
160     </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.
161     </li><li><b>backstore=xxx</b>: SystemRescueCd 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>. 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 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>.
162     </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 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.
163 sng 28 </li></ul>
164 sng 40 <a name="Hardware.2C_drivers_and_troubleshooting_options" id="Hardware.2C_drivers_and_troubleshooting_options"></a><p><b><br> <span class="mw-headline">Hardware, drivers and troubleshooting options</span></b></p>
165     <ul><li><b>dodebug</b>: Enables verbose messages in linuxrc
166     </li></ul>
167     <ul><li><b>doload=xxx</b>: loads needed modules, multiple occurrences are permitted (example: <code>doload=3c59x</code>)
168     </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.
169     </li><li><b>nonet</b>: this will disable the network auto detection at startup
170     </li></ul>
171     <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.
172     </li></ul>
173     <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.
174     </li><li><b>nodetect</b>: prevents generic hardware auto-detection. Use this option if you have problems with the hardware auto-detection.
175     </li></ul>
176     <ul><li><b>dostartx</b>: load the X.Org graphical environment.
177     </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.
178     </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>).
179     </li></ul>
180     <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>)
181     </li><li><b>nodmraid</b>: Disable dmraid, for some motherboards with built-in RAID controller.
182     </li><li><b>nomdadm</b>: Disable mdadm, for software RAID.
183     </li></ul>
184     <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, ...
185     </li></ul>
186     <ul><li><b>lowmem</b>: For systems with smaller memory, some daemons are not started including sshd and nfsd.
187     </li></ul>
188     <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.
189     </li></ul>
190     <a name="Network_configuration_and_remote_access" id="Network_configuration_and_remote_access"></a><p><b><br> <span class="mw-headline">Network configuration and remote access</span></b></p>
191     <ul><li><b>dodhcp</b>: to request a DHCP server provide network attributes including an IP address, gateway... . otherwise,
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 sng 28 </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>.
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.
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.
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.
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).
200     </li></ul>
201 sng 40 <a name="Network_boot_using_PXE" id="Network_boot_using_PXE"></a><p><b><br> <span class="mw-headline">Network boot using PXE</span></b></p>
202     <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 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 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     </p><p>The second stage downloads the kernel + initramfs using DHCP/TFTP.
205     </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 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> <span class="mw-headline">Options provided for autorun</span></b></p>
216 sng 28 <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>).
217 sng 40 </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 sng 28 </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
220     </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.
222     </li></ul>
223 sng 40 </p>
224 sng 28 </div>
225    
226    
227     <!-- Clonezilla -->
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>
229     <!-- note -->
230     <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>
232     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>"
234     </td></tr></table></div>
235    
236     <p>A typical Clonezilla Live isolinux entry is:</p>
237    
238     <p class="newcode"> kernel /live/vmlinuz1<br>
239     append initrd=/live/initrd1.img boot=live union=aufs ocs_live_run="ocs-live-general"<br>
240     ocs_live_extra_param="" ocs_live_keymap="" ocs_live_batch="no" ocs_lang="" vga=791 nolocales</p>
241     <!--empty-line-->
242     <p>The kernel used is <b>vmlinuz</b>, and anything after the word <b>append</b> is a boot parameter.</p>
243     <!--empty-line-->
244    
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>
247    
248 sng 40 <!-- Please do not delete these comented lines-->
249     <!-- Clonezilla documentation section. Please use "update-boot-params" script to update -->
250     <!--Clonezilla-Documentation-->
251 sng 28 <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:
252     <ol>
253 sng 40 <li>Boot parameters from live-initramfs. You can refer to this <a href="../live-initramfs-param.php" target=_blank>manual of live-initramfs</a>.
254 sng 28 <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>
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>
257 sng 40 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 sng 28 <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"
261     <li>ocs_live_keymap is for keymap used in Clonezilla live. Man install-keymap for more details.<br>
262     e.g. ocs_live_keymap="NONE" (won't change the default layout)<br>
263     ocs_live_keymap="/usr/share/keymaps/i386/azerty/fr-latin9.kmap.gz" (French keyboard)
264     <li>batch mode or not (yes/no), if no, will run interactively.<br>
265     e.g. ocs_live_batch="no"
266     <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/)
267     e.g. ocs_lang="en_US.UTF-8"
268     <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.
269     <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.
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.
272 sng 40 <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 sng 28 <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>
285     </ol>
286 sng 40
287 sng 28 <hr>
288    
289     With the above options, we have the following examples:
290     <ol>
291     <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>
292     ----------------------------------------<br>
293     label Clonezilla Live<br>
294     MENU LABEL Clonezilla Live<br>
295     MENU DEFAULT<br>
296     kernel vmlinuz1<br>
297     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>
298     ----------------------------------------<br>
299    
300     The usercrypted password is created by:<br>
301     echo YOUR_PASSWORD | mkpasswd -s<br>
302     ("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>
303     //NOTE// If you do not assign salt to mkpasswd, the encrypted password will not be the same every time you create it.<br>
304     For more about usercrypted discussion, please check the <a href="http://lists.debian.org/debian-live/2008/10/msg00020.html" target=_blank>here</a>.
305     <br><br>
306     <li>How to put your own binary driver in Clonezilla live without modifying /live/filesystem.squashfs:
307     <ul>
308     <li>Boot clonezilla live
309     <li>Become root by running "sudo su -"
310     <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>
311     cp -r /live/image/lsi /home/partimag
312     <li>cd /home/partimag
313     <li>/opt/drbl/sbin/ocs-live-dev -c -s -i lsi -u lsi -x "ocs_prerun=/live/image/lsi/prep-lsi.sh"
314     <li>/opt/drbl/sbin/ocs-iso -s -i lsi -u lsi -x "ocs_prerun=/live/image/lsi/prep-lsi.sh"
315     <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:
316     <pre>
317     ------------------------
318     #!/bin/bash
319     cp -f /live/image/lsi/megasr.ko /lib/modules/`uname -r`/kernel/drivers/block/
320     chown root.root /lib/modules/`uname -r`/kernel/drivers/block/megasr.ko
321     depmod -a modprobe megasr
322     sleep 1
323     ------------------------
324     </pre>
325     </ul>
326    
327     <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>
328     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>
329     Therefor your pxelinux.cfg/default file is like:
330     <p>------------------------<br>
331     label Clonezilla Live<br>
332     MENU DEFAULT<br>
333     # MENU HIDE<br>
334     MENU LABEL Clonezilla Live<br>
335     # MENU PASSWD<br>
336     kernel vmlinuz1<br>
337     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>
338     TEXT HELP<br>
339     Boot Clonezilla live via network<br>
340     ENDTEXT<br>
341     <p>------------------------<br>
342     The content of custom-ocs-2 can be like:
343     <pre>
344     ------------------------
345     #!/bin/bash
346     . /opt/drbl/sbin/drbl-conf-functions
347     . /opt/drbl/sbin/ocs-functions
348     . /etc/ocs/ocs-live.conf
349    
350     # Load language file
351     ask_and_load_lang_set en_US.UTF-8
352    
353     # 1. Mount the clonezilla image home.
354     # Types: local_dev, ssh_server, samba_server, nfs_server
355     prep-ocsroot -t nfs_server
356    
357     # 2. Restore the image
358     if mountpoint /home/partimag/ &>/dev/null; then
359     ocs-sr -l en_US.UTF-8 -c -p choose restoredisk ask_user ask_user
360     else
361     [ "$BOOTUP" = "color" ] && $SETCOLOR_FAILURE
362     echo "Fail to find the Clonezilla image home /home/partimag!"
363     echo "Program terminated!"
364     [ "$BOOTUP" = "color" ] && $SETCOLOR_NORMAL
365     fi
366     ------------------------
367     </pre>
368     </li>
369     </ol>
370     </div>
371     <!-- End of copy/paste 3 -->
372    
373     <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>
374    
375     <p>This is the manual of <a href="http://www.clonezilla.org/clonezilla-live/live-initramfs-param.php" target=_blank>live-initramfs</a>
376     <BR>
377     </p>
378    
379     <div class="otherpage"><pre>
380     live-initramfs(7)
381     =================
382    
383     Name
384     ----
385     live-initramfs - Debian Live initramfs hook
386    
387     Synopsis
388     --------
389     BOOT=live
390    
391     as kernel parameter at boot prompt.
392    
393     Description
394     -----------
395    
396     live-initramfs is a hook for the initramfs-tools, used to generate a initramfs
397     capable to boot live systems, such as those created by *live-helper*(7).
398     This includes the Debian Live isos, netboot tarballs, and usb stick images.
399    
400     At boot time it will look for a (read-only) media containing a "/live"
401     directory where a root filesystems (often a compressed filesystem image like
402     squashfs) is stored. If found, it will create a writable environment, using
403     aufs, for Debian like systems to boot from.
404    
405     You probably do not want to install this package onto a non-live system,
406     although it will do no harm.
407    
408     live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper].
409     casper was originally written by Tollef Fog Heen &lt;tfheen@canonical.com&gt;
410     and Matt Zimmerman &lt;mdz@canonical.com&gt;.
411    
412     Boot options
413     ------------
414    
415     Here is the complete list of recognized boot parameters by live-initramfs.
416    
417     access=*ACCESS*::
418    
419     Set the accessibility level for physically or visually impared users. ACCESS
420     must be one of v1, v2, v3, m1, or m2. v1=lesser visual impairment, v2=moderate
421     visual impairment, v3=blindness, m1=minor motor difficulties, m2=moderate motor
422     difficulties.
423    
424     console=*TTY,SPEED*::
425    
426     Set the default console to be used with the "live-getty" option. Example:
427     "console=ttyS0,115200"
428    
429     debug::
430    
431     Makes initramfs boot process more verbose.
432    
433     fetch=*URL*::
434    
435     Another form of netboot by downloading a squashfs image from a given url,
436     copying to ram and booting it.
437    
438     hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*::
439    
440     Those parameters lets you override values read from the config file.
441    
442     ignore_uuid
443    
444     Do not check that any UUID embedded in the initramfs matches the discovered
445     medium. live-initramfs may be told to generate a UUID by setting
446     LIVE_GENERATE_UUID=1 when building the initramfs.
447    
448     integrity-check::
449    
450     If specified, an MD5 sum is calculated on the live media during boot and
451     compared to the value found in md5sum.txt found in the root directory of the
452     live media.
453    
454     ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]
455     [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]]***::
456    
457     Let you specify the name(s) and the options of the interface(s) that should be
458     configured at boot time. Do not specify this if you want to use dhcp (default).
459     It will be changed in a future release to mimick official kernel boot param
460     specification (e.g. ip=10.0.0.1::10.0.0.254:255.255.255.0::eth0,:::::eth1:dhcp).
461    
462     ip[=**frommedia**]::
463    
464     If this variable is set, dhcp and static configuration are just skipped and the
465     system will use the (must be) media-preconfigured /etc/network/interfaces
466     instead.
467    
468     {keyb|kbd-chooser/method}=**KEYBOARD**, {klayout|console-setup/layoutcode}=**LAYOUT**,
469     {kvariant|console-setup/variantcode}=**VARIANT**,
470     {kmodel|console-setup/modelcode}=**CODE**, koptions=**OPTIONS**::
471    
472     Configure the running keyboard as specified, if this one misses live-initramfs
473     behaves as if "keyb=us" was specified. It will be interfered from "locale=" if
474     locale is only 2 lowecase letters as a special case. You could also specify
475     console layout, variant, code, and options (no defaults).
476    
477     live-getty::
478    
479     This changes the auto-login on virtual terminals to use the (experimental)
480     live-getty code. With this option set the standard kernel argument "console=" is
481     parsed and if a serial console is specified then live-getty is used to autologin
482     on the serial console.
483    
484     {live-media|bootfrom}=**DEVICE**::
485    
486     If you specify one of this two equivalent forms, live-initramfs will first try
487     to find this device for the "/live" directory where the read-only root
488     filesystem should reside. If it did not find something usable, the normal scan
489     for block devices is performed.
490    
491     {live-media-encryption|encryption}=**TYPE**::
492    
493     live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase,
494     useful to build paranoid live systems :-). TYPE supported so far are "aes" for
495     loop-aes encryption type.
496    
497     live-media-offset=**BYTES**::
498    
499     This way you could tell live-initramfs that your image starts at offset BYTES in
500     the above specified or autodiscovered device, this could be useful to hide the
501     Debian Live iso or image inside another iso or image, to create "clean" images.
502    
503     live-media-path=**PATH**::
504    
505     Sets the path to the live filesystem on the medium. By default, it is set to
506     '/live' and you should not change that unless you have customized your media
507     accordingly.
508    
509     live-media-timeout=**SECONDS**::
510    
511     Set the timeout in seconds for the device specified by "live-media=" to become
512     ready before giving up.
513    
514     {locale|debian-installer/locale}=**LOCALE**::
515    
516     Configure the running locale as specified, if not present the live-media rootfs
517     configured locale will be used and if also this one misses live-initramfs behave
518     as "locale=en_US.UTF-8" was specified. If only 2 lowercase letter are specified
519     (like "it"), the "maybe wanted" locale is generated (like en:EN.UTF-8), in this
520     case if also "keyb=" is unspecified is set with those 2 lowercase letters
521     (keyb=us). Beside that facility, only UTF8 locales are supported by
522     live-initramfs.
523    
524     module=**NAME**::
525    
526     Instead of using the default optional file "filesystem.module" (see below)
527     another file could be specified without the extension ".module"; it should be
528     placed on "/live" directory of the live medium.
529    
530     netboot[=**nfs**|**cifs**]::
531    
532     This tells live-initramfs to perform a network mount. The parameter "nfsroot="
533     (with optional "nfsopts="), should specify where is the location of the root
534     filesystem. With no args, will try cifs first, and if it fails nfs.
535    
536     nfsopts=::
537    
538     This lets you specify custom nfs options.
539    
540     noautologin::
541    
542     This parameter disables the automatic terminal login only, not touching gdk/kdm.
543    
544     noxautologin::
545    
546     This parameter disables the automatic login of gdm/kdm only, not touching
547     terminals.
548    
549     nofastboot::
550    
551     This parameter disables the default disabling of filesystem checks in
552     /etc/fstab. If you have static filesystems on your harddisk and you want them to
553     be checked at boot time, use this parameter, otherwise they are skipped.
554    
555     nopersistent::
556    
557     disables the "persistent" feature, useful if the bootloader (like syslinux) has
558     been installed with persistent enabled.
559    
560     noprompt
561    
562     Do not prompt to eject the CD on reboot.
563    
564     nosudo::
565    
566     This parameter disables the automatic configuration of sudo.
567    
568     swapon::
569    
570     This parameter enables usage of local swap partitions.
571    
572     nouser::
573    
574     This parameter disables the creation of the default user completely.
575    
576     noxautoconfig::
577    
578     This parameter disables Xorg auto-reconfiguration at boot time. This is valuable
579     if you either do the detection on your own, or, if you want to ship a custom,
580     premade xorg.conf in your live system.
581    
582     persistent[=nofiles]::
583    
584     live-initramfs will look for persistent and snapshot partitions or files labeled
585     "live-rw", "home-rw", and files called "live-sn*", "home-sn*" and will try to,
586     in order: mount as /cow the first, mount the second in /home, and just copy the
587     contents of the latter in appropriate locations (snapshots). Snapshots will be
588     tried to be updated on reboot/shutdown. Look at live-snapshot(1) for more
589     informations. If "nofiles" is specified, only filesystems with matching labels
590     will be searched; no filesystems will be traversed looking for archives or image
591     files. This results in shorter boot times.
592    
593     {preseed/file|file}=**FILE**::
594    
595     A path to a file present on the rootfs could be used to preseed debconf
596     database.
597    
598     package/question=**VALUE**::
599    
600     All debian installed packages could be preseeded from command-line that way,
601     beware of blanks spaces, they will interfere with parsing, use a preseed file in
602     this case.
603    
604     quickreboot::
605    
606     This option causes live-initramfs to reboot without attempting to eject the
607     media and without asking the user to remove the boot media.
608    
609     showmounts::
610    
611     This parameter will make live-initramfs to show on "/" the ro filesystems
612     (mostly compressed) on "/live". This is not enabled by default because could
613     lead to problems by applications like "mono" which store binary paths on
614     installation.
615    
616     textonly
617    
618     Start up to text-mode shell prompts, disabling the graphical user interface.
619    
620     timezone=**TIMEZONE**::
621    
622     By default, timezone is set to UTC. Using the timezone parameter, you can set it
623     to your local zone, e.g. Europe/Zurich.
624    
625     todisk=**DEVICE**::
626    
627     Adding this parameter, live-initramfs will try to copy the entire read-only
628     media to the specified device before mounting the root filesystem. It probably
629     needs a lot of free space. Subsequent boots should then skip this step and just
630     specify the "live-media=DEVICE" boot parameter with the same DEVICE used this
631     time.
632    
633     toram::
634    
635     Adding this parameter, live-initramfs will try to copy the whole read-only media
636     to the computer's RAM before mounting the root filesystem. This could need a lot
637     of ram, according to the space used by the read-only media.
638    
639     union=**aufs**|**unionfs**::
640    
641     By default, live-initramfs uses aufs. With this parameter, you can switch to
642     unionfs.
643    
644     utc=**yes**|**no**::
645    
646     By default, Debian systems do assume that the hardware clock is set to UTC. You
647     can change or explicitly set it with this parameter.
648    
649     xdebconf::
650    
651     Uses xdebconfigurator, if present on the rootfs, to configure X instead of the
652     standard procedure (experimental).
653    
654     xvideomode=**RESOLUTION**::
655    
656     Doesn't do xorg autodetection, but enforces a given resolution.
657    
658     Files
659     -----
660    
661     /etc/live.conf
662    
663     Some variables can be configured via this config file (inside the live system).
664    
665     /live/filesystem.module
666    
667     This optional file (inside the live media) contains a list of white-space or
668     carriage-return-separated file names corresponding to disk images in the "/live"
669     directory. If this file exists, only images listed here will be merged into the
670     root aufs, and they will be loaded in the order listed here. The first entry
671     in this file will be the "lowest" point in the aufs, and the last file in
672     this list will be on the "top" of the aufs, directly below /cow. Without
673     this file, any images in the "/live" directory are loaded in alphanumeric order.
674    
675     /etc/live-persistence.binds
676    
677     This optional file (which resides in the rootfs system, not in the live media)
678     is used as a list of directories which not need be persistent: ie. their
679     content does not need to survive reboots when using the persistence features.
680    
681     This saves expensive writes and speeds up operations on volatile data such as
682     web caches and temporary files (like e.g. /tmp and .mozilla) which are
683     regenerated each time. This is achieved by bind mounting each listed directory
684     with a tmpfs on the original path.
685    
686    
687     See also
688     --------
689    
690     live-snapshot(1), initramfs-tools(8), live-helper(7), live-initscripts(7),
691     live-webhelper(7)
692    
693     Bugs
694     ----
695    
696     Report bugs against live-initramfs
697     link:http://packages.qa.debian.org/live-initramfs[http://packages.qa.debian.org/live-initramfs].
698    
699     Homepage
700     --------
701    
702     More information about the Debian Live project can be found at
703     link:http://debian-live.alioth.debian.org/[http://debian-live.alioth.debian.org/] and
704     link:http://wiki.debian.org/DebianLive/[http://wiki.debian.org/DebianLive/].
705    
706     Authors
707     -------
708    
709     live-initramfs is maintained by Daniel Baumann &lt;daniel@debian.org&gt;
710     for the Debian project.
711    
712     live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper].
713     casper was originally written by Tollef Fog Heen &lt;tfheen@canonical.com&gt;
714     and Matt Zimmerman &lt;mdz@canonical.com&gt;.</pre>
715     </div>
716    
717    
718     </div>
719    
720    
721     <!--<a name="template-top"></a>-->
722    
723     <div id="footer">
724     <div id="docline-bottom"> <a href="usb.html">&lt; PREV</a> <a href="doc.html">UP</a> <a href="clonezilla.html">NEXT &gt;</a> </div>
725     <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/>
726     Hosted by <a href="http://www.hellug.gr" target="_blank" title="Hellenic Linux User Group">HEL.L.U.G.</a></p>
727     </div>
728     </div>
729     </body>
730     </html>

Properties

Name Value
svn:executable *

webmaster@linux.gr
ViewVC Help
Powered by ViewVC 1.1.26