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

Diff of /trunk/www/onepage.html

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

revision 38 by sng, Fri Mar 26 15:21:13 2010 UTC revision 71 by sng, Mon May 31 19:25:49 2010 UTC
# Line 72  Line 72 
72  <H2>Clonezilla-SysRescCD</H2>  <H2>Clonezilla-SysRescCD</H2>
73  <H3>Wellcome</H3>  <H3>Wellcome</H3>
74    <div style="margin:0; padding: 3px; width: 980; position relative;">    <div style="margin:0; padding: 3px; width: 980; position relative;">
75      <div style="position: absolute; left: 0px;"><H4>26/03/2010 - v 3.1.0</H4></div>      <div style="position: absolute; left: 0px;"><H4>25/05/2010 - v 3.1.0</H4></div>
76      <div style="position: absolute; right: 0px;"><H4>Last update: 26/03/2010</H4></div>      <div style="position: absolute; right: 0px;"><H4>Last update: 31/05/2010</H4></div>
77    </div>    </div>
78  </div>  </div>
79  <div id="linkline">  <div id="linkline">
# Line 131  Well, I started this project because I w Line 131  Well, I started this project because I w
131  <tr><td class="bordertable"  colspan="4"><b>Release table</b></td></tr>  <tr><td class="bordertable"  colspan="4"><b>Release table</b></td></tr>
132  <tr><td class="bordertable"  valign="top"><b>Date</b></td><td class="bordertable"  valign="top"><b>Version</b></td>  <tr><td class="bordertable"  valign="top"><b>Date</b></td><td class="bordertable"  valign="top"><b>Version</b></td>
133  <td class="bordertable"  valign="top"><b>Clonezilla Live Version</b></td><td class="bordertable"  valign="top"><b>SystemRescueCD Version</b></td></tr>  <td class="bordertable"  valign="top"><b>Clonezilla Live Version</b></td><td class="bordertable"  valign="top"><b>SystemRescueCD Version</b></td></tr>
134  <tr><td  class="bordertable" >25/02/10</td><td  class="bordertable" >3.1.0</td><td  class="bordertable" >1.2.3-27&nbsp;(mod)</td><td  class="bordertable" >1.4.0&nbsp;(mod)</td>  <tr><td  class="bordertable" >25/05/10</td><td  class="bordertable" >3.1.0</td><td  class="bordertable" >1.2.5-17&nbsp;(mod)</td><td  class="bordertable" >1.5.4&nbsp;(mod)</td>
135  </tr>  </tr>
136  <tr><td  class="bordertable" >02/07/08</td><td  class="bordertable" >2.6.0</td><td  class="bordertable" >1.1.0-8&nbsp;(mod)</td><td  class="bordertable" >1.0.4&nbsp;(mod)</td>  <tr><td  class="bordertable" >02/07/08</td><td  class="bordertable" >2.6.0</td><td  class="bordertable" >1.1.0-8&nbsp;(mod)</td><td  class="bordertable" >1.0.4&nbsp;(mod)</td>
137  </tr>  </tr>
# Line 162  Well, I started this project because I w Line 162  Well, I started this project because I w
162  <table class="bordertable"  cellpadding="5">  <table class="bordertable"  cellpadding="5">
163  <tr><td class="bordertable" width="10"><b>Version</b></td><td  class="bordertable" width="10"><b>Package/CD</b></td><td class="bordertable"><b>Comments</b></td></tr>  <tr><td class="bordertable" width="10"><b>Version</b></td><td  class="bordertable" width="10"><b>Package/CD</b></td><td class="bordertable"><b>Comments</b></td></tr>
164  <tr><td class="bordertable" width="10" valign="top"><a name="3.1.0"></a>3.1.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">  <tr><td class="bordertable" width="10" valign="top"><a name="3.1.0"></a>3.1.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">
165  -&nbsp;<b>Clonezilla Live</b> updated to version 1.2.4-28-686<br>  -&nbsp;<b>Clonezilla Live</b> updated to version 1.2.5-17-686<br>
166  -&nbsp;<b>SystemRescueCD</b> updated to version 1.4.0<br>  -&nbsp;<b>SystemRescueCD</b> updated to version 1.5.3<br>
167  -&nbsp;<b>Super Grub Disk</b> updated to version 0.9799<br>  -&nbsp;<b>Super Grub Disk</b> updated to version 0.9799<br>
168  -&nbsp;Added <b>Super Grub Disk 2</b> version 1.30<br>  -&nbsp;Added <b>Super Grub Disk 2</b> version 1.30<br>
169  -&nbsp;Most operations are now executed through the TUI (Text User Interface)<br>  -&nbsp;Most operations are now executed through the TUI (Text User Interface)<br>
# Line 300  More info: <a href="reloc-img.html">Rest Line 300  More info: <a href="reloc-img.html">Rest
300  </table>  </table>
301  <H2><a name="download"></a>Download <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="download"></a>Download <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>
302  <p>  <p>
303  Installation package: <a href="http://clonezilla-sysresccd.hellug.gr/create-clonezilla-sysresccd-3.1.0".tar.gz" target="_blank">create-clonezilla-sysresccd-3.1.0.tar.gz</a> [~ 1.7 MB]<br>  Installation package: <a href="http://clonezilla-sysresccd.hellug.gr/create-clonezilla-sysresccd-3.1.0".tar.gz" target="_blank">create-clonezilla-sysresccd-3.1.0.tar.gz</a> [~ B]<br>
304  ISO file: <a href="http://clonezilla-sysresccd.hellug.gr/clonezilla-sysresccd-full-mod-3.1.0.iso" target="_blank">clonezilla-sysresccd-full-mod-3.1.0.iso</a> [~ 366 MB]<br>  ISO file: <a href="http://clonezilla-sysresccd.hellug.gr/clonezilla-sysresccd-full-mod-3.1.0.iso" target="_blank">clonezilla-sysresccd-full-mod-3.1.0.iso</a> [~ B]<br>
305  md5sum file: <a href="http://clonezilla-sysresccd.hellug.gr/md5sum.txt" target="_blank">md5sum.txt</a><br><br>  md5sum file: <a href="http://clonezilla-sysresccd.hellug.gr/md5sum.txt" target="_blank">md5sum.txt</a><br><br>
306  ISO file md5sum: <b><i></i></b></p>  ISO file md5sum: <b><i></i></b></p>
307  <H2><a name="user-help"></a>Can I help? <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="user-help"></a>Can I help? <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>
# Line 526  While in the splash screen of <b>Clonezi Line 526  While in the splash screen of <b>Clonezi
526  </p>  </p>
527  <H2><a name="sysresccd"></a>SystemRescueCD boot parameters <span class="hideprint">[<a href="#boot-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="sysresccd"></a>SystemRescueCD boot parameters <span class="hideprint">[<a href="#boot-top" title="go to top of the page">^</a>]</span></H2>
528  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>
529  The following info applies to <b>SystemRescueCD v. 1.3.5</b>. In case<br>  The following info applies to <b>SystemRescueCD v. 1.5.4</b>. In case<br>
530   you need to get info for a more recent version of <b>SystemRescueCD</b><br>   you need to get info for a more recent version of <b>SystemRescueCD</b><br>
531  please see the page "<a href="http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM" target="_blank">Sysresccd-manual-en Booting the CD-ROM</a>"  please see the page "<a href="http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM" target="_blank">Sysresccd-manual-en Booting the CD-ROM</a>"
532  </td></tr></table></div>  </td></tr></table></div>
# Line 536  append initrd=initram.igz video=ofonly</ Line 536  append initrd=initram.igz video=ofonly</
536  <p>The kernel used is <b>rescuecd</b>, and anything after the word <b>append</b> is a boot parameter.<br><br>  <p>The kernel used is <b>rescuecd</b>, and anything after the word <b>append</b> is a boot parameter.<br><br>
537  Available kernels (boot images):</p>  Available kernels (boot images):</p>
538  <ul class="otherpage" style="padding: 0px 10px 20px 40px">  <ul class="otherpage" style="padding: 0px 10px 20px 40px">
539  <li><b>rescuecd</b> This is the default choice for 32bits systems, with Framebuffer disabled, best choice.</li>  <li><b>rescuecd</b> Default for 32bit systems, with Framebuffer disabled, best choice.
540  <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>  </li><li><b>rescue64</b> Default 64 bit kernel. Use it if you want to chroot to a 64bit linux system installed on your hard disk, or if you have to run 64 bits programs. This kernel is able to boot with 32bit programs, and it requires a processor with 64bit instructions (amd64 / em64t).
541  <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>  </li><li><b>altker32</b> an alternative kernel for 32bit systems. Boot with this kernel if you have problems with <b>rescuecd</b>
542  <li><b>altker64</b> This is an alternative kernel for 64bits systems. Boot with this kernel in case you have problems with rescue64. Only available from SystemRescueCd-1.0.0 and newer.</li>  </li><li><b>altker64</b> an alternative kernel for 64bit systems. Boot with this kernel in case you have problems with <b>rescue64</b>.
543    </li>
544  </ul>  </ul>
545  <p><br>The boot parameters you can use are:</p>  <p><br>The boot parameters you can use are:</p>
546  <div class="otherpage">  <div class="otherpage">
547  <p><b>General boot options</b></p>  <a name="General_boot_options" id="General_boot_options"></a><p><b> General boot options</b></p>
548  <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)  <p>Press &lt;TAB&gt; to add additional options.
549  </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.  </p>
550  </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.  <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.
551  </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.  </li></ul>
552  </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>.  <p>During boot you will be prompted for the keyboard configuration, avoid this by using
553    </p>
554    <ul><li><b>setkmap=kk</b>:  which defines the keymap to load  where <code>kk</code>  (example: <code>setkmap=de</code> for German keyboards)
555    </li><li><b>root=/dev/xdnp</b>: the <a target="_blank" href="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" class="external text" title="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" rel="nofollow">root=&lt;device&gt; option</a>  boots an existing linux system. For example, if you have linux Gentoo installed on <code>/dev/sda6</code>,  use <code>rescuecd root=/dev/sda6</code> to start it. Keep in mind that you must use a 64bit kernel if your system is made of 64bit programs. This option works with LVM volumes. Use <code>rescuecd root=/dev/VolGroup00/LogVol00</code>. Support is also provided for <code>root=auto</code>, which scans all the block devices tfor a linux system. The first linux system found will be started. So with <code>root=auto</code> let you start the system installed from the CD-ROM in case you have problem with your boot loader or kernel. It's also possible to specify a partition using its <code>filesystem label</code> or <code>filesystem uuid</code>. If the label of the partition where linux is installed is <code>mylinux</code>, then boot it using <code>rescuecd root=LABEL=mylinux</code>. Similarly <code>root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7</code>. See <a target="_blank" href="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" class="external text" title="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" rel="nofollow">more details</a>.
556    </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.
557    </li><li><b>backstore=xxx</b>: SystemRescueCd comes with support for the <a target="_blank" href="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" class="external text" title="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" rel="nofollow">backing-stores</a>. A backing-store  saves all the changes you can make. so that you keep these changes the next time you boot it. By default, sysresccd automatically scan removable devices (eg: USB sticks) at boot time and uses the first backing-store it finds. A backing-store is not mandatory and it the scan fails it will store the files which change in memory. To disable the disks scan at boot time specify <code>backstore=off</code> on the boot command line. If you want to save your backing-store file on an harddisk,  boot with <code>backstore=alldev</code> to scan all devices (not just removable devices). The default location for backing-stores file is any file named <code>sysrcd.bs</code> located at the root of a disk which is often an USB stick. Change the path by using  <code>backstore=/sysrcd/mybackstore.bs</code>. See <a target="_blank" href="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" class="external text" title="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" rel="nofollow">backing-stores</a>.
558    </li><li><b>isoloop=xxx</b>: Grub2 (currently in development: grub-1.98) provides a new feature to boot from an ISO image which is stored from the hard disk. If you put a copy of <code>systemrescuecd-x86-x.y.z.iso</code> on a partition that Grub2 can read then you can boot SystemRescueCd directly from the ISO image stored on your hard drive. This is very convenient if you frequently update SystemRescueCd and you want to boot it directly from Grub2. Grub2 knows what an ISO image is and it will load the kernel image (rescuecd/rescue64) and the initramfs (initram.igz) from the ISO into memory. It will then do its normal job and execute the kernel. The SystemRescueCd init script must then be aware that its <code>sysrcd.dat</code> file is in an ISO and not directly on the partition. For that reason, this <code>isoloop=xxx</code> boot option is required so you must use it in your <code>grub.cfg</code>. This option is only supported in SystemRescueCd-1.4.0 and more recent. This option specifies the path of the ISO image in the partition that grub considers as its root partition. It's important to understand that the path of the ISO image may be different from the path on your linux system. If you have a separate boot partition mounted on <code>/boot</code> and if you copy this ISO image to <code>/boot/sysrcd/systemrescuecd-x86-x.y.z.iso</code> then the option has to be <code>isoloop=/sysrcd/systemrescuecd-x86-x.y.z.iso</code>. This is because the boot partition is what Grub2 will consider as its root partition during the boot process. Please read <a target="_blank" href="http://www.sysresccd.org/Sysresccd-manual-en_Easy_install_SystemRescueCd_on_harddisk#Boot_the_ISO_image_from_the_disk_using_Grub2" title="Sysresccd-manual-en Easy install SystemRescueCd on harddisk">the section about isoloop</a> for more details.
559    </li></ul>
560    <a name="Hardware.2C_drivers_and_troubleshooting_options" id="Hardware.2C_drivers_and_troubleshooting_options"></a><p><b><br> Hardware, drivers and troubleshooting options</b></p>
561    <ul><li><b>dodebug</b>: Enables verbose messages in linuxrc
562    </li></ul>
563    <ul><li><b>doload=xxx</b>: loads needed modules, multiple occurrences are permitted (example: <code>doload=3c59x</code>)
564    </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.
565    </li><li><b>nonet</b>: this will disable the network auto detection at startup
566    </li></ul>
567    <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.
568  </li></ul>  </li></ul>
569  <p><b><BR>Hardware, drivers and troubleshooting options</b></p>  <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.
570  <ul><li><b>nonet</b>: this will disable the network auto detection at startup  </li><li><b>nodetect</b>: prevents generic hardware auto-detection. Use this option if you have problems with the hardware auto-detection.
 </li><li><b>scandelay=x</b>: pauses x seconds during the startup to allow slow devices to initialize. This is required when you boot an usb device. A delay of only few seconds should be enough.  
 </li><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.  
 </li><li><b>nodetect</b>: prevents the generic hardware auto-detection. Use this option if you have problems with the hardware auto-detection.  
 </li><li><b>doload=xxx</b>: forces to load one/several modules at startup (example: <code>doload=3c59x</code>)  
 </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.  
 </li><li><b>dostartx</b>: This option will force the system to load the X.Org graphical environment at boot time. You won't have to type <code>startx</code> by hand to get it.  
 </li><li><b>forcevesa</b>: Forces X.Org to work with the safe vesa driver instead of the best video driver detected for your video card. Use this option if you cannot get the graphical environment working with the default options.  
 </li><li><b>forcevesa=xxx</b>: The <code>startx</code> command will load the <code>Xvesa</code> server instead of <code>Xorg</code>, and Xvesa will use the screen resolution given as parameter (eg: <code>1024x768</code>, <code>1280x1024x32</code>). The <code>forcevesa</code> option can take a parameter from SystemRescueCd-1.0.0 and more recent.  
 </li><li><b>all-generic-ide</b>: In case of problems related to your hard disk, try to enable this option (eg <code>rescuecd all-generic-ide</code>)  
 </li><li><b>acpi-off</b> / <b>noapic</b> / <b>irqpool</b>: use these options if you have any problem when the kernel boots: if it hangs on a driver or if it crashes, ...  
 </li><li><b>dodebug</b>: Enables verbose messages in the linuxrc script.  
 </li><li><b>lowmem</b>: Prevents non critical things to be loaded into memory (like the sshd and nfsd services)  
 </li><li><b>skipmount=/dev/xxx</b>: The system mounts all the storage devices at boot time to find the sysrcd.dat file. You may not want it to mount a device, for instance if your hard disk is broken because it would crash the system. You can just boot with <code>skipmount=/dev/sda1 skipmount=/dev/sda2</code> if you want SystemRescueCd to ignore these two partitions. This boot option requires SystemRescueCd-1.0.1 or more recent.  
 </li><li><b>nodmraid</b>: Disable dmraid, which is the program that drives RAID disks based on cheap RAID controller built-in motherboards.  
 </li><li><b>nomdadm</b>: Disable mdadm, which is the program that drives software RAID.  
