tazusb rev 52

Tidy up manual
author Paul Issott <paul@slitaz.org>
date Sat Jan 23 11:54:11 2010 +0000 (2010-01-23)
parents ff2c55121408
children cb3667444dbb
files doc/tazusb.en.html
line diff
     1.1 --- a/doc/tazusb.en.html	Sat Jan 23 11:30:08 2010 +0000
     1.2 +++ b/doc/tazusb.en.html	Sat Jan 23 11:54:11 2010 +0000
     1.3 @@ -39,10 +39,19 @@
     1.4  </pre>
     1.5  <h2>DESCRIPTION</h2>
     1.6  <p>
     1.7 -TazUSB is a utility designed for installing SliTaz to a USB drive. Unlike a hard drive install, the filesystem is kept in a compressed "rootfs.gz" file. The filesystem is loaded entirely into memory upon boot. This should increase responsiveness, protect the filesystem against accidental corruption and reduce read/writes to the USB drive. Once setup, this utility can also rewrite the root filesystem with any changes you have made since booting up, giving the effective benefits of a hard drive install.
     1.8 +TazUSB is a utility designed for installing SliTaz to a USB drive. Unlike a 
     1.9 +hard drive install, the filesystem is kept in a compressed "rootfs.gz" file. 
    1.10 +The filesystem is loaded entirely into memory upon boot. This should increase 
    1.11 +responsiveness, protect the filesystem against accidental corruption and 
    1.12 +reduce read/writes to the USB drive. Once setup, this utility can also 
    1.13 +rewrite the root filesystem with any changes you have made since booting up, 
    1.14 +giving the effective benefits of a hard drive install.
    1.15  </p>
    1.16  <p>
    1.17 -TazUSB supports both FAT32/EXT3 formatted drives using SYSLINUX and EXTLINUX respectively. "/home" is mounted on boot using the UUID of your particular flash drive. Unlike a device name, the UUID has the benefit of never changing from machine to machine.  
    1.18 +TazUSB supports both FAT32/EXT3 formatted drives using SYSLINUX and EXTLINUX 
    1.19 +respectively. "/home" is mounted on boot using the UUID of your particular 
    1.20 +flash drive. Unlike a device name, the UUID has the benefit of never changing 
    1.21 +from machine to machine.  
    1.22  </p>
    1.23  <h2>COMMANDS</h2>
    1.24  <a name="usage"></a>
    1.25 @@ -56,10 +65,21 @@
    1.26  <a name="writefs"></a>
    1.27  <h3><font color="#6c0023">writefs</font></h3>
    1.28  <p>
    1.29 -The command 'writefs' will take the current memory resident filesystem and create a "rootfs.gz" file. If your flash drive is mounted as /home (as it should be), the new filesystem will be copied to the drive for you, otherwise it is left on the root of the drive. Your previous filesystem will be renamed to "previous.gz" and can be accessed on bootup by typing "previous" at the "boot:" prompt. All previous filesystems are renamed to rootfs.gz.unixtimestamp. These are not removed automatically, so you should periodically delete these to keep disk usage down.
    1.30 +The command 'writefs' will take the current memory resident filesystem and 
    1.31 +create a "rootfs.gz" file. If your flash drive is mounted as /home (as it 
    1.32 +should be), the new filesystem will be copied to the drive for you, otherwise 
    1.33 +it is left on the root of the drive. Your previous filesystem will be renamed 
    1.34 +to "previous.gz" and can be accessed on bootup by typing "previous" at the 
    1.35 +"boot:" prompt. All previous filesystems are renamed to 
    1.36 +rootfs.gz.unixtimestamp. These are not removed automatically, so you should 
    1.37 +periodically delete these to keep disk usage down.
    1.38  </p>
    1.39  <p>
    1.40 -Filesystem compression is supported in the form of lzma, gzip or none. Using no compression is very quick (under 5 seconds) and useful if you are experimenting with a lot of changes. By comparison, using lzma or gzip takes a few minutes but will dramatically reduce file size. This is recommended when committing permanent changes to the filesystem.
    1.41 +Filesystem compression is supported in the form of lzma, gzip or none. 
    1.42 +Using no compression is very quick (under 5 seconds) and useful if you are 
    1.43 +experimenting with a lot of changes. By comparison, using lzma or gzip takes 
    1.44 +a few minutes but will dramatically reduce file size. This is recommended when 
    1.45 +committing permanent changes to the filesystem.
    1.46  </p>
    1.47  <pre>
    1.48   # tazusb writefs compression
    1.49 @@ -71,7 +91,8 @@
    1.50  <a name="format"></a>
    1.51  <h3><font color="#6c0023">format</font></h3>
    1.52  <p>
    1.53 -The command 'format' is used for formatting a device for use as a LiveUSB device. Currently, it only supports formatting as EXT3.
    1.54 +The command 'format' is used for formatting a device for use as a LiveUSB 
    1.55 +device. Currently, it only supports formatting as EXT3.
    1.56  </p>
    1.57  <pre>
    1.58   # tazusb format /dev/name
    1.59 @@ -83,7 +104,10 @@
    1.60  <a name="gen-liveusb"></a>
    1.61  <h3><font color="#6c0023">gen-liveusb</font></h3>
    1.62  <p>
    1.63 -"gen-liveusb" will install a fresh MBR, set your partition as bootable and install syslinux/extlinux depending on the detected filesystem. It will then copy the kernel and filesystem from the CDROM drive, and place this on the target USB drive. This will leave you with a bootable USB copy of SliTaz. 
    1.64 +"gen-liveusb" will install a fresh MBR, set your partition as bootable and 
    1.65 +install syslinux/extlinux depending on the detected filesystem. It will then 
    1.66 +copy the kernel and filesystem from the CDROM drive, and place this on the 
    1.67 +target USB drive. This will leave you with a bootable USB copy of SliTaz. 
    1.68  </p>
    1.69  <pre>
    1.70   # tazusb gen-liveusb /dev/name