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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 37 - (show annotations)
Tue Mar 23 10:28:53 2010 UTC (14 years ago) by sng
File MIME type: text/html
File size: 44190 byte(s)
Changed onepage.php to onepage.html
  2site: adding creation of onepage.html
  .template.html: changed onepage.php to onepage.html
  usb.html: fixing H2 tags
  partitions.html: fixing H2 tags
Site update

H2 tags should always be used without any style modifiers.
Exception: the first H2 tag of the page should have a
[style="margin-top: 0;"] modifier

1 <!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 <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 <H2>Clonezilla-SysRescCD</H2>
79 <H3>Documentation: Boot parameters</H3>
80 <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>
82 <div style="position: absolute; right: 0px;"><H4>Last update: 23/03/2010</H4></div>
83 </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 <p><b>General boot options</b></p>
149
150 <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)
151 </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.
152 </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.
153 </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.
154 </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>.
155 </li></ul>
156
157 <p><b><BR>Hardware, drivers and troubleshooting options</b></p>
158
159 <ul><li><b>nonet</b>: this will disable the network auto detection at startup
160 </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.
161 </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.
162 </li><li><b>nodetect</b>: prevents the generic hardware auto-detection. Use this option if you have problems with the hardware auto-detection.
163 </li><li><b>doload=xxx</b>: forces to load one/several modules at startup (example: <code>doload=3c59x</code>)
164 </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.
165 </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.
166 </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.
167 </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.
168 </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>)
169 </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, ...
170 </li><li><b>dodebug</b>: Enables verbose messages in the linuxrc script.
171 </li><li><b>lowmem</b>: Prevents non critical things to be loaded into memory (like the sshd and nfsd services)
172 </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.
173 </li><li><b>nodmraid</b>: Disable dmraid, which is the program that drives RAID disks based on cheap RAID controller built-in motherboards.
174 </li><li><b>nomdadm</b>: Disable mdadm, which is the program that drives software RAID.
175 </li></ul>
176
177 <p><b><BR>Network auto-configuration and remote access</b></p>
178
179 <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.
180 </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.
181 </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.
182 </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.
183 </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>.
184 </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.
185 </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.
186 </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.
187 </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).
188 </li></ul>
189
190 <p><b><BR>Options provided by the autorun</b></p>
191
192 <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>).
193 </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.
194 </li><li><b>ar_ignorefail</b>: continue to execute the scripts chain even if a script failed (returned a non-zero status)
195 </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
196 </li><li><b>ar_disable</b>: completely disable autorun, the simple <code>autorun</code> script will not be executed
197 </li><li><b>ar_nowait</b>: do not wait for a keypress after the autorun script have been executed.
198 </li></ul>
199 </div>
200
201
202 <!-- Clonezilla -->
203 <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>
204 <!-- note -->
205 <div align="center"><table class="note" border="0" cellpadding="20"><tr valign="top"><td><img src="images/info.png"></td><td>
206 The following info applies to <b>Clonezilla Live v. 1.2.3-27</b><br>
207 In case you need to get info for a more recent version of <b>Clonezilla Live</b><br>
208 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>"
209 </td></tr></table></div>
210
211 <p>A typical Clonezilla Live isolinux entry is:</p>
212
213 <p class="newcode"> kernel /live/vmlinuz1<br>
214 append initrd=/live/initrd1.img boot=live union=aufs ocs_live_run="ocs-live-general"<br>
215 ocs_live_extra_param="" ocs_live_keymap="" ocs_live_batch="no" ocs_lang="" vga=791 nolocales</p>
216 <!--empty-line-->
217 <p>The kernel used is <b>vmlinuz</b>, and anything after the word <b>append</b> is a boot parameter.</p>
218 <!--empty-line-->
219
220
221 <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>
222
223 <!-- Start of copy/paste 3 -->
224 <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:
225 <ol>
226 <li>Boot parameters from live-initramfs. You can refer to this <a href="#live-initramfs">manual of live-initramfs</a>.
227 <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.
228 <ul>
229 <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>
230 e.g. ocs_live_run="ocs-live-general"
231 <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>
232 e.g. ocs_live_extra_param="-b -c restoredisk sarge-r5 hda"
233 <li>ocs_live_keymap is for keymap used in Clonezilla live. Man install-keymap for more details.<br>
234 e.g. ocs_live_keymap="NONE" (won't change the default layout)<br>
235 ocs_live_keymap="/usr/share/keymaps/i386/azerty/fr-latin9.kmap.gz" (French keyboard)
236 <li>batch mode or not (yes/no), if no, will run interactively.<br>
237 e.g. ocs_live_batch="no"
238 <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/)
239 e.g. ocs_lang="en_US.UTF-8"
240 <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.
241 <li>ocs_daemonon, ocs_daemonoff, ocs_numlk, ocs_capslk.<br>
242 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.
243 <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.
244 <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.
245 <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.
246 </ul>
247 </ol>
248 <hr>
249
250 With the above options, we have the following examples:
251 <ol>
252 <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>
253 ----------------------------------------<br>
254 label Clonezilla Live<br>
255 MENU LABEL Clonezilla Live<br>
256 MENU DEFAULT<br>
257 kernel vmlinuz1<br>
258 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>
259 ----------------------------------------<br>
260
261 The usercrypted password is created by:<br>
262 echo YOUR_PASSWORD | mkpasswd -s<br>
263 ("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>
264 //NOTE// If you do not assign salt to mkpasswd, the encrypted password will not be the same every time you create it.<br>
265 For more about usercrypted discussion, please check the <a href="http://lists.debian.org/debian-live/2008/10/msg00020.html" target=_blank>here</a>.
266 <br><br>
267 <li>How to put your own binary driver in Clonezilla live without modifying /live/filesystem.squashfs:
268 <ul>
269 <li>Boot clonezilla live
270 <li>Become root by running "sudo su -"
271 <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>
272 cp -r /live/image/lsi /home/partimag
273 <li>cd /home/partimag
274 <li>/opt/drbl/sbin/ocs-live-dev -c -s -i lsi -u lsi -x "ocs_prerun=/live/image/lsi/prep-lsi.sh"
275 <li>/opt/drbl/sbin/ocs-iso -s -i lsi -u lsi -x "ocs_prerun=/live/image/lsi/prep-lsi.sh"
276 <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:
277 <pre>
278 ------------------------
279 #!/bin/bash
280 cp -f /live/image/lsi/megasr.ko /lib/modules/`uname -r`/kernel/drivers/block/
281 chown root.root /lib/modules/`uname -r`/kernel/drivers/block/megasr.ko
282 depmod -a modprobe megasr
283 sleep 1
284 ------------------------
285 </pre>
286 </ul>
287
288 <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>
289 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>
290 Therefor your pxelinux.cfg/default file is like:
291 <p>------------------------<br>
292 label Clonezilla Live<br>
293 MENU DEFAULT<br>
294 # MENU HIDE<br>
295 MENU LABEL Clonezilla Live<br>
296 # MENU PASSWD<br>
297 kernel vmlinuz1<br>
298 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>
299 TEXT HELP<br>
300 Boot Clonezilla live via network<br>
301 ENDTEXT<br>
302 <p>------------------------<br>
303 The content of custom-ocs-2 can be like:
304 <pre>
305 ------------------------
306 #!/bin/bash
307 . /opt/drbl/sbin/drbl-conf-functions
308 . /opt/drbl/sbin/ocs-functions
309 . /etc/ocs/ocs-live.conf
310
311 # Load language file
312 ask_and_load_lang_set en_US.UTF-8
313
314 # 1. Mount the clonezilla image home.
315 # Types: local_dev, ssh_server, samba_server, nfs_server
316 prep-ocsroot -t nfs_server
317
318 # 2. Restore the image
319 if mountpoint /home/partimag/ &>/dev/null; then
320 ocs-sr -l en_US.UTF-8 -c -p choose restoredisk ask_user ask_user
321 else
322 [ "$BOOTUP" = "color" ] && $SETCOLOR_FAILURE
323 echo "Fail to find the Clonezilla image home /home/partimag!"
324 echo "Program terminated!"
325 [ "$BOOTUP" = "color" ] && $SETCOLOR_NORMAL
326 fi
327 ------------------------
328 </pre>
329 </li>
330 </ol>
331 </div>
332 <!-- End of copy/paste 3 -->
333
334 <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>
335
336 <p>This is the manual of <a href="http://www.clonezilla.org/clonezilla-live/live-initramfs-param.php" target=_blank>live-initramfs</a>
337 <BR>
338 </p>
339
340 <div class="otherpage"><pre>
341 live-initramfs(7)
342 =================
343
344 Name
345 ----
346 live-initramfs - Debian Live initramfs hook
347
348 Synopsis
349 --------
350 BOOT=live
351
352 as kernel parameter at boot prompt.
353
354 Description
355 -----------
356
357 live-initramfs is a hook for the initramfs-tools, used to generate a initramfs
358 capable to boot live systems, such as those created by *live-helper*(7).
359 This includes the Debian Live isos, netboot tarballs, and usb stick images.
360
361 At boot time it will look for a (read-only) media containing a "/live"
362 directory where a root filesystems (often a compressed filesystem image like
363 squashfs) is stored. If found, it will create a writable environment, using
364 aufs, for Debian like systems to boot from.
365
366 You probably do not want to install this package onto a non-live system,
367 although it will do no harm.
368
369 live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper].
370 casper was originally written by Tollef Fog Heen &lt;tfheen@canonical.com&gt;
371 and Matt Zimmerman &lt;mdz@canonical.com&gt;.
372
373 Boot options
374 ------------
375
376 Here is the complete list of recognized boot parameters by live-initramfs.
377
378 access=*ACCESS*::
379
380 Set the accessibility level for physically or visually impared users. ACCESS
381 must be one of v1, v2, v3, m1, or m2. v1=lesser visual impairment, v2=moderate
382 visual impairment, v3=blindness, m1=minor motor difficulties, m2=moderate motor
383 difficulties.
384
385 console=*TTY,SPEED*::
386
387 Set the default console to be used with the "live-getty" option. Example:
388 "console=ttyS0,115200"
389
390 debug::
391
392 Makes initramfs boot process more verbose.
393
394 fetch=*URL*::
395
396 Another form of netboot by downloading a squashfs image from a given url,
397 copying to ram and booting it.
398
399 hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*::
400
401 Those parameters lets you override values read from the config file.
402
403 ignore_uuid
404
405 Do not check that any UUID embedded in the initramfs matches the discovered
406 medium. live-initramfs may be told to generate a UUID by setting
407 LIVE_GENERATE_UUID=1 when building the initramfs.
408
409 integrity-check::
410
411 If specified, an MD5 sum is calculated on the live media during boot and
412 compared to the value found in md5sum.txt found in the root directory of the
413 live media.
414
415 ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]
416 [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]]***::
417
418 Let you specify the name(s) and the options of the interface(s) that should be
419 configured at boot time. Do not specify this if you want to use dhcp (default).
420 It will be changed in a future release to mimick official kernel boot param
421 specification (e.g. ip=10.0.0.1::10.0.0.254:255.255.255.0::eth0,:::::eth1:dhcp).
422
423 ip[=**frommedia**]::
424
425 If this variable is set, dhcp and static configuration are just skipped and the
426 system will use the (must be) media-preconfigured /etc/network/interfaces
427 instead.
428
429 {keyb|kbd-chooser/method}=**KEYBOARD**, {klayout|console-setup/layoutcode}=**LAYOUT**,
430 {kvariant|console-setup/variantcode}=**VARIANT**,
431 {kmodel|console-setup/modelcode}=**CODE**, koptions=**OPTIONS**::
432
433 Configure the running keyboard as specified, if this one misses live-initramfs
434 behaves as if "keyb=us" was specified. It will be interfered from "locale=" if
435 locale is only 2 lowecase letters as a special case. You could also specify
436 console layout, variant, code, and options (no defaults).
437
438 live-getty::
439
440 This changes the auto-login on virtual terminals to use the (experimental)
441 live-getty code. With this option set the standard kernel argument "console=" is
442 parsed and if a serial console is specified then live-getty is used to autologin
443 on the serial console.
444
445 {live-media|bootfrom}=**DEVICE**::
446
447 If you specify one of this two equivalent forms, live-initramfs will first try
448 to find this device for the "/live" directory where the read-only root
449 filesystem should reside. If it did not find something usable, the normal scan
450 for block devices is performed.
451
452 {live-media-encryption|encryption}=**TYPE**::
453
454 live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase,
455 useful to build paranoid live systems :-). TYPE supported so far are "aes" for
456 loop-aes encryption type.
457
458 live-media-offset=**BYTES**::
459
460 This way you could tell live-initramfs that your image starts at offset BYTES in
461 the above specified or autodiscovered device, this could be useful to hide the
462 Debian Live iso or image inside another iso or image, to create "clean" images.
463
464 live-media-path=**PATH**::
465
466 Sets the path to the live filesystem on the medium. By default, it is set to
467 '/live' and you should not change that unless you have customized your media
468 accordingly.
469
470 live-media-timeout=**SECONDS**::
471
472 Set the timeout in seconds for the device specified by "live-media=" to become
473 ready before giving up.
474
475 {locale|debian-installer/locale}=**LOCALE**::
476
477 Configure the running locale as specified, if not present the live-media rootfs
478 configured locale will be used and if also this one misses live-initramfs behave
479 as "locale=en_US.UTF-8" was specified. If only 2 lowercase letter are specified
480 (like "it"), the "maybe wanted" locale is generated (like en:EN.UTF-8), in this
481 case if also "keyb=" is unspecified is set with those 2 lowercase letters
482 (keyb=us). Beside that facility, only UTF8 locales are supported by
483 live-initramfs.
484
485 module=**NAME**::
486
487 Instead of using the default optional file "filesystem.module" (see below)
488 another file could be specified without the extension ".module"; it should be
489 placed on "/live" directory of the live medium.
490
491 netboot[=**nfs**|**cifs**]::
492
493 This tells live-initramfs to perform a network mount. The parameter "nfsroot="
494 (with optional "nfsopts="), should specify where is the location of the root
495 filesystem. With no args, will try cifs first, and if it fails nfs.
496
497 nfsopts=::
498
499 This lets you specify custom nfs options.
500
501 noautologin::
502
503 This parameter disables the automatic terminal login only, not touching gdk/kdm.
504
505 noxautologin::
506
507 This parameter disables the automatic login of gdm/kdm only, not touching
508 terminals.
509
510 nofastboot::
511
512 This parameter disables the default disabling of filesystem checks in
513 /etc/fstab. If you have static filesystems on your harddisk and you want them to
514 be checked at boot time, use this parameter, otherwise they are skipped.
515
516 nopersistent::
517
518 disables the "persistent" feature, useful if the bootloader (like syslinux) has
519 been installed with persistent enabled.
520
521 noprompt
522
523 Do not prompt to eject the CD on reboot.
524
525 nosudo::
526
527 This parameter disables the automatic configuration of sudo.
528
529 swapon::
530
531 This parameter enables usage of local swap partitions.
532
533 nouser::
534
535 This parameter disables the creation of the default user completely.
536
537 noxautoconfig::
538
539 This parameter disables Xorg auto-reconfiguration at boot time. This is valuable
540 if you either do the detection on your own, or, if you want to ship a custom,
541 premade xorg.conf in your live system.
542
543 persistent[=nofiles]::
544
545 live-initramfs will look for persistent and snapshot partitions or files labeled
546 "live-rw", "home-rw", and files called "live-sn*", "home-sn*" and will try to,
547 in order: mount as /cow the first, mount the second in /home, and just copy the
548 contents of the latter in appropriate locations (snapshots). Snapshots will be
549 tried to be updated on reboot/shutdown. Look at live-snapshot(1) for more
550 informations. If "nofiles" is specified, only filesystems with matching labels
551 will be searched; no filesystems will be traversed looking for archives or image
552 files. This results in shorter boot times.
553
554 {preseed/file|file}=**FILE**::
555
556 A path to a file present on the rootfs could be used to preseed debconf
557 database.
558
559 package/question=**VALUE**::
560
561 All debian installed packages could be preseeded from command-line that way,
562 beware of blanks spaces, they will interfere with parsing, use a preseed file in
563 this case.
564
565 quickreboot::
566
567 This option causes live-initramfs to reboot without attempting to eject the
568 media and without asking the user to remove the boot media.
569
570 showmounts::
571
572 This parameter will make live-initramfs to show on "/" the ro filesystems
573 (mostly compressed) on "/live". This is not enabled by default because could
574 lead to problems by applications like "mono" which store binary paths on
575 installation.
576
577 textonly
578
579 Start up to text-mode shell prompts, disabling the graphical user interface.
580
581 timezone=**TIMEZONE**::
582
583 By default, timezone is set to UTC. Using the timezone parameter, you can set it
584 to your local zone, e.g. Europe/Zurich.
585
586 todisk=**DEVICE**::
587
588 Adding this parameter, live-initramfs will try to copy the entire read-only
589 media to the specified device before mounting the root filesystem. It probably
590 needs a lot of free space. Subsequent boots should then skip this step and just
591 specify the "live-media=DEVICE" boot parameter with the same DEVICE used this
592 time.
593
594 toram::
595
596 Adding this parameter, live-initramfs will try to copy the whole read-only media
597 to the computer's RAM before mounting the root filesystem. This could need a lot
598 of ram, according to the space used by the read-only media.
599
600 union=**aufs**|**unionfs**::
601
602 By default, live-initramfs uses aufs. With this parameter, you can switch to
603 unionfs.
604
605 utc=**yes**|**no**::
606
607 By default, Debian systems do assume that the hardware clock is set to UTC. You
608 can change or explicitly set it with this parameter.
609
610 xdebconf::
611
612 Uses xdebconfigurator, if present on the rootfs, to configure X instead of the
613 standard procedure (experimental).
614
615 xvideomode=**RESOLUTION**::
616
617 Doesn't do xorg autodetection, but enforces a given resolution.
618
619 Files
620 -----
621
622 /etc/live.conf
623
624 Some variables can be configured via this config file (inside the live system).
625
626 /live/filesystem.module
627
628 This optional file (inside the live media) contains a list of white-space or
629 carriage-return-separated file names corresponding to disk images in the "/live"
630 directory. If this file exists, only images listed here will be merged into the
631 root aufs, and they will be loaded in the order listed here. The first entry
632 in this file will be the "lowest" point in the aufs, and the last file in
633 this list will be on the "top" of the aufs, directly below /cow. Without
634 this file, any images in the "/live" directory are loaded in alphanumeric order.
635
636 /etc/live-persistence.binds
637
638 This optional file (which resides in the rootfs system, not in the live media)
639 is used as a list of directories which not need be persistent: ie. their
640 content does not need to survive reboots when using the persistence features.
641
642 This saves expensive writes and speeds up operations on volatile data such as
643 web caches and temporary files (like e.g. /tmp and .mozilla) which are
644 regenerated each time. This is achieved by bind mounting each listed directory
645 with a tmpfs on the original path.
646
647
648 See also
649 --------
650
651 live-snapshot(1), initramfs-tools(8), live-helper(7), live-initscripts(7),
652 live-webhelper(7)
653
654 Bugs
655 ----
656
657 Report bugs against live-initramfs
658 link:http://packages.qa.debian.org/live-initramfs[http://packages.qa.debian.org/live-initramfs].
659
660 Homepage
661 --------
662
663 More information about the Debian Live project can be found at
664 link:http://debian-live.alioth.debian.org/[http://debian-live.alioth.debian.org/] and
665 link:http://wiki.debian.org/DebianLive/[http://wiki.debian.org/DebianLive/].
666
667 Authors
668 -------
669
670 live-initramfs is maintained by Daniel Baumann &lt;daniel@debian.org&gt;
671 for the Debian project.
672
673 live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper].
674 casper was originally written by Tollef Fog Heen &lt;tfheen@canonical.com&gt;
675 and Matt Zimmerman &lt;mdz@canonical.com&gt;.</pre>
676 </div>
677
678
679 </div>
680
681
682 <!--<a name="template-top"></a>-->
683
684 <div id="footer">
685 <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>
686 <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/>
687 Hosted by <a href="http://www.hellug.gr" target="_blank" title="Hellenic Linux User Group">HEL.L.U.G.</a></p>
688 </div>
689 </div>
690 </body>
691 </html>

Properties

Name Value
svn:executable *

webmaster@linux.gr
ViewVC Help
Powered by ViewVC 1.1.26