73 |
<H3>Wellcome</H3> |
<H3>Wellcome</H3> |
74 |
<div style="margin:0; padding: 3px; width: 980; position relative;"> |
<div style="margin:0; padding: 3px; width: 980; position relative;"> |
75 |
<div style="position: absolute; left: 0px;"><H4>25/05/2010 - v 3.1.0</H4></div> |
<div style="position: absolute; left: 0px;"><H4>25/05/2010 - v 3.1.0</H4></div> |
76 |
<div style="position: absolute; right: 0px;"><H4>Last update: 31/05/2010</H4></div> |
<div style="position: absolute; right: 0px;"><H4>Last update: 01/06/2010</H4></div> |
77 |
</div> |
</div> |
78 |
</div> |
</div> |
79 |
<div id="linkline"> |
<div id="linkline"> |
131 |
<tr><td class="bordertable" colspan="4"><b>Release table</b></td></tr> |
<tr><td class="bordertable" colspan="4"><b>Release table</b></td></tr> |
132 |
<tr><td class="bordertable" valign="top"><b>Date</b></td><td class="bordertable" valign="top"><b>Version</b></td> |
<tr><td class="bordertable" valign="top"><b>Date</b></td><td class="bordertable" valign="top"><b>Version</b></td> |
133 |
<td class="bordertable" valign="top"><b>Clonezilla Live Version</b></td><td class="bordertable" valign="top"><b>SystemRescueCD Version</b></td></tr> |
<td class="bordertable" valign="top"><b>Clonezilla Live Version</b></td><td class="bordertable" valign="top"><b>SystemRescueCD Version</b></td></tr> |
134 |
<tr><td class="bordertable" >25/05/10</td><td class="bordertable" >3.1.0</td><td class="bordertable" >1.2.5-17 (mod)</td><td class="bordertable" >1.5.4 (mod)</td> |
<tr><td class="bordertable" >25/05/10</td><td class="bordertable" >3.1.0</td><td class="bordertable" >1.2.5-17 (mod)</td><td class="bordertable" >1.5.5 (mod)</td> |
135 |
</tr> |
</tr> |
136 |
<tr><td class="bordertable" >02/07/08</td><td class="bordertable" >2.6.0</td><td class="bordertable" >1.1.0-8 (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> |
137 |
</tr> |
</tr> |
526 |
</p> |
</p> |
527 |
<H2><a name="sysresccd"></a>SystemRescueCD boot parameters <span class="hideprint">[<a href="#boot-top" title="go to top of the page">^</a>]</span></H2> |
<H2><a name="sysresccd"></a>SystemRescueCD boot parameters <span class="hideprint">[<a href="#boot-top" title="go to top of the page">^</a>]</span></H2> |
528 |
<div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td> |
<div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td> |
529 |
The following info applies to <b>SystemRescueCD v. 1.5.4</b>. In case<br> |
The following info applies to <b>SystemRescueCD v. 1.5.5</b>. In case<br> |
530 |
you need to get info for a more recent version of <b>SystemRescueCD</b><br> |
you need to get info for a more recent version of <b>SystemRescueCD</b><br> |
531 |
please see the page "<a href="http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM" target="_blank">Sysresccd-manual-en Booting the CD-ROM</a>" |
please see the page "<a href="http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM" target="_blank">Sysresccd-manual-en Booting the CD-ROM</a>" |
532 |
</td></tr></table></div> |
</td></tr></table></div> |
545 |
<p><br>The boot parameters you can use are:</p> |
<p><br>The boot parameters you can use are:</p> |
546 |
<div class="otherpage"> |
<div class="otherpage"> |
547 |
<a name="General_boot_options" id="General_boot_options"></a><p><b> General boot options</b></p> |
<a name="General_boot_options" id="General_boot_options"></a><p><b> General boot options</b></p> |
548 |
<p>Press <TAB> to add additional options. |
<p>Press <TAB> to add additional options (in SystemRescueCd-1.5 and more recent) |
549 |
</p> |
</p> |
550 |
<ul><li><b>docache</b>: causes the CD-ROM will be fully loaded into memory. A slower start but once complete, programs start faster and the CD drive will be released allowing normal access to other CDs. This requires 400MB of memory to cache everything (including the <code>bootdisks</code> and <code>isolinux</code> directories). Add <code>lowmem</code> if you have less that 400MB of memory of to prevent these directories to be copied. |
<ul><li><b>docache</b>: causes the CD-ROM will be fully loaded into memory. A slower start but once complete, programs start faster and the CD drive will be released allowing normal access to other CDs. This requires 400MB of memory to cache everything (including the <code>bootdisks</code> and <code>isolinux</code> directories). Add <code>lowmem</code> if you have less that 400MB of memory of to prevent these directories to be copied. |
551 |
</li></ul> |
</li><li><b>setkmap=kk</b>: which defines the keymap to load where <code>kk</code> (example: <code>setkmap=de</code> for German keyboards). This way you won't be prompted for the keyboard configuration during the boot. |
|
<p>During boot you will be prompted for the keyboard configuration, avoid this by using |
|
|
</p> |
|
|
<ul><li><b>setkmap=kk</b>: which defines the keymap to load where <code>kk</code> (example: <code>setkmap=de</code> for German keyboards) |
|
552 |
</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 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>. |
553 |
</li><li><b>initscript=service:action</b>: This options allows start/stop a service at boot time. For instance if you need the samba service to be started, you can boot with: <code>initscript=samba:start</code>. This does the same thing as <code>/etc/init.d/samba start</code>. Use this option multiple times for different services. All the actions that are supported by an initscript can be used. |
</li><li><b>initscript=service:action</b>: This options allows start/stop a service at boot time. For instance if you need the samba service to be started, you can boot with: <code>initscript=samba:start</code>. This does the same thing as <code>/etc/init.d/samba start</code>. Use this option multiple times for different services. All the actions that are supported by an initscript can be used. |
554 |
</li><li><b>backstore=xxx</b>: SystemRescueCd comes with support for the <a 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 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>. |
557 |
<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> |
558 |
<ul><li><b>dodebug</b>: Enables verbose messages in linuxrc |
<ul><li><b>dodebug</b>: Enables verbose messages in linuxrc |
559 |
</li></ul> |
</li></ul> |
560 |
<ul><li><b>doload=xxx</b>: loads needed modules, multiple occurrences are permitted (example: <code>doload=3c59x</code>) |
<ul><li><b>doload=xxx</b>: loads needed kernel modules, multiple comma separated occurrences are permitted (example: <code>doload=3c59x,e1000</code>) |
561 |
</li><li><b>noload=xxx</b>: prevents loading modules, multiple occurrences are permitted (example: <code>noload=3c59x</code>). Use this option if you have a problem when the system loads a particular module. |
</li><li><b>noload=xxx</b>: prevents loading kernel modules, multiple comma separated occurrences are permitted (example: <code>noload=3c59x,e1000</code>). Use this option if you have a problem when the system loads a particular module. |
562 |
</li><li><b>nonet</b>: this will disable the network auto detection at startup |
</li><li><b>nonet</b>: this will disable the network auto detection at startup |
563 |
</li></ul> |
</li></ul> |
564 |
<ul><li><b>scandelay=x</b>: pauses x seconds during the startup to allow slow devices to initialize. This is required when you boot an USB device. A delay of only few seconds should be enough. |
<ul><li><b>scandelay=x</b>: pauses x seconds during the startup to allow slow devices to initialize. This is required when you boot an USB device. A delay of only few seconds should be enough. |
581 |
<ul><li><b>skipmount=/dev/xxx</b>: The system mounts all the storage devices at boot time to find the sysrcd.dat file. If your hard disk is broken it should be mounted. Boot with <code>skipmount=/dev/sda1 skipmount=/dev/sda2</code> to ignore these two partitions. |
<ul><li><b>skipmount=/dev/xxx</b>: The system mounts all the storage devices at boot time to find the sysrcd.dat file. If your hard disk is broken it should be mounted. Boot with <code>skipmount=/dev/sda1 skipmount=/dev/sda2</code> to ignore these two partitions. |
582 |
</li></ul> |
</li></ul> |
583 |
<a name="Network_configuration_and_remote_access" id="Network_configuration_and_remote_access"></a><p><b><br> 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> |
584 |
<ul><li><b>dodhcp</b>: to request a DHCP server provide network attributes including an IP address, gateway... . otherwise, |
<ul><li><b>nonm</b>: to disable the Network-Manager service that conflicts with the standard network command line tools such as <code>ifconfig</code> and <code>ip</code>. You can use this option if you want to configure the network using these commands. This option is not necessary when SystemRescueCd is booting from the network since the service is automatically stopped in that case. This option requires SystemRescueCd-1.5.5 or more recent. |
585 |
|
</li><li><b>dodhcp</b>: to request a DHCP server provide network attributes including an IP address, gateway... |
586 |
|
</li><li><b>nodhcp</b>: never run the dhcp client in the initramfs boot script. May be useful if you use PXE boot on a computer with several ethernet interfaces. Support for this option is available in SystemRescueCd-1.5.5-beta2 and more recent |
587 |
</li><li><b>ethx=ipaddr/cidr</b>: Sets the static IP address of all the ethernet interfaces on the system. The <code>/cidr</code> extension is optional. For instance, if you use option <code>ethx=192.168.0.1</code> on a machine with two ethernet adapters, both <code>eth0</code> and <code>eth1</code> will be configured with <code>192.168.0.1</code>. You can use the format <code>ethx=10.0.0.1/24</code> (using the cidr notation) if you don't use the default netmask. |
</li><li><b>ethx=ipaddr/cidr</b>: Sets the static IP address of all the ethernet interfaces on the system. The <code>/cidr</code> extension is optional. For instance, if you use option <code>ethx=192.168.0.1</code> on a machine with two ethernet adapters, both <code>eth0</code> and <code>eth1</code> will be configured with <code>192.168.0.1</code>. You can use the format <code>ethx=10.0.0.1/24</code> (using the cidr notation) if you don't use the default netmask. |
588 |
</li><li><b>eth0=ipaddr/cidr</b>: This option is similar to <code>ethx=ipaddr/cidr</code> but it configures only one interface at a time. To configure the network on a server that has two interfaces, use: <code>eth0=192.168.10.1/24 eth1=192.168.20.1</code>. |
</li><li><b>eth0=ipaddr/cidr</b>: This option is similar to <code>ethx=ipaddr/cidr</code> but it configures only one interface at a time. To configure the network on a server that has two interfaces, use: <code>eth0=192.168.10.1/24 eth1=192.168.20.1</code>. |
589 |
</li><li><b>dns=ipaddr</b>: Sets the static IP address of the DNS nameserver you want to use to resolve the names. For instance <code>dns=192.168.0.254</code> means that you want to use <code>192.168.0.254</code> as the DNS server. |
</li><li><b>dns=ipaddr</b>: Sets the static IP address of the DNS nameserver you want to use to resolve the names. For instance <code>dns=192.168.0.254</code> means that you want to use <code>192.168.0.254</code> as the DNS server. |
591 |
</li><li><b>dhcphostname=myhost</b>: Sets the hostname that the DHCP client will send to the DHCP server. This may be required if the default hostname cannot be used with your DHCP configuration. This option has been introduced in SystemRescueCd-1.3.5. |
</li><li><b>dhcphostname=myhost</b>: Sets the hostname that the DHCP client will send to the DHCP server. This may be required if the default hostname cannot be used with your DHCP configuration. This option has been introduced in SystemRescueCd-1.3.5. |
592 |
</li><li><b>rootpass=123456</b>: Sets the root password of the system running on the livecd to <code>1234</code>. That way you can connect from the network and ssh on the livecd and give <code>123456</code> password as the root password. |
</li><li><b>rootpass=123456</b>: Sets the root password of the system running on the livecd to <code>1234</code>. That way you can connect from the network and ssh on the livecd and give <code>123456</code> password as the root password. |
593 |
</li><li><b>vncserver=x:123456</b>: The <a 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 5 and 8 characters, else the boot option will be ignored. In other words the <code>vncserver=2:MyPaSsWd</code> option will give you access to two displays (display=1 on tcp/5901 and display=2 on tcp/5902). Display 0 is reserved for X.Org since SystemRescueCd-1.1.0. |
594 |
</li><li><b>nameif=xxx</b>: You can can <a 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). |
</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. |
595 |
</li></ul> |
</li></ul> |
596 |
<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> |
597 |
<p>SystemRescueCd provides several options for booting from the network using PXE. |
<p>SystemRescueCd provides several options for booting from the network using PXE. |
1186 |
</ul> |
</ul> |
1187 |
<a name="backup-top"></a> |
<a name="backup-top"></a> |
1188 |
<H2 style="font-size: 2em;"><a name="backup-intro"></a>Getting backups <span class="hideprint">[<a href="#backup-top" title="go to top of the page">^</a>]</span></H2> |
<H2 style="font-size: 2em;"><a name="backup-intro"></a>Getting backups <span class="hideprint">[<a href="#backup-top" title="go to top of the page">^</a>]</span></H2> |
1189 |
<p>In this page I will demonstrate the creation of an image file by getting a backup of a virtual partition (<b>/dev/<font color="Red">hdb1</font></b>). The image file will be saved in another virtual partition (<b>/dev/<font color="Red">hda1</font></b>).<br></p> |
<p>In this page I will demonstrate the creation of an image file by getting a backup of a virtual partition (<b>/dev/<font color="Red">sdb1</font></b>). The image file will be saved in another virtual partition (<b>/dev/<font color="Red">sda1</font></b>).<br></p> |
1190 |
<p> |
<p> |
1191 |
The first thing you do when you want to get a backup of a disk/partition, is make sure both the souce (to be backed up) and target (to hold the image file) partitions are in excellent condition (error free). This is the logical thing to do, cause I wouldn't want to backup a corrupt partition, or end up with a corrupt image file.<br> |
The first thing you do when you want to get a backup of a disk/partition, is make sure both the souce (to be backed up) and target (to hold the image file) partitions are in excellent condition (error free). This is the logical thing to do, cause I wouldn't want to backup a corrupt partition, or end up with a corrupt image file.<br> |
1192 |
<br> |
<br> |
1196 |
<br> |
<br> |
1197 |
</p> |
</p> |
1198 |
<div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td> |
<div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td> |
1199 |
The following pressentation has been made using<br><b>Clonezilla Live v 1.2.3-27</b> |
The following pressentation has been made using<br><b>Clonezilla Live v 1.2.5-17</b> |
1200 |
</td></tr></table></div> |
</td></tr></table></div> |
1201 |
<H2><a name="backup"></a>Getting the backup <span class="hideprint">[<a href="#backup-top" title="go to top of the page">^</a>]</span></H2> |
<H2><a name="backup"></a>Getting the backup <span class="hideprint">[<a href="#backup-top" title="go to top of the page">^</a>]</span></H2> |
1202 |
<H3><a name="bck-0"></a>Clonezilla-SysRescCD starting screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3> |
<H3><a name="bck-0"></a>Clonezilla-SysRescCD starting screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3> |
1240 |
<H3><a name="bck-7"></a>Next screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3> |
<H3><a name="bck-7"></a>Next screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3> |
1241 |
<p>This is where I choose the location of the image file. It will be saved at the root directory of the selected partition.<br><br> |
<p>This is where I choose the location of the image file. It will be saved at the root directory of the selected partition.<br><br> |
1242 |
<img src="images/backup-06.png"><br> |
<img src="images/backup-06.png"><br> |
1243 |
I select partition <font color="Red"><b>hda1</b></font> and press ENTER.<br> |
I select partition <font color="Red"><b>sda1</b></font> and press ENTER.<br> |
1244 |
<br> |
<br> |
1245 |
<img src="images/backup-07.png"><br> |
<img src="images/backup-07.png"><br> |
1246 |
and then ENTER again.</p> |
and then ENTER again.</p> |
1247 |
<p><img src="images/backup-08.png"><br> |
<p><img src="images/backup-08.png"><br> |
1248 |
This screen displays the mounting result.<br> |
This screen displays the mounting result.<br> |
1249 |
As we can see, <font color="Red"><b>/dev/hda1</b></font> has been successfully mounted under <b>/tmp/local-dev</b>.</p> |
As we can see, <font color="Red"><b>/dev/sda1</b></font> has been successfully mounted under <b>/tmp/local-dev</b>.</p> |
1250 |
<H3><a name="bck-7a"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3> |
<H3><a name="bck-7a"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3> |
1251 |
<p><img src="images/backup-09.png"> |
<p><img src="images/backup-09.png"> |
1252 |
<br>I select <font color="Red"><b>Beginer mode</b></font> to accept the default backup options. If you select <font color="Red"><b>Expert mode</b></font>, you can choose the options yourself. More details can be found <a href="clonezilla.html#backup-options" target="_blank">here</a>.</p> |
<br>I select <font color="Red"><b>Beginer mode</b></font> to accept the default backup options. If you select <font color="Red"><b>Expert mode</b></font>, you can choose the options yourself. More details can be found <a href="clonezilla.html#backup-options" target="_blank">here</a>.</p> |
1258 |
<H3><a name="bck-9"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3> |
<H3><a name="bck-9"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3> |
1259 |
<p><img src="images/backup-11.png"><br> |
<p><img src="images/backup-11.png"><br> |
1260 |
In this screen I select the image name.<br> |
In this screen I select the image name.<br> |
1261 |
I type "Backup_5-2010_hdb", which in my opinion is more informative name than the default. |
I type "Backup_22-2010_sdb", which in my opinion is more informative name than the default. |
1262 |
</p> |
</p> |
1263 |
<H3><a name="bck-10"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3> |
<H3><a name="bck-10"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3> |
1264 |
<p><img src="images/backup-12.png"><br> |
<p><img src="images/backup-12.png"><br> |
1284 |
<H2 style="font-size: 2em;"><a name="backup-smb-intro"></a>Getting backups on Samba <span class="hideprint">[<a href="#backup-smb-top" title="go to top of the page">^</a>]</span></H2> |
<H2 style="font-size: 2em;"><a name="backup-smb-intro"></a>Getting backups on Samba <span class="hideprint">[<a href="#backup-smb-top" title="go to top of the page">^</a>]</span></H2> |
1285 |
<p>What if you don't have a spare local disk or partition or a USB disk? How will you be able to get a backup of your system? Well, if your PC is on the same LAN with another PC running Windows (or linux), you can use <b>Samba</b> to save your image file on that remote PC (which we will call <b>Samba server</b> from now on).<br><br> |
<p>What if you don't have a spare local disk or partition or a USB disk? How will you be able to get a backup of your system? Well, if your PC is on the same LAN with another PC running Windows (or linux), you can use <b>Samba</b> to save your image file on that remote PC (which we will call <b>Samba server</b> from now on).<br><br> |
1286 |
Using <b>Samba</b> you will be able to mount a Windows share resource (or Samba share resource), from within <b>Clonezilla Live</b>, and save the image file there. Then you can boot that PC using <b>SystemRescueCD</b> and create a restore DVD.<br><br> |
Using <b>Samba</b> you will be able to mount a Windows share resource (or Samba share resource), from within <b>Clonezilla Live</b>, and save the image file there. Then you can boot that PC using <b>SystemRescueCD</b> and create a restore DVD.<br><br> |
1287 |
In this page I will demonstrate the creation of an image file by getting a backup of my Windows partition (<b>/dev/<font color="Red">hda1</font></b>). The image file will be save in my Samba server which is my laptop (ip: <b><font color="Red">10.0.0.2</font></b>, Windows share resource name: <b><font color="Red">data</font></b>). |
In this page I will demonstrate the creation of an image file by getting a backup of my second disk (<b>/dev/<font color="Red">sdb</font></b>). The image file will be save in my Samba server which is my laptop (ip: <b><font color="Red">10.0.0.3</font></b>, Windows share resource name: <b><font color="Red">all_my_images</font></b>). |
1288 |
</p> |
</p> |
1289 |
<H3><a name="what-is"></a>What is Samba? [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3> |
<H3><a name="what-is"></a>What is Samba? [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3> |
1290 |
<p>We read at <a href="http://us1.samba.org/samba/" target="_blank">http://us1.samba.org/samba/</a>:</p> |
<p>We read at <a href="http://us1.samba.org/samba/" target="_blank">http://us1.samba.org/samba/</a>:</p> |
1336 |
<H3><a name="bck-smb-7"></a>Screen "Mount Samba Server" (fourth time) [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3> |
<H3><a name="bck-smb-7"></a>Screen "Mount Samba Server" (fourth time) [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3> |
1337 |
<p>This is where I have to enter the directory name on my Samba server, in which the image file will be saved.<br><br> I type "<font color="Red"><b>/all_my_images</b></font>" and press ENTER.<br><br> |
<p>This is where I have to enter the directory name on my Samba server, in which the image file will be saved.<br><br> I type "<font color="Red"><b>/all_my_images</b></font>" and press ENTER.<br><br> |
1338 |
<img src="images/backup-smb-09.png"><br> |
<img src="images/backup-smb-09.png"><br> |
1339 |
At this point I informed I will be asked for the password for user <b><font color="Red"><b>spiros</b></font></b>.<br><br> |
At this point I'm informed I'm going to be asked for the password for user <b><font color="Red"><b>spiros</b></font></b>.<br><br> |
1340 |
<img src="images/backup-smb-10.png"><br> |
<img src="images/backup-smb-10.png"><br> |
1341 |
I will be able to continue only after entering it correctly.<br><br> |
I will be able to continue only after entering it correctly.<br><br> |
1342 |
<img src="images/backup-smb-11.png"></p> |
<img src="images/backup-smb-11.png"></p> |
1351 |
<H3><a name="bck-smb-9"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3> |
<H3><a name="bck-smb-9"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3> |
1352 |
<p><img src="images/backup-11.png"><br> |
<p><img src="images/backup-11.png"><br> |
1353 |
In this screen I select the image name.<br> |
In this screen I select the image name.<br> |
1354 |
I type "Backup_5-2010_hdb", which in my opinion is more informative name than the default. |
I type "Backup_22-2010_sdb", which in my opinion is more informative name than the default. |
1355 |
</p> |
</p> |
1356 |
<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> |
1357 |
<p><img src="images/backup-12.png"><br> |
<p><img src="images/backup-12.png"><br> |
1753 |
<p class="newcode">eject /dev/dvd</p> |
<p class="newcode">eject /dev/dvd</p> |
1754 |
<p><b>Note:</b> If your drive can't reload the disc, insert the disc back right after ejecting it.</p> |
<p><b>Note:</b> If your drive can't reload the disc, insert the disc back right after ejecting it.</p> |
1755 |
<p>Finally, add the image file to the disc:</p> |
<p>Finally, add the image file to the disc:</p> |
1756 |
<p class="newcode">growisofs -M /dev/dvd -R -J -V "<font color="Green">Backup_5-2010_hdb</font>" --publisher "<font color="Green">Your Name</font>" -graft-points /<font color="Green">Backup_5-2010_hdb</font>/=/media/usb/<font color="Green">Backup_5-2010_hdb</font></p> |
<p class="newcode">growisofs -M /dev/dvd -R -J -V "<font color="Green">Backup_5-2010_hdb</font>" \<br> |
1757 |
|
--publisher "<font color="Green">Your Name</font>" -graft-points \<br> |
1758 |
|
/<font color="Green">Backup_5-2010_hdb</font>/=/media/usb/<font color="Green">Backup_5-2010_hdb</font></p> |
1759 |
<p><b>Note:</b> In the command replace <b><font color="Green">Your Name</font></b> with anything you want to be the publisher ID of the disc. If you don't want the disc to have any publisher ID, run this command instead:</p> |
<p><b>Note:</b> In the command replace <b><font color="Green">Your Name</font></b> with anything you want to be the publisher ID of the disc. If you don't want the disc to have any publisher ID, run this command instead:</p> |
1760 |
<p class="newcode">growisofs -M /dev/dvd -R -J -V "<font color="Green">Backup_5-2010_hdb</font>" -graft-points /<font color="Green">Backup_5-2010_hdb</font>/=/media/usb/<font color="Green">Backup_5-2010_hdb</font></p> |
<p class="newcode">growisofs -M /dev/dvd -R -J -V "<font color="Green">Backup_5-2010_hdb</font>" \<br> |
1761 |
|
-graft-points /<font color="Green">Backup_5-2010_hdb</font>/=/media/usb/<font color="Green">Backup_5-2010_hdb</font></p> |
1762 |
<p><img src="images/restore-20.png"><br>Here we can see the boot menu of the disc.</p> |
<p><img src="images/restore-20.png"><br>Here we can see the boot menu of the disc.</p> |
1763 |
<H2><a name="zip"></a>ZIP file instructions <span class="hideprint">[<a href="#restore-burn-top" title="go to top of the page">^</a>]</span></H2> |
<H2><a name="zip"></a>ZIP file instructions <span class="hideprint">[<a href="#restore-burn-top" title="go to top of the page">^</a>]</span></H2> |
1764 |
<p>Often the image file is way too big to fit to even 8 GB DVD. Some people may also want to be able to overwrite the backup when it becomes outdated. In addition, netbooks don't have optical drives at all.</p> |
<p>Often the image file is way too big to fit to even 8 GB DVD. Some people may also want to be able to overwrite the backup when it becomes outdated. In addition, netbooks don't have optical drives at all.</p> |