/[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 41 by sng, Mon May 17 23:45:40 2010 UTC revision 75 by sng, Tue Jun 1 13:23:50 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: 18/05/2010</H4></div>      <div style="position: absolute; right: 0px;"><H4>Last update: 01/06/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.5&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> [~ 370 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.5</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  <a name="General_boot_options" id="General_boot_options"></a><p><b> <span class="mw-headline">General boot options</span></b></p>  <a name="General_boot_options" id="General_boot_options"></a><p><b> General boot options</b></p>
548  <p>Press &lt;TAB&gt; to add additional options.  <p>Press &lt;TAB&gt; to add additional options (in SystemRescueCd-1.5 and more recent)
549  </p>  </p>
550  <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.  <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></ul>  </li><li><b>setkmap=kk</b>:  which defines the keymap to load  where <code>kk</code>  (example: <code>setkmap=de</code> for German keyboards). This way you won't be prompted for the keyboard configuration during the boot.
552  <p>During boot you will be prompted for the keyboard configuration, avoid this by using  </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>.
 </p>  
 <ul><li><b>setkmap=kk</b>:  which defines the keymap to load  where <code>kk</code>  (example: <code>setkmap=de</code> for German keyboards)  
 </li><li><b>root=/dev/xdnp</b>: the <a href="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" class="external text" title="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" rel="nofollow">root=&lt;device&gt; option</a>  boots an existing linux system. For example, if you have linux Gentoo installed on <code>/dev/sda6</code>,  use <code>rescuecd root=/dev/sda6</code> to start it. Keep in mind that you must use a 64bit kernel if your system is made of 64bit programs. This option works with LVM volumes. Use <code>rescuecd root=/dev/VolGroup00/LogVol00</code>. Support is also provided for <code>root=auto</code>, which scans all the block devices tfor a linux system. The first linux system found will be started. So with <code>root=auto</code> let you start the system installed from the CD-ROM in case you have problem with your boot loader or kernel. It's also possible to specify a partition using its <code>filesystem label</code> or <code>filesystem uuid</code>. If the label of the partition where linux is installed is <code>mylinux</code>, then boot it using <code>rescuecd root=LABEL=mylinux</code>. Similarly <code>root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7</code>. See <a href="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" class="external text" title="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" rel="nofollow">more details</a>.  
553  </li><li><b>initscript=service:action</b>: This options allows start/stop a service at boot time. For instance if you need the samba service to be started, you can boot with: <code>initscript=samba:start</code>. This does the same thing as <code>/etc/init.d/samba start</code>. Use this option multiple times for different services. All the actions that are supported by an initscript can be used.  </li><li><b>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.
554  </li><li><b>backstore=xxx</b>: SystemRescueCd comes with support for the <a href="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" class="external text" title="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" rel="nofollow">backing-stores</a>. A backing-store  saves all the changes you can make. so that you keep these changes the next time you boot it. By default, sysresccd automatically scan removable devices (eg: USB sticks) at boot time and uses the first backing-store it finds. A backing-store is not mandatory and it the scan fails it will store the files which change in memory. To disable the disks scan at boot time specify <code>backstore=off</code> on the boot command line. If you want to save your backing-store file on an harddisk,  boot with <code>backstore=alldev</code> to scan all devices (not just removable devices). The default location for backing-stores file is any file named <code>sysrcd.bs</code> located at the root of a disk which is often an USB stick. Change the path by using  <code>backstore=/sysrcd/mybackstore.bs</code>. See <a href="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" class="external text" title="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" rel="nofollow">backing-stores</a>.  </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>.
555  </li><li><b>isoloop=xxx</b>: Grub2 (currently in development: grub-1.98) provides a new feature to boot from an ISO image which is stored from the hard disk. If you put a copy of <code>systemrescuecd-x86-x.y.z.iso</code> on a partition that Grub2 can read then you can boot SystemRescueCd directly from the ISO image stored on your hard drive. This is very convenient if you frequently update SystemRescueCd and you want to boot it directly from Grub2. Grub2 knows what an ISO image is and it will load the kernel image (rescuecd/rescue64) and the initramfs (initram.igz) from the ISO into memory. It will then do its normal job and execute the kernel. The SystemRescueCd init script must then be aware that its <code>sysrcd.dat</code> file is in an ISO and not directly on the partition. For that reason, this <code>isoloop=xxx</code> boot option is required so you must use it in your <code>grub.cfg</code>. This option is only supported in SystemRescueCd-1.4.0 and more recent. This option specifies the path of the ISO image in the partition that grub considers as its root partition. It's important to understand that the path of the ISO image may be different from the path on your linux system. If you have a separate boot partition mounted on <code>/boot</code> and if you copy this ISO image to <code>/boot/sysrcd/systemrescuecd-x86-x.y.z.iso</code> then the option has to be <code>isoloop=/sysrcd/systemrescuecd-x86-x.y.z.iso</code>. This is because the boot partition is what Grub2 will consider as its root partition during the boot process. Please read <a href="http://www.sysresccd.org/Sysresccd-manual-en_Easy_install_SystemRescueCd_on_harddisk#Boot_the_ISO_image_from_the_disk_using_Grub2" title="Sysresccd-manual-en Easy install SystemRescueCd on harddisk">the section about isoloop</a> for more details.  </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.
556  </li></ul>  </li></ul>
557  <a name="Hardware.2C_drivers_and_troubleshooting_options" id="Hardware.2C_drivers_and_troubleshooting_options"></a><p><b><br> <span class="mw-headline">Hardware, drivers and troubleshooting options</span></b></p>  <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>
558  <ul><li><b>dodebug</b>: Enables verbose messages in linuxrc  <ul><li><b>dodebug</b>: Enables verbose messages in linuxrc
559  </li></ul>  </li></ul>
560  <ul><li><b>doload=xxx</b>: loads needed modules, multiple occurrences are permitted (example: <code>doload=3c59x</code>)  <ul><li><b>doload=xxx</b>: loads needed kernel modules, multiple comma separated occurrences are permitted (example: <code>doload=3c59x,e1000</code>)
561  </li><li><b>noload=xxx</b>: prevents loading modules, multiple occurrences are permitted (example: <code>noload=3c59x</code>). Use this option if you have a problem when the system loads a particular module.  </li><li><b>noload=xxx</b>: prevents loading kernel modules, multiple comma separated occurrences are permitted (example: <code>noload=3c59x,e1000</code>). Use this option if you have a problem when the system loads a particular module.
562  </li><li><b>nonet</b>: this will disable the network auto detection at startup  </li><li><b>nonet</b>: this will disable the network auto detection at startup
563  </li></ul>  </li></ul>
564  <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.  <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.
# Line 582  Available kernels (boot images):</p> Line 580  Available kernels (boot images):</p>
580  </li></ul>  </li></ul>
581  <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.  <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.
582  </li></ul>  </li></ul>
583  <a name="Network_configuration_and_remote_access" id="Network_configuration_and_remote_access"></a><p><b><br> <span class="mw-headline">Network configuration and remote access</span></b></p>  <a name="Network_configuration_and_remote_access" id="Network_configuration_and_remote_access"></a><p><b><br> Network configuration and remote access</b></p>
584  <ul><li><b>dodhcp</b>:  to request a DHCP server provide network attributes including an IP address, gateway... .  otherwise,  <ul><li><b>nonm</b>: to disable the Network-Manager service that conflicts with the standard network command line tools such as <code>ifconfig</code> and <code>ip</code>. You can use this option if you want to configure the network using these commands. This option is not necessary when SystemRescueCd is booting from the network since the service is automatically stopped in that case. This option requires SystemRescueCd-1.5.5 or more recent.
585    </li><li><b>dodhcp</b>: to request a DHCP server provide network attributes including an IP address, gateway...
586    </li><li><b>nodhcp</b>: never run the dhcp client in the initramfs boot script. May be useful if you use PXE boot on a computer with several ethernet interfaces. Support for this option is available in SystemRescueCd-1.5.5-beta2 and more recent
587  </li><li><b>ethx=ipaddr/cidr</b>: Sets the static IP address of all the ethernet interfaces on the system. The <code>/cidr</code> extension is optional. For instance, if you use option <code>ethx=192.168.0.1</code> on a machine with two ethernet adapters, both <code>eth0</code> and <code>eth1</code> will be configured with <code>192.168.0.1</code>. You can use the format <code>ethx=10.0.0.1/24</code> (using the cidr notation) if you don't use the default netmask.  </li><li><b>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.
588  </li><li><b>eth0=ipaddr/cidr</b>: This option is similar to <code>ethx=ipaddr/cidr</code> but it configures only one interface at a time.  To configure the network on a server that has two interfaces, use: <code>eth0=192.168.10.1/24 eth1=192.168.20.1</code>.  </li><li><b>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>.
589  </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.
590  </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>.
591  </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.
592  </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.
593  </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.
594  </li><li><b>nameif=xxx</b>: You can can <a href="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" class="external text" title="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" rel="nofollow">specify what interface name to give</a> to a particular interface using the mac address. You need SystemRescueCd-1.1.0 or newer to do that. Here is how you can specify which interface is using which mac address on a machine with two network interfaces: <code>nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64</code>. Be careful, you have to respect the separator (comma between the interfaces and exclamation marks between the name and the mac address).  </li><li><b>nameif=xxx</b>: You can can <a target="_blank" href="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" class="external text" title="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" rel="nofollow">specify what interface name to give</a> to a particular interface using the mac address. You need SystemRescueCd-1.1.0 or newer to do that. Here is how you can specify which interface is using which mac address on a machine with two network interfaces: <code>nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64</code>. Be careful, you have to respect the separator (comma between the interfaces and exclamation marks between the name and the mac address). You can also use the magic keyword <a target="_blank" href="http://www.sysresccd.org/forums/viewtopic.php?f=7&amp;t=2538&amp;start=0" class="external text" title="http://www.sysresccd.org/forums/viewtopic.php?f=7&amp;t=2538&amp;start=0" rel="nofollow">BOOTIF</a> with SystemRescueCd-1.5.4 and more recent when you boot from pxelinux. The pxeboot loader will set BOOTIF to the name of the interface used to boot. You can then use something like <code>nameif=eth0!BOOTIF</code> if you want the boot interface to be called <code>eth0</code> on a computer with several Ethernet interfaces.
595  </li></ul>  </li></ul>
596  <a name="Network_boot_using_PXE" id="Network_boot_using_PXE"></a><p><b><br> <span class="mw-headline">Network boot using PXE</span></b></p>  <a name="Network_boot_using_PXE" id="Network_boot_using_PXE"></a><p><b><br> Network boot using PXE</b></p>
597  <p>SystemRescueCd provides several options for booting from the network using PXE.  <p>SystemRescueCd provides several options for booting from the network using PXE.
598  These options can be combined with other network boot options such as <code>ethx</code> (cf previous section). See <a href="http://www.sysresccd.org/Sysresccd-manual-en_PXE_network_booting" class="external text" title="http://www.sysresccd.org/Sysresccd-manual-en_PXE_network_booting" rel="nofollow">PXE network booting</a> to get a global overview of SystemRescueCd and PXE and <a href="http://www.sysresccd.org/Sysresccd-manual-en_Manage_remote_windows_linux_servers_using_SystemRescueCd" class="external text" title="http://www.sysresccd.org/Sysresccd-manual-en_Manage_remote_windows_linux_servers_using_SystemRescueCd" rel="nofollow">Manage remote servers using PXE</a>.  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>.
599  </p><p>The second stage downloads the kernel + initramfs using DHCP/TFTP.  </p><p>The second stage downloads the kernel + initramfs using DHCP/TFTP.
600  </p><p>The third stage of the PXE boot process acquires the root files system.  </p><p>The third stage of the PXE boot process acquires the root files system.
601  </p><p>Several protocols are available.  </p><p>Several protocols are available.
# Line 605  These options can be combined with other Line 605  These options can be combined with other
605  </li><li><b>netboot=</b>nfs<b>://ip:/path</b>:  mount an NFSv3 directory. The NFS url must be the path of the directory that contains <code>sysrcd.dat</code>. Only NFSv3 can be used, NFSv4 is not supported. NFS it allows computers with smaller memory to boot SystemRescueCd from the network. After the boot process, the connection is required or you will loose the access to the root file system.  </li><li><b>netboot=</b>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.
606  </li><li><b>netboot=</b>nbd<b>://ip:port</b>:  connect to an NBD server  configured with <code>sysrcd.dat</code> on ip:port. NBD is easier to configure than NFS (only one TCP port involved) and it allows computers with smaller memort to boot SystemRescueCd from the network. After the boot process, the connection is required the access to the root system.  </li><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.
607  </li></ul>  </li></ul>
608  <p>For information on activating <b>speakup</b>, see the <a href="http://www.sysresccd.org/Speakup-info" title="Speakup-info">speakup info page</a>.  <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>.
609  </p>  </p>
610  <a name="Options_provided_for_autorun" id="Options_provided_for_autorun"></a><p><b><br> <span class="mw-headline">Options provided for autorun</span></b></p>  <a name="Options_provided_for_autorun" id="Options_provided_for_autorun"></a><p><b><br> Options provided for autorun</b></p>
611  <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>).  <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>).
612  </li><li><b>autoruns=[0-9]</b>: comma separated list of the autorun scrip to be run. For example <code>autoruns=0,2,7</code> the autorun sc <code>autorun0</code>, <code>autorun2</code>, <code>autorun7</code> are run. Use <code>autoruns=no</code> to disable all the autorun scripts with a number.  </li><li><b>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.
613  </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)
614  </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
# Line 619  These options can be combined with other Line 619  These options can be combined with other
619  </div>  </div>
620  <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>
621  <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>
622  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>
623  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>
624  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>"
625  </td></tr></table></div>  </td></tr></table></div>
# Line 629  please see the page "<a href="http://www Line 629  please see the page "<a href="http://www
629    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>
630  <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>
631  <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>
632  <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:
633  <ol>  <ol>
634  <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>.
635  <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.
# Line 746  fi Line 746  fi
746  <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>
747  <BR>  <BR>
748  </p>  </p>
749  <div class="otherpage"><pre>  <a name="live-initramfs"></a><div class="otherpage" style="overflow: auto;"><pre>
750  live-initramfs(7)  live-initramfs(7)
751  =================  =================
752  Name  Name
# Line 767  squashfs) is stored. If found, it will c Line 767  squashfs) is stored. If found, it will c
767  aufs, for Debian like systems to boot from.  aufs, for Debian like systems to boot from.
768  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,
769  although it will do no harm.  although it will do no harm.
770  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>.
771  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;
772  and Matt Zimmerman &lt;mdz@canonical.com&gt;.  and Matt Zimmerman &amp;lt;mdz@canonical.com&amp;gt;.
773  Boot options  Boot options
774  ------------  ------------
775  Here is the complete list of recognized boot parameters by live-initramfs.  Here is the complete list of recognized boot parameters by live-initramfs.
776   access=*ACCESS*::    access=*ACCESS*::
777  Set the accessibility level for physically or visually impared users. ACCESS  Set the accessibility level for physically or visually impared users. ACCESS
778  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
779  visual impairment, v3=blindness, m1=minor motor difficulties, m2=moderate motor  visual impairment, v3=blindness, m1=minor motor difficulties, m2=moderate motor
780  difficulties.  difficulties.
781   console=*TTY,SPEED*::    console=*TTY,SPEED*::
782  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:
783  "console=ttyS0,115200"  "console=ttyS0,115200"
784   debug::    debug::
785  Makes initramfs boot process more verbose.  Makes initramfs boot process more verbose.
786   fetch=*URL*::    fetch=*URL*::
787  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,
788  copying to ram and booting it.  copying to ram and booting it.
789   hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*::    hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*::
790  Those parameters lets you override values read from the config file.  Those parameters lets you override values read from the config file.
791   ignore_uuid    ignore_uuid
792  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
793  medium. live-initramfs may be told to generate a UUID by setting  medium. live-initramfs may be told to generate a UUID by setting
794  LIVE_GENERATE_UUID=1 when building the initramfs.  LIVE_GENERATE_UUID=1 when building the initramfs.
795   integrity-check::    integrity-check::
796  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
797  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
798  live media.  live media.
799   ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]    ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:
800      [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]]***::       [DEVICE]:[AUTOCONF] [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:
801         [DEVICE]:[AUTOCONF]]***::
802  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
803  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).
804  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
805  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).
806   ip[=**frommedia**]::    ip[=**frommedia**]::
807  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
808  system will use the (must be) media-preconfigured /etc/network/interfaces  system will use the (must be) media-preconfigured /etc/network/interfaces
809  instead.  instead.
810   {keyb|kbd-chooser/method}=**KEYBOARD**, {klayout|console-setup/layoutcode}=**LAYOUT**,    {keyb|kbd-chooser/method}=**KEYBOARD**, {klayout|console-setup/layoutcode}=**LAYOUT**,
811      {kvariant|console-setup/variantcode}=**VARIANT**,      {kvariant|console-setup/variantcode}=**VARIANT**, {kmodel|console-setup/modelcode}=
812      {kmodel|console-setup/modelcode}=**CODE**, koptions=**OPTIONS**::      **CODE**, koptions=**OPTIONS**::
813  Configure the running keyboard as specified, if this one misses live-initramfs  Configure the running keyboard as specified, if this one misses live-initramfs
814  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
815  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
816  console layout, variant, code, and options (no defaults).  console layout, variant, code, and options (no defaults).
817   live-getty::    live-getty::
818  This changes the auto-login on virtual terminals to use the (experimental)  This changes the auto-login on virtual terminals to use the (experimental)
819  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
820  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
821  on the serial console.  on the serial console.
822   {live-media|bootfrom}=**DEVICE**::    {live-media|bootfrom}=**DEVICE**::
823  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
824  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
825  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
826  for block devices is performed.  for block devices is performed.
827   {live-media-encryption|encryption}=**TYPE**::    {live-media-encryption|encryption}=**TYPE**::
828  live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase,  live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase,
829  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
830  loop-aes encryption type.  loop-aes encryption type.
831   live-media-offset=**BYTES**::    live-media-offset=**BYTES**::
832  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
833  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
834  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.
835   live-media-path=**PATH**::    live-media-path=**PATH**::
836  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
837  '/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
838  accordingly.  accordingly.
839   live-media-timeout=**SECONDS**::    live-media-timeout=**SECONDS**::
840  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
841  ready before giving up.  ready before giving up.
842   {locale|debian-installer/locale}=**LOCALE**::    {locale|debian-installer/locale}=**LOCALE**::
843  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
844  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
845  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 846  as "locale=en_US.UTF-8" was specified. I Line 847  as "locale=en_US.UTF-8" was specified. I
847  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
848  (keyb=us). Beside that facility, only UTF8 locales are supported by  (keyb=us). Beside that facility, only UTF8 locales are supported by
849  live-initramfs.  live-initramfs.
850   module=**NAME**::    module=**NAME**::
851  Instead of using the default optional file "filesystem.module" (see below)  Instead of using the default optional file "filesystem.module" (see below)
852  another file could be specified without the extension ".module"; it should be  another file could be specified without the extension ".module"; it should be
853  placed on "/live" directory of the live medium.  placed on "/live" directory of the live medium.
854   netboot[=**nfs**|**cifs**]::    netboot[=**nfs**|**cifs**]::
855  This tells live-initramfs to perform a network mount. The parameter "nfsroot="  This tells live-initramfs to perform a network mount. The parameter "nfsroot="
856  (with optional "nfsopts="), should specify where is the location of the root  (with optional "nfsopts="), should specify where is the location of the root
857  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.
858   nfsopts=::    nfsopts=::
859  This lets you specify custom nfs options.  This lets you specify custom nfs options.
860   noautologin::    noautologin::
861  This parameter disables the automatic terminal login only, not touching gdk/kdm.  This parameter disables the automatic terminal login only, not touching gdk/kdm.
862   noxautologin::    noxautologin::
863  This parameter disables the automatic login of gdm/kdm only, not touching  This parameter disables the automatic login of gdm/kdm only, not touching
864  terminals.  terminals.
865   nofastboot::    nofastboot::
866  This parameter disables the default disabling of filesystem checks in  This parameter disables the default disabling of filesystem checks in
867  /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
868  be checked at boot time, use this parameter, otherwise they are skipped.  be checked at boot time, use this parameter, otherwise they are skipped.
869   nopersistent::    nopersistent::
870  disables the "persistent" feature, useful if the bootloader (like syslinux) has  disables the "persistent" feature, useful if the bootloader (like syslinux) has
871  been installed with persistent enabled.  been installed with persistent enabled.
872   noprompt    noprompt
873  Do not prompt to eject the CD on reboot.  Do not prompt to eject the CD on reboot.
874   nosudo::    nosudo::
875  This parameter disables the automatic configuration of sudo.  This parameter disables the automatic configuration of sudo.
876   swapon::    swapon::
877  This parameter enables usage of local swap partitions.  This parameter enables usage of local swap partitions.
878   nouser::    nouser::
879  This parameter disables the creation of the default user completely.  This parameter disables the creation of the default user completely.
880   noxautoconfig::    noxautoconfig::
881  This parameter disables Xorg auto-reconfiguration at boot time. This is valuable  This parameter disables Xorg auto-reconfiguration at boot time. This is valuable
882  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,
883  premade xorg.conf in your live system.  premade xorg.conf in your live system.
884   persistent[=nofiles]::    persistent[=nofiles]::
885  live-initramfs will look for persistent and snapshot partitions or files labeled  live-initramfs will look for persistent and snapshot partitions or files labeled
886  "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,
887  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 889  tried to be updated on reboot/shutdown. Line 890  tried to be updated on reboot/shutdown.
890  informations. If "nofiles" is specified, only filesystems with matching labels  informations. If "nofiles" is specified, only filesystems with matching labels
891  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
892  files. This results in shorter boot times.  files. This results in shorter boot times.
893   {preseed/file|file}=**FILE**::    {preseed/file|file}=**FILE**::
894  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
895  database.  database.
896   package/question=**VALUE**::    package/question=**VALUE**::
897  All debian installed packages could be preseeded from command-line that way,  All debian installed packages could be preseeded from command-line that way,
898  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
899  this case.  this case.
900   quickreboot::    quickreboot::
901  This option causes live-initramfs to reboot without attempting to eject the  This option causes live-initramfs to reboot without attempting to eject the
902  media and without asking the user to remove the boot media.  media and without asking the user to remove the boot media.
903   showmounts::    showmounts::
904  This parameter will make live-initramfs to show on "/" the ro filesystems  This parameter will make live-initramfs to show on "/" the ro filesystems
905  (mostly compressed) on "/live". This is not enabled by default because could  (mostly compressed) on "/live". This is not enabled by default because could
906  lead to problems by applications like "mono" which store binary paths on  lead to problems by applications like "mono" which store binary paths on
907  installation.  installation.
908   textonly    textonly
909  Start up to text-mode shell prompts, disabling the graphical user interface.  Start up to text-mode shell prompts, disabling the graphical user interface.
910   timezone=**TIMEZONE**::    timezone=**TIMEZONE**::
911  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
912  to your local zone, e.g. Europe/Zurich.  to your local zone, e.g. Europe/Zurich.
913   todisk=**DEVICE**::    todisk=**DEVICE**::
914  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
915  media to the specified device before mounting the root filesystem. It probably  media to the specified device before mounting the root filesystem. It probably
916  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
917  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
918  time.  time.
919   toram::    toram::
920  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
921  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
922  of ram, according to the space used by the read-only media.  of ram, according to the space used by the read-only media.
923   union=**aufs**|**unionfs**::    union=**aufs**|**unionfs**::
924  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
925  unionfs.  unionfs.
926   utc=**yes**|**no**::    utc=**yes**|**no**::
927  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
928  can change or explicitly set it with this parameter.  can change or explicitly set it with this parameter.
929   xdebconf::    xdebconf::
930  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
931  standard procedure (experimental).  standard procedure (experimental).
932   xvideomode=**RESOLUTION**::    xvideomode=**RESOLUTION**::
933  Doesn't do xorg autodetection, but enforces a given resolution.  Doesn't do xorg autodetection, but enforces a given resolution.
934  Files  Files
935  -----  -----
936   /etc/live.conf    /etc/live.conf
937  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).
938    /live/filesystem.module     /live/filesystem.module
939  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
940  carriage-return-separated file names corresponding to disk images in the "/live"  carriage-return-separated file names corresponding to disk images in the "/live"
941  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 942  root aufs, and they will be loaded in th Line 943  root aufs, and they will be loaded in th
943  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
944  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
945  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.
946  /etc/live-persistence.binds   /etc/live-persistence.binds
947  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)
948  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
949  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 957  live-webhelper(7) Line 958  live-webhelper(7)
958  Bugs  Bugs
959  ----  ----
960  Report bugs against live-initramfs  Report bugs against live-initramfs
961  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>.
962  Homepage  Homepage
963  --------  --------
964  More information about the Debian Live project can be found at  More information about the Debian Live project can be found at
965  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
966  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>.
967  Authors  Authors
968  -------  -------
969  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;
970  for the Debian project.  for the Debian project.
971  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>.
972  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;
973  and Matt Zimmerman &lt;mdz@canonical.com&gt;.</pre>  and Matt Zimmerman &amp;lt;mdz@canonical.com&amp;gt;.
974    </pre>
975  </div>  </div>
976  <a name="clonezilla-top"></a>  <a name="clonezilla-top"></a>
977  <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 1014  If, on the other hand, you just want to Line 1016  If, on the other hand, you just want to
1016  <p class="newcode">ocs-live</p>  <p class="newcode">ocs-live</p>
1017  <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>
1018  <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>
1019  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>  
1020  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>
1021  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>
1022  <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 1045  Fianlly I should say that <b>Clonezilla Line 1046  Fianlly I should say that <b>Clonezilla
1046  <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>
1047  <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>
1048  <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>
1049    <p class="newcode"><a name="rescue"></a><font color="Red">-rescue&nbsp;Continue reading next one when disk blocks read errors</font></p>
1050    <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>
1051    <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>
1052    <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>
1053  <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>
1054  <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>
1055  <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>
1056  <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>
1057  <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>
1058  <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>
1059    -z1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;gzip compression (fast with a smaller image)<br>
1060    -z2p&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use parallel bzip2 compression (testing), for multicore/CPU<br>
1061  -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>
1062  -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>
1063  -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>
1064    -z5p&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use_parallel_xz_compression_(testing),_for_multicore/CPU<br>
1065    -z5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;xz_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2)<br>
1066    -z6p&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use_parallel_lzip_compression_(testing),_for_multicore/CPU<br>
1067    -z6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;lzip_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2)<br>
1068  -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>
1069  <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>
1070  <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>
1071  <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>
1072  <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>
1073    <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>
1074    <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>
1075    <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>
1076  <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>
1077  <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>
1078    <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>
1079  <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>
1080  <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>
1081  -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 1096  Fianlly I should say that <b>Clonezilla Line 1111  Fianlly I should say that <b>Clonezilla
1111  <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>
1112  <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>
1113  <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>
1114    <p class="newcode"><a name="ignore-crc"></a><font color="Red">-icrc&nbsp;Ignore CRC checking of partclone</font></p>
1115    <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>
1116  <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>
1117  <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>
1118  <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 1125  Fianlly I should say that <b>Clonezilla Line 1142  Fianlly I should say that <b>Clonezilla
1142  <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>
1143  <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>
1144  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>
1145  <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>
1146  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>
1147  &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>
1148  &nbsp;&nbsp;2. Try to choose<br>  &nbsp;&nbsp;2. Try to choose<br>
# Line 1155  Please boot into Windows TWICE, or use ' Line 1172  Please boot into Windows TWICE, or use '
1172  prompt, execute the command:</p>  prompt, execute the command:</p>
1173  <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>
1174  <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>
1175  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>
1176    <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>
1177  <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>
1178  <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>  
1179  <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>
1180  <p class="newcode" style="margin-left: 0pt;">sudo su -<br>  <p class="newcode" style="margin-left: 0pt;">sudo su -<br>
1181  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 1169  ocs-live</p> Line 1186  ocs-live</p>
1186  </ul>  </ul>
1187  <a name="backup-top"></a>  <a name="backup-top"></a>
1188  <H2 style="font-size: 2em;"><a name="backup-intro"></a>Getting backups <span class="hideprint">[<a href="#backup-top" title="go to top of the page">^</a>]</span></H2>  <H2 style="font-size: 2em;"><a name="backup-intro"></a>Getting backups <span class="hideprint">[<a href="#backup-top" title="go to top of the page">^</a>]</span></H2>
1189  <p>In this page I will demonstrate the creation of an image file by getting a backup of a virtual partition (<b>/dev/<font color="Red">hdb1</font></b>). The image file will be saved in another virtual partition (<b>/dev/<font color="Red">hda1</font></b>).<br></p>  <p>In this page I will demonstrate the creation of an image file by getting a backup of a virtual partition (<b>/dev/<font color="Red">sdb1</font></b>). The image file will be saved in another virtual partition (<b>/dev/<font color="Red">sda1</font></b>).<br></p>
1190  <p>  <p>
1191  The first thing you do when you want to get a backup of a disk/partition, is make sure both the souce (to be backed up) and target (to hold the image file) partitions are in excellent condition (error free). This is the logical thing to do, cause I wouldn't want to backup a corrupt partition, or end up with a corrupt image file.<br>  The first thing you do when you want to get a backup of a disk/partition, is make sure both the souce (to be backed up) and target (to hold the image file) partitions are in excellent condition (error free). This is the logical thing to do, cause I wouldn't want to backup a corrupt partition, or end up with a corrupt image file.<br>
1192  <br>  <br>
# Line 1179  Having done all of the above, I am ready Line 1196  Having done all of the above, I am ready
1196  <br>  <br>
1197  </p>  </p>
1198  <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>
1199  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.3-27</b>  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.5-17</b>
1200  </td></tr></table></div>  </td></tr></table></div>
1201  <H2><a name="backup"></a>Getting the backup <span class="hideprint">[<a href="#backup-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="backup"></a>Getting the backup <span class="hideprint">[<a href="#backup-top" title="go to top of the page">^</a>]</span></H2>
1202  <H3><a name="bck-0"></a>Clonezilla-SysRescCD starting screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-0"></a>Clonezilla-SysRescCD starting screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
# Line 1223  I select "<font color="Red"><b>local_dev Line 1240  I select "<font color="Red"><b>local_dev
1240  <H3><a name="bck-7"></a>Next screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-7"></a>Next screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1241  <p>This is where I choose the location of the image file. It will be saved at the root directory of the selected partition.<br><br>  <p>This is where I choose the location of the image file. It will be saved at the root directory of the selected partition.<br><br>
1242  <img src="images/backup-06.png"><br>  <img src="images/backup-06.png"><br>
1243  I select partition <font color="Red"><b>hda1</b></font> and press ENTER.<br>  I select partition <font color="Red"><b>sda1</b></font> and press ENTER.<br>
1244  <br>  <br>
1245  <img src="images/backup-07.png"><br>  <img src="images/backup-07.png"><br>
1246  and then ENTER again.</p>  and then ENTER again.</p>
1247  <p><img src="images/backup-08.png"><br>  <p><img src="images/backup-08.png"><br>
1248  This screen displays the mounting result.<br>  This screen displays the mounting result.<br>
1249  As we can see, <font color="Red"><b>/dev/hda1</b></font> has been successfully mounted under <b>/tmp/local-dev</b>.</p>  As we can see, <font color="Red"><b>/dev/sda1</b></font> has been successfully mounted under <b>/tmp/local-dev</b>.</p>
1250  <H3><a name="bck-7a"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-7a"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1251  <p><img src="images/backup-09.png">  <p><img src="images/backup-09.png">
1252  <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>  <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>
# Line 1241  I select "<font color="Red"><b>savedisk< Line 1258  I select "<font color="Red"><b>savedisk<
1258  <H3><a name="bck-9"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-9"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1259  <p><img src="images/backup-11.png"><br>  <p><img src="images/backup-11.png"><br>
1260  In this screen I select the image name.<br>  In this screen I select the image name.<br>
1261  I type "Backup_5-2010_hdb", which in my opinion is more informative name than the default.  I type "Backup_22-2010_sdb", which in my opinion is more informative name than the default.
1262  </p>  </p>
1263  <H3><a name="bck-10"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-10"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1264  <p><img src="images/backup-12.png"><br>  <p><img src="images/backup-12.png"><br>
# Line 1257  Then I will be asked to confirm the oper Line 1274  Then I will be asked to confirm the oper
1274  After that, the backup begins<br>  After that, the backup begins<br>
1275  <br>  <br>
1276  <img src="images/backup-15.png"><br>  <img src="images/backup-15.png"><br>
1277  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>
1278  </p>  <p class="newcode">sudo su -<br>
1279    cd<br>
1280    umount -a<br>
1281    reboot<br><br></p>
1282    <p>to reboot the system.</p>
1283  <a name="backup-smb-top"></a>  <a name="backup-smb-top"></a>
1284  <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>
1285  <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>
1286  Using <b>Samba</b> you will be able to mount a Windows share resource (or Samba share resource), from within <b>Clonezilla Live</b>, and save the image file there. Then you can boot that PC using <b>SystemRescueCD</b> and create a restore DVD.<br><br>  Using <b>Samba</b> you will be able to mount a Windows share resource (or Samba share resource), from within <b>Clonezilla Live</b>, and save the image file there. Then you can boot that PC using <b>SystemRescueCD</b> and create a restore DVD.<br><br>
1287  In this page I will demonstrate the creation of an image file by getting a backup of my Windows partition (<b>/dev/<font color="Red">hda1</font></b>). The image file will be save in my Samba server which is my laptop (ip: <b><font color="Red">10.0.0.2</font></b>, Windows share resource name: <b><font color="Red">data</font></b>).  In this page I will demonstrate the creation of an image file by getting a backup of my second disk (<b>/dev/<font color="Red">sdb</font></b>). The image file will be save in my Samba server which is my laptop (ip: <b><font color="Red">10.0.0.3</font></b>, Windows share resource name: <b><font color="Red">all_my_images</font></b>).
1288  </p>  </p>
1289  <H3><a name="what-is"></a>What is Samba? [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>  <H3><a name="what-is"></a>What is Samba? [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1290  <p>We read at <a href="http://us1.samba.org/samba/" target="_blank">http://us1.samba.org/samba/</a>:</p>  <p>We read at <a href="http://us1.samba.org/samba/" target="_blank">http://us1.samba.org/samba/</a>:</p>
# Line 1287  This is the name of the <b>Windows share Line 1308  This is the name of the <b>Windows share
1308  </p>  </p>
1309  <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>
1310  <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>
1311  <p>I select "<font color="Red"><b>Start Clonezilla</b></font>" and press ENTER.</p>  <p><img src="images/backup-03.png"><br>
1312    I select "<font color="Red"><b>Start Clonezilla</b></font>" and press ENTER.
1313    </p>
1314  <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>
1315  <p>I select "<font color="Red"><b>device-image</b></font>" and press ENTER.</p>  <p><img src="images/backup-04.png"><br>
1316  <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>
1317    </p>
1318    <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>
1319  <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.
1320  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>
1321  <br>  <br>
1322    <img src="images/backup-smb-05.png"><br>
1323  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>
1324  <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>
1325  <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>
1326    <img src="images/backup-smb-06.png"><br>
1327    I type "<font color="Red"><b>10.0.0.3</b></font>" and press ENTER.</p>
1328  <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>
1329  <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>
1330    <img src="images/backup-smb-07.png"><br>
1331    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>
1332  <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>
1333  <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>
1334    <img src="images/backup-smb-08.png"><br>
1335    I type "<font color="Red"><b>spiros</b></font>" and press ENTER.</p>
1336  <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>
1337  <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>
1338  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>
1339    At this point I'm informed I'm going to be asked for the password for user <b><font color="Red"><b>spiros</b></font></b>.<br><br>
1340    <img src="images/backup-smb-10.png"><br>
1341    I will be able to continue only after entering it correctly.<br><br>
1342    <img src="images/backup-smb-11.png"></p>
1343  <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>
1344  <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">
1345  <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>
1346  <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>
1347  <p>savedisk<br>  <p>Here I can select the desired operation.<br>
1348  &nbsp;&nbsp;&nbsp;&nbsp;Save entire disk to image<br>  <br>
1349  <br>  <img src="images/backup-10.png"><br>
1350  restoredisk<br>  I select "<font color="Red"><b>savedisk</b></font>" and press ENTER.<br> <br></p>
1351  &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>
1352  <br>  <p><img src="images/backup-11.png"><br>
1353  saveparts<br>  In this screen I select the image name.<br>
1354  &nbsp;&nbsp;&nbsp;&nbsp;Save partition to image<br>  I type "Backup_22-2010_sdb", which in my opinion is more informative name than the default.
1355  <br>  </p>
1356  restoreparts<br>  <H3><a name="bck-smb-10"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1357  &nbsp;&nbsp;&nbsp;&nbsp;Restore partition from image<br>  <p><img src="images/backup-12.png"><br>
1358  <br>  Finally I am asked to select the partition to save.<br>
1359  recovery-iso-zip<br>  I just press ENTER again.
1360  &nbsp;&nbsp;&nbsp;&nbsp;Create an automated restore CD/DVD/USB drive</p>  </p>
1361  <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>
1362  <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>
1363  <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>
1364  <br>  Then I will be asked to confirm the operation by pressing <font color="Red"><b>y</b></font> and ENTER.
1365  I insert "<font color="Red"><b>win_img</b></font>" and press ENTER.</p>  <br>
1366  <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>
1367  <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>
1368  <br>  <br>
1369  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>
1370  <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>  
1371  <p class="newcode">sudo su -<br>  <p class="newcode">sudo su -<br>
1372  cd<br>  cd<br>
1373  umount -a<br>  umount -a<br>
1374  reboot<br><br></p>  reboot<br><br></p>
1375    <p>to reboot the system.</p>
1376  <a name="restore-top"></a>  <a name="restore-top"></a>
1377    
1378    
# Line 1723  mount /dev/<font color="Green">sdc1</fon Line 1753  mount /dev/<font color="Green">sdc1</fon
1753  <p class="newcode">eject /dev/dvd</p>  <p class="newcode">eject /dev/dvd</p>
1754  <p><b>Note:</b> If your drive can't reload the disc, insert the disc back right after ejecting it.</p>  <p><b>Note:</b> If your drive can't reload the disc, insert the disc back right after ejecting it.</p>
1755  <p>Finally, add the image file to the disc:</p>  <p>Finally, add the image file to the disc:</p>
1756  <p class="newcode">growisofs -M /dev/dvd -R -J -V "<font color="Green">Backup_5-2010_hdb</font>" --publisher "<font color="Green">Your Name</font>" -graft-points /<font color="Green">Backup_5-2010_hdb</font>/=/media/usb/<font color="Green">Backup_5-2010_hdb</font></p>  <p class="newcode">growisofs -M /dev/dvd -R -J -V "<font color="Green">Backup_5-2010_hdb</font>" \<br>
1757    --publisher "<font color="Green">Your Name</font>" -graft-points \<br>
1758    /<font color="Green">Backup_5-2010_hdb</font>/=/media/usb/<font color="Green">Backup_5-2010_hdb</font></p>
1759  <p><b>Note:</b> In the command replace <b><font color="Green">Your Name</font></b> with anything you want to be the publisher ID of the disc. If you don't want the disc to have any publisher ID, run this command instead:</p>  <p><b>Note:</b> In the command replace <b><font color="Green">Your Name</font></b> with anything you want to be the publisher ID of the disc. If you don't want the disc to have any publisher ID, run this command instead:</p>
1760  <p class="newcode">growisofs -M /dev/dvd -R -J -V "<font color="Green">Backup_5-2010_hdb</font>" -graft-points /<font color="Green">Backup_5-2010_hdb</font>/=/media/usb/<font color="Green">Backup_5-2010_hdb</font></p>  <p class="newcode">growisofs -M /dev/dvd -R -J -V "<font color="Green">Backup_5-2010_hdb</font>" \<br>
1761    -graft-points /<font color="Green">Backup_5-2010_hdb</font>/=/media/usb/<font color="Green">Backup_5-2010_hdb</font></p>
1762  <p><img src="images/restore-20.png"><br>Here we can see the boot menu of the disc.</p>  <p><img src="images/restore-20.png"><br>Here we can see the boot menu of the disc.</p>
1763  <H2><a name="zip"></a>ZIP file instructions <span class="hideprint">[<a href="#restore-burn-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="zip"></a>ZIP file instructions <span class="hideprint">[<a href="#restore-burn-top" title="go to top of the page">^</a>]</span></H2>
1764  <p>Often the image file is way too big to fit to even 8 GB DVD. Some people may also want to be able to overwrite the backup when it becomes outdated. In addition, netbooks don't have optical drives at all.</p>  <p>Often the image file is way too big to fit to even 8 GB DVD. Some people may also want to be able to overwrite the backup when it becomes outdated. In addition, netbooks don't have optical drives at all.</p>
# Line 3184  Screenshots about Clonezilla - <a href=" Line 3217  Screenshots about Clonezilla - <a href="
3217  <ol>  <ol>
3218  <li><b>In Clonezilla Live</b><br><br>  <li><b>In Clonezilla Live</b><br><br>
3219  Type  Type
3220  <p class="newcode">less /live/image/README.txt</p>  <p class="newcode">less /README.txt</p>
3221  </li>  </li>
3222  <li><b>In SystemRescueCD</b><br><br>  <li><b>In SystemRescueCD</b><br><br>
3223  Type  Type

Legend:
Removed from v.41  
changed lines
  Added in v.75

webmaster@linux.gr
ViewVC Help
Powered by ViewVC 1.1.26