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

Diff of /trunk/www/onepage.html

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

revision 141 by sng, Wed Sep 29 20:23:58 2010 UTC revision 145 by sng, Thu Oct 7 09:19:52 2010 UTC
# Line 62  Line 62 
62      #content .red{color: white; background-color: Red; font-weight: bold;}      #content .red{color: white; background-color: Red; font-weight: bold;}
63      #lphp{text-align: right; padding-left: 10px; padding-right: 10px; padding-top: 50px; float: right;}      #lphp{text-align: right; padding-left: 10px; padding-right: 10px; padding-top: 50px; float: right;}
64      #lphp a{padding-left: 5px;}      #lphp a{padding-left: 5px;}
65        #warning { margin: 5px; padding: .4em; background-color: Red; color: White; align: center; font-weight: bold; border-width: 2px; border-color: white; border-style: solid; }
66        #warning a { color: white; font-weight: bold; text-decoration: underline;  }
67    </style>    </style>
68    <link href="warning.css" rel="stylesheet" type="text/css" />
69    <!--
70    The file waring.css exists only in the root of the site
71    and it hides the BETA 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 BETA version of Clonezilla-SysRescCD<br>
81    To acces 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>Wellcome</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: 07/10/2010</H4></div>
90    </div>    </div>
91  </div>  </div>
92  <div id="linkline">  <div id="linkline">
# Line 131  Well, I started this project because I w Line 144  Well, I started this project because I w
144  <tr><td class="bordertable"  colspan="4"><b>Release table</b></td></tr>  <tr><td class="bordertable"  colspan="4"><b>Release table</b></td></tr>
145  <tr><td class="bordertable"  valign="top"><b>Date</b></td><td class="bordertable"  valign="top"><b>Version</b></td>  <tr><td class="bordertable"  valign="top"><b>Date</b></td><td class="bordertable"  valign="top"><b>Version</b></td>
146  <td class="bordertable"  valign="top"><b>Clonezilla Live Version</b></td><td class="bordertable"  valign="top"><b>SystemRescueCD Version</b></td></tr>  <td class="bordertable"  valign="top"><b>Clonezilla Live Version</b></td><td class="bordertable"  valign="top"><b>SystemRescueCD Version</b></td></tr>
147    <tr><td  class="bordertable" >XX/XX/10</td><td  class="bordertable" >3.2.0</td><td  class="bordertable" >1.2.6-24&nbsp;(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&nbsp;(mod)</td><td  class="bordertable" >1.6.0</td>  <tr><td  class="bordertable" >15/09/10</td><td  class="bordertable" >3.1.0</td><td  class="bordertable" >1.2.5-35&nbsp;(mod)</td><td  class="bordertable" >1.6.0</td>
149  </tr>  </tr>
150  <tr><td  class="bordertable" >02/07/08</td><td  class="bordertable" >2.6.0</td><td  class="bordertable" >1.1.0-8&nbsp;(mod)</td><td  class="bordertable" >1.0.4&nbsp;(mod)</td>  <tr><td  class="bordertable" >02/07/08</td><td  class="bordertable" >2.6.0</td><td  class="bordertable" >1.1.0-8&nbsp;(mod)</td><td  class="bordertable" >1.0.4&nbsp;(mod)</td>
# Line 161  Well, I started this project because I w Line 175  Well, I started this project because I w
175  <H2><a name="changelog"></a>Changelog <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="changelog"></a>Changelog <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>
176  <table class="bordertable"  cellpadding="5">  <table class="bordertable"  cellpadding="5">
177  <tr><td class="bordertable" width="10"><b>Version</b></td><td  class="bordertable" width="10"><b>Package/CD</b></td><td class="bordertable"><b>Comments</b></td></tr>  <tr><td class="bordertable" width="10"><b>Version</b></td><td  class="bordertable" width="10"><b>Package/CD</b></td><td class="bordertable"><b>Comments</b></td></tr>
178    <tr><td class="bordertable" width="10" valign="top"><a name="3.2.0"></a>3.2.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">
179    -&nbsp;<b>Clonezilla Live</b> updated to version 1.2.6-24<br>
180    -&nbsp;<b>SystemRescueCD</b> updated to version 1.6.1<br>
181    -&nbsp;Fixed the splash image installation bug present in 3.1.0<br>
182    &nbsp;&nbsp;Also, a filename relative to /home/partimag, can now be used<br>
183    -&nbsp;Added -d command parameter to scrpit create-clonezilla-sysresccd<br>
184    &nbsp;&nbsp;This way the temporary and output folder can be specified<br>
185    -&nbsp;Using $HOME instead of /root in scrpit create-clonezilla-sysresccd<br>
186    -&nbsp;Script imginfo can display extended info (command line parameter -e)<br>
187    &nbsp;&nbsp;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  -&nbsp;<b>Clonezilla Live</b> updated to version 1.2.5-35<br>  -&nbsp;<b>Clonezilla Live</b> updated to version 1.2.5-35<br>
191  -&nbsp;<b>SystemRescueCD</b> updated to version 1.6.0<br>  -&nbsp;<b>SystemRescueCD</b> updated to version 1.6.0<br>
# Line 631  append initrd=initram.igz video=ofonly</ Line 656  append initrd=initram.igz video=ofonly</
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>
# Line 641  Available kernels (boot images):</p> Line 666  Available kernels (boot images):</p>
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 &lt;TAB&gt; to add additional options (in SystemRescueCd-1.5 and more recent)  <p>Press &lt;TAB&gt; to add additional options (in SystemRescueCd-1.5 and more recent)
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=&lt;device&gt; option</a>  boots an existing linux system. For example, if you have linux Gentoo installed on <code>/dev/sda6</code>,  use <code>rescuecd root=/dev/sda6</code> to start it. Keep in mind that you must use a 64bit kernel if your system is made of 64bit programs. This option works with LVM volumes. Use <code>rescuecd root=/dev/VolGroup00/LogVol00</code>. Support is also provided for <code>root=auto</code>, which scans all the block devices tfor a linux system. The first linux system found will be started. So with <code>root=auto</code> let you start the system installed from the CD-ROM in case you have problem with your boot loader or kernel. It's also possible to specify a partition using its <code>filesystem label</code> or <code>filesystem uuid</code>. If the label of the partition where linux is installed is <code>mylinux</code>, then boot it using <code>rescuecd root=LABEL=mylinux</code>. Similarly <code>root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7</code>. See <a target="_blank" href="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" class="external text" title="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" rel="nofollow">more details</a>.  </li><li><b>root=/dev/xdnp</b>: the <a target="_blank" href="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" class="external text" title="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" rel="nofollow">root=&lt;device&gt; option</a>  boots an existing linux system. For example, if you have linux Gentoo installed on <code>/dev/sda6</code>,  use <code>rescuecd root=/dev/sda6</code> to start it. Keep in mind that you must use a 64bit kernel if your system is made of 64bit programs. This option works with LVM volumes. Use <code>rescuecd root=/dev/VolGroup00/LogVol00</code>. Support is also provided for <code>root=auto</code>, which scans all the block devices for a linux system. The first linux system found will be started. So <code>root=auto</code> lets you start the system installed from the CD-ROM in case you have problem with your boot loader or kernel. It's also possible to specify a partition using its <code>filesystem label</code> or <code>filesystem uuid</code>. If the label of the partition where linux is installed is <code>mylinux</code>, then boot it using <code>rescuecd root=LABEL=mylinux</code>. Similarly <code>root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7</code>. See <a target="_blank" href="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" class="external text" title="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" rel="nofollow">more details</a>.
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
# Line 655  Available kernels (boot images):</p> Line 680  Available kernels (boot images):</p>
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.
# Line 672  Available kernels (boot images):</p> Line 697  Available kernels (boot images):</p>
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&amp;t=2538&amp;start=0" class="external text" title="http://www.sysresccd.org/forums/viewtopic.php?f=7&amp;t=2538&amp;start=0" rel="nofollow">BOOTIF</a> with SystemRescueCd-1.5.4 and more recent when you boot from pxelinux. The pxeboot loader will set BOOTIF to the name of the interface used to boot. You can then use something like <code>nameif=eth0!BOOTIF</code> if you want the boot interface to be called <code>eth0</code> on a computer with several Ethernet interfaces.  </li><li><b>nameif=xxx</b>: You can <a target="_blank" href="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" class="external text" title="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" rel="nofollow">specify what interface name to give</a> to a particular interface using the mac address. You need SystemRescueCd-1.1.0 or newer to do that. Here is how you can specify which interface is using which mac address on a machine with two network interfaces: <code>nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64</code>. Be careful, you have to respect the separator (comma between the interfaces and exclamation marks between the name and the mac address). You can also use the magic keyword <a target="_blank" href="http://www.sysresccd.org/forums/viewtopic.php?f=7&amp;t=2538&amp;start=0" class="external text" title="http://www.sysresccd.org/forums/viewtopic.php?f=7&amp;t=2538&amp;start=0" rel="nofollow">BOOTIF</a> with SystemRescueCd-1.5.4 and more recent when you boot from pxelinux. The pxeboot loader will set BOOTIF to the name of the interface used to boot. You can then use something like <code>nameif=eth0!BOOTIF</code> if you want the boot interface to be called <code>eth0</code> on a computer with several Ethernet interfaces.
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.
# Line 696  These options can be combined with other Line 721  These options can be combined with other
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>
# Line 732  please see the page "<a href="http://www Line 757  please see the page "<a href="http://www
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)
# Line 748  Ex. for the first 2 parameters, ocs_daem Line 773  Ex. for the first 2 parameters, ocs_daem
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>
# Line 843  fi Line 868  fi
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
# Line 879  Set the default console to be used with Line 906  Set the default console to be used with
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
# Line 897  Let you specify the name(s) and the opti Line 930  Let you specify the name(s) and the opti
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.
# Line 918  If you specify one of this two equivalen Line 951  If you specify one of this two equivalen
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
# Line 964  be checked at boot time, use this parame Line 1001  be checked at boot time, use this parame
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::
# Line 984  tried to be updated on reboot/shutdown. Line 1021  tried to be updated on reboot/shutdown.
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.
# Line 999  This parameter will make live-initramfs Line 1040  This parameter will make live-initramfs
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**::
# Line 3222  Smart BootManager - <a href="http://btmg Line 3266  Smart BootManager - <a href="http://btmg
3266    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>
3267    </div>    </div>
3268  </div>  </div>
3269    <div id="warning" align="center">
3270    WARNING<br>
3271    This is the BETA version of Clonezilla-SysRescCD<br>
3272    To acces our current stable version, please click <a href="../index.html">here</a>
3273    </div>
3274  </body>  </body>
3275  </html>  </html>

Legend:
Removed from v.141  
changed lines
  Added in v.145

webmaster@linux.gr
ViewVC Help
Powered by ViewVC 1.1.26