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

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

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

revision 111 by sng, Thu Jun 17 22:25:06 2010 UTC revision 112 by sng, Wed Sep 15 13:20:07 2010 UTC
# Line 1817  boot settings are correct, in order to b Line 1817  boot settings are correct, in order to b
1817  Having done all of the above, I am ready to boot from Clonezilla-SysRescCD.  Having done all of the above, I am ready to boot from Clonezilla-SysRescCD.
1818    
1819  [[ info.png ]]  [[ info.png ]]
1820  The following pressentation has been made usingClonezilla Live v 1.2.5-17  The following pressentation has been made usingClonezilla Live v 1.2.5-35
1821    
1822  Getting the backup  Getting the backup
1823  ****************************************  ****************************************
# Line 1922  Next Screen Line 1922  Next Screen
1922  ---------------------  ---------------------
1923  [[ backup-11.png ]]  [[ backup-11.png ]]
1924  In this screen I select the image name.  In this screen I select the image name.
1925  I type "Backup_22-2010_sdb", which in my opinion is more informative name  I type "Backup_32-2010_sdb", which in my opinion is more informative name
1926  than the default.  than the default.
1927    
1928  Next Screen  Next Screen
# Line 2094  Next Screen Line 2094  Next Screen
2094  ---------------------  ---------------------
2095  [[ backup-11.png ]]  [[ backup-11.png ]]
2096  In this screen I select the image name.  In this screen I select the image name.
2097  I type "Backup_22-2010_sdb", which in my opinion is more informative name  I type "Backup_32-2010_sdb", which in my opinion is more informative name
2098  than the default.  than the default.
2099    
2100  Next Screen  Next Screen
# Line 2162  restoring make sure you have backup of a Line 2162  restoring make sure you have backup of a
2162  disk/partition, even if the filesystem is corrupted.  disk/partition, even if the filesystem is corrupted.
2163    
2164  [[ info.png ]]  [[ info.png ]]
2165  The following pressentation has been made usingClonezilla Live v 1.2.5-17  The following pressentation has been made usingClonezilla Live v 1.2.5-35
2166    
2167  Restoring data  Restoring data
2168  ****************************************  ****************************************
# Line 2310  Creating a Restore DVD - Part 1 Line 2310  Creating a Restore DVD - Part 1
2310    
2311  Intro  Intro
2312  ****************************************  ****************************************
2313  Assuming you have used Clonezilla Live to make a backup of your Windows XP  Assuming you have used Clonezilla Live to make a backup of your Windows
2314  system (partition /dev/hda1), which you have saved as win_img, you will  XP system (partition /dev/sda1), you will probably be wondering what to
2315  probably be wondering what to do with it now. Well, one option would be  do with it now. Well, one option would be to keep it to the disk you used
2316  to keep it to the disk you used to save it in, store the disk, and use it  to save it in, store the disk, and use it whenever you need it. Another
2317  whenever you need it. Another option would be to create a DVD you can use  option would be to create a DVD you can use to restore this image.
 to restore this image.  
2318    
2319  Before, up to Clonezilla-SysRescCD 2.6.0, the process to create an automated  Before, up to Clonezilla-SysRescCD 2.6.0, the process to create an automated
2320  restore DVD required entering command line prompt and writing some commands,  restore DVD required entering command line prompt and writing some commands,
# Line 2327  Clonezilla Live, and ocs-iso script incl Line 2326  Clonezilla Live, and ocs-iso script incl
2326  supported. This page walks you through the creation of an automated restore  supported. This page walks you through the creation of an automated restore
2327  DVD via TUI.  DVD via TUI.
2328    
2329  Assuming you have saved your image file win_img in partition hdb4, you  You have to boot Clonezilla Live, using Clonezilla-SysRescCD.
 have to boot Clonezilla Live, using Clonezilla-SysRescCD.  
