/[clonezilla-sysresccd]/trunk/www/2doc/README.txt

Diff of /trunk/www/2doc/README.txt

Parent Directory | Revision Log | View Patch Patch

-revision 179 by sng,
Sat Dec 11 09:41:39 2010 UTC
+revision 180 by sng,
Mon Jun  6 18:57:10 2011 UTC
 Line 232 
 Now all you have to do is make your USB
  that you have to open a DOS window (in Windows XP press "Start / Run "
  and type cmd). Then type at DOS prompt:
  K:
- cd bootprog
+ cd utils/bootprog
  syslinux -ma K:
  Booting from USB
 Line 430 
 certainty make it unbootable. When you a
  SystemRescueCD boot parameters
  ****************************************
  [[ info.png ]]
- The following info applies to SystemRescueCD v. 1.5.5. In case
+ The following info applies to SystemRescueCD v. 2.1.1. In case
   you need to get info for a more recent version of SystemRescueCD
  please see the page "Sysresccd-manual-en Booting the CD-ROM {{
  http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM }}"
 Line 543 
 was useful in previous versions.
  * nodetect: prevents generic hardware auto-detection. Use this option if
  you have problems with the hardware auto-detection.
+ * nomodeset: Do not load the Kernel-Mode-Setting video driver. You can
+ use that option if you are experiencing problems with your screen during
+ the boot process (just after modules are being loaded).
  * dostartx: load the X.Org graphical environment.
  * forcevesa: Forces X.Org to use the safe VESA driver instead of the best
  video driver detected for your video card. Use this option if you cannot
-Line 576 
 option is not necessary when SystemRescu
+Line 579 
 option is not necessary when SystemRescu
  since the service is automatically stopped in that case. This option
  requires SystemRescueCd-1.5.5 or more recent.
  * dodhcp: to request a DHCP server provide network attributes including
- an IP address, gateway...
+ an IP address, gateway... If there are multiple interfaces on the computer
+ it will run the dhcp client on all of them by default, when no argument is
+ specified with this option. Thanks to emiliano SystemRescueCd-1.7.0-beta009
+ and more recent allows you to optionally specify which interfaces should
+ be configured with dhcp. This way you can combine static and dynamic
+ addresses in the automatic Ethernet configuration. For example you can now
+ use options like that: dodhcp=eth0,eth2 eth1=192.168.128.1/24 to use dhcp
+ for eth0 and eth2 and a static address on eth1.
  * nodhcp: 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
-Line 678 
 been executed.
+Line 688 
 been executed.
  Clonezilla Live boot parameters
  ****************************************
  [[ info.png ]]
- The following info applies to Clonezilla Live v. 1.2.5-17
+ The following info applies to Clonezilla Live v. 1.2.8-46
  In case you need to get info for a more recent version of Clonezilla Live
  please see the page "The boot parameters for Clonezilla live {{
- http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc
+ http://clonezilla.org/fine-print-live-doc.php?path=clonezilla-live/doc/99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc
  }}"
  A typical Clonezilla Live isolinux entry is:
-Line 734 
 live-initramfs.
+Line 744 
 live-initramfs.
  Ex. for the first 2 parameters, ocs_daemonon="ssh", then ssh service will
  be turned on when booting. For the last 2 parameters, use "on" or "off",
  e.g. ocs_numlk=on to turn on numberlock when booting.
-  * ocs_prerun, ocs_prerun1, ocs_prerun2... is for you to run a shell script
+  * ocs_prerun, ocs_prerun1, ocs_prerun2... is for you to run a command before
-  before Clonezilla is started. E.g. ocs_prerun="/live/image/myscript.sh". If
+  Clonezilla is started. E.g. ocs_prerun="/live/image/myscript.sh". If you
-  you have more commands to run, you can assign them in the order:
+  have more commands to run, you can assign them in the order: ocs_prerun=...,
-  ocs_prerun=..., ocs_prerun1=..., ocs_prerun2=.... If more than 10
+  ocs_prerun1=..., ocs_prerun2=.... If more than 10 parameters, remember
-  parameters, remember to use ocs_prerun01, ocs_prerun02..., ocs_prerun11
+  to use ocs_prerun01, ocs_prerun02..., ocs_prerun11 to make it in order.
-  to make it in order.
   * ocs_live_run_tty. This option allows you to specify the tty where
   $ocs_live_run is run. By default $ocs_live_run is run on /dev/tty1
-  only. (It was also on /dev/ttyS0 before, but since Clonezilla live >=
+  only. If you want to use ttyS0, for example, add live-getty and
-.2.3-22 no more this due to a problem). If you want to use ttyS0, for
+  console=ttyS0,38400n81 in the boot parameter.
-  example, add live-getty and console=ttyS0,38400n81 in the boot parameter.
   //NOTE//
-  * This parameter was added in Clonezilla live 1.2.3-22 or later.
   * 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.
