Changeset 2096

Show
Ignore:
Timestamp:
10/07/07 08:01:39 (1 year ago)
Author:
alexander
Message:

Adapted README.txt to the Markdown syntax instead of asciidoc

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • trunk/doc/README.txt

    r2092 r2096  
    8585 
    8686You can compile other programs from sources directly on the CD. All locations 
    87 on the CD can be written to (including '/usr'). 
     87on the CD can be written to (including /usr). 
    8888 
    8989VMWARE ISSUE 
    …… 
    9393VMware Workstation 5.x or earlier or VMware Server 1.0.x or earlier. This is 
    9494a known VMware bug. The solution is to upgrade to VMware Workstation 6.x, or 
    95 to choose 'BusLogic' as the virtual SCSI controller type instead of the 
    96 default 'LSI Logic'. 
     95to choose "BusLogic" as the virtual SCSI controller type instead of the 
     96default "LSI Logic". 
    9797 
    9898The same issue will be present on an LFS system built from this CD. 
    …… 
    105105background. If it is not correct to acquire the network settings via DHCP 
    106106in your location, or if you want to use dialup or GPRS connection, run the 
    107 'net-setup' command. 
     107"net-setup" command. 
    108108 
    109109If you don't want the CD to start dhcpcd on the detected network cards, 
    110 type 'linux nodhcp' at the boot loader prompt. This may be required for 
     110type "linux nodhcp" at the boot loader prompt. This may be required for 
    111111wireless connections that utilize WEP or WPA encryption. 
    112112 
    113113Users of wireless cards based on the Atheros chipset have to install the 
    114 proprietary 'madwifi' driver. The driver is provided in the precompiled form 
    115 in the '/drivers' directory (if you loaded the CD contents to RAM, you have to 
    116 mount the CD and look into '/media/cdrom/drivers' instead). To install it, 
     114proprietary "madwifi" driver. The driver is provided in the precompiled form 
     115in the /drivers directory (if you loaded the CD contents to RAM, you have to 
     116mount the CD and look into /media/cdrom/drivers instead). To install it, 
    117117run the following commands: 
    118118 
    119  cd /drivers 
    120  tar -C / -xf madwifi-x86-6.3-r2052-kernel-[kernel_version].tgz 
    121  tar -C / -xf madwifi-x86-6.3-r2052-tools.tgz 
    122  depmod -ae 
    123  modprobe ath_pci 
     119    cd /drivers 
     120    tar -C / -xf madwifi-x86-6.3-r2052-kernel-[kernel_version].tgz 
     121    tar -C / -xf madwifi-x86-6.3-r2052-tools.tgz 
     122    depmod -ae 
     123    modprobe ath_pci 
    124124 
    125125CONFIGURING X 
    …… 
    130130does not support 24-bit color depth, or if your monitor is not Plug-n-Play 
    131131compatible (in other words, does not tell its characteristics to Xorg via DDC). 
    132 In such cases, you have to edit the '/etc/X11/xorg.conf' file manually, using 
     132In such cases, you have to edit the /etc/X11/xorg.conf file manually, using 
    133133vim, joe or nano, as described below. 
    134134 
    135 In 'Section "Device"', specify the driver for your video card, e.g.: 
    136  
    137  Section "Device" 
    138        Identifier      "Generic Video Card" 
    139        Driver          "vesa" 
    140  EndSection 
    141  
    142 In 'Section "Monitor"', specify the allowed frequency ranges for your 
     135In Section "Device", specify the driver for your video card, e.g.: 
     136 
     137    Section "Device" 
     138        Identifier      "Generic Video Card" 
     139        Driver          "vesa" 
     140    EndSection 
     141 
     142In Section "Monitor", specify the allowed frequency ranges for your 
    143143monitor. If unsure, consult the manual that came with your monitor. If 
    144144such information is not there, but you know a working resolution and refresh 
    145 rate, run the 'gtf' command. E.g., if your monitor can handle 1280x1024@85Hz: 
    146  
    147  $ gtf 1280 1024 85 
     145rate, run the "gtf" command. E.g., if your monitor can handle 1280x1024@85Hz: 
     146 
     147    $ gtf 1280 1024 85 
    148148 
    149149NOTE: You must specify the refresh rate of 60 Hz for VGA-connected LCD monitors. 
    …… 
    151151Then look at the output: 
    152152 
    153  # 1280x1024 @ 85.00 Hz (GTF) hsync: 91.38 kHz; pclk: 159.36 MHz 
    154  Modeline "1280x1024_85.00"  159.36  1280 1376 1512 1744  1024 1025 1028 1075 -HSync +Vsync 
     153    # 1280x1024 @ 85.00 Hz (GTF) hsync: 91.38 kHz; pclk: 159.36 MHz 
     154    Modeline "1280x1024_85.00"  159.36  1280 1376 1512 1744  1024 1025 1028 1075 -HSync +Vsync 
    155155 
    156156Put the synchronization ranges that contain the printed values. For the above 
    …… 
    158158"Monitor" section: 
    159159 
    160  Section "Monitor" 
    161        Identifier     "Generic Monitor" 
    162        Option         "DPMS" 
    163        # Option       "NoDDC" # for broken monitors that 
    164                               # report max dot clock = 0 MHz 
    165        HorizSync      30-92   # because gtf said "hsync: 91.38 kHz" 
    166        VertRefresh    56-86   # because an 85 Hz mode has been requested 
    167        # the Modeline may also be pasted here 
    168        Option "PreferredMode" "1280x1024_85.00" # only for the "intel" driver 
    169  EndSection 
    170  
    171 In the 'Section "Screen"', change the 'DefaultDepth' and add the '"Modes"' 
    172 line to 'SubSection "Display"' with the proper color depth. If you added custom 
    173 Modelines, you have to specify them exactly as defined, i.e. '"1280x1024_85.00"' 
    174 in the example above. The built-in Modelines have names similar to '"1024x768"', 
     160    Section "Monitor" 
     161        Identifier    "Generic Monitor" 
     162        Option                "DPMS" 
     163        # Option      "NoDDC" # for broken monitors that 
     164                              # report max dot clock = 0 MHz 
     165        HorizSync     30-92   # because gtf said "hsync: 91.38 kHz" 
     166        VertRefresh   56-86   # because an 85 Hz mode has been requested 
     167        # the Modeline may also be pasted here 
     168        Option "PreferredMode" "1280x1024_85.00" # only for the "intel" driver 
     169    EndSection 
     170 
     171In the Section "Screen", change the DefaultDepth and add the "Modes" 
     172line to SubSection "Display" with the proper color depth. If you added custom 
     173Modelines, you have to specify them exactly as defined, i.e. "1280x1024_85.00" 
     174in the example above. The built-in Modelines have names similar to "1024x768", 
    175175without explicit specification of the refresh rate. 
    176176 
    177 When you are finished editing '/etc/X11/xorg.conf', run 'startx'. 
     177When you are finished editing /etc/X11/xorg.conf, run "startx". 
    178178 
    179179PROPRIETARY VIDEO DRIVERS 
    180180------------------------- 
    181181 
    182 The CD contains pre-built proprietary video drivers in the '/drivers' directory 
     182The CD contains pre-built proprietary video drivers in the /drivers directory 
    183183(if you loaded the CD contents to RAM, you have to mount the CD and look into 
    184 '/media/cdrom/drivers' instead). They are never selected by default by the 
     184/media/cdrom/drivers instead). They are never selected by default by the 
    185185autoconfiguration process. Here is how to enable them. 
    186186 
    187 NVIDIA 
    188 ~~~~~~ 
    189  
    190  cd /drivers 
    191  tar -C / -xf NVIDIA-Linux-[userspace_arch]-x86-6.3-r2052-glx.tgz 
    192  tar -C / -xf NVIDIA-Linux-[kernel_arch]-x86-6.3-r2052-kernel-[kernel_version].tgz 
    193  depmod -ae 
    194  ldconfig 
    195  vim /etc/X11/xorg.conf   # use the "nvidia" driver instead of "vesa" or "nv" 
    196  
    197 FGLRX 
    198 ~~~~~ 
    199  
    200  cd /drivers 
    201  tar -C / -xf fglrx-x710-x86-6.3-r2052-[userspace_arch]-1.tgz 
    202  tar -C / -xf fglrx-module-x86-6.3-r2052-[kernel_arch]-1_kernel_[kernel_version].tgz 
    203  depmod -ae 
    204  ldconfig 
    205  vim /etc/X11/xorg.conf   # use the "fglrx" driver instead of "vesa" or "ati" 
     187### NVIDIA ### 
     188 
     189    cd /drivers 
     190    tar -C / -xf NVIDIA-Linux-[userspace_arch]-x86-6.3-r2052-glx.tgz 
     191    tar -C / -xf NVIDIA-Linux-[kernel_arch]-x86-6.3-r2052-kernel-[kernel_version].tgz 
     192    depmod -ae 
     193    ldconfig 
     194    vim /etc/X11/xorg.conf   # use the "nvidia" driver instead of "vesa" or "nv" 
     195 
     196### FGLRX ### 
     197 
     198    cd /drivers 
     199    tar -C / -xf fglrx-x710-x86-6.3-r2052-[userspace_arch]-1.tgz 
     200    tar -C / -xf fglrx-module-x86-6.3-r2052-[kernel_arch]-1_kernel_[kernel_version].tgz 
     201    depmod -ae 
     202    ldconfig 
     203    vim /etc/X11/xorg.conf   # use the "fglrx" driver instead of "vesa" or "ati" 
    206204 
    207205CUSTOMIZING THE CD CONTENTS 
    …… 
    210208It is possible to burn a customized version of the official Linux From 
    211209Scratch LiveCD, with your own files added. To do that, follow the 
    212 instructions in the '/root/lfscd-remastering-howto.txt' file. 
     210instructions in the /root/lfscd-remastering-howto.txt file. 
    213211 
    214212AUTOSSHD 
    …… 
    218216you have to customize the CD. Create the following files: 
    219217 
    220 '/.autosshd':: 
     218/.autosshd: 
    221219    This is the file that indicates that the sshd daemon should be 
    222220    started automatically. It should be empty. 
    223221 
    224 '/root/.ssh/authorized_keys':: 
     222/root/.ssh/authorized_keys: 
    225223    Add your public key to that file in order to be able to log in. 
    226     Alternatively, modify '/etc/shadow'. 
    227  
    228 '/etc/shadow':: 
     224    Alternatively, modify /etc/shadow. 
     225 
     226/etc/shadow: 
    229227    Edit this file if you want to allow root to login using a password via 
    230228    ssh. It is more secure to use public key based authentication instead. 
    231229 
    232 '/etc/ssh/ssh_host_dsa_key', '/etc/ssh/ssh_host_rsa_key':: 
    233     Create those files as described in the 'ssh-keygen(1)' manual page. If you 
     230/etc/ssh/ssh_host_dsa_key, /etc/ssh/ssh_host_rsa_key: 
     231    Create those files as described in the *ssh-keygen(1)* manual page. If you 
    234232    do not do that, random host keys will be generated for you automatically 
    235233    during the boot process. This is less secure, because you cannot verify 
    236234    them. 
    237235 
    238 '/etc/sysconfig/network-devices/ifconfig.eth0':: 
     236/etc/sysconfig/network-devices/ifconfig.eth0: 
    239237    Configure a known static IP address there, as described in the LFS book, 
    240     section '7.12. Configuring the network Script'. 
     238    section "7.12. Configuring the network Script". 
    241239 
    242240INTERNATIONALIZATION 
    …… 
    245243It is possible to specify the locale using the bootloader prompt, like this: 
    246244 
    247  linux LANG=es_ES@euro 
     245    linux LANG=es_ES@euro 
    248246 
    249247The CD tries to guess the proper screen font and keymap based on this 
    …… 
    251249following parameters: 
    252250 
    253 KEYMAP:: 
     251KEYMAP: 
    254252  specifies the console keymap(s) to load (actually the arguments to 
    255   the 'loadkeys' program separated by the "+" sign), e.g: 'KEYMAP=es+euro1' 
    256  
    257 LEGACY_CHARSET:: 
     253  the "loadkeys" program separated by the "+" sign) 
     254 
     255Example: "KEYMAP=es+euro1" 
     256 
     257LEGACY_CHARSET: 
    258258  sometimes a ready-made UTF-8 keymap is not available and 
    259259  must be obtained by converting an existing keymap from this charset to UTF-8. 
    260   E.g.: 'LEGACY_CHARSET=iso-8859-15'. 
    261260  This parameter is not used in non-UTF-8 locales. 
    262261 
    263 FONT:: 
     262Example: "LEGACY_CHARSET=iso-8859-15". 
     263 
     264FONT: 
    264265  specifies the screen font to set (actually, the arguments to the 
    265   'setfont' program separated by the "+" sign), e.g: 
    266   'FONT=LatArCyrHeb-16+-m+8859-15' 
    267  
    268 XKEYMAP:: 
    269   the keymap to use with X window system, e.g.: 'XKEYMAP=us' 
     266  "setfont" program separated by the "+" sign). 
     267 
     268Example: "FONT=LatArCyrHeb-16+-m+8859-15" 
     269 
     270XKEYMAP: 
     271  the keymap to use with X window system 
     272 
     273Example: "XKEYMAP=us" 
    270274 
    271275Alternatively, these items can be configured interactively using dialog-based 
    272276interface if the locale is not specified on the boot prompt. 
    273277 
    274 For some locales (e.g. 'lv_LV.ISO-8859-13') there is no valid console keymap, 
     278For some locales (e.g. lv_LV.ISO-8859-13) there is no valid console keymap, 
    275279but there is a keymap for X. In this case, the only solution is to use X. 
    276280 
    277 While this CD configures the 'LANG' environment variable, console font and 
     281While this CD configures the "LANG" environment variable, console font and 
    278282keymap for you, it is your responsibility to configure other locale-dependent 
    279 parameters manually. You have to explicitly specify the 'iocharset' and 
    280 'codepage' options when mounting filesystems with Windows origin 
    281 (e.g., 'vfat' and 'isofs'). 
     283parameters manually. You have to explicitly specify the "iocharset" and 
     284"codepage" options when mounting filesystems with Windows origin 
     285(e.g., vfat and isofs). 
    282286 
    283287The CD contains TrueType fonts that cover the orthography of most of European 
    …… 
    290294minimum resolution: 
    291295 
    292 .-------.--------- 
    293 Size    Resolution 
    294 ------------------ 
    295 15"     1024x768 
    296 17"     1024x768 
    297 19"     1280x1024 
    298 20"     1280x1024 
    299 ------------------ 
     296    15"  =>    1024x768 
     297    17"  =>    1024x768 
     298    19"  =>   1280x1024 
     299    20"  =>   1280x1024 
    300300 
    301301If your monitor cannot handle such resolution, edit the 
    302 '/etc/X11/xinit/xserverrc' file with vim, nano or joe, and add the '-dpi 94' 
     302/etc/X11/xinit/xserverrc file with vim, nano or joe, and add the "-dpi 94" 
    303303parameter to the X server command line there. 
    304304 
    …… 
    306306----------------------- 
    307307 
    308 The LiveCD includes the 'brltty' program that allows a blind person to read 
     308The LiveCD includes the "brltty" program that allows a blind person to read 
    309309the contents of the Linux text console on a Braille display. In order to 
    310310activate it, insert the CD into the drive, reboot the computer. Some BIOSes 
    …… 
    314314upon startup), type: 
    315315 
    316    linux brltty=eu,ttyS0 
     316    linux brltty=eu,ttyS0 
    317317 
    318318[NOTE] 
    319319This example assumes that the EuroBraille device is connected to the 
    320 first serial port. For other device types, the 'brltty' parameter will 
     320first serial port. For other device types, the "brltty" parameter will 
    321321be different. 
    322322 
    323323[NOTE] 
    324 In some locales, 'brltty' displays incorrect Braille patterns. This is 
     324In some locales, "brltty" displays incorrect Braille patterns. This is 
    325325related to the fact that Braille tables in brltty are indexed with 
    326326encoding-dependent bytes representing the character. Such representation 
    327327becomes invalid when another encoding for the same language is used. 
    328 E.g., that is why the 'ru' table (designed for the KOI8-R encoding) produces 
    329 wrong result in the 'ru_RU.CP1251' locale. 
    330  
    331 Known non-working cases 
    332 ~~~~~~~~~~~~~~~~~~~~~~~ 
    333  
    334  * All CP1251-based locales (no CP1251 Braille table in 'brltty') 
     328E.g., that is why the "ru" table (designed for the KOI8-R encoding) produces 
     329wrong result in the ru_RU.CP1251 locale. 
     330 
     331### Known non-working cases ### 
     332 
     333 * All CP1251-based locales (no CP1251 Braille table in "brltty") 
    335334 
    336335 * All UTF-8 locales (kernel deficiency) 
    337336 
    338337 * zh_TW (configuration instructions available in Chinese only). If you use 
    339    this locale, please send mail to 
    340    mailto:livecd@linuxfromscratch.org[the LiveCD development list] 
     338   this locale, please send mail to <livecd@linuxfromscratch.org> 
    341339   and help us add support for it. 
    342340 
    …… 
    346344the en_US locale, thus avoiding the use of non-ASCII characters. If you know how 
    347345to fix this problem for your locale, mail this information to 
    348 mailto:livecd@linuxfromscratch.org[the LiveCD development list]. 
     346<livecd@linuxfromscratch.org>. 
    349347 
    350348RESUMING THE BUILD 
    351349------------------ 
    352350 
    353 There is a hint: 
    354  
    355 http://www.linuxfromscratch.org/hints/downloads/files/stages-stop-and-resume.txt[How to resume your work after a break at different LFS stages] 
     351There is a hint "How to resume your work after a break at different 
     352-LFS stages" available at: 
     353 
     354<http://www.linuxfromscratch.org/hints/downloads/files/stages-stop-and-resume.txt> 
    356355 
    357356Instructions from there should work on this CD, however, there is a simpler 
    358 method ('hibernation') described below. 
     357method ("hibernation") described below. 
    359358 
    360359Make sure you have (or are planning to create) a swap partition not used 
    361360by other Linux systems installed on your hard drive. The text below assumes 
    362 that '/dev/hda2' is your (existing or planned) swap partition. 
    363  
    364 Pass 'resume=/dev/hda2' as one of the kernel arguments when booting this CD. 
     361that /dev/hda2 is your (existing or planned) swap partition. 
     362 
     363Pass "resume=/dev/hda2" as one of the kernel arguments when booting this CD. 
    365364I.e., the complete boot line may look as: 
    366365   
    367    linux LANG=ru_RU.UTF-8 TZ=Asia/Yekaterinburg resume=/dev/hda2 
     366    linux LANG=ru_RU.UTF-8 TZ=Asia/Yekaterinburg resume=/dev/hda2 
    368367 
    369368Alternatively, once the system is running, you can activate hibernation by 
    …… 
    371370such: 
    372371 
    373    # ls -l /dev/hda2 
    374    brw-rw---- 1 root disk 3, 2 2006-07-10 17:51 /dev/hda2 
    375    # echo 3:2 >/sys/power/resume 
     372    # ls -l /dev/hda2 
     373    brw-rw---- 1 root disk 3, 2 2006-07-10 17:51 /dev/hda2 
     374    # echo 3:2 >/sys/power/resume 
    376375 
    377376At this point, the system is up and running. If you do not already have a 
    …… 
    381380If you use the X window system, take the following into account: 
    382381 
    383    * Users of old S3 video cards should uncomment the 'EnableVbetool' line 
    384      in the '/etc/hibernate/common.conf' file. 
    385  
    386    * Hibernation is incompatible with the proprietary 'nvidia' driver. 
     382   * Users of old S3 video cards should uncomment the "EnableVbetool" line 
     383     in the /etc/hibernate/common.conf file. 
     384 
     385   * Hibernation is incompatible with the proprietary "nvidia" driver. 
    387386 
    388387Follow the book as your time permits. 
    389388 
    390 When your time runs out, execute the 'hibernate' command as root. It is not 
     389When your time runs out, execute the "hibernate" command as root. It is not 
    391390necessary to stop the compilation, but running this command during a 
    392391testsuite may lead to failures that would not occur otherwise. 
    …… 
    399398 
    400399On some systems, hibernation refuses to work due to a broken ACPI 
    401 implementation, with the following message in 'dmesg | tail'  output: 
    402  
    403    acpi_pm_prepare does not support 4 
     400implementation, with the following message in "dmesg | tail"  output: 
     401 
     402    acpi_pm_prepare does not support 4 
    404403 
    405404Possible solutions: 
    406405 
    407    a. run the following command before hibernating the computer: 
    408  
    409        echo shutdown >/sys/power/disk 
    410  
    411    b. disable ACPI completely by adding 'acpi=off' to the kernel arguments. 
     406   1. run the following command before hibernating the computer: 
     407 
     408        echo shutdown >/sys/power/disk 
     409 
     410   2. disable ACPI completely by adding "acpi=off" to the kernel arguments. 
    412411 
    413412The computer will save its state to your swap partition and power down. 
    …… 
    415414 
    416415When you are ready to resume the build, boot this CD again and pass exactly 
    417 the same 'vga=...' and 'resume=...' arguments that you used earlier. 
     416the same "vga=..." and "resume=..." arguments that you used earlier. 
    418417 
    419418The computer will load its state from the swap partition and behave as if 
    …… 
    424423or on software RAID. In this case, instead of passing the 'resume=...' argument, 
    425424you should boot the CD as usual and make actions needed for the kernel to see 
    426 the swap device (for LVM, that is 'vgchange -ay'). After doing that, note 
     425the swap device (for LVM, that is "vgchange -ay"). After doing that, note 
    427426the major and minor device number for that device (assigning persistent numbers 
    428 is highly recommended), and echo them to '/sys/power/resume'. E.g., for LVM: 
    429  
    430  # ls -lL /dev/myvg/swap 
    431  brw------- 1 root root 254, 3 2006-07-10 17:51 /dev/myvg/swap 
    432  # echo 254:3 >/sys/power/resume 
     427is highly recommended), and echo them to /sys/power/resume. E.g., for LVM: 
     428 
     429    # ls -lL /dev/myvg/swap 
     430    brw------- 1 root root 254, 3 2006-07-10 17:51 /dev/myvg/swap 
     431    # echo 254:3 >/sys/power/resume 
    433432 
    434433In the case of the first boot, this will store the device numbers to be used 
    435 for hibernation. On the second boot (i.e., after hibernating), this 'echo' 
     434for hibernation. On the second boot (i.e., after hibernating), this "echo" 
    436435command will restore the computer state from the swap device. 
    437436 
    …… 
    439438-------------------- 
    440439 
    441 This CD comes with the 'jhalfs' tool that allows extracting commands from the 
     440This CD comes with the "jhalfs" tool that allows extracting commands from the 
    442441XML version of the LFS or CLFS book into Makefiles and shell scripts. You can 
    443 find the jhalfs installation in the home directory of the 'jhalfs' user, and the 
    444 XML LFS book is in '/usr/share/LFS-BOOK-6.3-XML'. In order to use 'jhalfs', 
     442find the jhalfs installation in the home directory of the "jhalfs" user, and the 
     443XML LFS book is in /usr/share/LFS-BOOK-6.3-XML. In order to use jhalfs, 
    445444you have to: 
    446445 
    447446 * create a directory for your future LFS system and mount a partition there 
    448447 
    449  * change the ownership of that directory to the 'jhalfs' user 
    450  
    451  * run 'su - jhalfs' in order to become that user 
    452  
    453  * as user 'jhalfs', follow the instructions in the 
    454  '/home/jhalfs/jhalfs-<version>/README' file 
    455  
    456 Note that this user already has the required root access (via 'sudo') to 
     448 * change the ownership of that directory to the "jhalfs" user 
     449 
     450 * run "su - jhalfs" in order to become that user 
     451 
     452 * as user "jhalfs", follow the instructions in the jhalfs README file 
     453 
     454Note that this user already has the required root access (via "sudo") to 
    457455complete the build. 
    458456 
    …… 
    464462purposes (e.g., for watching a DVD while compiling LFS). 
    465463 
    466 To load the CD contents to RAM, type 'linux toram' at the boot prompt. 
     464To load the CD contents to RAM, type "linux toram" at the boot prompt. 
    467465 
    468466The minimum required amount of RAM is 512 MB. If you have less than 768 MB of 
    …… 
    471469NOTE: in order to save RAM, sources and proprietary drivers are not loaded 
    472470there. In order to access them, please mount this CD and look into 
    473 '/media/cdrom/sources' and '/media/cdrom/drivers'. 
     471/media/cdrom/sources and /media/cdrom/drivers. 
    474472 
    475473BOOTING FROM ISO IMAGE 
    …… 
    480478Store the ISO image of this CD as a file on a partition formatted with 
    481479one of the following filesystems: 
    482 'vfat', 'ntfs', 'ext2', 'ext3', 'ext4', 'jfs', 'reiserfs', 'reiser4', 'xfs' 
    483  
    484 Copy the 'boot/isolinux/{linux,initramfs_data.cpio.gz}' files from the CD 
     480vfat, ntfs, ext2, ext3, ext4, jfs, reiserfs, reiser4, xfs 
     481 
     482Copy the boot/isolinux/{linux,initramfs_data.cpio.gz} files from the CD 
    485483to your hard disk 
    486484 
    487 Configure the boot loader to load 'linux' as a kernel image and 
    488 'initramfs_data.cpio.gz' as an initrd. The following parameters have to 
     485Configure the boot loader to load "linux" as a kernel image and 
     486"initramfs_data.cpio.gz" as an initrd. The following parameters have to 
    489487be passed to the kernel: 
    490488 
    491    rw root=iso:/dev/XXX:/path/to/lfslivecd.iso rootfstype=fs_type 
    492  
    493 where '/dev/XXX' is a partition where you stored the LiveCD image, and 
    494 'fs_type' is the type of the filesystem on that partition. You may 
    495 also want to add 'rootflags=...' option if mounting this partition requires 
     489    rw root=iso:/dev/XXX:/path/to/lfslivecd.iso rootfstype=fs_type 
     490 
     491where /dev/XXX is a partition where you stored the LiveCD image, and 
     492fs_type is the type of the filesystem on that partition. You may 
     493also want to add "rootflags=..." option if mounting this partition requires 
    496494special flags. 
    497495 
    498496If there is only Windows on the target computer, please use grub4dos as a boot 
    499 loader. It is available from 
    500 http://sourceforge.net/projects/grub4dos[grub4dos project page]. 
     497loader. It is available from <http://sourceforge.net/projects/grub4dos>. 
    501498 
    502499MAKING A BOOTABLE USB DRIVE 
    …… 
    508505computer: 
    509506 
    510  * Use the persistent symlink such as '/dev/disk/by-uuid/890C-F46A' to identify 
     507 * Use the persistent symlink such as "/dev/disk/by-uuid/890C-F46A" to identify 
    511508   the target partition. 
    512509 
    513  * Add 'rootdelay=20' to the kernel arguments. 
     510 * Add "rootdelay=20" to the kernel arguments. 
    514511 
    515512THANKS