/[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 127 by sng, Thu Sep 16 18:15:05 2010 UTC revision 164 by sng, Sat Apr 9 21:34:35 2011 UTC
# Line 3  Line 3 
3  <head>  <head>
4  <link rel="alternate" type="application/rss+xml" title="RSS" href="http://clonezilla-sysresccd.hellug.gr/clonezilla-sysresccd.rss">  <link rel="alternate" type="application/rss+xml" title="RSS" href="http://clonezilla-sysresccd.hellug.gr/clonezilla-sysresccd.rss">
5  <link rel="shortcut icon" href="favicon.ico">  <link rel="shortcut icon" href="favicon.ico">
6  <title>Clonezilla-SysRescCD - Wellcome</title>  <title>Clonezilla-SysRescCD - Welcome</title>
7    <style type="text/css">    <style type="text/css">
8      body { font-family: Arial, 'sans serif';  color: black;  font-size: 12pt; background : fixed no-repeat; background-color: #333333; padding: 0; margin: 0; margin-top: 5px;  margin-bottom: 5px; }      body { font-family: Arial, 'sans serif';  color: black;  font-size: 12pt; background : fixed no-repeat; background-color: #333333; padding: 0; margin: 0; margin-top: 5px;  margin-bottom: 5px; }
9        
# Line 62  Line 62 
62      #content .red{color: white; background-color: Red; font-weight: bold;}      #content .red{color: white; background-color: Red; font-weight: bold;}
63      #lphp{text-align: right; padding-left: 10px; padding-right: 10px; padding-top: 50px; float: right;}      #lphp{text-align: right; padding-left: 10px; padding-right: 10px; padding-top: 50px; float: right;}
64      #lphp a{padding-left: 5px;}      #lphp a{padding-left: 5px;}
65        #warning { margin: 5px; padding: .4em; background-color: Red; color: White; align: center; font-weight: bold; border-width: 2px; border-color: white; border-style: solid; }
66        #warning a { color: white; font-weight: bold; text-decoration: underline;  }
67    </style>    </style>
68    <link href="warning.css" rel="stylesheet" type="text/css" />
69    <!--
70    The file waring.css exists only in the root of the site
71    and it hides the UNSTABLE warnings. Its contents are
72        #warning { display: none; }
73    -->
74  <META NAME="Keywords" CONTENT="multiboot Multi Boot bootable cd rescue clonezilla sysresccd backup restore samba">  <META NAME="Keywords" CONTENT="multiboot Multi Boot bootable cd rescue clonezilla sysresccd backup restore samba">
75  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
76  </head>  </head>
77  <body>  <body>
78    <div id="warning" align="center">
79    WARNING<br>
80    This is the UNSTABLE version of Clonezilla-SysRescCD<br>
81    To access our current stable version, please click <a href="../index.html">here</a>
82    </div>
83  <div id="header">  <div id="header">
84  <div id="lphp" style=""><a target="_blank" title="Display all in one long page" href="onepage.html"><img src="images/chain.png" border="0" /></a><a target="_blank" title="Display printable page" href="printable.php"><img src="images/print_it.png" border="0" /></a></div>  <div id="lphp" style=""><a target="_blank" title="Display all in one long page" href="onepage.html"><img src="images/chain.png" border="0" /></a><a target="_blank" title="Display printable page" href="printable.php"><img src="images/print_it.png" border="0" /></a></div>
85  <H2>Clonezilla-SysRescCD</H2>  <H2>Clonezilla-SysRescCD</H2>
86  <H3>Wellcome</H3>  <H3>Welcome</H3>
87    <div style="margin:0; padding: 3px; width: 980; position relative;">    <div style="margin:0; padding: 3px; width: 980; position relative;">
88      <div style="position: absolute; left: 0px;"><H4>15/09/2010 - v 3.1.0</H4></div>      <div style="position: absolute; left: 0px;"><H4>30/09/2010 - v 3.2.0</H4></div>
89      <div style="position: absolute; right: 0px;"><H4>Last update: 16/09/2010</H4></div>      <div style="position: absolute; right: 0px;"><H4>Last update: 09/04/2011</H4></div>
90    </div>    </div>
91  </div>  </div>
92  <div id="linkline">  <div id="linkline">
# Line 131  Well, I started this project because I w Line 144  Well, I started this project because I w
144  <tr><td class="bordertable"  colspan="4"><b>Release table</b></td></tr>  <tr><td class="bordertable"  colspan="4"><b>Release table</b></td></tr>
145  <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>
146  <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>
147    <tr><td  class="bordertable" >XX/XX/10</td><td  class="bordertable" >3.2.0</td><td  class="bordertable" >1.2.8-23&nbsp;(mod)</td><td  class="bordertable" >2.0.1</td>
148  <tr><td  class="bordertable" >15/09/10</td><td  class="bordertable" >3.1.0</td><td  class="bordertable" >1.2.5-35&nbsp;(mod)</td><td  class="bordertable" >1.6.0</td>  <tr><td  class="bordertable" >15/09/10</td><td  class="bordertable" >3.1.0</td><td  class="bordertable" >1.2.5-35&nbsp;(mod)</td><td  class="bordertable" >1.6.0</td>
149  </tr>  </tr>
150  <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>
# Line 161  Well, I started this project because I w Line 175  Well, I started this project because I w
175  <H2><a name="changelog"></a>Changelog <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="changelog"></a>Changelog <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>
176  <table class="bordertable"  cellpadding="5">  <table class="bordertable"  cellpadding="5">
177  <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>
178    <tr><td class="bordertable" width="10" valign="top"><a name="3.2.0"></a>3.2.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">
179    -&nbsp;<b>Clonezilla Live</b> updated to version 1.2.8-23<br>
180    -&nbsp;<b>SystemRescueCD</b> updated to version 2.0.1<br>
181    -&nbsp;Fixed the splash image installation bug present in 3.1.0<br>
182    &nbsp;&nbsp;Also, a filename relative to /home/partimag, can now be used<br>
183    -&nbsp;Script imginfo can display extended info (command line parameter -e)<br>
184    &nbsp;&nbsp;Extended info is: image size and disk model<br>
185    </td></tr>
186    <tr><td class="bordertable" width="10" valign="top"></td><td class="bordertable" width="10" valign="top">Package</td><td class="bordertable">
187    -&nbsp;Added -d command parameter to scrpit create-clonezilla-sysresccd<br>
188    &nbsp;&nbsp;This way the temporary and output folder can be specified<br>
189    -&nbsp;Using $HOME instead of /root in scrpit create-clonezilla-sysresccd<br>
190    -&nbsp;Script create-clonezilla-sysrescc can now download the original<br>
191    &nbsp;&nbsp;ISO files (parameter -g), making easier to build Clonezilla-SysRescCD
192    </td></tr>
193  <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">
194  -&nbsp;<b>Clonezilla Live</b> updated to version 1.2.5-35<br>  -&nbsp;<b>Clonezilla Live</b> updated to version 1.2.5-35<br>
195  -&nbsp;<b>SystemRescueCD</b> updated to version 1.6.0<br>  -&nbsp;<b>SystemRescueCD</b> updated to version 1.6.0<br>
196  - Three <b>Clonezilla-SysRescCD</b> flavours are now available,<br>  - Three <b>Clonezilla-SysRescCD</b> flavours are now available,<br>
197  &nbsp;&nbsp;one for each architecture (i486,i686,amd64)<br>  &nbsp;&nbsp;one for each architecture (<a href="download.html#download-file" target="_blank">more information</a>)<br>
198  -&nbsp;<b>Super Grub Disk</b> updated to version 0.9799<br>  -&nbsp;<b>Super Grub Disk</b> updated to version 0.9799<br>
199  -&nbsp;Added <b>Super Grub Disk 2</b> version 1.98s<br>  -&nbsp;Added <b>Super Grub Disk 2</b> version 1.98s<br>
200  -&nbsp;<b>Smart Boot Manager</b> was added to the Tools section<br>  -&nbsp;<b>Smart Boot Manager</b> was added to the Tools section<br>
# Line 310  More info: <a href="reloc-img.html">Rest Line 339  More info: <a href="reloc-img.html">Rest
339  <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>
340  <p>  <p>
341  <!--Whenever possible I will provide a link to the CD created using profile 0 (full CD)<br><br>  <!--Whenever possible I will provide a link to the CD created using profile 0 (full CD)<br><br>
342  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> [~ 6.3 MB]<br>  Installation package: <a href="http://clonezilla-sysresccd.hellug.gr/create-clonezilla-sysresccd-3.2.0".tar.gz" target="_blank">create-clonezilla-sysresccd-3.2.0.tar.gz</a> [~ 6.1 MB]<br>
343  <!--Torrent: <a href="http://thepiratebay.org/tor/4272742" target="_blank">The Pirate Bay</a> | <a href="http://linuxtracker.org/index.php?page=torrent-details&id=4b0f13a25440e3d34fb700cc0ff884c28a73fadf" target="_blank">Linux Tracker</a><br>  <!--Torrent: <a href="http://thepiratebay.org/tor/4272742" target="_blank">The Pirate Bay</a> | <a href="http://linuxtracker.org/index.php?page=torrent-details&id=4b0f13a25440e3d34fb700cc0ff884c28a73fadf" target="_blank">Linux Tracker</a><br>
344  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> [~ ISO_SIZEB]<br>  ISO file: <a href="http://clonezilla-sysresccd.hellug.gr/clonezilla-sysresccd-full-mod-3.2.0.iso" target="_blank">clonezilla-sysresccd-full-mod-3.2.0.iso</a> [~ ISO_SIZEB]<br>
345  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>
346  ISO file md5sum: <b><i>"MD5SUM"</i></b></p>  ISO file md5sum: <b><i>"MD5SUM"</i></b></p>
347  -->  -->
# Line 362  The ISO 9660 filesystem is encapsulated Line 391  The ISO 9660 filesystem is encapsulated
391  Incorrect use of any raw disk writing tool could cause your<br> operating system (GNU/Linux / Windows) <b>not to boot</b>.<br><br> Confirm the command before you run it.<br></td></tr></table></div>  Incorrect use of any raw disk writing tool could cause your<br> operating system (GNU/Linux / Windows) <b>not to boot</b>.<br><br> Confirm the command before you run it.<br></td></tr></table></div>
392  <p>So, from any linux box, assuming <b>Clonezilla-SysRescCD</b> iso file is in your home directory, and your USB device name is <b><font color="Green">sdc4</font></b>, you just execute the commands:</p>  <p>So, from any linux box, assuming <b>Clonezilla-SysRescCD</b> iso file is in your home directory, and your USB device name is <b><font color="Green">sdc4</font></b>, you just execute the commands:</p>
393  <p class="newcode">umount /dev/<font color="Green">sdc4</font><br>  <p class="newcode">umount /dev/<font color="Green">sdc4</font><br>
394  dd if=~/clonezilla-sysresccd-full-mod-3.1.0.iso of=/dev/<font color="Green">sdc</font> bs=512</p>  dd if=~/clonezilla-sysresccd-full-mod-3.2.0.iso of=/dev/<font color="Green">sdc</font> bs=512</p>
395  <p>And that's it. Your usb device is ready to boot!!!</p>  <p>And that's it. Your usb device is ready to boot!!!</p>
396  <H3><a name="usb-free-space"></a>Using the extra space <span class="hideprint">[<a href="#usb-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="usb-free-space"></a>Using the extra space <span class="hideprint">[<a href="#usb-top" title="go to top of the page">^</a>]</span></H3>
397  <p>  <p>
# Line 511  You will have to</p> Line 540  You will have to</p>
540  </ul>  </ul>
541  <p>Now all you have to do is make your USB disk bootable. In order to do that you have to open a DOS window (in Windows XP press "<b>Start / Run </b>" and type <b>cmd</b>). Then type at DOS prompt:</p>  <p>Now all you have to do is make your USB disk bootable. In order to do that you have to open a DOS window (in Windows XP press "<b>Start / Run </b>" and type <b>cmd</b>). Then type at DOS prompt:</p>
542  <p class="newcode"><font color="Green">K:</font><br>  <p class="newcode"><font color="Green">K:</font><br>
543  cd bootprog<br>  cd utils/bootprog<br>
544  syslinux -ma <font color="Green">K:</font></p>  syslinux -ma <font color="Green">K:</font></p>
545  <H3><a name="booting"></a>Booting from USB <span class="hideprint">[<a href="#usb-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="booting"></a>Booting from USB <span class="hideprint">[<a href="#usb-top" title="go to top of the page">^</a>]</span></H3>
546  <p>Before trying to boot from your USB device, you have to set your boot device at your BIOS. This means you have to reboot having your USB device connected, get into your BIOS (usually pressing DEL) and make the appropriate settings in the BOOT section.<br><br>  <p>Before trying to boot from your USB device, you have to set your boot device at your BIOS. This means you have to reboot having your USB device connected, get into your BIOS (usually pressing DEL) and make the appropriate settings in the BOOT section.<br><br>
# Line 620  While in the splash screen of <b>Clonezi Line 649  While in the splash screen of <b>Clonezi
649  </p>  </p>
650  <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>
651  <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>
652  The following info applies to <b>SystemRescueCD v. 1.5.5</b>. In case<br>  The following info applies to <b>SystemRescueCD v. 2.0.1</b>. In case<br>
653   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>
654  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>"
655  </td></tr></table></div>  </td></tr></table></div>
# Line 631  append initrd=initram.igz video=ofonly</ Line 660  append initrd=initram.igz video=ofonly</
660  Available kernels (boot images):</p>  Available kernels (boot images):</p>
661  <ul class="otherpage" style="padding: 0px 10px 20px 40px">  <ul class="otherpage" style="padding: 0px 10px 20px 40px">
662  <li><b>rescuecd</b> Default for 32bit systems, with Framebuffer disabled, best choice.  <li><b>rescuecd</b> Default for 32bit systems, with Framebuffer disabled, best choice.
663  </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).  </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 bit programs. This kernel is able to boot with 32bit programs, and it requires a processor with 64bit instructions (amd64 / em64t).
664  </li><li><b>altker32</b> an alternative kernel for 32bit systems. Boot with this kernel if you have problems with <b>rescuecd</b>  </li><li><b>altker32</b> an alternative kernel for 32bit systems. Boot with this kernel if you have problems with <b>rescuecd</b>
665  </li><li><b>altker64</b> an alternative kernel for 64bit systems. Boot with this kernel in case you have problems with <b>rescue64</b>.  </li><li><b>altker64</b> an alternative kernel for 64bit systems. Boot with this kernel in case you have problems with <b>rescue64</b>.
666  </li>  </li>
# Line 641  Available kernels (boot images):</p> Line 670  Available kernels (boot images):</p>
670  <a name="General_boot_options" id="General_boot_options"></a><p><b> General boot options</b></p>  <a name="General_boot_options" id="General_boot_options"></a><p><b> General boot options</b></p>
671  <p>Press &lt;TAB&gt; to add additional options (in SystemRescueCd-1.5 and more recent)  <p>Press &lt;TAB&gt; to add additional options (in SystemRescueCd-1.5 and more recent)
672  </p>  </p>
673  <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 to 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 from being copied.
674  </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.  </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.
675  </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>.  </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 for a linux system. The first linux system found will be started. So <code>root=auto</code> lets 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>.
676  </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 option allows one to 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 a multiple of times for different services. All the actions that are supported by an initscript can be used.
677  </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>.  </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. 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 if the scan fails, it will store the files which have changed 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 a harddisk,  boot with <code>backstore=alldev</code> to scan all devices (not just removable devices). The default location for a backing-stores file is any file named <code>sysrcd.bs</code> located at the root of a disk which is often a 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>.
678  </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.  </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 on 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.
679  </li></ul>  </li></ul>
680  <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>  <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>
681  <ul><li><b>dodebug</b>: Enables verbose messages in linuxrc  <ul><li><b>dodebug</b>: Enables verbose messages in linuxrc
# Line 655  Available kernels (boot images):</p> Line 684  Available kernels (boot images):</p>
684  </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.  </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.
685  </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
686  </li></ul>  </li></ul>
687  <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 a USB device. A delay of only few seconds should be enough.
688  </li></ul>  </li></ul>
689  <ul><li><b>doxdetect</b>: Since version 0.3.5 the auto-configuration is done in X.Org itself,  mkxf86config is disabled by default. This option forces the system to run the mkxf86config startup script and to run the hardware auto-detection from this script. Use this option if you have problems with the graphical environment configuration. This option replaces the option <code>noxdetect</code> that was useful in previous versions.  <ul><li><b>doxdetect</b>: Since version 0.3.5 the auto-configuration is done in X.Org itself,  mkxf86config is disabled by default. This option forces the system to run the mkxf86config startup script and to run the hardware auto-detection from this script. Use this option if you have problems with the graphical environment configuration. This option replaces the option <code>noxdetect</code> that was useful in previous versions.
690  </li><li><b>nodetect</b>: prevents generic hardware auto-detection. Use this option if you have problems with the hardware auto-detection.  </li><li><b>nodetect</b>: prevents generic hardware auto-detection. Use this option if you have problems with the hardware auto-detection.
691  </li></ul>  </li></ul>
692  <ul><li><b>dostartx</b>:   load the X.Org graphical environment.  <ul><li><b>nomodeset</b>: Do not load the Kernel-Mode-Setting video driver. You can use that option if you are experiencing problems with your screen during the boot process (just after modules are being loaded).
693    </li><li><b>dostartx</b>: load the X.Org graphical environment.
694  </li><li><b>forcevesa</b>: Forces X.Org to use the safe VESA driver instead of the best video driver detected for your video card. Use this option if you cannot get the graphical environment working with the default options.  </li><li><b>forcevesa</b>: Forces X.Org to use the safe VESA driver instead of the best video driver detected for your video card. Use this option if you cannot get the graphical environment working with the default options.
695  </li><li><b>forcevesa=xxx</b>: The <code>startx</code> command will load the <code>Xvesa</code> server instead of <code>Xorg</code>, and  use the screen resolution given as parameter (eg: <code>1024x768</code>, <code>1280x1024x32</code>).  </li><li><b>forcevesa=xxx</b>: The <code>startx</code> command will load the <code>Xvesa</code> server instead of <code>Xorg</code>, and  use the screen resolution given as parameter (eg: <code>1024x768</code>, <code>1280x1024x32</code>).
696  </li></ul>  </li></ul>
# Line 672  Available kernels (boot images):</p> Line 702  Available kernels (boot images):</p>
702  </li></ul>  </li></ul>
703  <ul><li><b>lowmem</b>: For systems with smaller memory, some daemons are not started including sshd and nfsd.  <ul><li><b>lowmem</b>: For systems with smaller memory, some daemons are not started including sshd and nfsd.
704  </li></ul>  </li></ul>
705  <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 not be mounted. Boot with <code>skipmount=/dev/sda1 skipmount=/dev/sda2</code> to ignore these two partitions.
706  </li></ul>  </li></ul>
707  <a name="Network_configuration_and_remote_access" id="Network_configuration_and_remote_access"></a><p><b><br> Network configuration and remote access</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>
708  <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.  <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.
709  </li><li><b>dodhcp</b>: to request a DHCP server provide network attributes including an IP address, gateway...  </li><li><b>dodhcp</b>: to request a DHCP server provide network attributes including an IP address, gateway... If there are multiple interfaces on the computer it will run the dhcp client on all of them by default, when no argument is specified with this option. Thanks to <a target="_blank" href="http://www.sysresccd.org/forums/viewtopic.php?f=5&amp;t=3454" class="external text" title="http://www.sysresccd.org/forums/viewtopic.php?f=5&amp;t=3454" rel="nofollow">emiliano</a> SystemRescueCd-1.7.0-beta009 and more recent allows you to optionally specify which interfaces should be configured with dhcp. This way you can combine static and dynamic addresses in the automatic Ethernet configuration. For example you can now use options like that: <pre>dodhcp=eth0,eth2 eth1=192.168.128.1/24</pre> to use dhcp for eth0 and eth2 and a static address on eth1.
710  </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  </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 and more recent
711  </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.
712  </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, for example: <code>eth0=192.168.10.1/24 eth1=192.168.20.1</code>.
713  </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.
714  </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>.
715  </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.
716  </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>123456</code>. That way you can connect from the network and ssh on the livecd and give <code>123456</code> password as the root password.
717  </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.  </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 6 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. SystemRescueCd-1.5.7 and more recent accept a password longer than 8 chars (between 5 and 12 chars)
718  </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.  </li><li><b>nameif=xxx</b>: You 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.
719  </li></ul>  </li></ul>
720  <a name="Network_boot_using_PXE" id="Network_boot_using_PXE"></a><p><b><br> Network boot using PXE</b></p>  <a name="Network_boot_using_PXE" id="Network_boot_using_PXE"></a><p><b><br> Network boot using PXE</b></p>
721  <p>SystemRescueCd provides several options for booting from the network using PXE.  <p>SystemRescueCd provides several options for booting from the network using PXE.
# Line 696  These options can be combined with other Line 726  These options can be combined with other
726  </p>  </p>
727  <ul><li><b>netboot=</b>tftp<b>://ip/path/sysrcd.dat</b>: from a TFTP server. The filesystem is loaded into memory. As a consequence computers with less than 400MB of memory won't be able to boot this way. The system will continue to work if the network is disconnected after the boot process.  <ul><li><b>netboot=</b>tftp<b>://ip/path/sysrcd.dat</b>: from a TFTP server. The filesystem is loaded into memory. As a consequence computers with less than 400MB of memory won't be able to boot this way. The system will continue to work if the network is disconnected after the boot process.
728  </li><li><b>netboot=</b>http<b>://ip:port/path/sysrcd.dat</b>:  from a Web server. The file system is loaded into memory. Computers with smaller memory won't be able to boot this way. The the system continues to work if the network is disconnected after the boot process.  </li><li><b>netboot=</b>http<b>://ip:port/path/sysrcd.dat</b>:  from a Web server. The file system is loaded into memory. Computers with smaller memory won't be able to boot this way. The the system continues to work if the network is disconnected after the boot process.
729  </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 allows computers with smaller memory to boot SystemRescueCd from the network. After the boot process, continued network connection is required or you will loose access to the root file system.
730  </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 memory to boot SystemRescueCd from the network. After the boot process, the network connection continues to be required to access the root file system.
731  </li></ul>  </li></ul>
732  <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>.  <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>.
733  </p>  </p>
# Line 713  These options can be combined with other Line 743  These options can be combined with other
743  </div>  </div>
744  <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>
745  <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>
746  The following info applies to <b>Clonezilla Live v. 1.2.5-17</b><br>  The following info applies to <b>Clonezilla Live v. 1.2.8-23</b><br>
747  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>
748  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://clonezilla.org/clonezilla-live/doc/99_Misc/00_live-initramfs-manual.doc" target="_blank">The boot parameters for Clonezilla live</a>"
749  </td></tr></table></div>  </td></tr></table></div>
750  <p>A typical Clonezilla Live isolinux entry is:</p>  <p>A typical Clonezilla Live isolinux entry is:</p>
751  <p class="newcode">  kernel /live/vmlinuz1<br>  <p class="newcode">  kernel /live/vmlinuz1<br>
# Line 732  please see the page "<a href="http://www Line 762  please see the page "<a href="http://www
762        e.g. ocs_live_run="ocs-live-general"<br>        e.g. ocs_live_run="ocs-live-general"<br>
763        <font color="red">//NOTE// You might have to use "sudo" command inside your own script, or you can assign it like: ocs_live_run="sudo bash /my-clonezilla"</font><br>        <font color="red">//NOTE// You might have to use "sudo" command inside your own script, or you can assign it like: ocs_live_run="sudo bash /my-clonezilla"</font><br>
764    <li>ocs_live_extra_param will be used only when ocs_live_run=ocs-live-restore (not for ocs-live-general or any other), then it will be passed to ocs-sr. Therefore these parameters are actually those of ocs-sr.<br>    <li>ocs_live_extra_param will be used only when ocs_live_run=ocs-live-restore (not for ocs-live-general or any other), then it will be passed to ocs-sr. Therefore these parameters are actually those of ocs-sr.<br>
765        e.g. ocs_live_extra_param="-b -c restoredisk sarge-r5 hda"        e.g. ocs_live_extra_param="--batch -c restoredisk sarge-r5 hda"
766    <li>ocs_live_keymap is for keymap used in Clonezilla live. Man install-keymap for more details.<br>    <li>ocs_live_keymap is for keymap used in Clonezilla live. Man install-keymap for more details.<br>
767        e.g. ocs_live_keymap="NONE" (won't change the default layout)<br>        e.g. ocs_live_keymap="NONE" (won't change the default layout)<br>
768             ocs_live_keymap="/usr/share/keymaps/i386/azerty/fr-latin9.kmap.gz" (French keyboard)             ocs_live_keymap="/usr/share/keymaps/i386/azerty/fr-latin9.kmap.gz" (French keyboard)
# Line 743  please see the page "<a href="http://www Line 773  please see the page "<a href="http://www
773    <li>ocs_debug (or ocs-debug) is for you to enter command line prompt before any clonezilla-related action is run. This is easier for you to debug.    <li>ocs_debug (or ocs-debug) is for you to enter command line prompt before any clonezilla-related action is run. This is easier for you to debug.
774    <li>ocs_daemonon, ocs_daemonoff, ocs_numlk, ocs_capslk.<br>    <li>ocs_daemonon, ocs_daemonoff, ocs_numlk, ocs_capslk.<br>
775  Ex. for the first 2 parameters, ocs_daemonon="ssh", then ssh service will be turned on when booting. For the last 2 parameters, use "on" or "off", e.g. ocs_numlk=on to turn on numberlock when booting.  Ex. for the first 2 parameters, ocs_daemonon="ssh", then ssh service will be turned on when booting. For the last 2 parameters, use "on" or "off", e.g. ocs_numlk=on to turn on numberlock when booting.
776    <li>ocs_prerun, ocs_prerun1, ocs_prerun2... is for you to run a shell script before Clonezilla is started. E.g. ocs_prerun="/live/image/myscript.sh". If you have more commands to run, you can assign them in the order: ocs_prerun=..., ocs_prerun1=..., ocs_prerun2=.... If more than 10 parameters, remember to use ocs_prerun01, ocs_prerun02..., ocs_prerun11 to make it in order.    <li>ocs_prerun, ocs_prerun1, ocs_prerun2... is for you to run a command before Clonezilla is started. E.g. ocs_prerun="/live/image/myscript.sh". If you have more commands to run, you can assign them in the order: ocs_prerun=..., ocs_prerun1=..., ocs_prerun2=.... If more than 10 parameters, remember to use ocs_prerun01, ocs_prerun02..., ocs_prerun11 to make it in order.
777    <li>ocs_live_run_tty. This option allows you to specify the tty where $ocs_live_run is run. By default $ocs_live_run is run on /dev/tty1 only. (It was also on /dev/ttyS0 before, but since Clonezilla live >= 1.2.3-22 no more this due to a problem). If you want to use ttyS0, for example, add live-getty and console=ttyS0,38400n81 in the boot parameter.<br>    <li>ocs_live_run_tty. This option allows you to specify the tty where $ocs_live_run is run. By default $ocs_live_run is run on /dev/tty1 only. If you want to use ttyS0, for example, add live-getty and console=ttyS0,38400n81 in the boot parameter.<br>
778    <font color=red>//NOTE//</font><br>    <font color=red>//NOTE//</font><br>
779    <ul>    <ul>
780    <li>This parameter was added in Clonezilla live 1.2.3-22 or later.    <li>If "live-getty console=ttyS0,38400n81" are assigned in the boot parameters, ocs_live_run_tty will honor ttyS0, even other value is assigned to ocs_live_run_tty in boot parameter.
   <li>If "live-getty console=$tty,38400n81" are assigned in the boot parameters, ocs_live_run_tty will honor $tty, even other value is assigned to ocs_live_run_tty in boot parameter.  
781    <li>It's recommended to assign ocs_lang and ocs_live_keymap in the boot parameters too.    <li>It's recommended to assign ocs_lang and ocs_live_keymap in the boot parameters too.
782    </ul>    </ul>
783    <li>ip, this option allows you to specify the network parameters for network card. In Clonezilla live a patched live-initramfs is used, which is different from the original live-initramfs so that you can assign DNS server, too. Its format is: ip=ethernet port,IP address, netmask, gateway, DNS. E.g. If you want to assing eth0 with IP address 10.0.100.1, netmask 255.255.255.0, gateway 10.0.100.254, DNS server 8.8.8.8, you can assign the following in the boot parameter:<br>    <li>ip, this option allows you to specify the network parameters for network card. In Clonezilla live a patched live-initramfs is used, which is different from the original live-initramfs so that you can assign DNS server, too. Its format is: ip=ethernet port,IP address, netmask, gateway, DNS. E.g. If you want to assing eth0 with IP address 10.0.100.1, netmask 255.255.255.0, gateway 10.0.100.254, DNS server 8.8.8.8, you can assign the following in the boot parameter:<br>
784  ip=eth0,10.0.100.1,255.255.255.0,10.0.100.254,8.8.8.8<br>  ip=eth0:10.0.100.1:255.255.255.0:10.0.100.254:8.8.8.8<br>
785  If more than one network card, you can use ":" to separate them, e.g.:<br>  If more than one network card, you can use "," to separate them, e.g.:<br>
786  ip=eth0,10.0.100.1,255.255.255.0,10.0.100.254,8.8.8.8:eth1,192.168.120.1,255.255.255.0,192.168.120.254,,<br>  ip=eth0:10.0.100.1:255.255.255.0:10.0.100.254:8.8.8.8,eth1:192.168.120.1:255.255.255.0:192.168.120.254::<br>
787    <li>Besides, "live-netdev" (yes, not ocs_live_netdev) can be used when using PXE booting, you can force to assign the network device to get filesystem.squashfs. This is useful when there are two or more NICs are linked. E.g. live-netdev="eth1" allows you to force the live-initramfs to use eth1 to fetch the root file system filesystem.squashfs.    <li>Besides, "live-netdev" (yes, not ocs_live_netdev) can be used when using PXE booting, you can force to assign the network device to get filesystem.squashfs. This is useful when there are two or more NICs are linked. E.g. live-netdev="eth1" allows you to force the live-initramfs to use eth1 to fetch the root file system filesystem.squashfs.
788  </ul>  </ul>
789  </ol>  </ol>
# Line 843  fi Line 872  fi
872  <a name="live-initramfs"></a><div class="otherpage" style="overflow: auto;"><pre>  <a name="live-initramfs"></a><div class="otherpage" style="overflow: auto;"><pre>
873  live-initramfs(7)  live-initramfs(7)
874  =================  =================
875    :man source: 1.157.3
876    :man manual: Debian Live
877  Name  Name
878  ----  ----
879  live-initramfs - Debian Live initramfs hook  live-initramfs - Debian Live initramfs hook
# Line 879  Set the default console to be used with Line 910  Set the default console to be used with
910  Makes initramfs boot process more verbose.  Makes initramfs boot process more verbose.
911    fetch=*URL*::    fetch=*URL*::
912  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,
913  copying to ram and booting it.  copying to ram and booting it. Due to current limitations in busyboxs wget
914    and DNS resolution, an URL can not contain a hostname but an IP only.
915    Not working: http://example.com/path/to/your_filesystem.squashfs
916    Working: http://1.2.3.4/path/to/your_filesystem.squashfs
917    Also note that therefore it's currently not possible to fetch an image from a
918    namebased virtualhost of an httpd if it is sharing the ip with the main httpd
919    instance.
920    hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*::    hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*::
921  Those parameters lets you override values read from the config file.  Those parameters lets you override values read from the config file.
922    ignore_uuid    ignore_uuid
# Line 897  Let you specify the name(s) and the opti Line 934  Let you specify the name(s) and the opti
934  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).
935  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
936  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).
937    ip[=**frommedia**]::    ip=[**frommedia**]::
938  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
939  system will use the (must be) media-preconfigured /etc/network/interfaces  system will use the (must be) media-preconfigured /etc/network/interfaces
940  instead.  instead.
# Line 918  If you specify one of this two equivalen Line 955  If you specify one of this two equivalen
955  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
956  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
957  for block devices is performed.  for block devices is performed.
958    Instead of specifing an actual device name, the keyword 'removable' can be used
959    to limit the search of acceptable live media to removable type only. Note that
960    if you want to further restrict the media to usb mass storage only, you can use
961    the 'removable-usb' keyword.
962    {live-media-encryption|encryption}=**TYPE**::    {live-media-encryption|encryption}=**TYPE**::
963  live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase,  live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase,
964  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
# Line 964  be checked at boot time, use this parame Line 1005  be checked at boot time, use this parame
1005  disables the "persistent" feature, useful if the bootloader (like syslinux) has  disables the "persistent" feature, useful if the bootloader (like syslinux) has
1006  been installed with persistent enabled.  been installed with persistent enabled.
1007    noprompt    noprompt
1008  Do not prompt to eject the CD on reboot.  Do not prompt to eject the CD or remove the USB flash drive on reboot.
1009    nosudo::    nosudo::
1010  This parameter disables the automatic configuration of sudo.  This parameter disables the automatic configuration of sudo.
1011    swapon::    swapon::
# Line 984  tried to be updated on reboot/shutdown. Line 1025  tried to be updated on reboot/shutdown.
1025  informations. If "nofiles" is specified, only filesystems with matching labels  informations. If "nofiles" is specified, only filesystems with matching labels
1026  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
1027  files. This results in shorter boot times.  files. This results in shorter boot times.
1028      persistent-path=PATH
1029    live-initramfs will look for persistency files in the root directory of a partition,
1030    with this parameter, the path can be configured so that you can have multiple
1031    directories on the same partition to store persistency files.
1032    {preseed/file|file}=**FILE**::    {preseed/file|file}=**FILE**::
1033  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
1034  database.  database.
# Line 999  This parameter will make live-initramfs Line 1044  This parameter will make live-initramfs
1044  (mostly compressed) on "/live". This is not enabled by default because could  (mostly compressed) on "/live". This is not enabled by default because could
1045  lead to problems by applications like "mono" which store binary paths on  lead to problems by applications like "mono" which store binary paths on
1046  installation.  installation.
1047      silent
1048    If you boot with the normal quiet parameter, live-initramfs hides most messages
1049    of its own. When adding silent, it hides all.
1050    textonly    textonly
1051  Start up to text-mode shell prompts, disabling the graphical user interface.  Start up to text-mode shell prompts, disabling the graphical user interface.
1052    timezone=**TIMEZONE**::    timezone=**TIMEZONE**::
# Line 1236  Fianlly I should say that <b>Clonezilla Line 1284  Fianlly I should say that <b>Clonezilla
1284  <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>
1285  <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>
1286  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>
1287  <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>  <p class="otherpage">
1288    When I use clonezilla to clone MS 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 "Missing Operating System" or just a blinking underscore. What's going on ?<br><br>
1289  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>
1290  &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>
1291  &nbsp;&nbsp;2. Try to choose<br>  &nbsp;&nbsp;2. Try to choose both<br>
1292  &nbsp;&nbsp;&nbsp;&nbsp;<b>[ ] -j0 Use dd to create partition table instead of sfdisk</b><br>  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>[*] -j0 Use dd to create partition table instead of sfdisk</b><br>
1293  &nbsp;&nbsp;and<br>  &nbsp;&nbsp;and <br>
1294  &nbsp;&nbsp;&nbsp;&nbsp;<b>[ ] -t1 Client restores the prebuilt MBR from syslinux (For Windows only)</b><br>  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>[*] -t1 Client restores the prebuilt MBR from syslinux</b> (For Windows only)<br>
1295  &nbsp;&nbsp;when you restore the image.<br>  &nbsp;&nbsp;&nbsp;&nbsp;when you restore the image.<br>
1296  &nbsp;&nbsp;3. You can try to boot the machine with MS Windows 9x bootable floppy, and in the DOS command prompt, run: "fdisk /mbr".  &nbsp;&nbsp;3. Try to choose<br>
1297  &nbsp;&nbsp;4. You can try to boot the machine with MS Windows XP installation CD, enter recovery mode (by pressing F10 key in MS XP, for example), then in the console, run "fixmbr" to fix it. Maybe another command "fixboot" will help, too. For more info, refer to <a href="http://support.microsoft.com/?scid=kb%3Ben-us%3B314058&x=7&y=14" target="_blank">this doc</a><br>  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>[*] -t1 Client restores the prebuilt MBR from syslinux</b> (For Windows only)<br>
1298  &nbsp;&nbsp;5. Use ntfsreloc to adjust FS geometry on NTFS partitions. For more info, refer to <a href="http://www.linux-ntfs.org/doku.php?id=contrib:ntfsreloc" target="_blank">http://www.linux-ntfs.org/doku.php?id=contrib:ntfsreloc</a></p>  &nbsp;&nbsp;and *uncheck*<br>
1299  <p>It has been confirmed that activating the <font color="Red"><b>-j0</b></font> option, fixes the problem.</p>  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>[ ] -g auto  Reinstall grub in client disk MBR</b> (only if grub config exists)<br>
1300    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>[ ] -r       Try to resize the filesystem to fit partition size</b><br>
1301    &nbsp;&nbsp;when you restore the image. You can refer to <a href="http://www.ecs.umass.edu/pipermail/umasslug/2008-August/003380.html" target=_blank>this discussion</a>. Thanks to Alex Mckenzie for posting this on the forum.<br>
1302    &nbsp;&nbsp;4. You can try to boot the machine with MS Windows 9x bootable floppy, and in the DOS command prompt, run: "fdisk /mbr".<br>
1303    &nbsp;&nbsp;5. You can try to boot the machine with MS Windows XP installation CD, enter recovery mode (by pressing F10 key in MS XP, for example), then in the console, run "fixmbr" to fix it. Maybe another command "fixboot" will help, too. For more info, refer to <a href="http://support.microsoft.com/?scid=kb%3Ben-us%3B314058&x=7&y=14" _target=blank>this doc</a>
1304    &nbsp;&nbsp;6. Use <a href="http://sourceforge.net/projects/ntfsfixboot/" target=_blank>ntfsfixboot</a> to fix it. This program is included in Clonezila live and its name is partclone.ntfsfixboot, and you can use it to adjust FS geometry on NTFS partitions. By default this should be done by Clonezilla with the option -e1 and -e2 checked. If not, you can force to do that again. For more info, please run "partclone.ntfsfixboot --help" or refer to <a href="http://sourceforge.net/projects/ntfsfixboot/" target=_blank>http://sourceforge.net/projects/ntfsfixboot/</a>.<br>
1305    &nbsp;&nbsp;7. Use ntfsreloc to adjust FS geometry on NTFS partitions. For more info, refer to <a href="http://www.linux-ntfs.org/doku.php?id=contrib:ntfsreloc" target=_blank>http://www.linux-ntfs.org/doku.php?id=contrib:ntfsreloc</a>. //NOTE// ntfsreloc is an older version of partclone.ntfsfixboot.<br>
1306    &nbsp;&nbsp;8. If you get error messages like "0xc0000225, 0xc00000e", and something about Winload.exe, refer to <a href="../faq/fine-print.php?path=./2_System/94_windows_winload_err.faq#94_windows_winload_err.faq">this</a>.<br>
1307    &nbsp;&nbsp;9. Some more discussions are available <a href="https://sourceforge.net/projects/clonezilla/forums/forum/663168/topic/3748791" target=_blank>here</a>.
1308    </p>
1309    <p>It has been confirmed that activating the <font color="Red"><b>-j0</b></font> option, usually fixes the problem.</p>
1310  <p>This option doesn't work if you use LVM (Logical Volume Manager).</p>  <p>This option doesn't work if you use LVM (Logical Volume Manager).</p>
1311  <p class="newcode"><a name="exit"></a><font color="Red">exit&nbsp;Exit</font></p>  <p class="newcode"><a name="exit"></a><font color="Red">exit&nbsp;Exit</font></p>
1312  <p>This option ends the restore process and enters command line prompt.</p>  <p>This option ends the restore process and enters command line prompt.</p>
# Line 1280  ocs-live</p> Line 1339  ocs-live</p>
1339  </ul>  </ul>
1340  <a name="backup-top"></a>  <a name="backup-top"></a>
1341  <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>
1342  <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>  <p>In this page I will demonstrate the creation of an image file by getting a backup of a virtual disk (<b>/dev/<font color="Red">sdb</font></b>). The image file will be saved in a partition in another virtual disk (<b>/dev/<font color="Red">sda1</font></b>).<br></p>
1343  <p>  <p>
1344  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>
1345  <br>  <br>
# Line 1290  Having done all of the above, I am ready Line 1349  Having done all of the above, I am ready
1349  <br>  <br>
1350  </p>  </p>
1351  <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>
1352  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.5-35</b>  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.8-23</b>
1353  </td></tr></table></div>  </td></tr></table></div>
1354  <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>
1355  <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 1343  This screen displays the mounting result Line 1402  This screen displays the mounting result
1402  As we can see, <font color="Red"><b>/dev/sda1</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>
1403  <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>
1404  <p><img src="images/backup-09.png">  <p><img src="images/backup-09.png">
1405  <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>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>
1406  <H3><a name="bck-8"></a>Screen "Select mode" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-8"></a>Screen "Select mode" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1407  <p>Here I can select the desired operation.<br>  <p>Here I can select the desired operation.<br>
1408  <br>  <br>
# Line 1356  I type "Backup_32-2010_sdb", which in my Line 1415  I type "Backup_32-2010_sdb", which in my
1415  </p>  </p>
1416  <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>
1417  <p><img src="images/backup-12.png"><br>  <p><img src="images/backup-12.png"><br>
1418  Finally I am asked to select the partition to save.<br>  Finally I am asked to select the disk to save.<br>
1419  I just press ENTER again.  I just press ENTER again.
1420  </p>  </p>
1421  <H3><a name="bck-11"></a>Starting the backup [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-11"></a>Starting the backup [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
# Line 1436  I will be able to continue only after en Line 1495  I will be able to continue only after en
1495  <img src="images/backup-smb-11.png"></p>  <img src="images/backup-smb-11.png"></p>
1496  <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>
1497  <p><img src="images/backup-09.png">  <p><img src="images/backup-09.png">
1498  <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>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>
1499  <H3><a name="bck-smb-8"></a>Screen "Select mode" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-smb-8"></a>Screen "Select mode" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1500  <p>Here I can select the desired operation.<br>  <p>Here I can select the desired operation.<br>
1501  <br>  <br>
# Line 1449  I type "Backup_32-2010_sdb", which in my Line 1508  I type "Backup_32-2010_sdb", which in my
1508  </p>  </p>
1509  <H3><a name="bck-smb-10"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-smb-10"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1510  <p><img src="images/backup-12.png"><br>  <p><img src="images/backup-12.png"><br>
1511  Finally I am asked to select the partition to save.<br>  Finally I am asked to select the disk to save.<br>
1512  I just press ENTER again.  I just press ENTER again.
1513  </p>  </p>
1514  <H3><a name="bck-smb-11"></a>Starting the backup [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-smb-11"></a>Starting the backup [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
# Line 1478  reboot<br><br></p> Line 1537  reboot<br><br></p>
1537  Restore process erases all the data on the target disk/partition.<br><br>Before restoring make sure you have backup of all the data<br> on the target disk/partition, even if the filesystem is corrupted.  Restore process erases all the data on the target disk/partition.<br><br>Before restoring make sure you have backup of all the data<br> on the target disk/partition, even if the filesystem is corrupted.
1538  </td></tr></table></div>  </td></tr></table></div>
1539  <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>
1540  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.5-35</b>  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.8-23</b>
1541  </td></tr></table></div>  </td></tr></table></div>
1542  <H2><a name="restore"></a>Restoring data <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="restore"></a>Restoring data <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>
1543  <H3><a name="res-0"></a>Clonezilla-SysRescCD starting screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <H3><a name="res-0"></a>Clonezilla-SysRescCD starting screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
# Line 1530  This screen displays the mounting result Line 1589  This screen displays the mounting result
1589  As we can see, <font color="Red"><b>/dev/sda1</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>
1590  <H3><a name="res-7a"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <H3><a name="res-7a"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1591  <p><img src="images/backup-09.png"><br>  <p><img src="images/backup-09.png"><br>
1592  I select <font color="Red"><b>Beginer mode</b></font> to accept the default restore 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#restore-options" target="_blank">here</a>.</p>  I select <font color="Red"><b>Beginner mode</b></font> to accept the default restore 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#restore-options" target="_blank">here</a>.</p>
1593  <H3><a name="res-8"></a>Screen "Select mode" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <H3><a name="res-8"></a>Screen "Select mode" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1594  <p>Here I can select the desired operation.<br>  <p>Here I can select the desired operation.<br>
1595  <br>  <br>
# Line 1541  I select "<font color="Red"><b>restoredi Line 1600  I select "<font color="Red"><b>restoredi
1600  In this screen I select the image folder. This partition contains only one image.</p>  In this screen I select the image folder. This partition contains only one image.</p>
1601  <H3><a name="res-10"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <H3><a name="res-10"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1602  <p><img src="images/restoration-12.png"><br>  <p><img src="images/restoration-12.png"><br>
1603  Finally I am asked to select which partition the image will be restored to. After double-checking the disk doesn't contain anything important, I press ENTER.</p>  Finally I am asked to select which disk the image will be restored to. After double-checking the disk doesn't contain anything important, I press ENTER.</p>
1604  <H3><a name="res-11"></a>Starting the restoration [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <H3><a name="res-11"></a>Starting the restoration [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1605  <p><img src="images/restoration-13.png"><br>  <p><img src="images/restoration-13.png"><br>
1606  Then the program will display the command that will be executed and will ask me to press ENTER. <br>  Then the program will display the command that will be executed and will ask me to press ENTER. <br>
# Line 1564  reboot<br><br></p> Line 1623  reboot<br><br></p>
1623  <p>to reboot the system.</p>  <p>to reboot the system.</p>
1624  <a name="restore-top"></a>  <a name="restore-top"></a>
1625  <H2 style="font-size: 2em;"><a name="restore-intro"></a>Creating a Restore DVD - Part 1 <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>  <H2 style="font-size: 2em;"><a name="restore-intro"></a>Creating a Restore DVD - Part 1 <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>
1626  <p>Assuming you have used <b>Clonezilla Live</b> to make a backup of your Windows XP system (partition <b>/dev/<font color="Red">sda1</font></b>), you will probably be wondering what to do with it now. Well, one option would be to keep it to the disk you used to save it in, store the disk, and use it whenever you need it. Another option would be to create a DVD you can use to restore this image.<br><br>  <p>Assuming you have used <b>Clonezilla Live</b> to make a backup of your system (disk <b>/dev/<font color="Red">sdb</font></b>), you will probably be wondering what to do with it now. Well, one option would be to keep it to the disk you used to save it in, store the disk, and use it whenever you need it. Another option would be to create a DVD you can use to restore this image.<br><br>
1627  Before, up to <b>Clonezilla-SysRescCD 2.6.0</b>, the process to create an automated restore DVD required entering command line prompt and writing some commands, that can be uncomfortable or even difficult for many people.<br><br>  Before, up to <b>Clonezilla-SysRescCD 2.6.0</b>, the process to create an automated restore DVD required entering command line prompt and writing some commands, which can be uncomfortable or even difficult for many people.<br><br>
1628  Later, a TUI option to create an automated recovery disc was added to <b>Clonezilla Live</b>, and <b>ocs-iso</b> script included in <b>Clonezilla-SysRescCD 3.1.0</b> and newer has a TUI too. Old command-line options are no longer supported. This page walks you through the creation of an automated restore DVD via TUI.<br><br>  Later, a TUI option to create an automated recovery disc was added to <b>Clonezilla Live</b>, and <b>ocs-iso</b> script included in <b>Clonezilla-SysRescCD 3.1.0</b> and newer has a TUI too. Old command-line options are no longer supported. This page walks you through the creation of an automated restore DVD via TUI.<br><br>
1629  You have to boot <b>Clonezilla Live</b>, using <b>Clonezilla-SysRescCD</b>.</p>  You have to boot <b>Clonezilla Live</b>, using <b>Clonezilla-SysRescCD</b>.</p>
1630  <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>
1631  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.5-17</b>  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.8-23</b>
1632  </td></tr></table></div>  </td></tr></table></div>
1633  <H2><a name="dvd"></a>Creating the disk image <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="dvd"></a>Creating the disk image <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>
1634  <H3><a name="rui-0"></a>Clonezilla-SysRescCD starting screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <H3><a name="rui-0"></a>Clonezilla-SysRescCD starting screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
# Line 1622  This screen displays the mounting result Line 1681  This screen displays the mounting result
1681  As we can see, <font color="Red"><b>/dev/sda1</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>
1682  <H3><a name="rui-7a"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <H3><a name="rui-7a"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1683  <p><img src="images/backup-09.png"><br>  <p><img src="images/backup-09.png"><br>
1684  I select <font color="Red"><b>Beginer mode</b></font> to accept the default restore options, which are used if the recovery disk is ever used. 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#restore-options" target="_blank">here</a>.</p>  I select <font color="Red"><b>Beginner mode</b></font> to accept the default restore options, which are used if the recovery disk is ever used. 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#restore-options" target="_blank">here</a>.</p>
1685  <H3><a name="rui-8"></a>Screen "Clonezilla: Select mode" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <H3><a name="rui-8"></a>Screen "Clonezilla: Select mode" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1686  <p>Here I can select the desired operation.<br>  <p>Here I can select the desired operation.<br>
1687  <br>  <br>
# Line 1699  That's it. You own now an automated reco Line 1758  That's it. You own now an automated reco
1758  <img src="images/k3b-00.png"><br>  <img src="images/k3b-00.png"><br>
1759  I launch <b>K3b</b> and navigate to the folder where the disk image resides.<br><br>  I launch <b>K3b</b> and navigate to the folder where the disk image resides.<br><br>
1760  <img src="images/k3b-01.png"><br>  <img src="images/k3b-01.png"><br>
1761  I double-click the file <b>clonezilla-live-<font color="Green">Backup_5-2010_hda</font>.iso</b>.<br><br>  I double-click the file <b>clonezilla-live-<font color="Green">Backup_42-2010_sda</font>.iso</b>.<br><br>
1762  <img src="images/k3b-02.png"><br>  <img src="images/k3b-02.png"><br>
1763  This window allows me to choose burning settings. I don't touch <b>Image Type</b> or <b>Burn Medium</b>, because they're auto-detected anyway. The maximum burning speed allowed by the disc is 16x, so I choose speed 12x. According to <a href="http://club.myce.com/f33/high-speed-vs-low-speed-burning-69698/" target="_blank">this forum thread</a> low burning speed can decrease burning quality, so I always use speed near the maximum speed of the disc.<br><br>  This window allows me to choose burning settings. I don't touch <b>Image Type</b> or <b>Burn Medium</b>, because they're auto-detected anyway. The maximum burning speed allowed by the disc is 16x, so I choose speed 12x. According to <a href="http://club.myce.com/f33/high-speed-vs-low-speed-burning-69698/" target="_blank">this forum thread</a> low burning speed can decrease burning quality, so I always use speed near the maximum speed of the disc.<br><br>
1764  I keep <b>Writing Mode</b> as Auto and number of copies as 1. I also keep the <b>Simulate</b> option disabled and enable the <b>Verify written data</b> option. The latter allows me to notice immediately if the burning attempt failed, so I can try burning the disc again, rather than owning a so-called coaster and relying on it if something happens to my data...<br><br>  I keep <b>Writing Mode</b> as Auto and number of copies as 1. I also keep the <b>Simulate</b> option disabled and enable the <b>Verify written data</b> option. The latter allows me to notice immediately if the burning attempt failed, so I can try burning the disc again, rather than owning a so-called coaster and relying on it if something happens to my data...<br><br>
# Line 1729  The command below erases all the data on Line 1788  The command below erases all the data on
1788  <p><b>Note:</b> In the command replace <b>/dev/<font color="Green">sdc1</font></b> with the partition you wish to format.</p>  <p><b>Note:</b> In the command replace <b>/dev/<font color="Green">sdc1</font></b> with the partition you wish to format.</p>
1789  <p>After formatting the partition or noticing that it was already FAT32, extract the ZIP archive to the root of the partition. Also these commands need root rights.</p>  <p>After formatting the partition or noticing that it was already FAT32, extract the ZIP archive to the root of the partition. Also these commands need root rights.</p>
1790  <p class="newcode">mount /dev/<font color="Green">sdc1</font> /media/usb<br>  <p class="newcode">mount /dev/<font color="Green">sdc1</font> /media/usb<br>
1791  unzip clonezilla-live-<font color="Green">Backup_5-2010_hdb</font>.zip -d /media/usb/</p>  unzip clonezilla-live-<font color="Green">Backup_42-2010_sdb</font>.zip -d /media/usb/</p>
1792  <p><b>Note:</b> In the last command I have assumed your image file is <b>clonezilla-live-<font color="Green">Backup_5-2010_hdb</font>.zip</b>. You will have to replace this with the actual name of the file.</p>  <p><b>Note:</b> In the last command I have assumed your image file is <b>clonezilla-live-<font color="Green">Backup_42-2010_sdb</font>.zip</b>. You will have to replace this with the actual name of the file.</p>
1793  <p>ZIP package contains a script to make the USB drive bootable. Let's run it. The latter of these commands needs root access.</p>  <p>ZIP package contains a script to make the USB drive bootable. Let's run it. The latter of these commands needs root access.</p>
1794  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>
1795  The latter of the commands below replaces the<br>existing bootloader of the target disk, if there is one.<br><br>Make sure you don't select a wrong disk by accident.  The latter of the commands below replaces the<br>existing bootloader of the target disk, if there is one.<br><br>Make sure you don't select a wrong disk by accident.
# Line 2064  dd if=/mnt/usb/<font color="Green">Backu Line 2123  dd if=/mnt/usb/<font color="Green">Backu
2123    
2124  <p>It tells how many hard drives you have, how many partitions they contain and what filesystems the partitions use. If you know, for example, that the disk where you've saved the disk image contains only one partition, look for such disks.</p>  <p>It tells how many hard drives you have, how many partitions they contain and what filesystems the partitions use. If you know, for example, that the disk where you've saved the disk image contains only one partition, look for such disks.</p>
2125    
2126  <H3><a name="ntldr-vista"></a>Using Bootrec.exe (Windows Vista/7 only) <span class="hideprint">[<a href="#sgd-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="ntldr-7"></a>Using Bootrec.exe (Windows Vista/7 only) <span class="hideprint">[<a href="#sgd-top" title="go to top of the page">^</a>]</span></H3>
2127    
2128  <p>You need Windows Vista/7 install disc for this. If you don't have one (for example, if you bought a laptop that was bundled with preinstalled Windows and manufacturer's recovery disc), download a recovery disc from <a href="http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/" target="_blank">here</a>.<br>  <p>You need Windows Vista/7 install disc for this. If you don't have one (for example, if you bought a laptop that was bundled with preinstalled Windows and manufacturer's recovery disc), download a recovery disc from <a href="http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/" target="_blank">here</a>.<br>
2129  <br>  <br>
2130  Then boot from the disc. After selecting language, time, currency and keyboard, click <b>Repair your computer</b>. You'll get a list of operating systems you're able to repair. Choose any of them; that choice doesn't matter.<br>  Then boot from the disc.</p>
2131  <br>  
2132  After that, you'll see a dialog box named <b>System Recovery Options</b>. Click <b>Command Prompt</b>. Then you only need to execute one command:</p>  <p><img src="images/windows7-00.png"><br>
2133    After selecting language, time, currency and keyboard, click <b>Next</b>.</p>
2134    
2135    <p><img src="images/windows7-01.png"><br>
2136    Click <b>Repair your computer</b>.</p>
2137    
2138    <p><img src="images/windows7-02.png"><br>
2139    Choose the option <b>Use recovery tools that can help fix problems starting Windows</b> and click <b>Next</b>.</p>
2140    
2141    <p><img src="images/windows7-03.png"><br>
2142    You'll see a dialog box named <b>System Recovery Options</b>. Click <b>Command Prompt</b>.</p>
2143    
2144    <p><img src="images/windows7-04.png"><br>
2145    Then you only need to execute one command:</p>
2146    
2147  <p class="newcode">Bootrec /FixMbr</p>  <p class="newcode">Bootrec /FixMbr</p>
2148    
2149  <p><b>Note:</b> The command is case-insensitive. You can type, for example, "<b>bootrec /fixmbr</b>".</p>  <p><b>Note:</b> The command is case-insensitive. You can type, for example, "<b>bootrec /fixmbr</b>".</p>
2150    
2151    <p><img src="images/windows7-05.png"><br>
2152    </p>
2153    
2154  <H3><a name="ntldr-xp"></a>Using FIXMBR (Windows XP only) <span class="hideprint">[<a href="#sgd-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="ntldr-xp"></a>Using FIXMBR (Windows XP only) <span class="hideprint">[<a href="#sgd-top" title="go to top of the page">^</a>]</span></H3>
2155    
2156  <p>You need Windows XP install disc. Boot from it, and when you see the screen "Windows XP Home Edition Setup" or "Windows XP Professional Setup", press <font color="Red"><b>R</b></font> to enter the Recovery Console. Then choose the Windows installation you want to log onto. If you have only one copy of Windows installed, press <font color="Red"><b>1</b></font> and ENTER. After that, enter the administator password and press ENTER.<br>  <p>You need Windows XP install disc. Boot from it, and when you see the screen "Windows XP Home Edition Setup" or "Windows XP Professional Setup", press <font color="Red"><b>R</b></font> to enter the Recovery Console. Then choose the Windows installation you want to log onto. If you have only one copy of Windows installed, press <font color="Red"><b>1</b></font> and ENTER. After that, enter the administator password and press ENTER.<br>
# Line 2092  There is only one command to run:</p> Line 2167  There is only one command to run:</p>
2167  <br>  <br>
2168  Don't worry, <b>Super Grub Disk</b> makes it possible. Boot into it.</p>  Don't worry, <b>Super Grub Disk</b> makes it possible. Boot into it.</p>
2169    
2170  <p><img src="images/supergrubdisk-01.png"><br>  <p><img src="images/supergrubdisk-01.png"><br>
2171  Just choose the option "<font color="Red"><b>!WIN!&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:(((</b></font>" and press ENTER.<br>  Just choose the option "<font color="Red"><b>!WIN!&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:(((</b></font>" and press ENTER.<br>
2172  <br>  <br>
2173  When you have Windows up and running, download the boot disk image appropriate to your version of Windows from <a href="http://www.bootdisk.com/bootdisk.htm" target="_blank">Bootdisk.Com</a>. Then put a floppy to your floppy drive.<br>  When you have Windows up and running, download the boot disk image appropriate to your version of Windows from <a href="http://www.bootdisk.com/bootdisk.htm" target="_blank">Bootdisk.Com</a>. Then put a floppy to your floppy drive.<br>
# Line 2118  Maybe the easiest way to do so is instal Line 2193  Maybe the easiest way to do so is instal
2193  <br>  <br>
2194  Boot into <b>Super Grub Disk</b>.</p>  Boot into <b>Super Grub Disk</b>.</p>
2195    
2196  <p><img src="images/supergrubdisk-01a.png"><br>  <p><img src="images/supergrubdisk-01a.png"><br>
2197  Choose the option "<font color="Red"><b>WIN => MBR & !WIN!&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:(((((((((((((((((((((</b></font>" and press ENTER. Windows will be booted automatically right after installing syslinux.</p>  Choose the option "<font color="Red"><b>WIN => MBR & !WIN!&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:(((((((((((((((((((((</b></font>" and press ENTER. Windows will be booted automatically right after installing syslinux.</p>
2198    
2199    
# Line 2129  Choose the option "<font color="Red"><b> Line 2204  Choose the option "<font color="Red"><b>
2204    
2205  <p>Contrary to various ways to restore NTLDR, there is only one way to install GRUB I recommend. That's <b>Super Grub Disk</b>, because it contains GRUB no matter what has happened to the hard drive(s). First, I boot into it.</p>  <p>Contrary to various ways to restore NTLDR, there is only one way to install GRUB I recommend. That's <b>Super Grub Disk</b>, because it contains GRUB no matter what has happened to the hard drive(s). First, I boot into it.</p>
2206    
2207  <p><img src="images/supergrubdisk-01b.png"><br>  <p><img src="images/supergrubdisk-01b.png"><br>
2208  I select "<font color="Red"><b>Choose Language & HELP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:-)))</b></font>" and press ENTER.</p>  I select "<font color="Red"><b>Choose Language & HELP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:-)))</b></font>" and press ENTER.</p>
2209    
2210  <H3><a name="grub-1"></a>Screen "S.G.D. Language Selection." [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>  <H3><a name="grub-1"></a>Screen "S.G.D. Language Selection." [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>
2211    
2212  <p><img src="images/supergrubdisk-02.png"><br>  <p><img src="images/supergrubdisk-02.png"><br>
2213  I select "<font color="Red"><b>English Super Grub Disk</b></font>" and press ENTER.</p>  I select "<font color="Red"><b>English Super Grub Disk</b></font>" and press ENTER.</p>
2214    
2215  <p><img src="images/supergrubdisk-03.png"><br>  <p><img src="images/supergrubdisk-03.png"><br>
2216  I press ENTER...</p>  I press ENTER...</p>
2217    
2218  <p><img src="images/supergrubdisk-04.png"><br>  <p><img src="images/supergrubdisk-04.png"><br>
2219  ...and then ENTER again...</p>  ...and then ENTER again...</p>
2220    
2221  <p><img src="images/supergrubdisk-05.png"><br>  <p><img src="images/supergrubdisk-05.png"><br>
2222  ...and then ENTER once again...</p>  ...and then ENTER once again...</p>
2223    
2224  <p><img src="images/supergrubdisk-06.png"><br>  <p><img src="images/supergrubdisk-06.png"><br>
2225  ...and finally ENTER one more time.</p>  ...and finally ENTER one more time.</p>
2226    
2227  <H3><a name="grub-2"></a>Screen "English Super Grub Disk (Help)" [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>  <H3><a name="grub-2"></a>Screen "English Super Grub Disk (Help)" [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>
2228    
2229  <p><img src="images/supergrubdisk-07.png"><br>  <p><img src="images/supergrubdisk-07.png"><br>
2230  I select "<font color="Red"><b>Advanced</b></font>".</p>  I select "<font color="Red"><b>Advanced</b></font>".</p>
2231    
2232  <H3><a name="grub-3"></a>Screen "Advanced (Help)" [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>  <H3><a name="grub-3"></a>Screen "Advanced (Help)" [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>
2233    
2234  <p><img src="images/supergrubdisk-08.png"><br>  <p><img src="images/supergrubdisk-08.png"><br>
2235  I select "<font color="Red"><b>GRUB</b></font>" and press ENTER.</p>  I select "<font color="Red"><b>GRUB</b></font>" and press ENTER.</p>
2236    
2237  <H3><a name="grub-4"></a>Screen "GRUB (Help)" [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>  <H3><a name="grub-4"></a>Screen "GRUB (Help)" [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>
2238    
2239  <p><img src="images/supergrubdisk-09.png"><br>  <p><img src="images/supergrubdisk-09.png"><br>
2240  I select "<font color="Red"><b>Restore GRUB in Hard Disk (MBR)</b></font>" and press ENTER...</p>  I select "<font color="Red"><b>Restore GRUB in Hard Disk (MBR)</b></font>" and press ENTER...</p>
2241    
2242  <p><img src="images/supergrubdisk-10.png"><br>  <p><img src="images/supergrubdisk-10.png"><br>
2243  ...and ENTER.</p>  ...and ENTER.</p>
2244    
2245  <H3><a name="grub-5"></a>Screen "Restore GRUB in Hard Disk (MBR) (Help)" [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>  <H3><a name="grub-5"></a>Screen "Restore GRUB in Hard Disk (MBR) (Help)" [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>
2246    
2247  <p><img src="images/supergrubdisk-11.png"><br>  <p><img src="images/supergrubdisk-11.png"><br>
2248  I select "<font color="Red"><b>Manual Restore GRUB in Hard Disk (MBR)</b></font>" and press ENTER. If you want to install GRUB to the Master Boot Record of the first hard drive, "<font color="Red"><b>Automatically Install</b></font>" is a better choice. If you don't know if you want GRUB to the first or some other disk, you most likely want it to the first disk.</p>  I select "<font color="Red"><b>Manual Restore GRUB in Hard Disk (MBR)</b></font>" and press ENTER. If you want to install GRUB to the Master Boot Record of the first hard drive, "<font color="Red"><b>Automatically Install</b></font>" is a better choice. If you don't know if you want GRUB to the first or some other disk, you most likely want it to the first disk.</p>
2249    
2250  <H3><a name="grub-6"></a>Screen "Manual Restore GRUB in Hard Disk (MBR) (Help)" [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>  <H3><a name="grub-6"></a>Screen "Manual Restore GRUB in Hard Disk (MBR) (Help)" [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>
2251    
2252  <p><img src="images/supergrubdisk-12.png"><br>  <p><img src="images/supergrubdisk-12.png"><br>
2253  I confirm my decision by selecting "<font color="Red"><b>Manual Restore GRUB in Hard Disk (MBR)</b></font>" again and pressing ENTER.</p>  I confirm my decision by selecting "<font color="Red"><b>Manual Restore GRUB in Hard Disk (MBR)</b></font>" again and pressing ENTER.</p>
2254    
2255  <H3><a name="grub-7"></a>Screen "Partition of GRUB" [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>  <H3><a name="grub-7"></a>Screen "Partition of GRUB" [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>
2256    
2257  <p><img src="images/supergrubdisk-13.png"><br>  <p><img src="images/supergrubdisk-13.png"><br>
2258  In this screen I can select the disk that contains the partition that contains the files needed by GRUB. In this case, that disk is the external hard drive. As you can see, the disk is only three megabytes in size - because the computer used for screenshots is still virtual. Actually, the "disk" where I'm installing GRUB is just a file.</p>  In this screen I can select the disk that contains the partition that contains the files needed by GRUB. In this case, that disk is the external hard drive. As you can see, the disk is only three megabytes in size - because the computer used for screenshots is still virtual. Actually, the "disk" where I'm installing GRUB is just a file.</p>
2259    
2260  <H3><a name="grub-8"></a>Next Screen [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>  <H3><a name="grub-8"></a>Next Screen [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>
2261    
2262  <p><img src="images/supergrubdisk-14.png"><br>  <p><img src="images/supergrubdisk-14.png"><br>
2263  This is where I choose the partition where GRUB files reside. This disk contains only one partition.</p>  This is where I choose the partition where GRUB files reside. This disk contains only one partition.</p>
2264    
2265  <H3><a name="grub-9"></a>Screen "Restore to MBR of Hard Disk" [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>  <H3><a name="grub-9"></a>Screen "Restore to MBR of Hard Disk" [<a href="#sgd-top" title="go to top of the page">^</a>]</H3>
2266    
2267  <p><img src="images/supergrubdisk-15.png"><br>  <p><img src="images/supergrubdisk-15.png"><br>
2268  I select the external hard drive to install GRUB to its Master Boot Record.</p>  I select the external hard drive to install GRUB to its Master Boot Record.</p>
2269    
2270  <p><img src="images/supergrubdisk-12.png"><br>  <p><img src="images/supergrubdisk-12.png"><br>
2271  Some text scrolled in the screen (too fast to read or take a screenshot) and I was back at this screen. I rebooted the computer. (In this situation, you can safely do a "hard reboot" by pressing reset button once or power button twice.)</p>  Some text scrolled in the screen (too fast to read or take a screenshot) and I was back at this screen. I rebooted the computer. (In this situation, you can safely do a "hard reboot" by pressing reset button once or power button twice.)</p>
2272    
2273  <p><img src="images/grub-loading.png"><br>  <p><img src="images/grub-loading.png"><br>
2274  GRUB booted successfully.</p>  GRUB booted successfully.</p>
2275    
2276    
2277    </div>
2278    
2279  <a name="oldboot-top"></a>  <a name="oldboot-top"></a>
2280  <H2 style="font-size: 2em;"><a name="oldboot-intro"></a>Booting an old PC <span class="hideprint">[<a href="#oldboot-top" title="go to top of the page">^</a>]</span></H2>  <H2 style="font-size: 2em;"><a name="oldboot-intro"></a>Booting an old PC <span class="hideprint">[<a href="#oldboot-top" title="go to top of the page">^</a>]</span></H2>
2281  <p>Have you ever tried to boot an old PC off a CD-ROM, and found out it wouldn't, because its BIOS does not support it, or it's faulty or for any other reason? Well, I have. So this page is an effort to solve this problem.</p>  <p>Have you ever tried to boot an old PC off a CD-ROM, and found out it wouldn't, because its BIOS does not support it, or it's faulty or for any other reason? Well, I have. So this page is an effort to solve this problem.</p>
# Line 2391  The following pressentation has been mad Line 2468  The following pressentation has been mad
2468  <p>In UNIX-based systems, a partition is used to host the / (root) file system, and optionally the /opt, /usr and /home file systems. There may also be a swap partition, which doesn't host any file system.</p>  <p>In UNIX-based systems, a partition is used to host the / (root) file system, and optionally the /opt, /usr and /home file systems. There may also be a swap partition, which doesn't host any file system.</p>
2469  <p>Each operatin system provides some kind of tool to create and manage partitions. Examples of such tools are <b>fdisk</b> in DOS/Windows, <b>fdisk</b>, <b>sfdisk</b> and <b>parted</b> in Linux, etc.</p>  <p>Each operatin system provides some kind of tool to create and manage partitions. Examples of such tools are <b>fdisk</b> in DOS/Windows, <b>fdisk</b>, <b>sfdisk</b> and <b>parted</b> in Linux, etc.</p>
2470  <H3><a name="partitions-extended"></a>What is the difference between primary, extended and logical partitions? <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="partitions-extended"></a>What is the difference between primary, extended and logical partitions? <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>
2471  <p>Information about partitions is saved in so-called partition table in Master Boot Record. MBR itself is only 512 bytes in size, and only 64 bytes are reserved for partition table. That's not enough, and there are many workarounds to bypass limitations caused by the size, for example <a href="http://en.wikipedia.org/wiki/Logical_block_addressing#LBA.2C_ATA_devices_and_Enhanced_BIOS" target="_blank">logical block addressing</a>. Extended partitions are another workaround.</p>  <p>Information about partitions is saved in so-called partition table in Master Boot Record. MBR itself is only 512 bytes in size, and only 64 bytes are reserved for partition table. That's not enough, and there are many workarounds to bypass limitations caused by the size, for example <a href="http://en.wikipedia.org/wiki/Logical_block_addressing#Enhanced_BIOS" target="_blank">logical block addressing</a>. Extended partitions are another workaround.</p>
2472  <p>Partition table can only store information about four partitions. If one has, for example, two GNU/Linux distributions on the same disk, both of them having separate root partitions, shared /home and shared swap, the partition number limit has been hit already.</p>  <p>Partition table can only store information about four partitions. If one has, for example, two GNU/Linux distributions on the same disk, both of them having separate root partitions, shared /home and shared swap, the partition number limit has been hit already.</p>
2473  <p>A partition that is mentioned in the partition table is called primary partition. Because of the limit, one disk can only contain 1-4 primary partitions.</p>  <p>A partition that is mentioned in the partition table is called primary partition. Because of the limit, one disk can only contain 1-4 primary partitions.</p>
2474  <p>An extended partition fixes the problem simply by containing more boot records, called Extended Boot Records (EBR). Each EBR contains information about one logical partition and, if the extended partition contains multiple logical partitions, link to the next EBR. Thus, an extended partition can contain unlimited amount of logical partitions.</p>  <p>An extended partition fixes the problem simply by containing more boot records, called Extended Boot Records (EBR). Each EBR contains information about one logical partition and, if the extended partition contains multiple logical partitions, link to the next EBR. Thus, an extended partition can contain unlimited amount of logical partitions.</p>
# Line 2468  The following pressentation has been mad Line 2545  The following pressentation has been mad
2545    </tr>    </tr>
2546      <tr>      <tr>
2547      <th>ext4</th>      <th>ext4</th>
2548      <td style="background-color: rgb(255,0,0)">No***</td>      <td style="background-color: rgb(255,127,0)">3rd party driver</td>
2549          <td style="background-color: rgb(0,255,0)">Native</td>          <td style="background-color: rgb(0,255,0)">Native</td>
2550          <td style="background-color: rgb(255,127,0)">16 GB-16 TB*</td>          <td style="background-color: rgb(255,127,0)">16 GB-16 TB*</td>
2551          <td style="background-color: rgb(0,255,0)">Yes</td>          <td style="background-color: rgb(0,255,0)">Yes</td>
# Line 2484  The following pressentation has been mad Line 2561  The following pressentation has been mad
2561    </tr>    </tr>
2562  </table>  </table>
2563  <p>* Depends on cluster size<br>  <p>* Depends on cluster size<br>
2564  ** <a href="http://support.microsoft.com/kb/955704" target="_blank">This update</a> adds exFAT support to Windows XP<br>  ** <a href="http://support.microsoft.com/kb/955704" target="_blank">This update</a> adds exFAT support to Windows XP</p>
 *** <a href="http://ext2read.blogspot.com/" target="_blank">Ext2read</a> makes accessing ext4 partitions possible, but it's not a driver and the access is read-only</p>  
2565  <p>Operating system support:</p>  <p>Operating system support:</p>
2566  <ul>  <ul>
2567  <li>"Native" means that the kernel supports the filesystem and the OS can boot from a partition using that FS.</li>  <li>"Native" means that the kernel supports the filesystem and the OS can boot from a partition using that FS.</li>
2568  <li>"Built-in" means that the kernel supports the filesystem, but booting from a partition containing such FS is very difficult.</li>  <li>"Built-in" means that the kernel supports the filesystem, but booting from a partition containing such FS is very difficult.</li>
2569  <li>"Driver included" means that ntfs-3g (the driver that adds NTFS support to Linux) comes with most GNU/Linux distributions.</li>  <li>"Driver included" means that ntfs-3g (the driver that adds NTFS support to Linux) comes with most GNU/Linux distributions.</li>
2570  <li>"3rd party driver" means that drivers to add filesystem support are available, but must be downloaded and installed separately. The ext2/3 drivers are <a href="http://www.fs-driver.org" target="_blank">Ext2 IFS</a> and <a href="http://www.ext2fsd.com" target="_blank">Ext2fsd</a> and the exFAT driver is <a href="http://code.google.com/p/exfat/" target="_blank">exfat</a>.</li>  <li>"3rd party driver" means that a driver to add filesystem support is available, but must be downloaded and installed separately. The ext2/3/4 driver is <a href="http://www.ext2fsd.com" target="_blank">Ext2fsd</a> and the exFAT driver is <a href="http://code.google.com/p/exfat/" target="_blank">exfat</a>.</li>
 <li>"No" means that there is no way to get read-write filesystem support.</li>  
2571  </ul>  </ul>
2572  <H2><a name="filesystems"></a>Filesystems <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="filesystems"></a>Filesystems <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H2>
2573  <p>This section contains more information about most popular filesystems.</p>  <p>This section contains more information about most popular filesystems.</p>
# Line 2500  The following pressentation has been mad Line 2575  The following pressentation has been mad
2575  <p>The initial version of FAT (File Allocation Table), now referred as FAT12, was designed for floppy disks. A FAT12 partition can only be up to 32 megabytes in size. After that, PCs equipped with hard drives were introcuded by IBM and the sizes of hard drives began growing. Microsoft answered the need by developing first initial FAT16 and then final FAT16.</p>  <p>The initial version of FAT (File Allocation Table), now referred as FAT12, was designed for floppy disks. A FAT12 partition can only be up to 32 megabytes in size. After that, PCs equipped with hard drives were introcuded by IBM and the sizes of hard drives began growing. Microsoft answered the need by developing first initial FAT16 and then final FAT16.</p>
2576  <p>FAT16 partition can be up to two gigabytes in size. In the middle of 1990s, that limit was becoming a problem. Microsoft pushed the limit up by updating FAT again.</p>  <p>FAT16 partition can be up to two gigabytes in size. In the middle of 1990s, that limit was becoming a problem. Microsoft pushed the limit up by updating FAT again.</p>
2577  <p>FAT32 was first introduced with Windows 95 OSR2. Windows 98, Windows Me, Windows 2000 and newer support FAT32 too. Linux kernel has supported FAT32 almost as long as Windows, but booting GNU/Linux from FAT32 partition is difficult and actually requires DOS to be installed in the partition as well. (<a href="http://en.wikipedia.org/wiki/FAT_filesystem_and_Linux#Installing_Linux_on_and_booting_it_from_FAT_volumes_using_umsdos" target="_blank">more information</a>)</p>  <p>FAT32 was first introduced with Windows 95 OSR2. Windows 98, Windows Me, Windows 2000 and newer support FAT32 too. Linux kernel has supported FAT32 almost as long as Windows, but booting GNU/Linux from FAT32 partition is difficult and actually requires DOS to be installed in the partition as well. (<a href="http://en.wikipedia.org/wiki/FAT_filesystem_and_Linux#Installing_Linux_on_and_booting_it_from_FAT_volumes_using_umsdos" target="_blank">more information</a>)</p>
2578  <p>FAT32 partition can be up to two terabytes in size. As of now (July 2010), there are hard drives that hit the limit, but don't exceed it. A single file within FAT32 partition can be up to four gigabytes in size.</p>  <p>FAT32 partition can be up to two terabytes in size. There are already hard drives that exceed the limit. A single file within FAT32 partition can be up to four gigabytes in size.</p>
2579  <p>Because FAT32 is, in the end, based on FAT12, it has very few features. It doesn't support file permissions, hard/symbolic links, encryption, compression, alternative data streams, journaling... It lacks support for nearly anything that defines a modern filesystem. However, due to very few features, FAT32 is very fast filesystem if it's not fragmented or on a Flash-based drive. Mind you, FAT32 fragments very fast.</p>  <p>Because FAT32 is, in the end, based on FAT12, it has very few features. It doesn't support file permissions, hard/symbolic links, encryption, compression, alternative data streams, journaling... It lacks support for nearly anything that defines a modern filesystem. However, due to very few features, FAT32 is very fast filesystem if it's not fragmented or on a Flash-based drive. Mind you, FAT32 fragments very fast.</p>
2580  <p>Due to excellent operating system support, I recommend FAT32 for storing files which should be accessible in both Windows and GNU/Linux. FAT32 is also a good filesystem on Solid State Drives and thumb drives due to its performance.</p>  <p>Due to excellent operating system support, I recommend FAT32 for storing files which should be accessible in both Windows and GNU/Linux. FAT32 is also a good filesystem on Solid State Drives and thumb drives due to its performance.</p>
2581  <H3><a name="partitions-ext2"></a>ext2 <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="partitions-ext2"></a>ext2 <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>
2582  <p>Ext2 or ext2fs is the successor of extfs (extended file system). Extfs didn't support separated timestamps for access, data modification and inode modification. In order to add support for them, and make the filesystem extendable, a new filesystem had to be created.</p>  <p>Ext2 or ext2fs is the successor of extfs (extended file system). Extfs didn't support separated timestamps for access, data modification and inode modification. In order to add support for them, and make the filesystem extendable, a new filesystem had to be created.</p>
2583  <p>Ext2 was developed in January 1993, earlier than any other filesystem mentioned in this page.</p>  <p>Ext2 was developed in January 1993, earlier than any other filesystem mentioned in this page.</p>
2584  <p>Because ext2 is designed for GNU/Linux, support in Linux kernel was implemented immediately. The first Windows driver supporting ext2, <a href="http://www.ext2fsd.com" target="_blank">Ext2fsd</a> 0.01, was released on 25 January 2002. Both Windows drivers for ext2 work only on Windows NT operating systems (NT 4.0 up to Vista, 7 isn't supported yet).</p>  <p>Because ext2 is designed for GNU/Linux, support in Linux kernel was implemented immediately. The first Windows driver supporting ext2, <a href="http://www.ext2fsd.com" target="_blank">Ext2fsd</a> 0.01, was released on 25 January 2002. Ext2fsd works only on Windows NT operating systems starting from Windows 2000.</p>
2585  <p>The best property of ext2 is extensibility. The superblock contains information about which version the filesystem is (ext2, ext3 or ext4) and which extensions and features are in use. By using these pieces of information, the operating system or driver can decide whether or not mounting the partition is safe. That's the most important reason why most GNU/Linux distributions still use successors of ext2 as default filesystems.</p>  <p>The best property of ext2 is extensibility. The superblock contains information about which version the filesystem is (ext2, ext3 or ext4) and which extensions and features are in use. By using these pieces of information, the operating system or driver can decide whether or not mounting the partition is safe. That's the most important reason why most GNU/Linux distributions still use successors of ext2 as default filesystems.</p>
2586  <p>Depending on cluster size, ext2 partition can be up to 2-32 terabytes in size. File size limit is 16 GB-2 TB.</p>  <p>Depending on cluster size, ext2 partition can be up to 2-32 terabytes in size. File size limit is 16 GB-2 TB.</p>
2587  <p>Ext2 supports file permissions, both hard and symbolic links and extended file attributes. Encryption, compression and journaling are unsupported.</p>  <p>Ext2 supports file permissions, both hard and symbolic links and extended file attributes. Encryption, compression and journaling are unsupported.</p>
2588  <p>Due to lack of journaling support and existence of Windows drivers, I recommend using ext2 if you're going to install GNU/Linux on a SSD drive and want to be able to access files within Windows too.</p>  <p>Lack of journaling support is the worst limitation of ext2. What was done in order to get rid of the limitation?</p>
 <p>However, lack of journaling support is the worst limitation of ext2. And what was done in order to get rid of the limitation?</p>  
2589  <H3><a name="partitions-ext3"></a>ext3 <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="partitions-ext3"></a>ext3 <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>
2590  <p>Ext3, the successor of ext2, was introduced in Linux kernel on November 2001. It supports journaling, can be grown online and optionally indexes large directories.</p>  <p>Ext3, the successor of ext2, was introduced in Linux kernel on November 2001. It supports journaling, can be grown online and optionally indexes large directories.</p>
2591  <p>Ext2 IFS and Ext2fsd can mount ext3 partition as ext2 if the journal is empty. (If it's not, something is wrong - journal is always emptied when the partition is unmounted or the computer is shut down.) Thus, ext3 support under Windows is just as good/bad as ext2 support.</p>  <p>Ext2fsd can mount ext3 partition as ext2. Thus, ext3 support under Windows is just as good/bad as ext2 support.</p>
2592  <p>Partition and file size limits are the same as in ext2: partition size limit is 2-32 TB and file size limit 16 GB-2 TB, depending on cluster size.</p>  <p>Partition and file size limits are the same as in ext2: partition size limit is 2-32 TB and file size limit 16 GB-2 TB, depending on cluster size.</p>
2593  <p>Due to journaling support and existence of Windows drivers, ext3 is a good choice if you're going to install GNU/Linux on a mechanical hard drive and want to be able to access files within Windows.</p>  <p>Ext3 is becoming obsolete because there is...</p>
2594  <H3><a name="partitions-ext4"></a>ext4 <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="partitions-ext4"></a>ext4 <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>
2595  <p>Linux kernel support for ext4, the successor of ext3, was marked stable code on October 2008. Ext4 contains multiple performance and stability improvements over ext3.</p>  <p>Linux kernel support for ext4, the successor of ext3, was marked stable code on October 2008. Ext4 contains multiple performance and stability improvements over ext3.</p>
2596  <p>The most important new feature is extents. An extent is a contiguous area of storage that has been reserved for a file. When a process starts to write to a file, the whole extent is allocated even before the write operation begins. The idea is that even if the file is larger than expected, it doesn't fragment if it doesn't exceed the size of the extent.</p>  <p>The most important new feature is extents. An extent is a contiguous area of storage that has been reserved for a file. When a process starts to write to a file, the whole extent is allocated even before the write operation begins. The idea is that even if the file is larger than expected, it doesn't fragment if it doesn't exceed the size of the extent.</p>
2597  <p>Another important improvement is larger partition size limit: an ext4 partition can be even one exabyte in size. (An exabyte is a million terabytes.) In addition, a directory within an ext4 partition can contain up to 64 000 subdirectories (instead of 32 000, as in ext2/3) and timestamps are much more accurate. The file size limit is 16 GB-16 TB, depending on cluster size.</p>  <p>Another important improvement is larger partition size limit: an ext4 partition can be even one exabyte in size. (An exabyte is a million terabytes.) In addition, a directory within an ext4 partition can contain up to 64 000 subdirectories (instead of 32 000, as in ext2/3) and timestamps are much more accurate. The file size limit is 16 GB-16 TB, depending on cluster size.</p>
2598  <p>Unfortunately, Ext2 IFS and Ext2Fsd don't support ext4 and are unable to mount ext4 partition if extents are enabled. They can be disabled, but other improvements of ext4 aren't that important for most people - using ext2 or ext3 is just easier. It is also possible to keep extents enabled and browse the partition using <a href="http://ext2read.blogspot.com/" target="_blank">Ext2read</a>, but Ext2read doesn't allow the user to write to the partition.</p>  <p>Ext2fsd 0.50, released on 5 February 2011, supports ext4 and is able to mount ext4 partition even if extents are enabled. Thus, ext4 support under Windows is just as good/bad as ext2 support.</p>
2599  <p>Due to its features, ext4 is a good filesystem on computers that only have GNU/Linux installed. Because journaling can be disabled, it is suitable for Solid State Drives and thumb drives too.</p>  <p>Due to availability of Ext2fsd 0.50 and additional features, ext4 has become the de-facto GNU/Linux filesystem. Because journaling can be disabled, it is suitable for Solid State Drives and thumb drives too.</p>
2600  <H3><a name="partitions-ntfs"></a>NTFS <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="partitions-ntfs"></a>NTFS <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>
2601  <p>At the end of 1980s, IBM and Microsoft were developing OS/2 operating system. Both companies expected OS/2 1.1, released on 1988, to be the first popular operating system having a GUI, Presentation Manager. Even though it didn't become too popular during its first years, Microsoft didn't complain: Windows 2 didn't sell any better.</p>  <p>At the end of 1980s, IBM and Microsoft were developing OS/2 operating system. Both companies expected OS/2 1.1, released on 1988, to be the first popular operating system having a GUI, Presentation Manager. Even though it didn't become too popular during its first years, Microsoft didn't complain: Windows 2 didn't sell any better.</p>
2602  <p>But on May 1990, Microsoft released Windows 3.0. Millions of copies of it were sold during its first year, and Microsoft began to believe that OS/2 had failed due to decisions of IBM. At autumn 1990, Microsoft stopped cooperating with IBM, recasted OS/2 3.0 as Windows NT and continued developing it alone, leaving IBM alone with OS/2.</p>  <p>But on May 1990, Microsoft released Windows 3.0. Millions of copies of it were sold during its first year, and Microsoft began to believe that OS/2 had failed due to decisions of IBM. At autumn 1990, Microsoft stopped cooperating with IBM, recasted OS/2 3.0 as Windows NT and continued developing it alone, leaving IBM alone with OS/2.</p>
# Line 2607  Linux partitions, such as <b>ext2</b>, < Line 2681  Linux partitions, such as <b>ext2</b>, <
2681  </ul>  </ul>
2682  <H2><a name="example"></a>Partitioning example <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="example"></a>Partitioning example <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H2>
2683  <p>This section contains a partitioning example. I simulate the following situation in a virtual machine:</p>  <p>This section contains a partitioning example. I simulate the following situation in a virtual machine:</p>
2684  <p>I have two partitions in my disk: <b>/dev/sda1</b> that contains a GNU/Linux distribution, and <b>/dev/sda2</b> that is a swap partition. Here we can see the output of <b>fdisk</b>:</p>  <p>I have two partitions in my disk: <b>/dev/sda1</b> that contains a GNU/Linux distribution, and <b>/dev/sda2</b> that is a swap partition. Here we can see the output of <b>parted</b>:</p>
2685  <p class="newcode">root@sysresccd /root % fdisk -l<br>  <p class="newcode">root@sysresccd /root % parted -l<br>
2686    Model: ATA VBOX HARDDISK (scsi)<br>
2687    Disk /dev/sda: 2097MB<br>
2688    Sector size (logical/physical): 512B/512B<br>
2689    Partition Table: msdos<br>
2690    <br>
2691    Number&nbsp;&nbsp;Start&nbsp;&nbsp;&nbsp;End&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Size&nbsp;&nbsp;&nbsp;&nbsp;Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;File&nbsp;system&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Flags<br>
2692    &nbsp;1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;32.3kB&nbsp;&nbsp;1679MB&nbsp;&nbsp;1679MB&nbsp;&nbsp;primary&nbsp;&nbsp;ext4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;boot<br>
2693    &nbsp;2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1679MB&nbsp;&nbsp;2097MB&nbsp;&nbsp;418MB&nbsp;&nbsp;&nbsp;primary&nbsp;&nbsp;linux-swap(v1)<br>
2694    <br>
2695  <br>  <br>
2696  Disk /dev/sda: 2097 MB, 2097152000 bytes<br>  Warning: Unable to open /dev/sr0 read-write (Read-only file system).&nbsp;&nbsp;/dev/sr0 has been opened read-only.<br>
2697  64 heads, 63 sectors/track, 1015 cylinders<br>  Error: /dev/sr0: unrecognised disk label<br>
2698  Units = cylinders of 4032 * 512 = 2064384 bytes<br>  <br>
2699  Disk identifier: 0x00058a4a<br>  Error: /dev/fd0: unrecognised disk label</p>
 <br>  
 &nbsp;&nbsp;&nbsp;Device&nbsp;Boot&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Start&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;End&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Blocks&nbsp;&nbsp;&nbsp;Id&nbsp;&nbsp;System<br>  
 /dev/sda1&nbsp;&nbsp;&nbsp;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;812&nbsp;&nbsp;&nbsp;&nbsp;1636960+&nbsp;&nbsp;83&nbsp;&nbsp;Linux<br>  
 /dev/sda2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;813&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1015&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;409248&nbsp;&nbsp;&nbsp;82&nbsp;&nbsp;Linux swap / Solaris</p>  
2700  <p>Now I'm going to install another distribution on the same disk. First of all, I need one more partition, because only one distro can be installed on one partition. In addition, I want to separate /home to its own partition in order to be able to share it between distributions.</p>  <p>Now I'm going to install another distribution on the same disk. First of all, I need one more partition, because only one distro can be installed on one partition. In addition, I want to separate /home to its own partition in order to be able to share it between distributions.</p>
2701  <p>Because the whole disk is already allocated, I must shrink at least one existing partition in order to create new partitions. I'll shrink both of them to half (<b>/dev/sda1</b> from 1,6 gigabytes to 800 megabytes, and <b>/dev/sda2</b> from 400 MB to 200 MB). In addition, I'll move <b>/dev/sda2</b> right next to <b>/dev/sda1</b> to keep the partitions in order.</p>  <p>Because the whole disk is already allocated, I must shrink at least one existing partition in order to create new partitions. I'll shrink both of them to half (<b>/dev/sda1</b> from 1,6 gigabytes to 800 megabytes, and <b>/dev/sda2</b> from 400 MB to 200 MB). In addition, I'll move <b>/dev/sda2</b> right next to <b>/dev/sda1</b> to keep the partitions in order.</p>
2702  <p>But how many partitions there will be in total? One, two, three... four! Phew, I was near to paint myself into a corner. If I created only primary partitions, I'd be unable to create any more partitions on the disk. Thus, I'll create an extended partition instead and two logical partitions within it. Then I'll be able to create more logical partitions later if required.</p>  <p>But how many partitions there will be in total? One, two, three... four! Phew, I was near to paint myself into a corner. If I created only primary partitions, I'd be unable to create any more partitions on the disk. Thus, I'll create an extended partition instead and two logical partitions within it. Then I'll be able to create more logical partitions later if required.</p>
# Line 3218  Smart BootManager - <a href="http://btmg Line 3297  Smart BootManager - <a href="http://btmg
3297  </p>  </p>
3298  </div>  </div>
3299    <div id="footer">    <div id="footer">
3300    <p>Copyright: &#169; <a href="mailto:&#115;&#110;&#103;&#064;&#104;&#101;&#108;&#108;&#117;&#103;&#046;&#103;&#114;?subject=About Clonezilla-SysRescCD v 3.1.0">Spiros Georgaras</a>, 2007-2010<br /><br/>    <p>Copyright: &#169; <a href="mailto:&#115;&#110;&#103;&#064;&#104;&#101;&#108;&#108;&#117;&#103;&#046;&#103;&#114;?subject=About Clonezilla-SysRescCD v 3.2.0">Spiros Georgaras</a>, 2007-2010<br /><br/>
3301    Hosted by <a href="http://www.hellug.gr" target="_blank" title="Hellenic Linux User Group">HEL.L.U.G.</a></p>    Hosted by <a href="http://hellug.gr/index.php/OSullogos/Tautothta?from=Main.HELLUG" target="_blank" title="Hellenic Linux User Group">HEL.L.U.G.</a></p>
3302    </div>    </div>
3303  </div>  </div>
3304    <div id="warning" align="center">
3305    WARNING<br>
3306    This is the UNSTABLE version of Clonezilla-SysRescCD<br>
3307    To access our current stable version, please click <a href="../index.html">here</a>
3308    </div>
3309  </body>  </body>
3310  </html>  </html>

Legend:
Removed from v.127  
changed lines
  Added in v.164

webmaster@linux.gr
ViewVC Help
Powered by ViewVC 1.1.26