-Line 759 
 e.g. ocs_numlk=on to turn on numberlock
+Line 766 
 e.g. ocs_numlk=on to turn on numberlock
   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:
- ip=eth0,10.0.100.1,255.255.255.0,10.0.100.254,8.8.8.8
+ ip=eth0:10.0.100.1:255.255.255.0:10.0.100.254:8.8.8.8
- If more than one network card, you can use ":" to separate them, e.g.:
+ If more than one network card, you can use "," to separate them, e.g.:
- ip=eth0,10.0.100.1,255.255.255.0,10.0.100.254,8.8.8.8:eth1,192.168.120.1,255.255.255.0,192.168.120.254,,
+ ip=eth0:10.0.100.1:255.255.255.0:10.0.100.254:8.8.8.8,eth1:192.168.120.1:255.255.255.0:192.168.120.254::
   * Besides, "live-netdev" (yes, not ocs_live_netdev) can be used when
   using PXE booting, you can force to assign the network device to get
   filesystem.squashfs. This is useful when there are two or more NICs are
-Line 1741 
 We read in DRBL FAQ/Q&A {{
+Line 1748 
 We read in DRBL FAQ/Q&A {{
  http://drbl.sourceforge.net/faq/fine-print.php?path=./2_System/23_Missing_OS.faq#23_Missing_OS.faq
  }}:
- When I use clonezilla to clone M$ windows, there is no any problem
+ When I use clonezilla to clone MS windows, there is no any problem
  when saving an image from template machine. However, after the image
  is restored to another machine, it fails to boot, the error message is
- "Missing Operating System". What's going on ?
+ "Missing Operating System" or just a blinking underscore. What's going on ?
  Usually this is because GNU/Linux and M$ windows interpret the CHS (cylinder,
  head, sector) value of harddrive differently. Some possible solutions:
 . Maybe you can change the IDE harddrive setting in BIOS, try to use
    LBA instead of auto mode.
-. Try to choose
+. Try to choose both
-     [ ] -j0 Use dd to create partition table instead of sfdisk
+         [*] -j0 Use dd to create partition table instead of sfdisk
    and
-     [ ] -t1 Client restores the prebuilt MBR from syslinux (For Windows only)
+         [*] -t1 Client restores the prebuilt MBR from syslinux (For
-   when you restore the image.
+         Windows only)
-. You can try to boot the machine with MS Windows 9x bootable floppy,
+     when you restore the image.
+. Try to choose
+         [*] -t1 Client restores the prebuilt MBR from syslinux (For
+         Windows only)
+   and *uncheck*
+         [ ] -g auto Reinstall grub in client disk MBR (only if grub
+         config exists)
+         [ ] -r Try to resize the filesystem to fit partition size
+   when you restore the image. You can refer to this discussion {{
+   http://www.ecs.umass.edu/pipermail/umasslug/2008-August/003380.html
+   }}. Thanks to Alex Mckenzie for posting this on the forum.
+. You can try to boot the machine with MS Windows 9x bootable floppy,
    and in the DOS command prompt, run: "fdisk /mbr".
 . You can try to boot the machine with MS Windows XP installation
    CD, enter recovery mode (by pressing F10 key in MS XP, for example),
    then in the console, run "fixmbr" to fix it. Maybe another command
    "fixboot" will help, too. For more info, refer to this doc {{
    http://support.microsoft.com/?scid=kb%3Ben-us%3B314058&x=7&y=14 }}
-. Use ntfsreloc to adjust FS geometry on NTFS partitions. For more info,
+. Use ntfsfixboot to fix it. This program is included in Clonezila live
-   refer to http://www.linux-ntfs.org/doku.php?id=contrib:ntfsreloc
+   and its name is partclone.ntfsfixboot, and you can use it to adjust FS
+   geometry on NTFS partitions. By default this should be done by Clonezilla
+   with the option -e1 and -e2 checked. If not, you can force to do that
+   again. For more info, please run "partclone.ntfsfixboot --help" or refer
+   to http://sourceforge.net/projects/ntfsfixboot/.
+. Use ntfsreloc to adjust FS geometry on NTFS partitions. For more info,
+   refer to http://www.linux-ntfs.org/doku.php?id=contrib:ntfsreloc. //NOTE//
+   ntfsreloc is an older version of partclone.ntfsfixboot.
+. If you get error messages like "0xc0000225, 0xc00000e", and something
+   about Winload.exe, refer to this.
+. Some more discussions are available here.
- It has been confirmed that activating the -j0 option, fixes the problem.
+ It has been confirmed that activating the -j0 option, usually fixes the
+ problem.
  This option doesn't work if you use LVM (Logical Volume Manager).
-Line 1835 
 Getting backups
+Line 1863 
 Getting backups
  Intro
  ****************************************
  In this page I will demonstrate the creation of an image file by getting
- a backup of a virtual partition (/dev/sdb1). The image file will be saved
+ a backup of a virtual disk (/dev/sdb). The image file will be saved in a
- in another virtual partition (/dev/sda1).
+ partition in another virtual disk (/dev/sda1).
  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
-Line 1850 
 boot settings are correct, in order to b
+Line 1878 
 boot settings are correct, in order to b
  Having done all of the above, I am ready to boot from Clonezilla-SysRescCD.
  [[ info.png ]]
- The following pressentation has been made usingClonezilla Live v 1.2.5-35
+ The following pressentation has been made usingClonezilla Live v 1.2.8-46
  Getting the backup
  ****************************************
-Line 1870 
 displayed.
+Line 1898 
 displayed.
  The default parameters for booting Clonezilla Live on a 1024x768 screen,
  are the following:
- append initrd=/live/initrd1.img boot=live union=aufs
+ append initrd=/live/initrd.img boot=live config nomodeset nolocales noprompt
-   ocs_live_run="ocs-live-general" ocs_live_extra_param=""
+   noswap edd=on ocs_live_run="ocs-live-general" ocs_live_extra_param=""
-   ocs_prerun="/live/image/restorecd/prerun.normal" ocs_live_batch="no"
+   ocs_prerun="/restorecd/prerun.normal" ocs_live_batch="no"
-   ocs_lang="en_US.UTF-8" ocs_live_keymap="NONE" vga=791 nolocales
+   ocs_lang="en_US.UTF-8" ocs_live_keymap="NONE" vga=791
  By deleting the words in red, you instruct Clonezilla Live to ask you the
  values of these parameters. When the appropriate changes have been done
  (as shown bellow), just press ENTER to boot.
- append initrd=/live/initrd1.img boot=live union=aufs
+ append initrd=/live/initrd.img boot=live config nomodeset nolocales noprompt
-   ocs_live_run="ocs-live-general" ocs_live_extra_param=""
+   noswap edd=on ocs_live_run="ocs-live-general" ocs_live_extra_param=""
-   ocs_prerun="/live/image/restorecd/prerun.normal" ocs_live_batch="no"
+   ocs_prerun="/restorecd/prerun.normal" ocs_live_batch="no"
-   ocs_lang="" ocs_live_keymap="" vga=791 nolocales
+   ocs_lang="" ocs_live_keymap="" vga=791
  Screen "Choose Language"
  ---------------------
-Line 1940 
 As we can see, /dev/sda1 has been succes
+Line 1968 
 As we can see, /dev/sda1 has been succes
  Next Screen
  ---------------------
  [[ backup-09.png ]]
- I select Beginer mode to accept the default backup options. If you select
+ I select Beginner mode to accept the default backup options. If you select
  Expert mode, you can choose the options yourself. More details can be
  found here.
-Line 1955 
 Next Screen
+Line 1983 
 Next Screen
  ---------------------
  [[ backup-11.png ]]
  In this screen I select the image name.
- I type "Backup_32-2010_sdb", which in my opinion is more informative name
+ I type "Backup_32-2011_sdb", which in my opinion is more informative name
  than the default.
  Next Screen
  ---------------------
  [[ backup-12.png ]]
- Finally I am asked to select the partition to save.
+ Then I am asked to select the disk to save.
  I just press ENTER again.
+ Next screen
+ ---------------------
+ [[ backup-12a.png ]]
+ And I press ENTER again to enable image validation.
  Starting the backup
  ---------------------
  [[ backup-13.png ]]
-Line 2112 
 I will be able to continue only after en
+Line 2145 
 I will be able to continue only after en
  Screen "Clonezilla - Opensource Clone System (OCS)"
  ---------------------
  [[ backup-09.png ]]
- I select Beginer mode to accept the default backup options. If you select
+ I select Beginner mode to accept the default backup options. If you select
  Expert mode, you can choose the options yourself. More details can be
  found here.
-Line 2127 
 Next Screen
+Line 2160 
 Next Screen
  ---------------------
  [[ backup-11.png ]]
  In this screen I select the image name.
- I type "Backup_32-2010_sdb", which in my opinion is more informative name
+ I type "Backup_32-2011_sdb", which in my opinion is more informative name
  than the default.
  Next Screen
  ---------------------
  [[ backup-12.png ]]
- Finally I am asked to select the partition to save.
+ Finally I am asked to select the disk to save.
  I just press ENTER again.
+ Next screen
+ ---------------------
+ [[ backup-12a.png ]]
+ And I press ENTER again to enable image validation.
  Starting the backup
  ---------------------
  [[ backup-13.png ]]
-Line 2195 
 restoring make sure you have backup of a
+Line 2233 
 restoring make sure you have backup of a
  disk/partition, even if the filesystem is corrupted.
  [[ info.png ]]
- The following pressentation has been made usingClonezilla Live v 1.2.5-35
+ The following pressentation has been made usingClonezilla Live v 1.2.8-46
  Restoring data
  ****************************************
-Line 2283 
 As we can see, /dev/sda1 has been succes
+Line 2321 
 As we can see, /dev/sda1 has been succes
  Next Screen
  ---------------------
  [[ backup-09.png ]]
- I select Beginer mode to accept the default restore options. If you select
+ I select Beginner mode to accept the default restore options. If you
- Expert mode, you can choose the options yourself. More details can be
+ select Expert mode, you can choose the options yourself. More details can
- found here.
+ be found here.
  Screen "Select mode"
  ---------------------
-Line 2303 
 one image.
+Line 2341 
 one image.
  Next Screen
  ---------------------
  [[ restoration-12.png ]]
- Finally I am asked to select which partition the image will be restored
+ Finally I am asked to select which disk the image will be restored to. After
- to. After double-checking the disk doesn't contain anything important,
+ double-checking the disk doesn't contain anything important, I press ENTER.
- I press ENTER.
  Starting the restoration
  ---------------------
-Line 2343 
 Creating a Restore DVD - Part 1
+Line 2380 
 Creating a Restore DVD - Part 1
  Intro
  ****************************************
- Assuming you have used Clonezilla Live to make a backup of your Windows
+ Assuming you have used Clonezilla Live to make a backup of your system (disk
- XP system (partition /dev/sda1), you will probably be wondering what to
+ /dev/sdb), you will probably be wondering what to do with it now. Well,
- do with it now. Well, one option would be to keep it to the disk you used
+ one option would be to keep it to the disk you used to save it in, store
- to save it in, store the disk, and use it whenever you need it. Another
+ the disk, and use it whenever you need it. Another option would be to
- option would be to create a DVD you can use to restore this image.
+ create a DVD you can use to restore this image.
  Before, up to Clonezilla-SysRescCD 2.6.0, 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.
+ which can be uncomfortable or even difficult for many people.
  Later, a TUI option to create an automated recovery disc was added to
  Clonezilla Live, and ocs-iso script included in Clonezilla-SysRescCD
-Line 2362 
 DVD via TUI.
+Line 2399 
 DVD via TUI.
  You have to boot Clonezilla Live, using Clonezilla-SysRescCD.
  [[ info.png ]]
- The following pressentation has been made usingClonezilla Live v 1.2.5-17
+ The following pressentation has been made usingClonezilla Live v 1.2.8-46
  Creating the disk image
  ****************************************
-Line 2450 
 As we can see, /dev/sda1 has been succes
+Line 2487 
 As we can see, /dev/sda1 has been succes
  Next Screen
  ---------------------
  [[ backup-09.png ]]
- I select Beginer mode to accept the default restore options, which are
+ I select Beginner mode to accept the default restore options, which are
  used if the recovery disk is ever used. If you select Expert mode, you
  can choose the options yourself. More details can be found here.
-Line 2671 
 and it doesn't make much sense to instal
+Line 2708 
 and it doesn't make much sense to instal
  I launch K3b and navigate to the folder where the disk image resides.
  [[ k3b-01.png ]]
- I double-click the file clonezilla-live-Backup_5-2010_hda.iso.
+ I double-click the file clonezilla-live-Backup_42-2010_sda.iso.
  [[ k3b-02.png ]]
  This window allows me to choose burning settings. I don't touch Image Type or
-Line 2750 
 extract the ZIP archive to the root of t
+Line 2787 
 extract the ZIP archive to the root of t
  need root rights.
  mount /dev/sdc1 /media/usb
- unzip clonezilla-live-Backup_5-2010_hdb.zip -d /media/usb/
+ unzip clonezilla-live-Backup_42-2010_sdb.zip -d /media/usb/
  Note: In the last command I have assumed your image file is
- clonezilla-live-Backup_5-2010_hdb.zip. You will have to replace this with
+ clonezilla-live-Backup_42-2010_sdb.zip. You will have to replace this with
  the actual name of the file.
  ZIP package contains a script to make the USB drive bootable. Let's run
-Line 2863 
 Its help screen is:
+Line 2900 
 Its help screen is:
  # imginfo -h
  Clonezilla Live Image Information
- imginfo v. 0.1 - (C) 2009 S. Georgaras <sng@hellug.gr>
+ imginfo v. 0.2 - (C) 2009-2010 S. Georgaras <sng@hellug.gr>
  Usage: imginfo <options> <directory>
-Line 2875 
 Available options:
+Line 2912 
 Available options:
  Script imgconvert
  ****************************************
- The script will be used to convert an existing disk image file to a new
+ The script will be used to convert an existing disk or partition image
- partition image file.
+ file to a new partition image file.
  imgconvert can create two type of images:
-Line 2896 
 Its help screen is:
+Line 2933 
 Its help screen is:
  # imgconvert -h
  Clonezilla Live Image Conversion
- imgconvert v. 0.1 - (C) 2009 S. Georgaras <sng@hellug.gr>
+ imgconvert v. 0.2 - (C) 2009-2011 S. Georgaras <sng@hellug.gr>
  Usage: imgconvert <options> [image] [partition] <new partition>
-Line 2949 
 existing disk image file, by executing t
+Line 2986 
 existing disk image file, by executing t
  # imgconvert sys-bck hda3 sdb2
  Clonezilla Live Image Conversion
- imgconvert v. 0.1 - (C) 2009 S. Georgaras
+ imgconvert v. 0.2 - (C) 2009-2011 S. Georgaras
  Determining input image
    Input image: "/home/partimag/sys-bck"
-Line 2995 
 Converting image files
+Line 3032 
 Converting image files
  ---------------------
  # imgconvert -p -o other_data sys-bck hda3 sdb2
  Clonezilla Live Image Conversion
- imgconvert v. 0.1 - (C) 2009 S. Georgaras
+ imgconvert v. 0.2 - (C) 2009-2011 S. Georgaras
  Determining input image
    Input image: "/home/partimag/sys-bck"
-Line 3249 
 You need Windows Vista/7 install disc fo
+Line 3286 
 You need Windows Vista/7 install disc fo
  example, if you bought a laptop that was bundled with preinstalled Windows
  and manufacturer's recovery disc), download a recovery disc from here.
- Then boot from the disc. After selecting language, time, currency and
+ Then boot from the disc.
- keyboard, click Repair your computer. You'll get a list of operating systems
- you're able to repair. Choose any of them; that choice doesn't matter.
+ [[ windows7-00.png ]]
+ After selecting language, time, currency and keyboard, click Next.
+ [[ windows7-01.png ]]
+ Click Repair your computer.
+ [[ windows7-02.png ]]
+ Choose the option Use recovery tools that can help fix problems starting
+ Windows and click Next.
- After that, you'll see a dialog box named System Recovery Options. Click
+ [[ windows7-03.png ]]
- Command Prompt. Then you only need to execute one command:
+ You'll see a dialog box named System Recovery Options. Click Command Prompt.
+ [[ windows7-04.png ]]
+ Then you only need to execute one command:
  Bootrec /FixMbr
  Note: The command is case-insensitive. You can type, for example,
  "bootrec /fixmbr".
+ [[ windows7-05.png ]]
  Using FIXMBR (Windows XP only)
  ---------------------
  You need Windows XP install disc. Boot from it, and when you see the screen
-Line 3565 
 you to look for more help in SystemRescu
+Line 3615 
 you to look for more help in SystemRescu
  Which boot option to pick?
  ****************************************
- You may be confused because of the number of boot options you have. After
+ Here is a list of the most important boot options:
- choosing "CD 2: System Rescue CD" you have a total of 15 options to boot
- SystemRescueCD. Here is a table of them.
+) SystemRescueCd: default boot options
+) SystemRescueCd: all files cached to memory (docache)
- kernel         Normal   To RAM   Graphical Environment   VESA   Mini Shell
+) SystemRescueCd: framebuffer console in high resolution
--bit          xxx                      +++
+) SystemRescueCd: do not ask for keyboard, use US keymap
--bit (alt)
+) SystemRescueCd: directly start the graphical environment
--bit          xxx                      +++
+) SystemRescueCd: 64bit kernel with default options
- In the table, I have marked the options you most likely need. You should
+ If you're accustomed to graphical environment, choose the option directly
- choose either of the options marked with a '+++' if you have no idea and/or
+ start the graphical environment. In graphical environment you're able
- time to read the next sections.
+ to use graphical programs, like GParted and Mozilla Firefox. Terminals
+ are also available, so using graphical environment doesn't prevent using
- Choosing the column
+ command line. The only negative thing of graphical environment is that it
- ---------------------
+ slows booting process down a bit - and it's often just plain unneeded.
- If you're accustomed to graphical environment, choose Graphical
- Environment. In Graphical Environment you're able to use graphical programs,
+ If you're accustomed to command line and know already that you're not
- like GParted and Mozilla Firefox. Terminals are also available, so using
+ going to use any graphical program, choose the option framebuffer console
- Graphical Environment doesn't prevent using command line. The only negative
+ in high resolution. Booting to command line is a bit faster process than
- thing of Graphical Environment is that it slows booting process down a bit -
+ booting to graphical environment, and you can start X manually later.
- and it's often just plain unneeded.
+ Alternatively, you can select default boot options. However, if you do so,
- Try VESA, if normal Graphical Environment doesn't work. VESA uses Xvesa
+ the text in the screen will be bigger and you'll be able to see less text
- graphical environment instead of X.Org that sometimes doesn't work. The
+ at once.
- drawback of Xvesa compared to X.Org is that Xvesa isn't optimized to any
- hardware, which means poorer performance.
+ If you want to chroot on an existing GNU/Linux partition containing 64-bit
+ programs, select 64bit kernel with default options. Even if you don't want
- If you're accustomed to command line and know already that you're not going
+ to chroot, 64-bit kernel may be a bit faster than 32-bit one. However,
- to use any graphical program, choose one of the normal options (just below
+-bit kernel requires a x86-64 processor, for example AMD Athlon 64 or
- "System Rescue CD Menu"). Booting to command line is a bit faster process
+ Intel Core 2.
- than booting to graphical environment, and you can start X manually later.
+ You need the option all files cached to memory (docache) if you plan to burn
- You need the option To RAM if you plan to burn discs while using
+ discs while using SystemRescueCD. The option copies the whole SystemRescueCD
- SystemRescueCD. The option copies the whole SystemRescueCD to the memory of
+ to the memory of the computer during the boot process, allowing you to
- the computer during the boot process, allowing you to put another disc to
+ put another disc to your CD/DVD writer while using SystemRescueCD. The
- your CD/DVD writer while using SystemRescueCD. The negative thing is that
+ negative thing is that reading all the contents of the disc slows boot
- reading all the contents of the disc slows boot process down a lot. There
+ process down a lot.
- is no option which copies the disc to the memory and starts graphical
- environment automatically, but you can easily start it manually.
+ Finally, the option do not ask for keyboard, use US keymap may be useful if
+ you have an English keyboard. By default, SystemRescueCD asks the keymap
- Mini Shell is probably the least used option. It enters BusyBox
+ to use during boot. If you don't answer in 20 seconds, SystemRescueCD
- shell after booting. BusyBox is an application that "combines
+ chooses the US keymap. However, if you have chosen the option do not ask
- tiny versions of many common UNIX utilities into a single small
+ for keyboard, use US keymap in the boot menu, SystemRescueCD chooses the
- executable." However, SystemRescueCD contains most of these utilities
+ US keymap immediately. No waiting, no questions.
- anyway, so there is not much need to use this option. some information {{
- http://www.busybox.net/about.html }} about BusyBox
- Choosing the row (kernel)
- ---------------------
- After having chosen the column of the above table, you still have three
- options. Now you need to choose the kernel.
- The optimal kernel depends on the processor of your computer. If it's an
- IA-32 processor, like Intel Pentium 4 or AMD Athlon XP, you should choose
--bit kernel, because 64-bit kernel doesn't work at all. If you have
- a x86-64 processor, like AMD Athlon 64 or Intel Core 2, you can choose
- any kernel - the processor can run all of them. 64-bit kernel should be
- preferred, because it allows chrooting on an existing GNU/Linux partition
- containing 64-bit programs.
- If you don't know your processor architecture, try 64-bit kernel. If your
- processor architecture is IA-32, you'll see the following error message:
- This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable
- to boot - please use a kernel appropriate for your CPU.
- At this stage, simply press Ctrl-Alt-Del to reboot and use always 32-bit
- kernel on the machine.
- There is one more kernel - 32-bit kernel (alternative). It's designed to
- support more recent hardware than the regular kernel. Try it if standard
--bit kernel doesn't work.
  After booting
  ****************************************
  HELP!!! Where are the desktop and Start menu?
  ---------------------
- You should have read this section if you're looking for them. However,
+ Simply type this command and press ENTER twice:
- you don't need to reboot in order to enter graphical environment. Simply
- type this command and press ENTER:
  wizard
- The command asks you to choose a graphical environment. Try first X.Org,
- and if it fails, run the command again and choose Xvesa.
  Connecting to the Internet
  ---------------------
  The CD doesn't contain any SystemRescueCD documentation, because we don't
-Line 3658 
 have permission to redistribute it. In a
+Line 3675 
 have permission to redistribute it. In a
  we can't rewrite it all. So, you need to connect to the Internet to be
  able to read SystemRescueCD's official online documentation.
- Luckily, establishing Internet connection should be easy, if you're in a
+ SystemRescueCD establishes an Internet connection automatically, if you're
- network using DHCP. Nowadays, most people are. If you're using graphical
+ in a network using DHCP. Nowadays, most people are.
- mode and terminal isn't already open, open it via the menu that opens when
- you click the leftmost icon in the bottom pane.
+ If the network doesn't use DHCP, you have to configure Internet settings
+ by hand. You should be able to do so if you've previously configured
+ your settings in the operating system you normally use. First, stop the
+ NetworkManager daemon:
- Then, type this command and press ENTER:
+ /etc/init.d/NetworkManager stop
- dhcpcd eth0
+ After that, run the following command:
- If the network doesn't use DHCP, you can also configure Internet settings
+ net-setup eth0
- by hand. You should be able to do so if you've previously configured your
- settings in the operating system you normally use. The command to run is
- net-setup
+ Note: In the command replace eth0 with the network interface you want to use.
  When you're done
  ****************************************
-Line 3735 
 partitions.Creating a disk image of the
+Line 3753 
 partitions.Creating a disk image of the
  is highly recommended.
  [[ info.png ]]
- The following pressentation has been made usingSystemRescueCD v 1.5.8
+ The following pressentation has been made usingSystemRescueCD v 2.1.1
  Some theory
  ****************************************
-Line 3768 
 in Master Boot Record. MBR itself is onl
+Line 3786 
 in Master Boot Record. MBR itself is onl
  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 logical block addressing {{
- http://en.wikipedia.org/wiki/Logical_block_addressing#LBA.2C_ATA_devices_and_Enhanced_BIOS
+ http://en.wikipedia.org/wiki/Logical_block_addressing#Enhanced_BIOS
  }}. Extended partitions are another workaround.
  Partition table can only store information about four partitions. If one
-Line 3912 
 FAT32        Native           Built-in
+Line 3930 
 FAT32        Native           Built-in
  NTFS         Native           Included     16 EB         Yes          Yes
  ext2    3rd party driver       Native    16 GB-2 TB*     No           Yes
  ext3    3rd party driver       Native    16 GB-2 TB*     Yes          Yes
- ext4          No***            Native    16 GB-16 TB*    Yes          Yes
+ ext4    3rd party driver       Native    16 GB-16 TB*    Yes          Yes
  exFAT  Built-in (Vista/7)**    Driver       64 ZB        No           Yes
  * Depends on cluster size
  ** This update {{ http://support.microsoft.com/kb/955704 }} adds exFAT
  support to Windows XP
- *** Ext2read makes accessing ext4 partitions possible, but it's not a
- driver and the access is read-only
  Operating system support:
-Line 3929 
 boot from a partition using that FS.
+Line 3945 
 boot from a partition using that FS.
  from a partition containing such FS is very difficult.
  * "Driver included" means that ntfs-3g (the driver that adds NTFS support
  to Linux) comes with most GNU/Linux distributions.
- * "3rd party driver" means that drivers to add filesystem support are
+ * "3rd party driver" means that a driver to add filesystem support
- available, but must be downloaded and installed separately. The ext2/3
+ is available, but must be downloaded and installed separately. The
- drivers are Ext2 IFS and Ext2fsd and the exFAT driver is exfat {{
+ ext2/3/4 driver is Ext2fsd and the exFAT driver is exfat {{
  http://code.google.com/p/exfat/ }}.
- * "No" means that there is no way to get read-write filesystem support.
  Filesystems
  ****************************************
-Line 3959 
 requires DOS to be installed in the part
+Line 3974 
 requires DOS to be installed in the part
  http://en.wikipedia.org/wiki/FAT_filesystem_and_Linux#Installing_Linux_on_and_booting_it_from_FAT_volumes_using_umsdos
  }})
- FAT32 partition can be up to two terabytes in size. As of now (July 2010),
+ FAT32 partition can be up to two terabytes in size. There are already hard
- there are hard drives that hit the limit, but don't exceed it. A single
+ drives that exceed the limit. A single file within FAT32 partition can be
- file within FAT32 partition can be up to four gigabytes in size.
+ up to four gigabytes in size.
  Because FAT32 is, in the end, based on FAT12, it has very few features. It
  doesn't support file permissions, hard/symbolic links, encryption,
-Line 3986 
 Ext2 was developed in January 1993, earl
+Line 4001 
 Ext2 was developed in January 1993, earl
  mentioned in this page.
  Because ext2 is designed for GNU/Linux, support in Linux kernel was
- implemented immediately. The first Windows driver supporting ext2,
+ implemented immediately. The first Windows driver supporting ext2, Ext2fsd
- Ext2fsd 0.01, was released on 25 January 2002. Both Windows drivers
+.01, was released on 25 January 2002. Ext2fsd works only on Windows NT
- for ext2 work only on Windows NT operating systems (NT 4.0 up to Vista,
+ operating systems starting from Windows 2000.
-isn't supported yet).
  The best property of ext2 is extensibility. The superblock contains
  information about which version the filesystem is (ext2, ext3 or ext4)
-Line 4004 
 size. File size limit is 16 GB-2 TB.
+Line 4018 
 size. File size limit is 16 GB-2 TB.
  Ext2 supports file permissions, both hard and symbolic links and extended
  file attributes. Encryption, compression and journaling are unsupported.
- Due to lack of journaling support and existence of Windows drivers, I
+ Lack of journaling support is the worst limitation of ext2. What was done
- recommend using ext2 if you're going to install GNU/Linux on a SSD drive
+ in order to get rid of the limitation?
- and want to be able to access files within Windows too.
- However, lack of journaling support is the worst limitation of ext2. And
- what was done in order to get rid of the limitation?
  ext3
  ---------------------
-Line 4017 
 Ext3, the successor of ext2, was introdu
+Line 4027 
 Ext3, the successor of ext2, was introdu
 . It supports journaling, can be grown online and optionally indexes
  large directories.
- Ext2 IFS and Ext2fsd can mount ext3 partition as ext2 if the journal
+ Ext2fsd can mount ext3 partition as ext2. Thus, ext3 support under Windows
- is empty. (If it's not, something is wrong - journal is always emptied
+ is just as good/bad as ext2 support.
- when the partition is unmounted or the computer is shut down.) Thus,
- ext3 support under Windows is just as good/bad as ext2 support.
  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.
- Due to journaling support and existence of Windows drivers, ext3 is a good
+ Ext3 is becoming obsolete because there is...
- choice if you're going to install GNU/Linux on a mechanical hard drive
- and want to be able to access files within Windows.
  ext4
  ---------------------
-Line 4048 
 to 64 000 subdirectories (instead of 32
+Line 4054 
 to 64 000 subdirectories (instead of 32
  are much more accurate. The file size limit is 16 GB-16 TB, depending on
  cluster size.
- Unfortunately, Ext2 IFS and Ext2Fsd don't support ext4 and are unable
+ Ext2fsd 0.50, released on 5 February 2011, supports ext4 and is able to
- to mount ext4 partition if extents are enabled. They can be disabled,
+ mount ext4 partition even if extents are enabled. Thus, ext4 support under
- but other improvements of ext4 aren't that important for most people -
+ Windows is just as good/bad as ext2 support.
- using ext2 or ext3 is just easier. It is also possible to keep extents
- enabled and browse the partition using Ext2read, but Ext2read doesn't
+ Due to availability of Ext2fsd 0.50 and additional features, ext4 has become
- allow the user to write to the partition.
+ the de-facto GNU/Linux filesystem. Because journaling can be disabled,
+ it is suitable for Solid State Drives and thumb drives too.
- 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.
  NTFS
  ---------------------
-Line 4213 
 situation in a virtual machine:
+Line 4216 
 situation in a virtual machine:
  I have two partitions in my disk: /dev/sda1 that contains a GNU/Linux
  distribution, and /dev/sda2 that is a swap partition. Here we can see the
- output of fdisk:
+ output of parted:
- root@sysresccd /root % fdisk -l
+ root@sysresccd /root % parted -l
+ Model: ATA VBOX HARDDISK (scsi)
+ Disk /dev/sda: 2097MB
+ Sector size (logical/physical): 512B/512B
+ Partition Table: msdos
+ Number  Start   End     Size    Type     File system     Flags
+     32.3kB  1679MB  1679MB  primary  ext4            boot
+     1679MB  2097MB  418MB   primary  linux-swap(v1)
+ Warning: Unable to open /dev/sr0 read-write (Read-only file system).
+ /dev/sr0 has been opened read-only.
+ Error: /dev/sr0: unrecognised disk label
- Disk /dev/sda: 2097 MB, 2097152000 bytes
+ Error: /dev/fd0: unrecognised disk label
-heads, 63 sectors/track, 1015 cylinders
- Units = cylinders of 4032 * 512 = 2064384 bytes
- Disk identifier: 0x00058a4a
-    Device Boot     Start        End     Blocks   Id  System
- /dev/sda1   *          1        812    1636960+  83  Linux
- /dev/sda2            813       1015     409248   82  Linux swap / Solaris
  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
-Line 4269 
 I right-click now /dev/sda2 and select R
+Line 4277 
 I right-click now /dev/sda2 and select R
  [[ gparted-03.png ]]
  I enter 0 MB as preceding free space and 200 MB as partition size, click
  the Free Space Following (MiB) combo box and press Resize/Move.
+ [[ gparted-03a.png ]]
+ I read the warning. As the swap partition doesn't contain /boot (or any
+ files, for that matter), I just click OK.
  [[ gparted-04.png ]]
  I right-click the unallocated area and select New.
  [[ gparted-05.png ]]
-Line 4285 
 that, I click first the Free Space Follo
+Line 4296 
 that, I click first the Free Space Follo
  I right-click the remaining unallocated space and select New one more time.
  [[ gparted-09.png ]]
  I choose the ext4 filesystem again. The partition size setting was already
 megabytes (the whole available space), so I just press Add.
  [[ gparted-10.png ]]
  [[ important.png ]]
  The next step is to commit the changes.After that some operations, for

 Legend:



Removed from v.179
 


changed lines


 
Added in v.180
 Legend:



Removed from v.179
 


changed lines


 
Added in v.180
-Removed from v.179
+Added in v.180

webmaster@linux.gr	ViewVC Help
Powered by ViewVC 1.1.26