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 |
|
|
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>30/09/2010 - v 3.2.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: 29/09/2010</H4></div> |
<div style="position: absolute; right: 0px;"><H4>Last update: 11/03/2011</H4></div> |
90 |
</div> |
</div> |
91 |
</div> |
</div> |
92 |
<div id="linkline"> |
<div id="linkline"> |
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.6-24 (mod)</td><td class="bordertable" >1.6.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 (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 (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 (mod)</td><td class="bordertable" >1.0.4 (mod)</td> |
<tr><td class="bordertable" >02/07/08</td><td class="bordertable" >2.6.0</td><td class="bordertable" >1.1.0-8 (mod)</td><td class="bordertable" >1.0.4 (mod)</td> |
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 |
|
- <b>Clonezilla Live</b> updated to version 1.2.6-24<br> |
180 |
|
- <b>SystemRescueCD</b> updated to version 1.6.1<br> |
181 |
|
- Fixed the splash image installation bug present in 3.1.0<br> |
182 |
|
Also, a filename relative to /home/partimag, can now be used<br> |
183 |
|
- Added -d command parameter to scrpit create-clonezilla-sysresccd<br> |
184 |
|
This way the temporary and output folder can be specified<br> |
185 |
|
- Using $HOME instead of /root in scrpit create-clonezilla-sysresccd<br> |
186 |
|
- Script imginfo can display extended info (command line parameter -e)<br> |
187 |
|
Extended info is: image size and disk model |
188 |
|
</td></tr> |
189 |
<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"> |
190 |
- <b>Clonezilla Live</b> updated to version 1.2.5-35<br> |
- <b>Clonezilla Live</b> updated to version 1.2.5-35<br> |
191 |
- <b>SystemRescueCD</b> updated to version 1.6.0<br> |
- <b>SystemRescueCD</b> updated to version 1.6.0<br> |
536 |
</ul> |
</ul> |
537 |
<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> |
538 |
<p class="newcode"><font color="Green">K:</font><br> |
<p class="newcode"><font color="Green">K:</font><br> |
539 |
cd bootprog<br> |
cd utils/bootprog<br> |
540 |
syslinux -ma <font color="Green">K:</font></p> |
syslinux -ma <font color="Green">K:</font></p> |
541 |
<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> |
542 |
<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> |
656 |
Available kernels (boot images):</p> |
Available kernels (boot images):</p> |
657 |
<ul class="otherpage" style="padding: 0px 10px 20px 40px"> |
<ul class="otherpage" style="padding: 0px 10px 20px 40px"> |
658 |
<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. |
659 |
</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). |
660 |
</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> |
661 |
</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>. |
662 |
</li> |
</li> |
666 |
<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> |
667 |
<p>Press <TAB> to add additional options (in SystemRescueCd-1.5 and more recent) |
<p>Press <TAB> to add additional options (in SystemRescueCd-1.5 and more recent) |
668 |
</p> |
</p> |
669 |
<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. |
670 |
</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. |
671 |
</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=<device> 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=<device> 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>. |
672 |
</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. |
673 |
</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>. |
674 |
</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. |
675 |
</li></ul> |
</li></ul> |
676 |
<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> |
677 |
<ul><li><b>dodebug</b>: Enables verbose messages in linuxrc |
<ul><li><b>dodebug</b>: Enables verbose messages in linuxrc |
680 |
</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. |
681 |
</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 |
682 |
</li></ul> |
</li></ul> |
683 |
<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. |
684 |
</li></ul> |
</li></ul> |
685 |
<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. |
686 |
</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. |
697 |
</li></ul> |
</li></ul> |
698 |
<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. |
699 |
</li></ul> |
</li></ul> |
700 |
<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. |
701 |
</li></ul> |
</li></ul> |
702 |
<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> |
703 |
<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. |
704 |
</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... |
705 |
</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 |
706 |
</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. |
707 |
</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>. |
708 |
</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. |
709 |
</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>. |
710 |
</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. |
711 |
</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. |
712 |
</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) |
713 |
</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&t=2538&start=0" class="external text" title="http://www.sysresccd.org/forums/viewtopic.php?f=7&t=2538&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&t=2538&start=0" class="external text" title="http://www.sysresccd.org/forums/viewtopic.php?f=7&t=2538&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. |
714 |
</li></ul> |
</li></ul> |
715 |
<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> |
716 |
<p>SystemRescueCd provides several options for booting from the network using PXE. |
<p>SystemRescueCd provides several options for booting from the network using PXE. |
721 |
</p> |
</p> |
722 |
<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. |
723 |
</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. |
724 |
</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. |
725 |
</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. |
726 |
</li></ul> |
</li></ul> |
727 |
<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>. |
728 |
</p> |
</p> |
757 |
e.g. ocs_live_run="ocs-live-general"<br> |
e.g. ocs_live_run="ocs-live-general"<br> |
758 |
<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> |
759 |
<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> |
760 |
e.g. ocs_live_extra_param="-b -c restoredisk sarge-r5 hda" |
e.g. ocs_live_extra_param="--batch -c restoredisk sarge-r5 hda" |
761 |
<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> |
762 |
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> |
763 |
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) |
773 |
<font color=red>//NOTE//</font><br> |
<font color=red>//NOTE//</font><br> |
774 |
<ul> |
<ul> |
775 |
<li>This parameter was added in Clonezilla live 1.2.3-22 or later. |
<li>This parameter was added in Clonezilla live 1.2.3-22 or later. |
776 |
<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. |
<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. |
777 |
<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. |
778 |
</ul> |
</ul> |
779 |
<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> |
868 |
<a name="live-initramfs"></a><div class="otherpage" style="overflow: auto;"><pre> |
<a name="live-initramfs"></a><div class="otherpage" style="overflow: auto;"><pre> |
869 |
live-initramfs(7) |
live-initramfs(7) |
870 |
================= |
================= |
871 |
|
:man source: 1.157.3 |
872 |
|
:man manual: Debian Live |
873 |
Name |
Name |
874 |
---- |
---- |
875 |
live-initramfs - Debian Live initramfs hook |
live-initramfs - Debian Live initramfs hook |
906 |
Makes initramfs boot process more verbose. |
Makes initramfs boot process more verbose. |
907 |
fetch=*URL*:: |
fetch=*URL*:: |
908 |
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, |
909 |
copying to ram and booting it. |
copying to ram and booting it. Due to current limitations in busyboxs wget |
910 |
|
and DNS resolution, an URL can not contain a hostname but an IP only. |
911 |
|
Not working: http://example.com/path/to/your_filesystem.squashfs |
912 |
|
Working: http://1.2.3.4/path/to/your_filesystem.squashfs |
913 |
|
Also note that therefore it's currently not possible to fetch an image from a |
914 |
|
namebased virtualhost of an httpd if it is sharing the ip with the main httpd |
915 |
|
instance. |
916 |
hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*:: |
hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*:: |
917 |
Those parameters lets you override values read from the config file. |
Those parameters lets you override values read from the config file. |
918 |
ignore_uuid |
ignore_uuid |
930 |
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). |
931 |
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 |
932 |
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). |
933 |
ip[=**frommedia**]:: |
ip=[**frommedia**]:: |
934 |
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 |
935 |
system will use the (must be) media-preconfigured /etc/network/interfaces |
system will use the (must be) media-preconfigured /etc/network/interfaces |
936 |
instead. |
instead. |
951 |
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 |
952 |
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 |
953 |
for block devices is performed. |
for block devices is performed. |
954 |
|
Instead of specifing an actual device name, the keyword 'removable' can be used |
955 |
|
to limit the search of acceptable live media to removable type only. Note that |
956 |
|
if you want to further restrict the media to usb mass storage only, you can use |
957 |
|
the 'removable-usb' keyword. |
958 |
{live-media-encryption|encryption}=**TYPE**:: |
{live-media-encryption|encryption}=**TYPE**:: |
959 |
live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase, |
live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase, |
960 |
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 |
1001 |
disables the "persistent" feature, useful if the bootloader (like syslinux) has |
disables the "persistent" feature, useful if the bootloader (like syslinux) has |
1002 |
been installed with persistent enabled. |
been installed with persistent enabled. |
1003 |
noprompt |
noprompt |
1004 |
Do not prompt to eject the CD on reboot. |
Do not prompt to eject the CD or remove the USB flash drive on reboot. |
1005 |
nosudo:: |
nosudo:: |
1006 |
This parameter disables the automatic configuration of sudo. |
This parameter disables the automatic configuration of sudo. |
1007 |
swapon:: |
swapon:: |
1021 |
informations. If "nofiles" is specified, only filesystems with matching labels |
informations. If "nofiles" is specified, only filesystems with matching labels |
1022 |
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 |
1023 |
files. This results in shorter boot times. |
files. This results in shorter boot times. |
1024 |
|
persistent-path=PATH |
1025 |
|
live-initramfs will look for persistency files in the root directory of a partition, |
1026 |
|
with this parameter, the path can be configured so that you can have multiple |
1027 |
|
directories on the same partition to store persistency files. |
1028 |
{preseed/file|file}=**FILE**:: |
{preseed/file|file}=**FILE**:: |
1029 |
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 |
1030 |
database. |
database. |
1040 |
(mostly compressed) on "/live". This is not enabled by default because could |
(mostly compressed) on "/live". This is not enabled by default because could |
1041 |
lead to problems by applications like "mono" which store binary paths on |
lead to problems by applications like "mono" which store binary paths on |
1042 |
installation. |
installation. |
1043 |
|
silent |
1044 |
|
If you boot with the normal quiet parameter, live-initramfs hides most messages |
1045 |
|
of its own. When adding silent, it hides all. |
1046 |
textonly |
textonly |
1047 |
Start up to text-mode shell prompts, disabling the graphical user interface. |
Start up to text-mode shell prompts, disabling the graphical user interface. |
1048 |
timezone=**TIMEZONE**:: |
timezone=**TIMEZONE**:: |
1324 |
</ul> |
</ul> |
1325 |
<a name="backup-top"></a> |
<a name="backup-top"></a> |
1326 |
<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> |
1327 |
<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> |
1328 |
<p> |
<p> |
1329 |
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> |
1330 |
<br> |
<br> |
1387 |
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> |
1388 |
<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> |
1389 |
<p><img src="images/backup-09.png"> |
<p><img src="images/backup-09.png"> |
1390 |
<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> |
1391 |
<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> |
1392 |
<p>Here I can select the desired operation.<br> |
<p>Here I can select the desired operation.<br> |
1393 |
<br> |
<br> |
1400 |
</p> |
</p> |
1401 |
<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> |
1402 |
<p><img src="images/backup-12.png"><br> |
<p><img src="images/backup-12.png"><br> |
1403 |
Finally I am asked to select the partition to save.<br> |
Finally I am asked to select the disk to save.<br> |
1404 |
I just press ENTER again. |
I just press ENTER again. |
1405 |
</p> |
</p> |
1406 |
<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> |
1480 |
<img src="images/backup-smb-11.png"></p> |
<img src="images/backup-smb-11.png"></p> |
1481 |
<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> |
1482 |
<p><img src="images/backup-09.png"> |
<p><img src="images/backup-09.png"> |
1483 |
<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> |
1484 |
<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> |
1485 |
<p>Here I can select the desired operation.<br> |
<p>Here I can select the desired operation.<br> |
1486 |
<br> |
<br> |
1493 |
</p> |
</p> |
1494 |
<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> |
1495 |
<p><img src="images/backup-12.png"><br> |
<p><img src="images/backup-12.png"><br> |
1496 |
Finally I am asked to select the partition to save.<br> |
Finally I am asked to select the disk to save.<br> |
1497 |
I just press ENTER again. |
I just press ENTER again. |
1498 |
</p> |
</p> |
1499 |
<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> |
1574 |
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> |
1575 |
<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> |
1576 |
<p><img src="images/backup-09.png"><br> |
<p><img src="images/backup-09.png"><br> |
1577 |
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> |
1578 |
<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> |
1579 |
<p>Here I can select the desired operation.<br> |
<p>Here I can select the desired operation.<br> |
1580 |
<br> |
<br> |
1585 |
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> |
1586 |
<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> |
1587 |
<p><img src="images/restoration-12.png"><br> |
<p><img src="images/restoration-12.png"><br> |
1588 |
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> |
1589 |
<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> |
1590 |
<p><img src="images/restoration-13.png"><br> |
<p><img src="images/restoration-13.png"><br> |
1591 |
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> |
1608 |
<p>to reboot the system.</p> |
<p>to reboot the system.</p> |
1609 |
<a name="restore-top"></a> |
<a name="restore-top"></a> |
1610 |
<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> |
1611 |
<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> |
1612 |
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> |
1613 |
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> |
1614 |
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> |
1615 |
<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> |
1666 |
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> |
1667 |
<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> |
1668 |
<p><img src="images/backup-09.png"><br> |
<p><img src="images/backup-09.png"><br> |
1669 |
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> |
1670 |
<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> |
1671 |
<p>Here I can select the desired operation.<br> |
<p>Here I can select the desired operation.<br> |
1672 |
<br> |
<br> |
1743 |
<img src="images/k3b-00.png"><br> |
<img src="images/k3b-00.png"><br> |
1744 |
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> |
1745 |
<img src="images/k3b-01.png"><br> |
<img src="images/k3b-01.png"><br> |
1746 |
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> |
1747 |
<img src="images/k3b-02.png"><br> |
<img src="images/k3b-02.png"><br> |
1748 |
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> |
1749 |
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> |
1773 |
<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> |
1774 |
<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> |
1775 |
<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> |
1776 |
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> |
1777 |
<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> |
1778 |
<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> |
1779 |
<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> |
1780 |
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. |
2108 |
|
|
2109 |
<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> |
2110 |
|
|
2111 |
<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> |
2112 |
|
|
2113 |
<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> |
2114 |
<br> |
<br> |
2115 |
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> |
2116 |
<br> |
|
2117 |
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> |
2118 |
|
After selecting language, time, currency and keyboard, click <b>Next</b>.</p> |
2119 |
|
|
2120 |
|
<p><img src="images/windows7-01.png"><br> |
2121 |
|
Click <b>Repair your computer</b>.</p> |
2122 |
|
|
2123 |
|
<p><img src="images/windows7-02.png"><br> |
2124 |
|
Choose the option <b>Use recovery tools that can help fix problems starting Windows</b> and click <b>Next</b>.</p> |
2125 |
|
|
2126 |
|
<p><img src="images/windows7-03.png"><br> |
2127 |
|
You'll see a dialog box named <b>System Recovery Options</b>. Click <b>Command Prompt</b>.</p> |
2128 |
|
|
2129 |
|
<p><img src="images/windows7-04.png"><br> |
2130 |
|
Then you only need to execute one command:</p> |
2131 |
|
|
2132 |
<p class="newcode">Bootrec /FixMbr</p> |
<p class="newcode">Bootrec /FixMbr</p> |
2133 |
|
|
2134 |
<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> |
2135 |
|
|
2136 |
|
<p><img src="images/windows7-05.png"><br> |
2137 |
|
</p> |
2138 |
|
|
2139 |
<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> |
2140 |
|
|
2141 |
<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> |
2152 |
<br> |
<br> |
2153 |
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> |
2154 |
|
|
2155 |
<p><img src="images/supergrubdisk-01.png"><br> |
<p><img src="images/supergrubdisk-01.png"><br> |
2156 |
Just choose the option "<font color="Red"><b>!WIN! :(((</b></font>" and press ENTER.<br> |
Just choose the option "<font color="Red"><b>!WIN! :(((</b></font>" and press ENTER.<br> |
2157 |
<br> |
<br> |
2158 |
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> |
2178 |
<br> |
<br> |
2179 |
Boot into <b>Super Grub Disk</b>.</p> |
Boot into <b>Super Grub Disk</b>.</p> |
2180 |
|
|
2181 |
<p><img src="images/supergrubdisk-01a.png"><br> |
<p><img src="images/supergrubdisk-01a.png"><br> |
2182 |
Choose the option "<font color="Red"><b>WIN => MBR & !WIN! :(((((((((((((((((((((</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! :(((((((((((((((((((((</b></font>" and press ENTER. Windows will be booted automatically right after installing syslinux.</p> |
2183 |
|
|
2184 |
|
|
2189 |
|
|
2190 |
<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> |
2191 |
|
|
2192 |
<p><img src="images/supergrubdisk-01b.png"><br> |
<p><img src="images/supergrubdisk-01b.png"><br> |
2193 |
I select "<font color="Red"><b>Choose Language & HELP :-)))</b></font>" and press ENTER.</p> |
I select "<font color="Red"><b>Choose Language & HELP :-)))</b></font>" and press ENTER.</p> |
2194 |
|
|
2195 |
<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> |
2196 |
|
|
2197 |
<p><img src="images/supergrubdisk-02.png"><br> |
<p><img src="images/supergrubdisk-02.png"><br> |
2198 |
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> |
2199 |
|
|
2200 |
<p><img src="images/supergrubdisk-03.png"><br> |
<p><img src="images/supergrubdisk-03.png"><br> |
2201 |
I press ENTER...</p> |
I press ENTER...</p> |
2202 |
|
|
2203 |
<p><img src="images/supergrubdisk-04.png"><br> |
<p><img src="images/supergrubdisk-04.png"><br> |
2204 |
...and then ENTER again...</p> |
...and then ENTER again...</p> |
2205 |
|
|
2206 |
<p><img src="images/supergrubdisk-05.png"><br> |
<p><img src="images/supergrubdisk-05.png"><br> |
2207 |
...and then ENTER once again...</p> |
...and then ENTER once again...</p> |
2208 |
|
|
2209 |
<p><img src="images/supergrubdisk-06.png"><br> |
<p><img src="images/supergrubdisk-06.png"><br> |
2210 |
...and finally ENTER one more time.</p> |
...and finally ENTER one more time.</p> |
2211 |
|
|
2212 |
<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> |
2213 |
|
|
2214 |
<p><img src="images/supergrubdisk-07.png"><br> |
<p><img src="images/supergrubdisk-07.png"><br> |
2215 |
I select "<font color="Red"><b>Advanced</b></font>".</p> |
I select "<font color="Red"><b>Advanced</b></font>".</p> |
2216 |
|
|
2217 |
<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> |
2218 |
|
|
2219 |
<p><img src="images/supergrubdisk-08.png"><br> |
<p><img src="images/supergrubdisk-08.png"><br> |
2220 |
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> |
2221 |
|
|
2222 |
<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> |
2223 |
|
|
2224 |
<p><img src="images/supergrubdisk-09.png"><br> |
<p><img src="images/supergrubdisk-09.png"><br> |
2225 |
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> |
2226 |
|
|
2227 |
<p><img src="images/supergrubdisk-10.png"><br> |
<p><img src="images/supergrubdisk-10.png"><br> |
2228 |
...and ENTER.</p> |
...and ENTER.</p> |
2229 |
|
|
2230 |
<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> |
2231 |
|
|
2232 |
<p><img src="images/supergrubdisk-11.png"><br> |
<p><img src="images/supergrubdisk-11.png"><br> |
2233 |
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> |
2234 |
|
|
2235 |
<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> |
2236 |
|
|
2237 |
<p><img src="images/supergrubdisk-12.png"><br> |
<p><img src="images/supergrubdisk-12.png"><br> |
2238 |
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> |
2239 |
|
|
2240 |
<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> |
2241 |
|
|
2242 |
<p><img src="images/supergrubdisk-13.png"><br> |
<p><img src="images/supergrubdisk-13.png"><br> |
2243 |
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> |
2244 |
|
|
2245 |
<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> |
2246 |
|
|
2247 |
<p><img src="images/supergrubdisk-14.png"><br> |
<p><img src="images/supergrubdisk-14.png"><br> |
2248 |
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> |
2249 |
|
|
2250 |
<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> |
2251 |
|
|
2252 |
<p><img src="images/supergrubdisk-15.png"><br> |
<p><img src="images/supergrubdisk-15.png"><br> |
2253 |
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> |
2254 |
|
|
2255 |
<p><img src="images/supergrubdisk-12.png"><br> |
<p><img src="images/supergrubdisk-12.png"><br> |
2256 |
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> |
2257 |
|
|
2258 |
<p><img src="images/grub-loading.png"><br> |
<p><img src="images/grub-loading.png"><br> |
2259 |
GRUB booted successfully.</p> |
GRUB booted successfully.</p> |
2260 |
|
|
2261 |
|
|
2262 |
|
</div> |
2263 |
|
|
2264 |
<a name="oldboot-top"></a> |
<a name="oldboot-top"></a> |
2265 |
<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> |
2266 |
<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> |
2453 |
<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> |
2454 |
<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> |
2455 |
<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> |
2456 |
<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> |
2457 |
<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> |
2458 |
<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> |
2459 |
<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> |
2530 |
</tr> |
</tr> |
2531 |
<tr> |
<tr> |
2532 |
<th>ext4</th> |
<th>ext4</th> |
2533 |
<td style="background-color: rgb(255,0,0)">No***</td> |
<td style="background-color: rgb(255,127,0)">3rd party driver</td> |
2534 |
<td style="background-color: rgb(0,255,0)">Native</td> |
<td style="background-color: rgb(0,255,0)">Native</td> |
2535 |
<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> |
2536 |
<td style="background-color: rgb(0,255,0)">Yes</td> |
<td style="background-color: rgb(0,255,0)">Yes</td> |
2546 |
</tr> |
</tr> |
2547 |
</table> |
</table> |
2548 |
<p>* Depends on cluster size<br> |
<p>* Depends on cluster size<br> |
2549 |
** <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> |
|
2550 |
<p>Operating system support:</p> |
<p>Operating system support:</p> |
2551 |
<ul> |
<ul> |
2552 |
<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> |
2553 |
<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> |
2554 |
<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> |
2555 |
<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> |
|
2556 |
</ul> |
</ul> |
2557 |
<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> |
2558 |
<p>This section contains more information about most popular filesystems.</p> |
<p>This section contains more information about most popular filesystems.</p> |
2560 |
<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> |
2561 |
<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> |
2562 |
<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> |
2563 |
<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> |
2564 |
<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> |
2565 |
<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> |
2566 |
<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> |
2567 |
<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> |
2568 |
<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> |
2569 |
<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> |
2570 |
<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> |
2571 |
<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> |
2572 |
<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> |
2573 |
<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> |
|
2574 |
<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> |
2575 |
<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> |
2576 |
<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> |
2577 |
<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> |
2578 |
<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> |
2579 |
<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> |
2580 |
<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> |
2581 |
<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> |
2582 |
<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> |
2583 |
<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> |
2584 |
<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> |
2585 |
<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> |
2586 |
<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> |
2587 |
<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> |
2666 |
</ul> |
</ul> |
2667 |
<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> |
2668 |
<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> |
2669 |
<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> |
2670 |
<p class="newcode">root@sysresccd /root % fdisk -l<br> |
<p class="newcode">root@sysresccd /root % parted -l<br> |
2671 |
|
Model: ATA VBOX HARDDISK (scsi)<br> |
2672 |
|
Disk /dev/sda: 2097MB<br> |
2673 |
|
Sector size (logical/physical): 512B/512B<br> |
2674 |
|
Partition Table: msdos<br> |
2675 |
|
<br> |
2676 |
|
Number Start End Size Type File system Flags<br> |
2677 |
|
1 32.3kB 1679MB 1679MB primary ext4 boot<br> |
2678 |
|
2 1679MB 2097MB 418MB primary linux-swap(v1)<br> |
2679 |
|
<br> |
2680 |
<br> |
<br> |
2681 |
Disk /dev/sda: 2097 MB, 2097152000 bytes<br> |
Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0 has been opened read-only.<br> |
2682 |
64 heads, 63 sectors/track, 1015 cylinders<br> |
Error: /dev/sr0: unrecognised disk label<br> |
2683 |
Units = cylinders of 4032 * 512 = 2064384 bytes<br> |
<br> |
2684 |
Disk identifier: 0x00058a4a<br> |
Error: /dev/fd0: unrecognised disk label</p> |
|
<br> |
|
|
Device Boot Start End Blocks Id System<br> |
|
|
/dev/sda1 * 1 812 1636960+ 83 Linux<br> |
|
|
/dev/sda2 813 1015 409248 82 Linux swap / Solaris</p> |
|
2685 |
<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> |
2686 |
<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> |
2687 |
<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> |
3286 |
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> |
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> |
3287 |
</div> |
</div> |
3288 |
</div> |
</div> |
3289 |
|
<div id="warning" align="center"> |
3290 |
|
WARNING<br> |
3291 |
|
This is the UNSTABLE version of Clonezilla-SysRescCD<br> |
3292 |
|
To access our current stable version, please click <a href="../index.html">here</a> |
3293 |
|
</div> |
3294 |
</body> |
</body> |
3295 |
</html> |
</html> |