571  </li></ul>  </li></ul>
572  <p><b><BR>Network auto-configuration and remote access</b></p>  <ul><li><b>dostartx</b>:   load the X.Org graphical environment.
573  <ul><li><b>dodhcp</b>: Use <code>dodhcp</code> if you have a DHCP server on your network and you want the system to get a dynamic IP address at boot time.  </li><li><b>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.
574  </li><li><b>ethx=ipaddr/cidr</b>: Sets the static IP address of all the ethernet interfaces found on the system. The <code>/cidr</code> extension is optional. For instance, if you use option <code>ethx=192.168.0.1</code> on a machine with two ethernet adapters, both <code>eth0</code> and <code>eth1</code> will be configured with <code>192.168.0.1</code>. You can also write something like <code>ethx=10.0.0.1/24</code> (using the cidr notation) if you don't use the default netmask.  </li><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>).
575  </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.  </li></ul>
576    <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>)
577    </li><li><b>nodmraid</b>: Disable dmraid,  for some motherboards with built-in RAID controller.
578    </li><li><b>nomdadm</b>: Disable mdadm,  for software RAID.
579    </li></ul>
580    <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, ...
581    </li></ul>
582    <ul><li><b>lowmem</b>: For systems with smaller memory, some daemons are not started including sshd and nfsd.
583    </li></ul>
584    <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.
585    </li></ul>
586    <a name="Network_configuration_and_remote_access" id="Network_configuration_and_remote_access"></a><p><b><br> Network configuration and remote access</b></p>
587    <ul><li><b>dodhcp</b>:  to request a DHCP server provide network attributes including an IP address, gateway... .  otherwise,
588    </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.
589    </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>.
590  </li><li><b>dns=ipaddr</b>: Sets the static IP address of the DNS nameserver you want to use to resolve the names. For instance <code>dns=192.168.0.254</code> means that you want to use <code>192.168.0.254</code> as the DNS server.  </li><li><b>dns=ipaddr</b>: Sets the static IP address of the DNS nameserver you want to use to resolve the names. For instance <code>dns=192.168.0.254</code> means that you want to use <code>192.168.0.254</code> as the DNS server.
591  </li><li><b>gateway=ipaddr</b>: Sets the static IP address of the default route on your network. For instance <code>gateway=192.168.0.254</code> means that the computer can connect to a computer outside of the local network via <code>192.168.0.254</code>.  </li><li><b>gateway=ipaddr</b>: Sets the static IP address of the default route on your network. For instance <code>gateway=192.168.0.254</code> means that the computer can connect to a computer outside of the local network via <code>192.168.0.254</code>.
592  </li><li><b>dhcphostname=myhost</b>: Sets the hostname that the DHCP client will send to the DHCP server. This may be required if the default hostname cannot be used with your DHCP configuration. This option has been introduced in SystemRescueCd-1.3.5.  </li><li><b>dhcphostname=myhost</b>: Sets the hostname that the DHCP client will send to the DHCP server. This may be required if the default hostname cannot be used with your DHCP configuration. This option has been introduced in SystemRescueCd-1.3.5.
593  </li><li><b>rootpass=123456</b>: Sets the root password of the system running on the livecd to <code>1234</code>. That way you can connect from the network and ssh on the livecd and give <code>123456</code> password as the root password.  </li><li><b>rootpass=123456</b>: Sets the root password of the system running on the livecd to <code>1234</code>. That way you can connect from the network and ssh on the livecd and give <code>123456</code> password as the root password.
594  </li><li><b>vncserver=x:123456</b>: The <a href="http://www.sysresccd.org/news/2008/04/12/use-systemrescuecd-remotely-with-vnc-server/" class="external text" title="http://www.sysresccd.org/news/2008/04/12/use-systemrescuecd-remotely-with-vnc-server/" rel="nofollow">vncserver boot option</a> has been introduced in SystemRescueCd-1.0.2. This options forces the system to configure the VNC-server and to start it automatically at boot time. You have to replace <code>x</code> with the number of displays you want, and <code>123456</code> with your password The password must be between 5 and 8 characters, else the boot option will be ignored. In other words the <code>vncserver=2:MyPaSsWd</code> option will give you access to two displays (display=1 on tcp/5901 and display=2 on tcp/5902). Display 0 is reserved for X.Org since SystemRescueCd-1.1.0.  </li><li><b>vncserver=x:123456</b>: The <a target="_blank" href="http://www.sysresccd.org/news/2008/04/12/use-systemrescuecd-remotely-with-vnc-server/" class="external text" title="http://www.sysresccd.org/news/2008/04/12/use-systemrescuecd-remotely-with-vnc-server/" rel="nofollow">vncserver boot option</a> has been introduced in SystemRescueCd-1.0.2. This options forces the system to configure the VNC-server and to start it automatically at boot time. You have to replace <code>x</code> with the number of displays you want, and <code>123456</code> with your password The password must be between 5 and 8 characters, else the boot option will be ignored. In other words the <code>vncserver=2:MyPaSsWd</code> option will give you access to two displays (display=1 on tcp/5901 and display=2 on tcp/5902). Display 0 is reserved for X.Org since SystemRescueCd-1.1.0.
595  </li><li><b>nameif=xxx</b>: You can can <a href="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" class="external text" title="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" rel="nofollow">specify what interface name to give</a> to a particular interface using the mac address. You need SystemRescueCd-1.1.0 or newer to do that. Here is how you can specify which interface is using which mac address on a machine with two network interfaces: <code>nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64</code>. Be careful, you have to respect the separator (comma between the interfaces and exclamation marks between the name and the mac address).  </li><li><b>nameif=xxx</b>: You can can <a target="_blank" href="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" class="external text" title="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" rel="nofollow">specify what interface name to give</a> to a particular interface using the mac address. You need SystemRescueCd-1.1.0 or newer to do that. Here is how you can specify which interface is using which mac address on a machine with two network interfaces: <code>nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64</code>. Be careful, you have to respect the separator (comma between the interfaces and exclamation marks between the name and the mac address).
596    </li></ul>
597    <a name="Network_boot_using_PXE" id="Network_boot_using_PXE"></a><p><b><br> Network boot using PXE</b></p>
598    <p>SystemRescueCd provides several options for booting from the network using PXE.
599    These options can be combined with other network boot options such as <code>ethx</code> (cf previous section). See <a target="_blank" href="http://www.sysresccd.org/Sysresccd-manual-en_PXE_network_booting" class="external text" title="http://www.sysresccd.org/Sysresccd-manual-en_PXE_network_booting" rel="nofollow">PXE network booting</a> to get a global overview of SystemRescueCd and PXE and <a target="_blank" href="http://www.sysresccd.org/Sysresccd-manual-en_Manage_remote_windows_linux_servers_using_SystemRescueCd" class="external text" title="http://www.sysresccd.org/Sysresccd-manual-en_Manage_remote_windows_linux_servers_using_SystemRescueCd" rel="nofollow">Manage remote servers using PXE</a>.
600    </p><p>The second stage downloads the kernel + initramfs using DHCP/TFTP.
601    </p><p>The third stage of the PXE boot process acquires the root files system.
602    </p><p>Several protocols are available.
603    </p>
604    <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.
605    </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.
606    </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.
607    </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.
608  </li></ul>  </li></ul>
609  <p><b><BR>Options provided by the autorun</b></p>  <p>For information on activating <b>speakup</b>, see the <a target="_blank" href="http://www.sysresccd.org/Speakup-info" title="Speakup-info">speakup info page</a>.
610  <ul><li><b>ar_source=xxx</b>: place where the autorun are stored. It may be the root directory of a partition (<code>/dev/sda1</code>), an nfs share (<code>nfs://192.168.1.1:/path/to/scripts</code>), a samba share (<code>smb://192.168.1.1/path/to/scripts</code>), or an http directory (<code><a href="http://192.168.1.1/path/to/scripts" class="external free" title="http://192.168.1.1/path/to/scripts" rel="nofollow">http://192.168.1.1/path/to/scripts</a></code>).  </p>
611  </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.  <a name="Options_provided_for_autorun" id="Options_provided_for_autorun"></a><p><b><br> Options provided for autorun</b></p>
612    <ul><li><b>ar_source=xxx</b>: place where the autorun are stored. It may be the root directory of a partition (<code>/dev/sda1</code>), an nfs share (<code>nfs://192.168.1.1:/path/to/scripts</code>), a samba share (<code>smb://192.168.1.1/path/to/scripts</code>), or an http directory (<code><a target="_blank" href="http://192.168.1.1/path/to/scripts" class="external free" title="http://192.168.1.1/path/to/scripts" rel="nofollow">http://192.168.1.1/path/to/scripts</a></code>).
613    </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.
614  </li><li><b>ar_ignorefail</b>: continue to execute the scripts chain even if a script failed (returned a non-zero status)  </li><li><b>ar_ignorefail</b>: continue to execute the scripts chain even if a script failed (returned a non-zero status)
615  </li><li><b>ar_nodel</b>: do not delete the temporary copy of the autorun scripts located in <code>/var/autorun/tmp</code> after execution  </li><li><b>ar_nodel</b>: do not delete the temporary copy of the autorun scripts located in <code>/var/autorun/tmp</code> after execution
616  </li><li><b>ar_disable</b>: completely disable autorun, the simple <code>autorun</code> script will not be executed  </li><li><b>ar_disable</b>: completely disable autorun, the simple <code>autorun</code> script will not be executed
617  </li><li><b>ar_nowait</b>: do not wait for a keypress after the autorun script have been executed.  </li><li><b>ar_nowait</b>: do not wait for a keypress after the autorun script have been executed.
618  </li></ul>  </li></ul>
619    </p>
620  </div>  </div>
621  <H2><a name="clonezilla"></a>Clonezilla Live boot parameters <span class="hideprint">[<a href="#boot-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="clonezilla"></a>Clonezilla Live boot parameters <span class="hideprint">[<a href="#boot-top" title="go to top of the page">^</a>]</span></H2>
622  <div align="center"><table class="note" border="0" cellpadding="20"><tr valign="top"><td><img src="images/info.png"></td><td>  <div align="center"><table class="note" border="0" cellpadding="20"><tr valign="top"><td><img src="images/info.png"></td><td>
623  The following info applies to <b>Clonezilla Live v. 1.2.3-27</b><br>  The following info applies to <b>Clonezilla Live v. 1.2.5-17</b><br>
624  In case you need to get info for a more recent version of  <b>Clonezilla Live</b><br>  In case you need to get info for a more recent version of  <b>Clonezilla Live</b><br>
625  please see the page "<a href="http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc" target="_blank">The boot parameters for Clonezilla live</a>"  please see the page "<a href="http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc" target="_blank">The boot parameters for Clonezilla live</a>"
626  </td></tr></table></div>  </td></tr></table></div>
# Line 600  please see the page "<a href="http://www Line 630  please see the page "<a href="http://www
630    ocs_live_extra_param="" ocs_live_keymap="" ocs_live_batch="no" ocs_lang="" vga=791 nolocales</p>    ocs_live_extra_param="" ocs_live_keymap="" ocs_live_batch="no" ocs_lang="" vga=791 nolocales</p>
631  <p>The kernel used is <b>vmlinuz</b>, and anything after the word <b>append</b> is a boot parameter.</p>  <p>The kernel used is <b>vmlinuz</b>, and anything after the word <b>append</b> is a boot parameter.</p>
632  <p>The following info comes from the page titled <a href="http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc" target="_blank">The boot parameters for Clonezilla live</a>.</p>  <p>The following info comes from the page titled <a href="http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc" target="_blank">The boot parameters for Clonezilla live</a>.</p>
633  <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:  <div class="otherpage">Clonezilla live is based on <a target="_blank" href="http://wiki.debian.org/DebianLive/" >Debian live</a> with clonezilla installed. Therefore there are 2 kinds of boot parameters:
634  <ol>  <ol>
635  <li>Boot parameters from live-initramfs. You can refer to this <a href="#live-initramfs">manual of live-initramfs</a>.  <li>Boot parameters from live-initramfs. You can refer to this <a href="#live-initramfs">manual of live-initramfs</a>.
636  <li>Boot parameters specially for Clonezilla. All of them are named as "ocs_*", e.g. ocs_live_run, ocs_live_extra_param, ocs_live_batch, ocs_lang.  <li>Boot parameters specially for Clonezilla. All of them are named as "ocs_*", e.g. ocs_live_run, ocs_live_extra_param, ocs_live_batch, ocs_lang.
637    <ul>    <ul>
638    <li>ocs_live_run is the main program to run in Clonezilla live to save or restore. or other command. Available program: ocs-live-general, ocs-live-restore or any command you write. Use the Absolute path in Clonezilla live.<br>    <li>ocs_live_run is the main program to run in Clonezilla live to save or restore. or other command. Available program: ocs-live-general, ocs-live-restore or any command you write. Use the Absolute path in Clonezilla live.<br>
639        e.g. ocs_live_run="ocs-live-general"        e.g. ocs_live_run="ocs-live-general"<br>
640          <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>
641    <li>ocs_live_extra_param will be used only when ocs_live_run=ocs-live-restore (not for ocs-live-general or any other), then it will be passed to ocs-sr. Therefore these parameters are actually those of ocs-sr.<br>    <li>ocs_live_extra_param will be used only when ocs_live_run=ocs-live-restore (not for ocs-live-general or any other), then it will be passed to ocs-sr. Therefore these parameters are actually those of ocs-sr.<br>
642        e.g. ocs_live_extra_param="-b -c restoredisk sarge-r5 hda"        e.g. ocs_live_extra_param="-b -c restoredisk sarge-r5 hda"
643    <li>ocs_live_keymap is for keymap used in Clonezilla live. Man install-keymap for more details.<br>    <li>ocs_live_keymap is for keymap used in Clonezilla live. Man install-keymap for more details.<br>
# Line 620  please see the page "<a href="http://www Line 651  please see the page "<a href="http://www
651    <li>ocs_daemonon, ocs_daemonoff, ocs_numlk, ocs_capslk.<br>    <li>ocs_daemonon, ocs_daemonoff, ocs_numlk, ocs_capslk.<br>
652  Ex. for the first 2 parameters, ocs_daemonon="ssh", then ssh service will be turned on when booting. For the last 2 parameters, use "on" or "off", e.g. ocs_numlk=on to turn on numberlock when booting.  Ex. for the first 2 parameters, ocs_daemonon="ssh", then ssh service will be turned on when booting. For the last 2 parameters, use "on" or "off", e.g. ocs_numlk=on to turn on numberlock when booting.
653    <li>ocs_prerun, ocs_prerun1, ocs_prerun2... is for you to run a shell script before Clonezilla is started. E.g. ocs_prerun="/live/image/myscript.sh". If you have more commands to run, you can assign them in the order: ocs_prerun=..., ocs_prerun1=..., ocs_prerun2=.... If more than 10 parameters, remember to use ocs_prerun01, ocs_prerun02..., ocs_prerun11 to make it in order.    <li>ocs_prerun, ocs_prerun1, ocs_prerun2... is for you to run a shell script before Clonezilla is started. E.g. ocs_prerun="/live/image/myscript.sh". If you have more commands to run, you can assign them in the order: ocs_prerun=..., ocs_prerun1=..., ocs_prerun2=.... If more than 10 parameters, remember to use ocs_prerun01, ocs_prerun02..., ocs_prerun11 to make it in order.
654    <li>ocs_live_run_tty. This option allows you to specify the tty where $ocs_live_run is run. By default $ocs_live_run is run on /dev/tty1 only. (It was also on /dev/ttyS0 before, but since Clonezilla live >= 1.2.3-22 no more this due to a problem). If you want to use ttyS0, for example, add live-getty and console=ttyS0,38400n81 in the boot parameter.    <li>ocs_live_run_tty. This option allows you to specify the tty where $ocs_live_run is run. By default $ocs_live_run is run on /dev/tty1 only. (It was also on /dev/ttyS0 before, but since Clonezilla live >= 1.2.3-22 no more this due to a problem). If you want to use ttyS0, for example, add live-getty and console=ttyS0,38400n81 in the boot parameter.<br>
655      <font color=red>//NOTE//</font><br>
656      <ul>
657      <li>This parameter was added in Clonezilla live 1.2.3-22 or later.
658      <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.
659      <li>It's recommended to assign ocs_lang and ocs_live_keymap in the boot parameters too.
660      </ul>
661      <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>
662    ip=eth0,10.0.100.1,255.255.255.0,10.0.100.254,8.8.8.8<br>
663    If more than one network card, you can use ":" to separate them, e.g.:<br>
664    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>
665    <li>Besides, "live-netdev" (yes, not ocs_live_netdev) can be used when using PXE booting, you can force to assign the network device to get filesystem.squashfs. This is useful when there are two or more NICs are linked. E.g. live-netdev="eth1" allows you to force the live-initramfs to use eth1 to fetch the root file system filesystem.squashfs.    <li>Besides, "live-netdev" (yes, not ocs_live_netdev) can be used when using PXE booting, you can force to assign the network device to get filesystem.squashfs. This is useful when there are two or more NICs are linked. E.g. live-netdev="eth1" allows you to force the live-initramfs to use eth1 to fetch the root file system filesystem.squashfs.
666  </ul>  </ul>
667  </ol>  </ol>
# Line 706  fi Line 747  fi
747  <p>This is the manual of <a href="http://www.clonezilla.org/clonezilla-live/live-initramfs-param.php" target=_blank>live-initramfs</a>  <p>This is the manual of <a href="http://www.clonezilla.org/clonezilla-live/live-initramfs-param.php" target=_blank>live-initramfs</a>
748  <BR>  <BR>
749  </p>  </p>
750  <div class="otherpage"><pre>  <a name="live-initramfs"></a><div class="otherpage" style="overflow: auto;"><pre>
751  live-initramfs(7)  live-initramfs(7)
752  =================  =================
753  Name  Name
# Line 727  squashfs) is stored. If found, it will c Line 768  squashfs) is stored. If found, it will c
768  aufs, for Debian like systems to boot from.  aufs, for Debian like systems to boot from.
769  You probably do not want to install this package onto a non-live system,  You probably do not want to install this package onto a non-live system,
770  although it will do no harm.  although it will do no harm.
771  live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper].  live-initramfs is a fork of <a href="http://packages.ubuntu.com/casper/" target="_blank">casper</a>.
772  casper was originally written by Tollef Fog Heen &lt;tfheen@canonical.com&gt;  casper was originally written by Tollef Fog Heen &amp;lt;tfheen@canonical.com&amp;gt;
773  and Matt Zimmerman &lt;mdz@canonical.com&gt;.  and Matt Zimmerman &amp;lt;mdz@canonical.com&amp;gt;.
774  Boot options  Boot options
775  ------------  ------------
776  Here is the complete list of recognized boot parameters by live-initramfs.  Here is the complete list of recognized boot parameters by live-initramfs.
777   access=*ACCESS*::    access=*ACCESS*::
778  Set the accessibility level for physically or visually impared users. ACCESS  Set the accessibility level for physically or visually impared users. ACCESS
779  must be one of v1, v2, v3, m1, or m2. v1=lesser visual impairment, v2=moderate  must be one of v1, v2, v3, m1, or m2. v1=lesser visual impairment, v2=moderate
780  visual impairment, v3=blindness, m1=minor motor difficulties, m2=moderate motor  visual impairment, v3=blindness, m1=minor motor difficulties, m2=moderate motor
781  difficulties.  difficulties.
782   console=*TTY,SPEED*::    console=*TTY,SPEED*::
783  Set the default console to be used with the "live-getty" option. Example:  Set the default console to be used with the "live-getty" option. Example:
784  "console=ttyS0,115200"  "console=ttyS0,115200"
785   debug::    debug::
786  Makes initramfs boot process more verbose.  Makes initramfs boot process more verbose.
787   fetch=*URL*::    fetch=*URL*::
788  Another form of netboot by downloading a squashfs image from a given url,  Another form of netboot by downloading a squashfs image from a given url,
789  copying to ram and booting it.  copying to ram and booting it.
790   hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*::    hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*::
791  Those parameters lets you override values read from the config file.  Those parameters lets you override values read from the config file.
792   ignore_uuid    ignore_uuid
793  Do not check that any UUID embedded in the initramfs matches the discovered  Do not check that any UUID embedded in the initramfs matches the discovered
794  medium. live-initramfs may be told to generate a UUID by setting  medium. live-initramfs may be told to generate a UUID by setting
795  LIVE_GENERATE_UUID=1 when building the initramfs.  LIVE_GENERATE_UUID=1 when building the initramfs.
796   integrity-check::    integrity-check::
797  If specified, an MD5 sum is calculated on the live media during boot and  If specified, an MD5 sum is calculated on the live media during boot and
798  compared to the value found in md5sum.txt found in the root directory of the  compared to the value found in md5sum.txt found in the root directory of the
799  live media.  live media.
800   ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]    ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:
801      [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]]***::       [DEVICE]:[AUTOCONF] [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:
802         [DEVICE]:[AUTOCONF]]***::
803  Let you specify the name(s) and the options of the interface(s) that should be  Let you specify the name(s) and the options of the interface(s) that should be
804  configured at boot time. Do not specify this if you want to use dhcp (default).  configured at boot time. Do not specify this if you want to use dhcp (default).
805  It will be changed in a future release to mimick official kernel boot param  It will be changed in a future release to mimick official kernel boot param
806  specification (e.g. ip=10.0.0.1::10.0.0.254:255.255.255.0::eth0,:::::eth1:dhcp).  specification (e.g. ip=10.0.0.1::10.0.0.254:255.255.255.0::eth0,:::::eth1:dhcp).
807   ip[=**frommedia**]::    ip[=**frommedia**]::
808  If this variable is set, dhcp and static configuration are just skipped and the  If this variable is set, dhcp and static configuration are just skipped and the
809  system will use the (must be) media-preconfigured /etc/network/interfaces  system will use the (must be) media-preconfigured /etc/network/interfaces
810  instead.  instead.
811   {keyb|kbd-chooser/method}=**KEYBOARD**, {klayout|console-setup/layoutcode}=**LAYOUT**,    {keyb|kbd-chooser/method}=**KEYBOARD**, {klayout|console-setup/layoutcode}=**LAYOUT**,
812      {kvariant|console-setup/variantcode}=**VARIANT**,      {kvariant|console-setup/variantcode}=**VARIANT**, {kmodel|console-setup/modelcode}=
813      {kmodel|console-setup/modelcode}=**CODE**, koptions=**OPTIONS**::      **CODE**, koptions=**OPTIONS**::
814  Configure the running keyboard as specified, if this one misses live-initramfs  Configure the running keyboard as specified, if this one misses live-initramfs
815  behaves as if "keyb=us" was specified. It will be interfered from "locale=" if  behaves as if "keyb=us" was specified. It will be interfered from "locale=" if
816  locale is only 2 lowecase letters as a special case. You could also specify  locale is only 2 lowecase letters as a special case. You could also specify
817  console layout, variant, code, and options (no defaults).  console layout, variant, code, and options (no defaults).
818   live-getty::    live-getty::
819  This changes the auto-login on virtual terminals to use the (experimental)  This changes the auto-login on virtual terminals to use the (experimental)
820  live-getty code. With this option set the standard kernel argument "console=" is  live-getty code. With this option set the standard kernel argument "console=" is
821  parsed and if a serial console is specified then live-getty is used to autologin  parsed and if a serial console is specified then live-getty is used to autologin
822  on the serial console.  on the serial console.
823   {live-media|bootfrom}=**DEVICE**::    {live-media|bootfrom}=**DEVICE**::
824  If you specify one of this two equivalent forms, live-initramfs will first try  If you specify one of this two equivalent forms, live-initramfs will first try
825  to find this device for the "/live" directory where the read-only root  to find this device for the "/live" directory where the read-only root
826  filesystem should reside. If it did not find something usable, the normal scan  filesystem should reside. If it did not find something usable, the normal scan
827  for block devices is performed.  for block devices is performed.
828   {live-media-encryption|encryption}=**TYPE**::    {live-media-encryption|encryption}=**TYPE**::
829  live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase,  live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase,
830  useful to build paranoid live systems :-). TYPE supported so far are "aes" for  useful to build paranoid live systems :-). TYPE supported so far are "aes" for
831  loop-aes encryption type.  loop-aes encryption type.
832   live-media-offset=**BYTES**::    live-media-offset=**BYTES**::
833  This way you could tell live-initramfs that your image starts at offset BYTES in  This way you could tell live-initramfs that your image starts at offset BYTES in
834  the above specified or autodiscovered device, this could be useful to hide the  the above specified or autodiscovered device, this could be useful to hide the
835  Debian Live iso or image inside another iso or image, to create "clean" images.  Debian Live iso or image inside another iso or image, to create "clean" images.
836   live-media-path=**PATH**::    live-media-path=**PATH**::
837  Sets the path to the live filesystem on the medium. By default, it is set to  Sets the path to the live filesystem on the medium. By default, it is set to
838  '/live' and you should not change that unless you have customized your media  '/live' and you should not change that unless you have customized your media
839  accordingly.  accordingly.
840   live-media-timeout=**SECONDS**::    live-media-timeout=**SECONDS**::
841  Set the timeout in seconds for the device specified by "live-media=" to become  Set the timeout in seconds for the device specified by "live-media=" to become
842  ready before giving up.  ready before giving up.
843   {locale|debian-installer/locale}=**LOCALE**::    {locale|debian-installer/locale}=**LOCALE**::
844  Configure the running locale as specified, if not present the live-media rootfs  Configure the running locale as specified, if not present the live-media rootfs
845  configured locale will be used and if also this one misses live-initramfs behave  configured locale will be used and if also this one misses live-initramfs behave
846  as "locale=en_US.UTF-8" was specified. If only 2 lowercase letter are specified  as "locale=en_US.UTF-8" was specified. If only 2 lowercase letter are specified
# Line 806  as "locale=en_US.UTF-8" was specified. I Line 848  as "locale=en_US.UTF-8" was specified. I
848  case if also "keyb=" is unspecified is set with those 2 lowercase letters  case if also "keyb=" is unspecified is set with those 2 lowercase letters
849  (keyb=us). Beside that facility, only UTF8 locales are supported by  (keyb=us). Beside that facility, only UTF8 locales are supported by
850  live-initramfs.  live-initramfs.
851   module=**NAME**::    module=**NAME**::
852  Instead of using the default optional file "filesystem.module" (see below)  Instead of using the default optional file "filesystem.module" (see below)
853  another file could be specified without the extension ".module"; it should be  another file could be specified without the extension ".module"; it should be
854  placed on "/live" directory of the live medium.  placed on "/live" directory of the live medium.
855   netboot[=**nfs**|**cifs**]::    netboot[=**nfs**|**cifs**]::
856  This tells live-initramfs to perform a network mount. The parameter "nfsroot="  This tells live-initramfs to perform a network mount. The parameter "nfsroot="
857  (with optional "nfsopts="), should specify where is the location of the root  (with optional "nfsopts="), should specify where is the location of the root
858  filesystem.  With no args, will try cifs first, and if it fails nfs.  filesystem.  With no args, will try cifs first, and if it fails nfs.
859   nfsopts=::    nfsopts=::
860  This lets you specify custom nfs options.  This lets you specify custom nfs options.
861   noautologin::    noautologin::
862  This parameter disables the automatic terminal login only, not touching gdk/kdm.  This parameter disables the automatic terminal login only, not touching gdk/kdm.
863   noxautologin::    noxautologin::
864  This parameter disables the automatic login of gdm/kdm only, not touching  This parameter disables the automatic login of gdm/kdm only, not touching
865  terminals.  terminals.
866   nofastboot::    nofastboot::
867  This parameter disables the default disabling of filesystem checks in  This parameter disables the default disabling of filesystem checks in
868  /etc/fstab. If you have static filesystems on your harddisk and you want them to  /etc/fstab. If you have static filesystems on your harddisk and you want them to
869  be checked at boot time, use this parameter, otherwise they are skipped.  be checked at boot time, use this parameter, otherwise they are skipped.
870   nopersistent::    nopersistent::
871  disables the "persistent" feature, useful if the bootloader (like syslinux) has  disables the "persistent" feature, useful if the bootloader (like syslinux) has
872  been installed with persistent enabled.  been installed with persistent enabled.
873   noprompt    noprompt
874  Do not prompt to eject the CD on reboot.  Do not prompt to eject the CD on reboot.
875   nosudo::    nosudo::
876  This parameter disables the automatic configuration of sudo.  This parameter disables the automatic configuration of sudo.
877   swapon::    swapon::
878  This parameter enables usage of local swap partitions.  This parameter enables usage of local swap partitions.
879   nouser::    nouser::
880  This parameter disables the creation of the default user completely.  This parameter disables the creation of the default user completely.
881   noxautoconfig::    noxautoconfig::
882  This parameter disables Xorg auto-reconfiguration at boot time. This is valuable  This parameter disables Xorg auto-reconfiguration at boot time. This is valuable
883  if you either do the detection on your own, or, if you want to ship a custom,  if you either do the detection on your own, or, if you want to ship a custom,
884  premade xorg.conf in your live system.  premade xorg.conf in your live system.
885   persistent[=nofiles]::    persistent[=nofiles]::
886  live-initramfs will look for persistent and snapshot partitions or files labeled  live-initramfs will look for persistent and snapshot partitions or files labeled
887  "live-rw", "home-rw", and files called "live-sn*", "home-sn*" and will try to,  "live-rw", "home-rw", and files called "live-sn*", "home-sn*" and will try to,
888  in order: mount as /cow the first, mount the second in /home, and just copy the  in order: mount as /cow the first, mount the second in /home, and just copy the
# Line 849  tried to be updated on reboot/shutdown. Line 891  tried to be updated on reboot/shutdown.
891  informations. If "nofiles" is specified, only filesystems with matching labels  informations. If "nofiles" is specified, only filesystems with matching labels
892  will be searched; no filesystems will be traversed looking for archives or image  will be searched; no filesystems will be traversed looking for archives or image
893  files. This results in shorter boot times.  files. This results in shorter boot times.
894   {preseed/file|file}=**FILE**::    {preseed/file|file}=**FILE**::
895  A path to a file present on the rootfs could be used to preseed debconf  A path to a file present on the rootfs could be used to preseed debconf
896  database.  database.
897   package/question=**VALUE**::    package/question=**VALUE**::
898  All debian installed packages could be preseeded from command-line that way,  All debian installed packages could be preseeded from command-line that way,
899  beware of blanks spaces, they will interfere with parsing, use a preseed file in  beware of blanks spaces, they will interfere with parsing, use a preseed file in
900  this case.  this case.
901   quickreboot::    quickreboot::
902  This option causes live-initramfs to reboot without attempting to eject the  This option causes live-initramfs to reboot without attempting to eject the
903  media and without asking the user to remove the boot media.  media and without asking the user to remove the boot media.
904   showmounts::    showmounts::
905  This parameter will make live-initramfs to show on "/" the ro filesystems  This parameter will make live-initramfs to show on "/" the ro filesystems
906  (mostly compressed) on "/live". This is not enabled by default because could  (mostly compressed) on "/live". This is not enabled by default because could
907  lead to problems by applications like "mono" which store binary paths on  lead to problems by applications like "mono" which store binary paths on
908  installation.  installation.
909   textonly    textonly
910  Start up to text-mode shell prompts, disabling the graphical user interface.  Start up to text-mode shell prompts, disabling the graphical user interface.
911   timezone=**TIMEZONE**::    timezone=**TIMEZONE**::
912  By default, timezone is set to UTC. Using the timezone parameter, you can set it  By default, timezone is set to UTC. Using the timezone parameter, you can set it
913  to your local zone, e.g. Europe/Zurich.  to your local zone, e.g. Europe/Zurich.
914   todisk=**DEVICE**::    todisk=**DEVICE**::
915  Adding this parameter, live-initramfs will try to copy the entire read-only  Adding this parameter, live-initramfs will try to copy the entire read-only
916  media to the specified device before mounting the root filesystem. It probably  media to the specified device before mounting the root filesystem. It probably
917  needs a lot of free space. Subsequent boots should then skip this step and just  needs a lot of free space. Subsequent boots should then skip this step and just
918  specify the "live-media=DEVICE" boot parameter with the same DEVICE used this  specify the "live-media=DEVICE" boot parameter with the same DEVICE used this
919  time.  time.
920   toram::    toram::
921  Adding this parameter, live-initramfs will try to copy the whole read-only media  Adding this parameter, live-initramfs will try to copy the whole read-only media
922  to the computer's RAM before mounting the root filesystem. This could need a lot  to the computer's RAM before mounting the root filesystem. This could need a lot
923  of ram, according to the space used by the read-only media.  of ram, according to the space used by the read-only media.
924   union=**aufs**|**unionfs**::    union=**aufs**|**unionfs**::
925  By default, live-initramfs uses aufs. With this parameter, you can switch to  By default, live-initramfs uses aufs. With this parameter, you can switch to
926  unionfs.  unionfs.
927   utc=**yes**|**no**::    utc=**yes**|**no**::
928  By default, Debian systems do assume that the hardware clock is set to UTC. You  By default, Debian systems do assume that the hardware clock is set to UTC. You
929  can change or explicitly set it with this parameter.  can change or explicitly set it with this parameter.
930   xdebconf::    xdebconf::
931  Uses xdebconfigurator, if present on the rootfs, to configure X instead of the  Uses xdebconfigurator, if present on the rootfs, to configure X instead of the
932  standard procedure (experimental).  standard procedure (experimental).
933   xvideomode=**RESOLUTION**::    xvideomode=**RESOLUTION**::
934  Doesn't do xorg autodetection, but enforces a given resolution.  Doesn't do xorg autodetection, but enforces a given resolution.
935  Files  Files
936  -----  -----
937   /etc/live.conf    /etc/live.conf
938  Some variables can be configured via this config file (inside the live system).  Some variables can be configured via this config file (inside the live system).
939    /live/filesystem.module     /live/filesystem.module
940  This optional file (inside the live media) contains a list of white-space or  This optional file (inside the live media) contains a list of white-space or
941  carriage-return-separated file names corresponding to disk images in the "/live"  carriage-return-separated file names corresponding to disk images in the "/live"
942  directory. If this file exists, only images listed here will be merged into the  directory. If this file exists, only images listed here will be merged into the
# Line 902  root aufs, and they will be loaded in th Line 944  root aufs, and they will be loaded in th
944  in this file will be the "lowest" point in the aufs, and the last file in  in this file will be the "lowest" point in the aufs, and the last file in
945  this list will be on the "top" of the aufs, directly below /cow.  Without  this list will be on the "top" of the aufs, directly below /cow.  Without
946  this file, any images in the "/live" directory are loaded in alphanumeric order.  this file, any images in the "/live" directory are loaded in alphanumeric order.
947  /etc/live-persistence.binds   /etc/live-persistence.binds
948  This optional file (which resides in the rootfs system, not in the live media)  This optional file (which resides in the rootfs system, not in the live media)
949  is used as a list of directories which not need be persistent: ie. their  is used as a list of directories which not need be persistent: ie. their
950  content does not need to survive reboots when using the persistence features.  content does not need to survive reboots when using the persistence features.
# Line 917  live-webhelper(7) Line 959  live-webhelper(7)
959  Bugs  Bugs
960  ----  ----
961  Report bugs against live-initramfs  Report bugs against live-initramfs
962  link:http://packages.qa.debian.org/live-initramfs[http://packages.qa.debian.org/live-initramfs].  <a href="http://packages.qa.debian.org/live-initramfs" target="_blank">http://packages.qa.debian.org/live-initramfs</a>.
963  Homepage  Homepage
964  --------  --------
965  More information about the Debian Live project can be found at  More information about the Debian Live project can be found at
966  link:http://debian-live.alioth.debian.org/[http://debian-live.alioth.debian.org/] and  <a href="http://debian-live.alioth.debian.org/" target="_blank">http://debian-live.alioth.debian.org/</a> and
967  link:http://wiki.debian.org/DebianLive/[http://wiki.debian.org/DebianLive/].  <a href="http://wiki.debian.org/DebianLive/" target="_blank">http://wiki.debian.org/DebianLive/</a>.
968  Authors  Authors
969  -------  -------
970  live-initramfs is maintained by Daniel Baumann &lt;daniel@debian.org&gt;  live-initramfs is maintained by Daniel Baumann &amp;lt;daniel@debian.org&amp;gt;
971  for the Debian project.  for the Debian project.
972  live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper].  live-initramfs is a fork of <a href="http://packages.ubuntu.com/casper/" target="_blank">casper</a>.
973  casper was originally written by Tollef Fog Heen &lt;tfheen@canonical.com&gt;  casper was originally written by Tollef Fog Heen &amp;lt;tfheen@canonical.com&amp;gt;
974  and Matt Zimmerman &lt;mdz@canonical.com&gt;.</pre>  and Matt Zimmerman &amp;lt;mdz@canonical.com&amp;gt;.
975    </pre>
976  </div>  </div>
977  <a name="clonezilla-top"></a>  <a name="clonezilla-top"></a>
978  <H2 style="font-size: 2em;"><a name="clonezilla-intro"></a>About Clonezilla Live <span class="hideprint">[<a href="#clonezilla-top" title="go to top of the page">^</a>]</span></H2>  <H2 style="font-size: 2em;"><a name="clonezilla-intro"></a>About Clonezilla Live <span class="hideprint">[<a href="#clonezilla-top" title="go to top of the page">^</a>]</span></H2>
# Line 974  If, on the other hand, you just want to Line 1017  If, on the other hand, you just want to
1017  <p class="newcode">ocs-live</p>  <p class="newcode">ocs-live</p>
1018  <H2><a name="about"></a>About the Image file <span class="hideprint">[<a href="#clonezilla-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="about"></a>About the Image file <span class="hideprint">[<a href="#clonezilla-top" title="go to top of the page">^</a>]</span></H2>
1019  <p>One thing should be made clear about the image file: it is not a file, it is a <b>folder</b>, containing the actual image file and some data about the disk/partition it is associated with. So when you insert the image file name, you actually insert the folder name where the image will be saved/restored.<br><br>  <p>One thing should be made clear about the image file: it is not a file, it is a <b>folder</b>, containing the actual image file and some data about the disk/partition it is associated with. So when you insert the image file name, you actually insert the folder name where the image will be saved/restored.<br><br>
1020  Before you are able to insert the image file name, a list of partitions will be presented to you, so that you can choose where it should be saved/found. When you select one of them, it will be mounted under <b>/home/partimag</b>.<br><br>  Before you are able to insert the image file name, a list of partitions will be presented to you, so that you can choose where it should be saved/found. When you select one of them, it will be mounted and a list of folders will be presented to you, so you can select the base image directory (first level directory within the partition), which will then be mounted under <b>/home/partimag</b>. This way you can, for example, create a folder called <b>all_my_images</b> in one of your disk partitions, and move all your image files in there; <b>Clonezilla Live</b> will be able to find them!!!<br><br>
 This folder is very important for <b>Clonezilla Live</b>; the image file <b>must</b> be located under this directory, which means that the image file <b>must</b> be on the root directory of the mounted partition. So you can not, for example, create a folder called <b>all_my_images</b> and move all your image files in there; <b>Clonezilla Live</b> will not be able to find them!!!<br><br>  
1021  Another thing that should be pointed out is that <b>only unmounted</b> partitions will be included in the above list. This means that if you have stopped the program at some point after specifying the partition where the image file resides, and it has been mounted, it will not be present in the list the next time it is presented to you, and you will not be able to use it.<br><br>  Another thing that should be pointed out is that <b>only unmounted</b> partitions will be included in the above list. This means that if you have stopped the program at some point after specifying the partition where the image file resides, and it has been mounted, it will not be present in the list the next time it is presented to you, and you will not be able to use it.<br><br>
1022  There are two things you can do in this case; either unmount the partition, as stated <a href="#umount">above</a>, or select</p>  There are two things you can do in this case; either unmount the partition, as stated <a href="#umount">above</a>, or select</p>
1023  <p class="newcode"><font color="Red">skip&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use existing /home/partimag</font></p>  <p class="newcode"><font color="Red">skip&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use existing /home/partimag</font></p>
# Line 1005  Fianlly I should say that <b>Clonezilla Line 1047  Fianlly I should say that <b>Clonezilla
1047  <p>This option prevents <b>Clonezilla Live</b> from cloning your page file if you are cloning a partition containing Windows. Often the page file is big and unneeded, and skipping it may speed cloning up without causing any harm. Mind you, this option is disabled by default because sometimes the page file may be necessary.</p>  <p>This option prevents <b>Clonezilla Live</b> from cloning your page file if you are cloning a partition containing Windows. Often the page file is big and unneeded, and skipping it may speed cloning up without causing any harm. Mind you, this option is disabled by default because sometimes the page file may be necessary.</p>
1048  <p class="newcode"><a name="ntfs-ok"></a><font color="Red">-ntfs-ok&nbsp;Skip checking NTFS integrity, even bad sectors (ntfsclone only)</font></p>  <p class="newcode"><a name="ntfs-ok"></a><font color="Red">-ntfs-ok&nbsp;Skip checking NTFS integrity, even bad sectors (ntfsclone only)</font></p>
1049  <p>This option works only if you selected the <font color="Red"><b>-q</b></font> option and you're cloning a NTFS partition. It prevents the integrity check of NTFS partitions and speeds the cloning process up a little. However, if the check is disabled, there is a risk that the filesystem is damaged and the image created from it is useless.</p>  <p>This option works only if you selected the <font color="Red"><b>-q</b></font> option and you're cloning a NTFS partition. It prevents the integrity check of NTFS partitions and speeds the cloning process up a little. However, if the check is disabled, there is a risk that the filesystem is damaged and the image created from it is useless.</p>
1050    <p class="newcode"><a name="rescue"></a><font color="Red">-rescue&nbsp;Continue reading next one when disk blocks read errors</font></p>
1051    <p>If this option is set, <b>Clonezilla Live</b> continues cloning even if a read error occurs. If there is one, the disk image will be corrupted, but failing hard drives can only be cloned with this option enabled.</p>
1052    <p class="newcode"><a name="fsck-src-part"></a><font color="Red">-fsck-src-part&nbsp;Check and repair source file system before saving</font></p>
1053    <p>This option causes <b>Clonezilla Live</b> to check the integrity of the partition(s) to be cloned. If the filesystem of the partition is damaged, <b>Clonezilla Live</b> also attempts to repair it automatically. Enabling this option reduces the risk that the image contains a damaged filesystem. However, the option is disabled by default because the automatic filesystem repair attempt may cause data loss.</p>
1054  <p class="newcode"><a name="gen-md5"></a><font color="Red">-gm&nbsp;Generate image MD5 checksums</font></p>  <p class="newcode"><a name="gen-md5"></a><font color="Red">-gm&nbsp;Generate image MD5 checksums</font></p>
1055  <p>Causes <b>Clonezilla Live</b> to calculate MD5 checksum(s) of image(s) created. If the image cets corrupted afterwards, the checksum allows to notice the corruption before the image is restored. Mind you, calculating the checksum takes some time and slows the process down a little.</p>  <p>Causes <b>Clonezilla Live</b> to calculate MD5 checksum(s) of image(s) created. If the image gets corrupted afterwards, the checksum allows to notice the corruption before the image is restored. Mind you, calculating the checksum takes some time and slows the process down a little.</p>
1056  <p class="newcode"><a name="gen-sha1"></a><font color="Red">-gs&nbsp;Generate image SHA1 checksums</font></p>  <p class="newcode"><a name="gen-sha1"></a><font color="Red">-gs&nbsp;Generate image SHA1 checksums</font></p>
1057  <p>This option is identical to the above, but creates SHA1 checksum(s) instead of MD5. SHA1 is considered to be more accurate checksum algorithm than MD5, but MD5 is more popular.</p>  <p>This option is identical to the above, but creates SHA1 checksum(s) instead of MD5. SHA1 is considered to be more accurate checksum algorithm than MD5, but MD5 is more popular.</p>
1058  <H4><a name="compression-method"></a>Compression method [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H4>  <H4><a name="compression-method"></a>Compression method [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H4>
1059  <p class="newcode"><a name="z_option"></a><font color="Red">-z1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;gzip compression (fast with a smaller image)<br>  <p class="newcode"><a name="z_option"></a><font color="Red">-z1p&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use parallel gzip compression (testing), for multicore/CPU<br>
1060    -z1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;gzip compression (fast with a smaller image)<br>
1061    -z2p&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use parallel bzip2 compression (testing), for multicore/CPU<br>
1062  -z2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;bzip2 compression (slowest but smallest image)<br>  -z2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;bzip2 compression (slowest but smallest image)<br>
1063  -z3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;lzo compression (faster with image size approx. to that of gzip)(NOTE!!)<br>  -z3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;lzo compression (faster with image size approx. to that of gzip)(NOTE!!)<br>
1064  -z4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;lzma compression (slowest but also small image, faster decompression than bzip2)<br>  -z4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;lzma_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2)<br>
1065    -z5p&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use_parallel_xz_compression_(testing),_for_multicore/CPU<br>
1066    -z5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;xz_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2)<br>
1067    -z6p&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use_parallel_lzip_compression_(testing),_for_multicore/CPU<br>
1068    -z6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;lzip_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2)<br>
1069  -z0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;No compression (fastest but largest image size)</font></p>  -z0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;No compression (fastest but largest image size)</font></p>
1070  <p>This option chooses the method which is used to compress the image while creating it.</p>  <p>This option chooses the method which is used to compress the image while creating it.</p>
1071  <p>If no compression is used at all, there won't be any negative speed impact caused by compression. However, the image file size is the size of all the data backed up - for example, if you clone a 160 GB hard drive containing 60 gigabytes of data, the resulting disk image will be 60 gigabytes in size.</p>  <p>If no compression is used at all, there won't be any negative speed impact caused by compression. However, the image file size is the size of all the data backed up - for example, if you clone a 160 GB hard drive containing 60 gigabytes of data, the resulting disk image will be 60 gigabytes in size.</p>
1072  <p><b>Gzip</b> and <b>lzop</b> are fast compression methods. <b>Lzop</b> is many times faster than <b>gzip</b>, but creates slightly larger images. <b>Clonezilla Live</b> warns that <b>lzop</b> requires good-quality RAM, but I (the contributor who wrote this chapter) think other compression methods require good RAM too.</p>  <p><b>Gzip</b> and <b>lzop</b> are fast compression methods. <b>Lzop</b> is many times faster than <b>gzip</b>, but creates slightly larger images. <b>Clonezilla Live</b> warns that <b>lzop</b> requires good-quality RAM, but I (the contributor who wrote this chapter) think other compression methods require good RAM too.</p>
1073  <p><b>Bzip2</b> and <b>lzma</b> are powerful compression methods. <b>Lzma</b> creates a little smaller images than <b>bzip2</b>, and decompressing lzma-compressed images is faster than decompressing <b>bzip2</b> images. But there is no free lunch: <b>lzma</b> compression method is very slow compared even to <b>bzip2</b>, which isn't fast method either.</p>  <p><b>Bzip2</b>, <b>lzma</b>, <b>xz</b> and <b>lzip</b> are powerful compression methods. <b>Lzma</b> creates a little smaller images than <b>bzip2</b>, and decompressing lzma-compressed images is faster than decompressing <b>bzip2</b> images. But there is no free lunch: <b>lzma</b> compression method is very slow compared even to <b>bzip2</b>, which isn't fast method either.</p>
1074    <p><b>Lzma</b> method is becoming obsolete, and both <b>xz</b> and <b>lzip</b> are attempting to become its successor. They are a bit less powerful compression methods than <b>lzma</b>, but much faster. The differences between <b>xz</b> and <b>lzip</b> are virtually non-existent.</p>
1075    <p>If you don't use the i486 version of <b>Clonezilla-SysRescCD</b> and your processor contains multiple cores and/or supports Hyper-Threading, parallel <b>gzip</b>, <b>bzip2</b>, <b>xz</b> and <b>lzip</b> compression methods are also available. Parallel compression means that each processor core compresses a different part of the image at a time. Without parallel compression one core compresses everything.</p>
1076    <p>The speed impact caused by parallel compression depends on the number of processor cores available. In addition, Hyper-Threading increases the speed by about 30 % if parallel compression is used. For example, if your processor contains four cores and supports Hyper-Threading, speed with parallel compression is nearly 5,2 times as high as without. However, parallel compression is currently an experimental feature.</p>
1077  <H4><a name="splitting"></a>Splitting [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H4>  <H4><a name="splitting"></a>Splitting [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H4>
1078  <p>This option (command line: <b>-i <font color="Red">[number]</font></b>) decides if the created image files are splitted into smaller pieces, and if yes, how large the pieces are. This setting doesn't usually matter, but some filesystems (most importantly FAT32) don't allow files larger than four gigabytes. If you're saving the disk image to a FAT32 partition, enter 4000 or less. (Value 0 disables splitting, so don't use it in that case.) If the filesystem allows files big enough, enter any value which isn't too small (you don't want to split the image into too many pieces, do you?)</p>  <p>This option (command line: <b>-i <font color="Red">[number]</font></b>) decides if the created image files are splitted into smaller pieces, and if yes, how large the pieces are. This setting doesn't usually matter, but some filesystems (most importantly FAT32) don't allow files larger than four gigabytes. If you're saving the disk image to a FAT32 partition, enter 4000 or less. (Value 0 disables splitting, so don't use it in that case.) If the filesystem allows files big enough, enter any value which isn't too small (you don't want to split the image into too many pieces, do you?)</p>
1079    <p><b>Clonezilla Live</b> warns that it is no longer safe to disable splitting because value 0 can confuse init. I (the contributor) don't know what the warning exactly means and haven't been able to reproduce the problem. Anyway, entering a very big value, for example 999999999999, is a safe way to keep the image in one piece.</p>
1080  <H4><a name="backup-postaction"></a>Postaction [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H4>  <H4><a name="backup-postaction"></a>Postaction [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H4>
1081  <p class="newcode"><a name="backup_p_option"></a><font color="Red">-p true&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Do nothing when the clone finishes<br>  <p class="newcode"><a name="backup_p_option"></a><font color="Red">-p true&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Do nothing when the clone finishes<br>
1082  -p reboot&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Reboot client when the clone finishes<br>  -p reboot&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Reboot client when the clone finishes<br>
# Line 1056  Fianlly I should say that <b>Clonezilla Line 1112  Fianlly I should say that <b>Clonezilla
1112  <p>This option is useful if you are cloning a small disk to larger one. It tries to resize the restored filesystem to the size of the partition where it was restored to. It allows you to use the whole size of your new disk without resizing the partition afterwards. The option requires that the disk where the image is copied already contains a partition where the image is restored or that the option <font color="Red"><b>-k1</b></font> is enabled.</p>  <p>This option is useful if you are cloning a small disk to larger one. It tries to resize the restored filesystem to the size of the partition where it was restored to. It allows you to use the whole size of your new disk without resizing the partition afterwards. The option requires that the disk where the image is copied already contains a partition where the image is restored or that the option <font color="Red"><b>-k1</b></font> is enabled.</p>
1113  <p class="newcode"><a name="load-geometry"></a><font color="Red">-e&nbsp;sfdisk uses the CHS value of hard drive from the saved image</font></p>  <p class="newcode"><a name="load-geometry"></a><font color="Red">-e&nbsp;sfdisk uses the CHS value of hard drive from the saved image</font></p>
1114  <p>Force to use the saved CHS (cylinders, heads, sectors) when using sfdisk. Of cource, there is no use of it when using any of <b><font color="Red">-j0</font></b>, <b><font color="Red">-k</font></b> or <b><font color="Red">-k2</font></b> options.</p>  <p>Force to use the saved CHS (cylinders, heads, sectors) when using sfdisk. Of cource, there is no use of it when using any of <b><font color="Red">-j0</font></b>, <b><font color="Red">-k</font></b> or <b><font color="Red">-k2</font></b> options.</p>
1115    <p class="newcode"><a name="ignore-crc"></a><font color="Red">-icrc&nbsp;Ignore CRC checking of partclone</font></p>
1116    <p>This option causes <b>partclone</b> to skip checking the CRC32 checksums of the image. Enabling this option speeds the restore process up. However, if this option is enabled and the <b><font color="Red">-cm</font></b> and <b><font color="Red">-cs</font></b> options are disabled, there is no way to notice if the image has corrupted.</p>
1117  <p class="newcode"><a name="mbr-again"></a><font color="Red">-j1&nbsp;Write MBR (512 B) again after image is restored. Not OK for partition table diffe</font></p>  <p class="newcode"><a name="mbr-again"></a><font color="Red">-j1&nbsp;Write MBR (512 B) again after image is restored. Not OK for partition table diffe</font></p>
1118  <p>When a disk image is restored, the partition table must be updated to reflect the actual partitions in the disk. If you don't want it to happen, enable this option. Then the Master Boot Record (including the partition table) is restored again after restoring the image. Note that using this option can destroy all the data in the target drive.</p>  <p>When a disk image is restored, the partition table must be updated to reflect the actual partitions in the disk. If you don't want it to happen, enable this option. Then the Master Boot Record (including the partition table) is restored again after restoring the image. Note that using this option can destroy all the data in the target drive.</p>
1119  <p class="newcode"><a name="restore-hidden-data"></a><font color="Red">-j2&nbsp;Clone the hidden data between MBR and 1st partition</font></p>  <p class="newcode"><a name="restore-hidden-data"></a><font color="Red">-j2&nbsp;Clone the hidden data between MBR and 1st partition</font></p>
# Line 1085  Fianlly I should say that <b>Clonezilla Line 1143  Fianlly I should say that <b>Clonezilla
1143  <p class="newcode"><a name="dd"></a><font color="Red">-j0&nbsp;Use dd to create partition (NOT OK if logical drives exist)</font></p>  <p class="newcode"><a name="dd"></a><font color="Red">-j0&nbsp;Use dd to create partition (NOT OK if logical drives exist)</font></p>
1144  <p>Use dd to dump the partition table from saved image instead of sfdisk.<br><br>  <p>Use dd to dump the partition table from saved image instead of sfdisk.<br><br>
1145  We read in <a href="http://drbl.sourceforge.net/faq/fine-print.php?path=./2_System/23_Missing_OS.faq#23_Missing_OS.faq" target="_blank">DRBL FAQ/Q&#038;A</a>:</p>  We read in <a href="http://drbl.sourceforge.net/faq/fine-print.php?path=./2_System/23_Missing_OS.faq#23_Missing_OS.faq" target="_blank">DRBL FAQ/Q&#038;A</a>:</p>
1146  <p style="margin-left: 40pt; margin-right: 40pt;">When I use clonezilla to clone M$ windows, there is no any problem when saving an image from template machine. However, after the image is restored to another machine, it fails to boot, the error message is "<b>Missing Operating System</b>". What's going on ?<br><br>  <p class="otherpage">When I use clonezilla to clone M$ windows, there is no any problem when saving an image from template machine. However, after the image is restored to another machine, it fails to boot, the error message is "<b>Missing Operating System</b>". What's going on ?<br><br>
1147  Usually this is because GNU/Linux and M$ windows interpret the CHS (cylinder, head, sector) value of harddrive differently. Some possible solutions:<br>  Usually this is because GNU/Linux and M$ windows interpret the CHS (cylinder, head, sector) value of harddrive differently. Some possible solutions:<br>
1148  &nbsp;&nbsp;1. Maybe you can change the IDE harddrive setting in BIOS, try to use LBA instead of auto mode.<br>  &nbsp;&nbsp;1. Maybe you can change the IDE harddrive setting in BIOS, try to use LBA instead of auto mode.<br>
1149  &nbsp;&nbsp;2. Try to choose<br>  &nbsp;&nbsp;2. Try to choose<br>
# Line 1115  Please boot into Windows TWICE, or use ' Line 1173  Please boot into Windows TWICE, or use '
1173  prompt, execute the command:</p>  prompt, execute the command:</p>
1174  <p class="newcode" style="margin-left: 0pt;"><font color="Red">chkdsk /f X:</font></p>  <p class="newcode" style="margin-left: 0pt;"><font color="Red">chkdsk /f X:</font></p>
1175  <p style="margin-left: 0pt;">where <font color="Red"><b>X:</b></font> is the drive letter of the disk. When done, boot back into <b>Clonezilla Live</b> and repeat the backup procedure.</p>  <p style="margin-left: 0pt;">where <font color="Red"><b>X:</b></font> is the drive letter of the disk. When done, boot back into <b>Clonezilla Live</b> and repeat the backup procedure.</p>
1176  If the Windows version you use is not XP, boot into <b>SystemRescueCD</b> (graphical mode is not needed) and run the following command:  <p style="margin-left: 0pt;">If the disk/partition you are trying to backup is not the Windows System disk (usually <b>C:</b>), you can boot Windows, and execute the command in a DOS window. To open a DOS window click <b>Start / Run... </b> and at the prompt <b>Open:</b>  type <b><font color="Red">cmd</font>.</b></li></p>
1177    <p style="margin-left: 0pt;">If the Windows version you use is not XP and you're trying to backup the Windows System drive, boot into <b>SystemRescueCD</b> (graphical mode is not needed) and run the following command:</p>
1178  <p class="newcode" style="margin-left: 0pt;"><font color="Red">ntfsfix /dev/hda1</font></p>  <p class="newcode" style="margin-left: 0pt;"><font color="Red">ntfsfix /dev/hda1</font></p>
1179  <p style="margin-left: 0pt;">where <b>/dev/<font color="Red">hda1</font></b> is the partition name in GNU/Linux. When done, boot back into <b>Clonezilla Live</b> and repeat the backup procedure.</p>  <p style="margin-left: 0pt;">where <b>/dev/<font color="Red">hda1</font></b> is the partition name in GNU/Linux. When done, boot back into <b>Clonezilla Live</b> and repeat the backup procedure.</p>
 If the disk/partition you are trying to backup is not the Windows System disk (usually <b>C:</b>), you can boot Windows, and execute the command in a DOS window. To open a DOS window click <b>Start / Run... </b> and at the prompt <b>Open:</b>  type <b><font color="Red">cmd</font>.</b></li>  
1180  <li><p style="margin-left: 0pt;">If <b>Windows XP Recovery Console</b> is not available, you don't have the time to execute the procedure described above, or even if you have executed it but you still get the same message, and you are <b><u>absolutely sure</u></b> that you get this message because the NTFS partition is really scheduled for check, and it's not because Windows crushed or have become corrupt, you can mount the patririon by hand and tell <b>Clonezilla Live</b> to use it. Assuming the partition is <b>/dev/<font color="Red">hda1</font></b>, exit the program and execute the commands:</p>  <li><p style="margin-left: 0pt;">If <b>Windows XP Recovery Console</b> is not available, you don't have the time to execute the procedure described above, or even if you have executed it but you still get the same message, and you are <b><u>absolutely sure</u></b> that you get this message because the NTFS partition is really scheduled for check, and it's not because Windows crushed or have become corrupt, you can mount the patririon by hand and tell <b>Clonezilla Live</b> to use it. Assuming the partition is <b>/dev/<font color="Red">hda1</font></b>, exit the program and execute the commands:</p>
1181  <p class="newcode" style="margin-left: 0pt;">sudo su -<br>  <p class="newcode" style="margin-left: 0pt;">sudo su -<br>
1182  ntfs-3g -o force /dev/<font color="Red">hda1</font> /home/partimag<br>  ntfs-3g -o force /dev/<font color="Red">hda1</font> /home/partimag<br>
# Line 1217  Then I will be asked to confirm the oper Line 1275  Then I will be asked to confirm the oper
1275  After that, the backup begins<br>  After that, the backup begins<br>
1276  <br>  <br>
1277  <img src="images/backup-15.png"><br>  <img src="images/backup-15.png"><br>
1278  and when it's successfully completed, I will be able to reboot the system by pressing <font color="Red"><b>1</b></font> and ENTER.  and when it's successfully completed, I press ENTER to get to the shell. Then, I execute the commands:</p>
1279  </p>  <p class="newcode">sudo su -<br>
1280    cd<br>
1281    umount -a<br>
1282    reboot<br><br></p>
1283    <p>to reboot the system.</p>
1284  <a name="backup-smb-top"></a>  <a name="backup-smb-top"></a>
1285  <H2 style="font-size: 2em;"><a name="backup-smb-intro"></a>Getting backups on Samba <span class="hideprint">[<a href="#backup-smb-top" title="go to top of the page">^</a>]</span></H2>  <H2 style="font-size: 2em;"><a name="backup-smb-intro"></a>Getting backups on Samba <span class="hideprint">[<a href="#backup-smb-top" title="go to top of the page">^</a>]</span></H2>
1286  <p>What if you don't have a spare local disk or partition or a USB disk? How will you be able to get a backup of your system? Well, if your PC is on the same LAN with another PC running Windows (or linux), you can use <b>Samba</b> to save your image file on that remote PC (which we will call <b>Samba server</b> from now on).<br><br>  <p>What if you don't have a spare local disk or partition or a USB disk? How will you be able to get a backup of your system? Well, if your PC is on the same LAN with another PC running Windows (or linux), you can use <b>Samba</b> to save your image file on that remote PC (which we will call <b>Samba server</b> from now on).<br><br>
# Line 1247  This is the name of the <b>Windows share Line 1309  This is the name of the <b>Windows share
1309  </p>  </p>
1310  <p>If you need to change these settings, go to the <a href="backup.html#bck-0" target="_blank">Getting backups</a> page for instructions .</p>  <p>If you need to change these settings, go to the <a href="backup.html#bck-0" target="_blank">Getting backups</a> page for instructions .</p>
1311  <H3><a name="bck-smb-1"></a>Screen "Start Clonezilla" [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-smb-1"></a>Screen "Start Clonezilla" [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1312  <p>I select "<font color="Red"><b>Start Clonezilla</b></font>" and press ENTER.</p>  <p><img src="images/backup-03.png"><br>
1313    I select "<font color="Red"><b>Start Clonezilla</b></font>" and press ENTER.
1314    </p>
1315  <H3><a name="bck-smb-2"></a>Screen "Clonezilla" [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-smb-2"></a>Screen "Clonezilla" [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1316  <p>I select "<font color="Red"><b>device-image</b></font>" and press ENTER.</p>  <p><img src="images/backup-04.png"><br>
1317  <H3><a name="bck-smb-3"></a>Screen "Mount clonezilla image directory" [<a href="#backup-smb-top" title="go to top of the page">^</a></H3>  I select "<font color="Red"><b>device-image</b></font>" and press ENTER.<br> <br>
1318    </p>
1319    <H3><a name="bck-smb-3"></a>Screen "Mount clonezilla image directory" [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1320  <p>In this screen I can select the way the image file directory will be saved.  <p>In this screen I can select the way the image file directory will be saved.
1321  Available options are local directory, remote directory through <b>ssh</b>, <b>samba</b> or <b>nfs</b> and skip, to use the previously used directory. More info about the image file can be found at section "<a href="clonezilla.html#about">About the Image file</a>".<br>  Available options are local directory, remote directory through <b>ssh</b>, <b>samba</b> or <b>nfs</b> and skip, to use the previously used directory. More info about the image file can be found at section "<a href="clonezilla.html#about">About the Image file</a>".<br>
1322  <br>  <br>
1323    <img src="images/backup-smb-05.png"><br>
1324  I select "<font color="Red"><b>samba server</b></font>" and press ENTER.</p>  I select "<font color="Red"><b>samba server</b></font>" and press ENTER.</p>
1325  <H3><a name="bck-smb-4"></a>Screen "Mount Samba Server" [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-smb-4"></a>Screen "Mount Samba Server" [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1326  <p>This is where I have to enter the IP address of my Samba server.<br><br> I type "<font color="Red"><b>10.0.0.2</b></font>" and press ENTER.</p>  <p>This is where I have to enter the IP address of my Samba server.<br><br>
1327    <img src="images/backup-smb-06.png"><br>
1328    I type "<font color="Red"><b>10.0.0.3</b></font>" and press ENTER.</p>
1329  <H3><a name="bck-smb-5"></a>Screen "Mount Samba Server" (second time) [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-smb-5"></a>Screen "Mount Samba Server" (second time) [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1330  <p>This is where I have to enter the account (user) name on my Samba server.<br><br> I type "<font color="Red"><b>spiros</b></font>" and press ENTER.</p>  <p>This is where I have to enter the domain name on my Samba server.<br><br>
1331    <img src="images/backup-smb-07.png"><br>
1332    I just press ENTER, as there is no domain in my LAN. If there is a domain in your network, you have to type its name (something like <b>my_company.com</b>) and press ENTER.</p>
1333  <H3><a name="bck-smb-6"></a>Screen "Mount Samba Server" (third time) [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-smb-6"></a>Screen "Mount Samba Server" (third time) [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1334  <p>This is where I have to enter the domain name on my Samba server.<br><br> I select "<font color="Red"><b>Cancel</b></font>" and press ENTER, as there is no domain in my LAN. If there is a domain in your network, you have to type its name (something like <b>my_company.com</b>) and press ENTER.</p>  <p>This is where I have to enter the account (user) name on my Samba server.<br><br>
1335    <img src="images/backup-smb-08.png"><br>
1336    I type "<font color="Red"><b>spiros</b></font>" and press ENTER.</p>
1337  <H3><a name="bck-smb-7"></a>Screen "Mount Samba Server" (fourth time) [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-smb-7"></a>Screen "Mount Samba Server" (fourth time) [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1338  <p>This is where I have to enter the directory name on my Samba server, in which the image file will be saved.<br><br> I type "/<font color="Red"><b>data</b></font>" and press ENTER.<br><br>  <p>This is where I have to enter the directory name on my Samba server, in which the image file will be saved.<br><br> I type "<font color="Red"><b>/all_my_images</b></font>" and press ENTER.<br><br>
1339  At this point I will be asked for the password for user <b><font color="Red"><b>spiros</b></font></b>. I will be able to continue only after entering it correctly.</p>  <img src="images/backup-smb-09.png"><br>
1340    At this point I informed I will be asked for the password for user <b><font color="Red"><b>spiros</b></font></b>.<br><br>
1341    <img src="images/backup-smb-10.png"><br>
1342    I will be able to continue only after entering it correctly.<br><br>
1343    <img src="images/backup-smb-11.png"></p>
1344  <H3><a name="bck-smb-7a"></a>Screen "Clonezilla - Opensource Clone System (OCS)" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-smb-7a"></a>Screen "Clonezilla - Opensource Clone System (OCS)" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1345  <p>I select <font color="Red"><b>Beginner mode</b></font> to accept the default backup options. If you select <font color="Red"><b>Expert mode</b></font>, you can choose the options yourself. More details can be found <a href="clonezilla.html#backup-options" target="_blank">here</a>.</p>  <p><img src="images/backup-09.png">
1346  <H3><a name="bck-smb-8"></a>Screen "Clonezilla: Select mode" [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>  <br>I select <font color="Red"><b>Beginer mode</b></font> to accept the default backup options. If you select <font color="Red"><b>Expert mode</b></font>, you can choose the options yourself. More details can be found <a href="clonezilla.html#backup-options" target="_blank">here</a>.</p>
1347  <p>Here I can select the desired operation. Available options are:</p>  <H3><a name="bck-smb-8"></a>Screen "Select mode" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1348  <p>savedisk<br>  <p>Here I can select the desired operation.<br>
1349  &nbsp;&nbsp;&nbsp;&nbsp;Save entire disk to image<br>  <br>
1350  <br>  <img src="images/backup-10.png"><br>
1351  restoredisk<br>  I select "<font color="Red"><b>savedisk</b></font>" and press ENTER.<br> <br></p>
1352  &nbsp;&nbsp;&nbsp;&nbsp;Restore entire disk from image<br>  <H3><a name="bck-smb-9"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1353  <br>  <p><img src="images/backup-11.png"><br>
1354  saveparts<br>  In this screen I select the image name.<br>
1355  &nbsp;&nbsp;&nbsp;&nbsp;Save partition to image<br>  I type "Backup_5-2010_hdb", which in my opinion is more informative name than the default.
1356  <br>  </p>
1357  restoreparts<br>  <H3><a name="bck-smb-10"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1358  &nbsp;&nbsp;&nbsp;&nbsp;Restore partition from image<br>  <p><img src="images/backup-12.png"><br>
1359  <br>  Finally I am asked to select the partition to save.<br>
1360  recovery-iso-zip<br>  I just press ENTER again.
1361  &nbsp;&nbsp;&nbsp;&nbsp;Create an automated restore CD/DVD/USB drive</p>  </p>
1362  <p>I select "<font color="Red"><b>saveparts</b></font>" and press ENTER.<br> <br></p>  <H3><a name="bck-smb-11"></a>Starting the backup [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1363  <H3><a name="bck-smb-11"></a>Screen "Clonezilla - Opensource Clone System (OCS) | Mode: saveparts" [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>  <p><img src="images/backup-13.png"><br>
1364  <p>This is the name of the image file. You can insert anything you like, as long as it makes sence to you, so that you can distinguish the image file afterwards.<br>  Then the program will display the command that will be executed and will ask me to press ENTER. <br>
1365  <br>  Then I will be asked to confirm the operation by pressing <font color="Red"><b>y</b></font> and ENTER.
1366  I insert "<font color="Red"><b>win_img</b></font>" and press ENTER.</p>  <br>
1367  <H3><a name="bck-smb-12"></a>Next screen [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>  <br><img src="images/backup-14.png"><br>
1368  <p>Here I can select the partition that will be backed up. <br><br> I select "<font color="Red"><b>( ) hda1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ntfs</b></font>" by pressing SPACE and press ENTER, and ENTER again.<br>  After that, the backup begins<br>
1369  <br>  <br>
1370  Then a message is displayed asking for confirmation in order to continue. I just press <b>y</b>, and the backup procedure begins.</p>  <img src="images/backup-15.png"><br>
1371  <H2><a name="reboot"></a>Rebooting the system <span class="hideprint">[<a href="#backup-smb-top" title="go to top of the page">^</a>]</span></H2>  and when it's successfully completed, I press ENTER to get to the shell. Then, I execute the commands:</p>
 <p>When the backup is done, I get the following:</p>  
 <p class="newcode">(0) Poweroff<br>  
 (1) Reboot<br>  
 (2) Enter command line prompt<br>  
 (3) Start over<br>  
 [2]</p>  
 <p>Then I press ENTER and get to the shell. I execute the commands:</p>  
1372  <p class="newcode">sudo su -<br>  <p class="newcode">sudo su -<br>
1373  cd<br>  cd<br>
1374  umount -a<br>  umount -a<br>
1375  reboot<br><br></p>  reboot<br><br></p>
1376    <p>to reboot the system.</p>
1377  <a name="restore-top"></a>  <a name="restore-top"></a>
1378    
1379    
# Line 3144  Screenshots about Clonezilla - <a href=" Line 3215  Screenshots about Clonezilla - <a href="
3215  <ol>  <ol>
3216  <li><b>In Clonezilla Live</b><br><br>  <li><b>In Clonezilla Live</b><br><br>
3217  Type  Type
3218  <p class="newcode">less /live/image/README.txt</p>  <p class="newcode">less /README.txt</p>
3219  </li>  </li>
3220  <li><b>In SystemRescueCD</b><br><br>  <li><b>In SystemRescueCD</b><br><br>
3221  Type  Type
3222  <p class="newcode">less /mnt/livecd/README.txt</p>  <p class="newcode">less /livemnt/boot/README.txt</p>
3223  or  or
3224  <p class="newcode">links /mnt/livecd/README.html</p>  <p class="newcode">links /livemnt/boot/README.html</p>
3225  to view the html pages in links web browser.</li>  to view the html pages in links web browser.</li>
3226  </ol>  </ol>
3227  <H3><a name="searching"></a>Searching for text [<a href="#help-top" title="go to top of the page">^</a>]</H3>  <H3><a name="searching"></a>Searching for text [<a href="#help-top" title="go to top of the page">^</a>]</H3>

Legend:
Removed from v.38  
changed lines
  Added in v.71

webmaster@linux.gr
ViewVC Help
Powered by ViewVC 1.1.26