2330    
2331  [[ info.png ]]  [[ info.png ]]
2332  The following pressentation has been made usingClonezilla Live v 1.2.3-27  The following pressentation has been made usingClonezilla Live v 1.2.5-17
2333    
2334  Creating the disk image  Creating the disk image
2335  ****************************************  ****************************************
# Line 2407  Next screen Line 2405  Next screen
2405  ---------------------  ---------------------
2406  This is where I choose the location of the image file.  This is where I choose the location of the image file.
2407  [[ restore-06.png ]]  [[ restore-06.png ]]
2408  I select partition hda1 and press ENTER.  I select partition sda1 and press ENTER.
2409    
2410  [[ backup-07.png ]]  [[ backup-07.png ]]
2411  and then ENTER again.  and then ENTER again.
2412    
2413  [[ restore-08.png ]]  [[ restore-08.png ]]
2414  This screen displays the mounting result.  This screen displays the mounting result.
2415  As we can see, /dev/hda1 has been successfully mounted under /tmp/local-dev.  As we can see, /dev/sda1 has been successfully mounted under /tmp/local-dev.
2416    
2417  Next Screen  Next Screen
2418  ---------------------  ---------------------
# Line 2470  which can be used to create a bootable p Line 2468  which can be used to create a bootable p
2468  Then the program will display the command that will be executed and will  Then the program will display the command that will be executed and will
2469  ask me to press ENTER.  ask me to press ENTER.
2470    
2471  [[ cust-menu-01.png ]]  Screen "Excessive Image Size"
2472  Due to limitations of mkisofs, the script can't create a ISO file which  ---------------------
2473  is over 4,5 gigabytes in size. It causes problems if the size of your  [[ restore-16a.png ]]
2474  image is over 4,4 gigabytes. Clonezilla-SysRescCD contains a workaround  You will see this screen if the image file you're about to create is larger
2475  that creates a ISO file that contains no image, so you can add the image  than a single layer DVD. The screen warns that mkisofs or genisoimage
2476  manually later. This dialog asks if you want to do so. Note that if you  (the programs which actually create the image) might be unable to process
2477  see this dialog, you most likely need a dual layer DVD+R or Blu-ray disc  a disk image that big. However, even bigger problem is that you need a
2478  to burn the image. Growisofs doesn't support multisession burning on dual  dual layer DVD or Blu-ray disc to burn the image.
 layer DVD-R discs, so such disc can't be used either.  
2479    
2480  Screen "Customization section"  Screen "Customization section"
2481  ---------------------  ---------------------
# Line 2552  Starting the creation of the disk image Line 2549  Starting the creation of the disk image
2549  After that, creation of the disk image begins. Note that no confirmation  After that, creation of the disk image begins. Note that no confirmation
2550  is asked it the disk image is small enough to fit to a CD.  is asked it the disk image is small enough to fit to a CD.
2551    
 [[ cust-menu-10.png ]]  
   
 If you have above enabled the workaround to create a ISO file without any  
 image, you get the info screen, which explains the actions to be taken  
 in order to burn the ISO file and add the iamge file to the DVD. A script  
 file is also saved as /tmp/burnISO.  
   
2552  [[ restore-18.png ]]  [[ restore-18.png ]]
2553  When the disk image is successfully created, I must reboot in order to  When the disk image is successfully created, I must reboot in order to
2554  burn the disc because my DVD burner is still in use. Clonezilla Live can  burn the disc because my DVD burner is still in use. Clonezilla Live can
# Line 2567  disc(s) within it. However, due to a kno Line 2557  disc(s) within it. However, due to a kno
2557  be created if Clonezilla Live has been loaded into memory. (source {{  be created if Clonezilla Live has been loaded into memory. (source {{
2558  http://free.nchc.org.tw/clonezilla-live/stable/Known-issues-Clonezilla-live.txt  http://free.nchc.org.tw/clonezilla-live/stable/Known-issues-Clonezilla-live.txt
2559  }}) Thus, I press 1 and ENTER to reboot to another operating system and  }}) Thus, I press 1 and ENTER to reboot to another operating system and
2560  burn the image using graphical burning program. For instructions, follow  burn the image using graphical burning program. Follow this link for
2561  one of these links:  instructions. If you've created a ZIP file, follow this one instead.
   
 If the ISO file contains the disk image  
 If the ISO file contains no image  
 If you've created a ZIP file  
2562    
2563    
2564    
# Line 2610  to your burner. Line 2596  to your burner.
2596    
2597  Burning the disc  Burning the disc
2598  ****************************************  ****************************************
2599  If the ISO file contains the disk image  Using ImgBurn
2600  ---------------------  ---------------------
 > Using ImgBurn  
   
2601  ImgBurn {{ http://www.imgburn.com/ }} is a lightweight but very feature-rich  ImgBurn {{ http://www.imgburn.com/ }} is a lightweight but very feature-rich
2602  disc burning program. It only requires about two megabytes disk space  disc burning program. It only requires about two megabytes disk space
2603  and contains a lot of settings. ImgBurn is closed-source freeware and -  and contains a lot of settings. ImgBurn is closed-source freeware and -
# Line 2642  burning, because doing so increases the Line 2626  burning, because doing so increases the
2626    
2627  That's it. You own now an automated recovery disc.  That's it. You own now an automated recovery disc.
2628    
2629  > Using K3b  Using K3b
2630    ---------------------
2631  K3b (KDE Burn Baby Burn) is the disc burning program included in KDE  K3b (KDE Burn Baby Burn) is the disc burning program included in KDE
2632  Software Compilation. It comes with most, if not all, KDE-based GNU/Linux  Software Compilation. It comes with most, if not all, KDE-based GNU/Linux
2633  distributions. It can also be installed on other distributions, but I  distributions. It can also be installed on other distributions, but I
# Line 2680  the integrity of the disc right after bu Line 2664  the integrity of the disc right after bu
2664  [[ k3b-05.png ]]  [[ k3b-05.png ]]
2665  The burning attempt succeeded.  The burning attempt succeeded.
2666    
 If the ISO file contains no image  
 ---------------------  
 If you have enabled the workaround to create a ISO file that contains  
 no disk image (required if the size of the image is over 4,4 gigabytes),  
 things become much more problematic. The ISO file and the image can't be  
 burned to the disc simultaneously, they must be written one-by-one. That  
 requires two burning sessions: the first for writing the ISO file to the  
 disc and the second for adding the disk image. Many burning programs don't  
 even support multisession burning at all. About the programs I've mentioned  
 in this page: K3b supports multisession burning, ImgBurn doesn't.  
   
 I didn't find any instructions for adding an additional file to a  
 spesific directory by using K3b. Actually, I don't even know if that's  
 possible at all. Thus, I recommend using growisofs for burning the disc  
 if the workaround has been enabled, because growisofs allows adding  
 any file to any directory. However, there's one more limitation:  
 growisofs doesn't support multisession burning on dual layer DVD-R  
 discs, so you must use dual layer DVD+R or Blu-ray disc. (source {{  
 http://fy.chalmers.se/~appro/linux/DVD+RW/-RW/#nomultisess }})  
   
 Growisofs is a command-line program and a part of dvd+rw-tools that is  
 installed on most GNU/Linux distributions. Dvd+rw-tools is Linux-only  
 software, so if you use a competing operating system, you must boot into  
 SystemRescueCD (graphical mode is not needed) in order to burn the disc.  
   
 Open terminal and mount the partition that contains the image. The commands  
 below must be run as root.  
   
 mkdir /media/usb  
 mount /dev/sdc1 /media/usb  
   
 Note: How a command can be run as root depends on the GNU/Linux distribution  
 you use. If it's Ubuntu or a distro based on it, simply put "sudo" above the  
 command. For example, the latter of the above commands can be executed by  
 typing "sudo mount /dev/sdc1 /media/usb". If you're using SystemRescueCD,  
 all commands are run as root, so you don't need to add any prefix to  
 the commands.  
   
 Note: In the command replace /dev/sdc1 with the partition where the disk  
 image resides. It's the same partition you mounted as /home/partimag when  
 creating the image.  
   
 Go to root of the partition:  
   
 cd /media/usb  
   
 Burn the ISO file to the disc:  
   
 growisofs -Z /dev/dvd=clonezilla-live-Backup_5-2010_hdb.iso  
   
 Note: In the last command I have assumed your ISO file is  
 clonezilla-live-Backup_5-2010_hdb.iso. You will have to replace this with  
 the actual name of the file.  
   
 Note: If your computer has multiple DVD drives, replace /dev/dvd with the  
 name of your DVD writer.  
   
 The disc must be ejected because it's the only known way to force the  
 drive to reread the disc. Do it:  
   
 eject /dev/dvd  
   
 Note: If your drive can't reload the disc, insert the disc back right  
 after ejecting it.  
   
 Finally, add the image file to the disc:  
   
 growisofs -M /dev/dvd -R -J -V "Backup_5-2010_hdb" \  
 --publisher "Your Name" -graft-points \  
 /Backup_5-2010_hdb/=/media/usb/Backup_5-2010_hdb  
   
 Note: In the command replace Your Name 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:  
   
 growisofs -M /dev/dvd -R -J -V "Backup_5-2010_hdb" \  
 -graft-points /Backup_5-2010_hdb/=/media/usb/Backup_5-2010_hdb  
   
2667  [[ restore-20.png ]]  [[ restore-20.png ]]
2668    Here we can see the boot menu of the disc.
2669    
2670  ZIP file instructions  ZIP file instructions
2671  ****************************************  ****************************************
# Line 2785  After creating the disk image and bootin Line 2692  After creating the disk image and bootin
2692  filesystem of the partition where you plan to put the disk image is FAT32. If  filesystem of the partition where you plan to put the disk image is FAT32. If
2693  you don't know the filesystem, open terminal and run this command as root:  you don't know the filesystem, open terminal and run this command as root:
2694    
2695  fdisk -l /dev/sdc  parted -l
2696    
2697  Note: How a command can be run as root depends on the GNU/Linux distribution  Note: How a command can be run as root depends on the GNU/Linux distribution
2698  you use. If it's Ubuntu or a distro based on it, simply put "sudo" above  you use. If it's Ubuntu or a distro based on it, simply put "sudo" above
2699  the command. For example, the above command can be executed by typing  the command. For example, the above command can be executed by typing
2700  "sudo fdisk -l /dev/sdc"  "sudo parted -l"
   
 Note: In the command replace /dev/sdc with the name of your USB disk.  
   
2701  Note: The l in parameter -l is lowercase L, not number 1.  Note: The l in parameter -l is lowercase L, not number 1.
2702    
2703  If your disk doesn't contain any FAT32 partition, but it contains a  If your disk doesn't contain any FAT32 partition, but it contains a
# Line 2806  you don't format a wrong partition by ac Line 2710  you don't format a wrong partition by ac
2710    
2711  mkfs.vfat -F 32 /dev/sdc1  mkfs.vfat -F 32 /dev/sdc1
2712    
2713    Note: In the command replace /dev/sdc1 with the partition you wish to format.
2714    
2715  After formatting the partition or noticing that it was already FAT32,  After formatting the partition or noticing that it was already FAT32,
2716  extract the ZIP archive to the root of the partition. Also these commands  extract the ZIP archive to the root of the partition. Also these commands
2717  need root rights.  need root rights.
# Line 2842  need graphical mode this time) and follo Line 2748  need graphical mode this time) and follo
2748  SystemRescueCD all commands are run as root, so you don't need to add any  SystemRescueCD all commands are run as root, so you don't need to add any
2749  prefix to the commands.  prefix to the commands.
2750    
 If you normally use Windows, you maybe don't know the name of your USB  
 disk in GNU/Linux. If that's the case, don't specify any disk in the first  
 command. It causes fdisk to tell about all disks in the computer and you  
 should be able to identify both the right disk and the right partition.  
   
2751  After creating the disk image and booting into Windows, make sure that  After creating the disk image and booting into Windows, make sure that
2752  the filesystem of the partition where you plan to put the disk image is  the filesystem of the partition where you plan to put the disk image is
2753  FAT32. If you don't know the filesystem, open My Computer, right-click the  FAT32. If you don't know the filesystem, open My Computer, right-click the
# Line 3655  and it's often just plain unneeded. Line 3556  and it's often just plain unneeded.
3556    
3557  Try VESA, if normal Graphical Environment doesn't work. VESA uses Xvesa  Try VESA, if normal Graphical Environment doesn't work. VESA uses Xvesa
3558  graphical environment instead of X.Org that sometimes doesn't work. The  graphical environment instead of X.Org that sometimes doesn't work. The
3559  drawbacks of Xvesa compared to X.Org are that Xvesa isn't optimized to  drawback of Xvesa compared to X.Org is that Xvesa isn't optimized to any
3560  any hardware (which means poorer performance) and Xvesa requires 32-bit  hardware, which means poorer performance.
 kernel. Thus, if you use this option, do NOT choose 64-bit kernel, the  
 combination leaves you at command line.  
3561    
3562  If you're accustomed to command line and know already that you're not going  If you're accustomed to command line and know already that you're not going
3563  to use any graphical program, choose one of the normal options (just below  to use any graphical program, choose one of the normal options (just below
# Line 3691  IA-32 processor, like Intel Pentium 4 or Line 3590  IA-32 processor, like Intel Pentium 4 or
3590  a x86-64 processor, like AMD Athlon 64 or Intel Core 2, you can choose  a x86-64 processor, like AMD Athlon 64 or Intel Core 2, you can choose
3591  any kernel - the processor can run all of them. 64-bit kernel should be  any kernel - the processor can run all of them. 64-bit kernel should be
3592  preferred, because it allows chrooting on an existing GNU/Linux partition  preferred, because it allows chrooting on an existing GNU/Linux partition
3593  containing 64-bit programs. Note, though, that you can't use 64-bit kernel  containing 64-bit programs.
 with VESA option.  
3594    
3595  If you don't know your processor architecture, try 64-bit kernel. If your  If you don't know your processor architecture, try 64-bit kernel. If your
3596  processor architecture is IA-32, you'll see the following error message:  processor architecture is IA-32, you'll see the following error message:
# Line 3804  partitions.Creating a disk image of the Line 3702  partitions.Creating a disk image of the
3702  is highly recommended.  is highly recommended.
3703    
3704  [[ info.png ]]  [[ info.png ]]
3705  The following pressentation has been made usingSystemRescueCD v 1.4.0  The following pressentation has been made usingSystemRescueCD v 1.5.8
3706    
3707  Some theory  Some theory
3708  ****************************************  ****************************************
# Line 3860  unallocated space). Extended partition d Line 3758  unallocated space). Extended partition d
3758  files can't be stored in it. Of course, logical partition can contain any  files can't be stored in it. Of course, logical partition can contain any
3759  filesystem (or be unformatted).  filesystem (or be unformatted).
3760    
3761  Extended partition itself must be primary partition: an extended partition  Logical partitions can always be used for storing data: any operating
3762  can't be within another extended partition. In addition, a disk can contain  system can see logical partitions. GNU/Linux supports both multiple primary
3763  only one extended partition.  extended partitions and extended partitions within each other, while
3764    Windows supports only the latter. GNU/Linux distributions can be installed
3765  Logical partitions can always be used for storing data: any operating system  to logical partitions as well, but Windows requires a lot of tweaking. See
 can see logical partitions. GNU/Linux distributions can be installed to  
 logical partitions as well, but Windows requires a lot of tweaking. See  
3766  this outdated guide {{ http://www.goodells.net/multiboot/index.htm }}.  this outdated guide {{ http://www.goodells.net/multiboot/index.htm }}.
3767    
3768  What is LVM?  What is LVM?
# Line 3949  filesystem itself. If power failure or O Line 3845  filesystem itself. If power failure or O
3845  filesystem itself, the write operation is finished by using the information  filesystem itself, the write operation is finished by using the information
3846  in journal.  in journal.
3847    
3848  Journaling helps most of the time when the computer has been forcefully  Journaling is always a trade-off between reliability and performance. In
3849  shut down, but not always. Due to performance reasons, only some  fact, the ext3 and ext4 filesystems support multiple journaling modes in
3850  write operations are written to the journal, mostly the biggest  order to allow the user to choose the optimal compromise. The most popular
3851  operations. Of course, journaling doesn't help if that particular  choices are ordered and writeback.
3852  operation that was in progress while power was lost didn't go  
3853  through the journal. Journaling also doesn't protect from everything:  Both modes only write metadata changes to the journal before committing
3854  for example, using ext4 filesystem in conjuction with programs that  them: data itself is written directly to the main filesystem. The difference
3855  write a lot of files in a short time can result in massive data loss {{  between the modes is that ordered mode guarantees that the data is written
3856  http://www.h-online.com/open/news/item/Possible-data-loss-in-Ext4-740467.html  before the change is marked as committed. The difference may sound small, but
3857  }}, regardless if journaling is enabled or not.  in some cases ordered mode causes horrible performance. In Linux 2.6.30, the
3858    default journaling mode was changed to writeback - and it was quickly found
3859  In addition, journaling reduces performance. It causes more writes to  out that writeback mode may cause massive data loss. See this forum post {{
3860  the disk. That's not a big problem on mechanical hard drives, but on SSDs  http://forums.raiden.net/viewtopic.php?p=155912#155912 }} for details. Most
3861  (Solid State Drives) and thumb drives write speed is much slower than read  GNU/Linux distributions are now using ordered mode as the default again.
3862  speed. They also have a limited number of writing cycles, so journaling  
3863  reduces their lifetime. I (Jyrki) actually use ext2 and FAT32 filesystems  In addition, on SSDs (Solid State Drives) and thumb drives write speed is
3864  on my external SSD drive because they do NOT support journaling at all.  much slower than read speed. They also have a limited number of writing
3865    cycles, so journaling reduces their lifetime. Thus, I (Jyrki) recommend
3866    against using journaling fileystems on such drives.
3867    
3868  What are the differences between most popular filesystems?  What are the differences between most popular filesystems?
3869  ---------------------  ---------------------
# Line 3981  FAT32        Native           Built-in Line 3879  FAT32        Native           Built-in
3879  NTFS         Native           Included     16 EB         Yes          Yes  NTFS         Native           Included     16 EB         Yes          Yes
3880  ext2    3rd party driver       Native    16 GB-2 TB*     No           Yes  ext2    3rd party driver       Native    16 GB-2 TB*     No           Yes
3881  ext3    3rd party driver       Native    16 GB-2 TB*     Yes          Yes  ext3    3rd party driver       Native    16 GB-2 TB*     Yes          Yes
3882  ext4           No              Native    16 GB-16 TB*    Yes          Yes  ext4          No***            Native    16 GB-16 TB*    Yes          Yes
3883  exFAT   Native (Vista/7)**       No         64 ZB        No           Yes  exFAT  Built-in (Vista/7)**    Driver       64 ZB        No           Yes
3884    
3885  * Depends on cluster size  * Depends on cluster size
3886  ** This update {{ http://support.microsoft.com/kb/955704 }} adds exFAT  ** This update {{ http://support.microsoft.com/kb/955704 }} adds exFAT
3887  support to Windows XP  support to Windows XP
3888    *** Ext2read makes accessing ext4 partitions possible, but it's not a
3889    driver and the access is read-only
3890    
3891  Operating system support:  Operating system support:
3892    
# Line 3997  from a partition containing such FS is v Line 3897  from a partition containing such FS is v
3897  * "Driver included" means that ntfs-3g (the driver that adds NTFS support  * "Driver included" means that ntfs-3g (the driver that adds NTFS support
3898  to Linux) comes with most GNU/Linux distributions.  to Linux) comes with most GNU/Linux distributions.
3899  * "3rd party driver" means that drivers to add filesystem support are  * "3rd party driver" means that drivers to add filesystem support are
3900  available, but must be downloaded and installed separately. The drivers  available, but must be downloaded and installed separately. The ext2/3
3901  are Ext2 IFS and Ext2fsd.  drivers are Ext2 IFS and Ext2fsd and the exFAT driver is exfat {{
3902  * "No" means that there is no way to use the filesystem within the  http://code.google.com/p/exfat/ }}.
3903  operating system.  * "No" means that there is no way to get read-write filesystem support.
3904    
3905  Filesystems  Filesystems
3906  ****************************************  ****************************************
# Line 4026  requires DOS to be installed in the part Line 3926  requires DOS to be installed in the part
3926  http://en.wikipedia.org/wiki/FAT_filesystem_and_Linux#Installing_Linux_on_and_booting_it_from_FAT_volumes_using_umsdos  http://en.wikipedia.org/wiki/FAT_filesystem_and_Linux#Installing_Linux_on_and_booting_it_from_FAT_volumes_using_umsdos
3927  }})  }})
3928    
3929  FAT32 partition can be up to two terabytes in size. As of now (March 2010),  FAT32 partition can be up to two terabytes in size. As of now (July 2010),
3930  there are hard drives that hit the limit, but don't exceed it. A single  there are hard drives that hit the limit, but don't exceed it. A single
3931  file within FAT32 partition can be up to four gigabytes in size.  file within FAT32 partition can be up to four gigabytes in size.
3932    
# Line 4073  file attributes. Encryption, compression Line 3973  file attributes. Encryption, compression
3973    
3974  Due to lack of journaling support and existence of Windows drivers, I  Due to lack of journaling support and existence of Windows drivers, I
3975  recommend using ext2 if you're going to install GNU/Linux on a SSD drive  recommend using ext2 if you're going to install GNU/Linux on a SSD drive
3976  and want to be able to access files within Windows too. In fact, that's  and want to be able to access files within Windows too.
 exactly the setup I have.  
3977    
3978  However, lack of journaling support is the worst limitation of ext2. And  However, lack of journaling support is the worst limitation of ext2. And
3979  what was done in order to get rid of the limitation?  what was done in order to get rid of the limitation?
# Line 4082  what was done in order to get rid of the Line 3981  what was done in order to get rid of the
3981  ext3  ext3
3982  ---------------------  ---------------------
3983  Ext3, the successor of ext2, was introduced in Linux kernel on November  Ext3, the successor of ext2, was introduced in Linux kernel on November
3984  2001. It supports journaling, can be grown online and indexes large  2001. It supports journaling, can be grown online and optionally indexes
3985  directories.  large directories.
3986    
3987  Ext2 IFS and Ext2fsd can mount ext3 partition as ext2 if the journal  Ext2 IFS and Ext2fsd can mount ext3 partition as ext2 if the journal
3988  is empty. (If it's not, something is wrong - journal is always emptied  is empty. (If it's not, something is wrong - journal is always emptied
# Line 4119  cluster size. Line 4018  cluster size.
4018  Unfortunately, Ext2 IFS and Ext2Fsd don't support ext4 and are unable  Unfortunately, Ext2 IFS and Ext2Fsd don't support ext4 and are unable
4019  to mount ext4 partition if extents are enabled. They can be disabled,  to mount ext4 partition if extents are enabled. They can be disabled,
4020  but other improvements of ext4 aren't that important for most people -  but other improvements of ext4 aren't that important for most people -
4021  using ext2 or ext3 is just easier.  using ext2 or ext3 is just easier. It is also possible to keep extents
4022    enabled and browse the partition using Ext2read, but Ext2read doesn't
4023    allow the user to write to the partition.
4024    
4025  Due to its features, ext4 is a good filesystem on computers that only have  Due to its features, ext4 is a good filesystem on computers that only have
4026  GNU/Linux installed. Because journaling can be disabled, it is suitable  GNU/Linux installed. Because journaling can be disabled, it is suitable
# Line 4180  updated it one more time. Line 4081  updated it one more time.
4081  ExFAT (extended FAT), also known as FAT64, was introduced with Windows CE  ExFAT (extended FAT), also known as FAT64, was introduced with Windows CE
4082  6.0, on November 2006. Windows Vista SP1, Windows 7 and newer support exFAT  6.0, on November 2006. Windows Vista SP1, Windows 7 and newer support exFAT
4083  too, and by installing this update {{ http://support.microsoft.com/kb/955704  too, and by installing this update {{ http://support.microsoft.com/kb/955704
4084  }} Windows XP can be extended to support exFAT as well. Unfortunately,  }} Windows XP can be extended to support exFAT as well. GNU/Linux drivers
4085  the only read-write exFAT driver for GNU/Linux (Tuxera exFAT for Embedded  are available too, but currently none of them are both stable and free. The
4086  Systems) is payware.  best option seems to be exfat, an open-source driver in beta stage.
4087    
4088  The partition and file size limits of exFAT are the same: 64  The partition and file size limits of exFAT are the same: 64
4089  zettabytes. Another important improvement is file permission support that,  zettabytes. Another important improvement is file permission support that,
# Line 4250  The following table presents known parti Line 4151  The following table presents known parti
4151    
4152  The partitions you are most likely to see in use, are:  The partitions you are most likely to see in use, are:
4153    
 * FAT16 (ID = 6)  
 This is the old DOS partition type  
 You may still find it in pure DOS installations, like vendor diagnostics  
 tool partitions, and small USB sticks (128 - 250 MB)  
   
4154  * HPFS/NTFS (ID = 7)  * HPFS/NTFS (ID = 7)
4155  This is the Windows XP partition, also known as NTFS  This is the Windows XP partition, also known as NTFS
4156    
# Line 4264  It is used in any kind of disk and large Line 4160  It is used in any kind of disk and large
4160    
4161  * W95 Ext'd (LBA) (ID = f)  * W95 Ext'd (LBA) (ID = f)
4162  Extended partition. It acts as a container for other partitions  Extended partition. It acts as a container for other partitions
4163  There is one more extended partition type (ID = 5), but it does not seem  
4164  to be in use as much  * Extended (ID = 5)
4165    Another extended partition type. It acts as a container for other partitions
4166    There is one more extended partition type (ID = 85), but Windows doesn't
4167    recognise it
4168    
4169  * Linux swap / Solaris (ID = 82)  * Linux swap / Solaris (ID = 82)
4170  Swap partition, acting as Virtual Memory  Swap partition, acting as Virtual Memory
# Line 4341  the Free Space Following (MiB) combo box Line 4240  the Free Space Following (MiB) combo box
4240  I right-click the unallocated area and select New.  I right-click the unallocated area and select New.
4241  [[ gparted-05.png ]]  [[ gparted-05.png ]]
4242  I select Extended Partition as the partition type. The size was already  I select Extended Partition as the partition type. The size was already
4243  998 megabytes (the maximum) and as said, an extended partition doesn't  1000 megabytes (the maximum) and as said, an extended partition doesn't
4244  contain any filesystem. I click Add.  contain any filesystem. I click Add.
4245  [[ gparted-06.png ]]  [[ gparted-06.png ]]
4246  I right-click the unallocated area within the extended partition and  I right-click the unallocated area within the extended partition and
4247  select New.  select New.
4248  [[ gparted-07.png ]]  [[ gparted-07.png ]]
4249  I choose the ext4 filesystem and enter 798 MB as the partition size. After  I choose the ext4 filesystem and enter 799 MB as the partition size. After
4250  that, I click first the Free Space Following (MiB) combo box and then Add.  that, I click first the Free Space Following (MiB) combo box and then Add.
4251  [[ gparted-08.png ]]  [[ gparted-08.png ]]
4252  I right-click the remaining unallocated space and select New one more time.  I right-click the remaining unallocated space and select New one more time.
4253  [[ gparted-09.png ]]  [[ gparted-09.png ]]
4254  I choose the ext4 filesystem again. The partition size setting was already  I choose the ext4 filesystem again. The partition size setting was already
4255  201 megabytes (the whole available space), so I just press Add.  200 megabytes (the whole available space), so I just press Add.
4256  [[ gparted-10.png ]]  [[ gparted-10.png ]]
4257  [[ important.png ]]  [[ important.png ]]
4258  The next step is to commit the changes.After that some operations, for  The next step is to commit the changes.After that some operations, for
# Line 4384  Then I mount the partitions: Line 4283  Then I mount the partitions:
4283  mount /dev/sda1 /mnt/sda1  mount /dev/sda1 /mnt/sda1
4284  mount /dev/sda6 /mnt/sda6  mount /dev/sda6 /mnt/sda6
4285    
4286  I move the directory:  I copy the directory to the new partition:
4287    
4288    cd /mnt/sda1
4289    rsync -aAPSX home/ /mnt/sda6
4290    
4291  mv /mnt/sda1/home/* /mnt/sda6/  I move the original directory out of my way and create a new directory in
4292    place of it:
4293    
4294    mv home home-old
4295    mkdir home
4296    
4297  After that, I unmount /dev/sda6, because it no longer needs to be mounted:  After that, I unmount /dev/sda6, because it no longer needs to be mounted:
4298    
 sync  
4299  umount /dev/sda6  umount /dev/sda6
4300  [[ terminal.png ]]  [[ terminal.png ]]
 As you can see, under Linux it's perfectly normal that the terminal doesn't  
 answer to the commands. Don't worry - they are really executed.  
   
4301  Now I close Terminal and launch Geany by pressing the fourth icon in the  Now I close Terminal and launch Geany by pressing the fourth icon in the
4302  bottom pane.  bottom pane.
4303  [[ geany-00.png ]]  [[ geany-00.png ]]
# Line 4412  I add the following line: Line 4314  I add the following line:
4314  Finally, I select File -> Save.  Finally, I select File -> Save.
4315  [[ geany-04.png ]]  [[ geany-04.png ]]
4316  It's a good idea to reboot the computer now and check if the distribution  It's a good idea to reboot the computer now and check if the distribution
4317  in /dev/sda1 still works. Anyway, the disk should now be ready for the  in /dev/sda1 still works. If yes, the /home-old directory can be removed
4318  new distro.  and the disk is ready for the new distro.
4319    
4320    
4321    

Legend:
Removed from v.111  
changed lines
  Added in v.112

webmaster@linux.gr
ViewVC Help
Powered by ViewVC 1.1.26