Changeset 2097
- Timestamp:
- 10/07/07 08:17:25 (1 year ago)
- Files:
-
- branches/minimal/doc/README.txt (modified) (19 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
branches/minimal/doc/README.txt
r2093 r2097 77 77 78 78 You can compile other programs from sources directly on the CD. All locations 79 on the CD can be written to (including '/usr').79 on the CD can be written to (including /usr). 80 80 81 81 VMWARE ISSUE … … 85 85 VMware Workstation 5.x or earlier or VMware Server 1.0.x or earlier. This is 86 86 a known VMware bug. The solution is to upgrade to VMware Workstation 6.x, or 87 to choose 'BusLogic'as the virtual SCSI controller type instead of the88 default 'LSI Logic'.87 to choose "BusLogic" as the virtual SCSI controller type instead of the 88 default "LSI Logic". 89 89 90 90 The same issue will be present on an LFS system built from this CD. … … 97 97 background. If it is not correct to acquire the network settings via DHCP 98 98 in your location, or if you want to use dialup or GPRS connection, run the 99 'net-setup'command.99 "net-setup" command. 100 100 101 101 If you don't want the CD to start dhcpcd on the detected network cards, 102 type 'linux nodhcp'at the boot loader prompt. This may be required for102 type "linux nodhcp" at the boot loader prompt. This may be required for 103 103 wireless connections that utilize WEP or WPA encryption. 104 104 105 105 Users of wireless cards based on the Atheros chipset have to install the 106 proprietary 'madwifi'driver. The driver is provided in the precompiled form107 in the '/drivers'directory (if you loaded the CD contents to RAM, you have to108 mount the CD and look into '/media/cdrom/drivers'instead). To install it,106 proprietary "madwifi" driver. The driver is provided in the precompiled form 107 in the /drivers directory (if you loaded the CD contents to RAM, you have to 108 mount the CD and look into /media/cdrom/drivers instead). To install it, 109 109 run the following commands: 110 110 111 cd /drivers112 tar -C / -xf madwifi-x86-6.3-r2052-kernel-[kernel_version].tgz113 tar -C / -xf madwifi-x86-6.3-r2052-tools.tgz114 depmod -ae115 modprobe ath_pci111 cd /drivers 112 tar -C / -xf madwifi-x86-6.3-r2052-kernel-[kernel_version].tgz 113 tar -C / -xf madwifi-x86-6.3-r2052-tools.tgz 114 depmod -ae 115 modprobe ath_pci 116 116 117 117 CUSTOMIZING THE CD CONTENTS … … 120 120 It is possible to burn a customized version of the official Linux From 121 121 Scratch LiveCD, with your own files added. To do that, follow the 122 instructions in the '/root/lfscd-remastering-howto.txt'file.122 instructions in the /root/lfscd-remastering-howto.txt file. 123 123 124 124 AUTOSSHD … … 128 128 you have to customize the CD. Create the following files: 129 129 130 '/.autosshd'::130 /.autosshd: 131 131 This is the file that indicates that the sshd daemon should be 132 132 started automatically. It should be empty. 133 133 134 '/root/.ssh/authorized_keys'::134 /root/.ssh/authorized_keys: 135 135 Add your public key to that file in order to be able to log in. 136 Alternatively, modify '/etc/shadow'.137 138 '/etc/shadow'::136 Alternatively, modify /etc/shadow. 137 138 /etc/shadow: 139 139 Edit this file if you want to allow root to login using a password via 140 140 ssh. It is more secure to use public key based authentication instead. 141 141 142 '/etc/ssh/ssh_host_dsa_key', '/etc/ssh/ssh_host_rsa_key'::143 Create those files as described in the 'ssh-keygen(1)'manual page. If you142 /etc/ssh/ssh_host_dsa_key, /etc/ssh/ssh_host_rsa_key: 143 Create those files as described in the *ssh-keygen(1)* manual page. If you 144 144 do not do that, random host keys will be generated for you automatically 145 145 during the boot process. This is less secure, because you cannot verify 146 146 them. 147 147 148 '/etc/sysconfig/network-devices/ifconfig.eth0'::148 /etc/sysconfig/network-devices/ifconfig.eth0: 149 149 Configure a known static IP address there, as described in the LFS book, 150 section '7.12. Configuring the network Script'.150 section "7.12. Configuring the network Script". 151 151 152 152 INTERNATIONALIZATION … … 155 155 It is possible to specify the locale using the bootloader prompt, like this: 156 156 157 linux LANG=es_ES@euro157 linux LANG=es_ES@euro 158 158 159 159 The CD tries to guess the proper screen font and keymap based on this … … 161 161 following parameters: 162 162 163 KEYMAP: :163 KEYMAP: 164 164 specifies the console keymap(s) to load (actually the arguments to 165 the 'loadkeys' program separated by the "+" sign), e.g: 'KEYMAP=es+euro1' 166 167 LEGACY_CHARSET:: 165 the "loadkeys" program separated by the "+" sign) 166 167 Example: "KEYMAP=es+euro1" 168 169 LEGACY_CHARSET: 168 170 sometimes a ready-made UTF-8 keymap is not available and 169 171 must be obtained by converting an existing keymap from this charset to UTF-8. 170 E.g.: 'LEGACY_CHARSET=iso-8859-15'.171 172 This parameter is not used in non-UTF-8 locales. 172 173 173 FONT:: 174 Example: "LEGACY_CHARSET=iso-8859-15". 175 176 FONT: 174 177 specifies the screen font to set (actually, the arguments to the 175 'setfont' program separated by the "+" sign), e.g: 176 'FONT=LatArCyrHeb-16+-m+8859-15' 178 "setfont" program separated by the "+" sign). 179 180 Example: "FONT=LatArCyrHeb-16+-m+8859-15" 177 181 178 182 Alternatively, these items can be configured interactively using dialog-based 179 183 interface if the locale is not specified on the boot prompt. 180 184 181 For some locales (e.g. 'lv_LV.ISO-8859-13') there is no valid console keymap,185 For some locales (e.g. lv_LV.ISO-8859-13) there is no valid console keymap, 182 186 but there is a keymap for X. In this case, the only solution is to use a CD 183 187 with X. 184 188 185 While this CD configures the 'LANG'environment variable, console font and189 While this CD configures the "LANG" environment variable, console font and 186 190 keymap for you, it is your responsibility to configure other locale-dependent 187 parameters manually. You have to explicitly specify the 'iocharset'and188 'codepage'options when mounting filesystems with Windows origin189 (e.g., 'vfat' and 'isofs').191 parameters manually. You have to explicitly specify the "iocharset" and 192 "codepage" options when mounting filesystems with Windows origin 193 (e.g., vfat and isofs). 190 194 191 195 BRAILLE DISPLAY SUPPORT 192 196 ----------------------- 193 197 194 The LiveCD includes the 'brltty'program that allows a blind person to read198 The LiveCD includes the "brltty" program that allows a blind person to read 195 199 the contents of the Linux text console on a Braille display. In order to 196 200 activate it, insert the CD into the drive, reboot the computer. Some BIOSes … … 200 204 upon startup), type: 201 205 202 linux brltty=eu,ttyS0206 linux brltty=eu,ttyS0 203 207 204 208 [NOTE] 205 209 This example assumes that the EuroBraille device is connected to the 206 first serial port. For other device types, the 'brltty'parameter will210 first serial port. For other device types, the "brltty" parameter will 207 211 be different. 208 212 209 213 [NOTE] 210 In some locales, 'brltty'displays incorrect Braille patterns. This is214 In some locales, "brltty" displays incorrect Braille patterns. This is 211 215 related to the fact that Braille tables in brltty are indexed with 212 216 encoding-dependent bytes representing the character. Such representation 213 217 becomes invalid when another encoding for the same language is used. 214 E.g., that is why the 'ru' table (designed for the KOI8-R encoding) produces 215 wrong result in the 'ru_RU.CP1251' locale. 216 217 Known non-working cases 218 ~~~~~~~~~~~~~~~~~~~~~~~ 219 220 * All CP1251-based locales (no CP1251 Braille table in 'brltty') 218 E.g., that is why the "ru" table (designed for the KOI8-R encoding) produces 219 wrong result in the ru_RU.CP1251 locale. 220 221 ### Known non-working cases ### 222 223 * All CP1251-based locales (no CP1251 Braille table in "brltty") 221 224 222 225 * All UTF-8 locales (kernel deficiency) 223 226 224 227 * zh_TW (configuration instructions available in Chinese only). If you use 225 this locale, please send mail to 226 mailto:livecd@linuxfromscratch.org[the LiveCD development list] 228 this locale, please send mail to <livecd@linuxfromscratch.org> 227 229 and help us add support for it. 228 230 … … 232 234 the en_US locale, thus avoiding the use of non-ASCII characters. If you know how 233 235 to fix this problem for your locale, mail this information to 234 mailto:livecd@linuxfromscratch.org[the LiveCD development list].236 <livecd@linuxfromscratch.org>. 235 237 236 238 RESUMING THE BUILD 237 239 ------------------ 238 240 239 There is a hint: 240 241 http://www.linuxfromscratch.org/hints/downloads/files/stages-stop-and-resume.txt[How to resume your work after a break at different LFS stages] 241 There is a hint "How to resume your work after a break at different 242 -LFS stages" available at: 243 244 <http://www.linuxfromscratch.org/hints/downloads/files/stages-stop-and-resume.txt> 242 245 243 246 Instructions from there should work on this CD, however, there is a simpler 244 method ( 'hibernation') described below.247 method ("hibernation") described below. 245 248 246 249 Make sure you have (or are planning to create) a swap partition not used 247 250 by other Linux systems installed on your hard drive. The text below assumes 248 that '/dev/hda2'is your (existing or planned) swap partition.249 250 Pass 'resume=/dev/hda2'as one of the kernel arguments when booting this CD.251 that /dev/hda2 is your (existing or planned) swap partition. 252 253 Pass "resume=/dev/hda2" as one of the kernel arguments when booting this CD. 251 254 I.e., the complete boot line may look as: 252 255 253 linux LANG=ru_RU.UTF-8 TZ=Asia/Yekaterinburg resume=/dev/hda2256 linux LANG=ru_RU.UTF-8 TZ=Asia/Yekaterinburg resume=/dev/hda2 254 257 255 258 Alternatively, once the system is running, you can activate hibernation by … … 257 260 such: 258 261 259 # ls -l /dev/hda2260 brw-rw---- 1 root disk 3, 2 2006-07-10 17:51 /dev/hda2261 # echo 3:2 >/sys/power/resume262 # ls -l /dev/hda2 263 brw-rw---- 1 root disk 3, 2 2006-07-10 17:51 /dev/hda2 264 # echo 3:2 >/sys/power/resume 262 265 263 266 At this point, the system is up and running. If you do not already have a … … 267 270 Follow the book as your time permits. 268 271 269 When your time runs out, execute the 'hibernate'command as root. It is not272 When your time runs out, execute the "hibernate" command as root. It is not 270 273 necessary to stop the compilation, but running this command during a 271 274 testsuite may lead to failures that would not occur otherwise. … … 278 281 279 282 On some systems, hibernation refuses to work due to a broken ACPI 280 implementation, with the following message in 'dmesg | tail'output:281 282 acpi_pm_prepare does not support 4283 implementation, with the following message in "dmesg | tail" output: 284 285 acpi_pm_prepare does not support 4 283 286 284 287 Possible solutions: 285 288 286 a. run the following command before hibernating the computer:287 288 echo shutdown >/sys/power/disk289 290 b. disable ACPI completely by adding 'acpi=off'to the kernel arguments.289 1. run the following command before hibernating the computer: 290 291 echo shutdown >/sys/power/disk 292 293 2. disable ACPI completely by adding "acpi=off" to the kernel arguments. 291 294 292 295 The computer will save its state to your swap partition and power down. … … 294 297 295 298 When you are ready to resume the build, boot this CD again and pass exactly 296 the same 'vga=...' and 'resume=...'arguments that you used earlier.299 the same "vga=..." and "resume=..." arguments that you used earlier. 297 300 298 301 The computer will load its state from the swap partition and behave as if … … 303 306 or on software RAID. In this case, instead of passing the 'resume=...' argument, 304 307 you should boot the CD as usual and make actions needed for the kernel to see 305 the swap device (for LVM, that is 'vgchange -ay'). After doing that, note308 the swap device (for LVM, that is "vgchange -ay"). After doing that, note 306 309 the major and minor device number for that device (assigning persistent numbers 307 is highly recommended), and echo them to '/sys/power/resume'. E.g., for LVM:308 309 # ls -lL /dev/myvg/swap310 brw------- 1 root root 254, 3 2006-07-10 17:51 /dev/myvg/swap311 # echo 254:3 >/sys/power/resume310 is highly recommended), and echo them to /sys/power/resume. E.g., for LVM: 311 312 # ls -lL /dev/myvg/swap 313 brw------- 1 root root 254, 3 2006-07-10 17:51 /dev/myvg/swap 314 # echo 254:3 >/sys/power/resume 312 315 313 316 In the case of the first boot, this will store the device numbers to be used 314 for hibernation. On the second boot (i.e., after hibernating), this 'echo'317 for hibernation. On the second boot (i.e., after hibernating), this "echo" 315 318 command will restore the computer state from the swap device. 316 319 … … 318 321 -------------------- 319 322 320 This CD comes with the 'jhalfs'tool that allows extracting commands from the323 This CD comes with the "jhalfs" tool that allows extracting commands from the 321 324 XML version of the LFS or CLFS book into Makefiles and shell scripts. You can 322 find the jhalfs installation in the home directory of the 'jhalfs'user, and the323 XML LFS book is in '/usr/share/LFS-BOOK-6.3-XML'. In order to use 'jhalfs',325 find the jhalfs installation in the home directory of the "jhalfs" user, and the 326 XML LFS book is in /usr/share/LFS-BOOK-6.3-XML. In order to use jhalfs, 324 327 you have to: 325 328 326 329 * create a directory for your future LFS system and mount a partition there 327 330 328 * change the ownership of that directory to the 'jhalfs' user 329 330 * run 'su - jhalfs' in order to become that user 331 332 * as user 'jhalfs', follow the instructions in the 333 '/home/jhalfs/jhalfs-<version>/README' file 334 335 Note that this user already has the required root access (via 'sudo') to 331 * change the ownership of that directory to the "jhalfs" user 332 333 * run "su - jhalfs" in order to become that user 334 335 * as user "jhalfs", follow the instructions in the jhalfs README file 336 337 Note that this user already has the required root access (via "sudo") to 336 338 complete the build. 337 339 … … 343 345 purposes (e.g., for watching a DVD while compiling LFS). 344 346 345 To load the CD contents to RAM, type 'linux toram'at the boot prompt.347 To load the CD contents to RAM, type "linux toram" at the boot prompt. 346 348 347 349 The minimum required amount of RAM is 512 MB. If you have less than 768 MB of … … 350 352 NOTE: in order to save RAM, sources and proprietary drivers are not loaded 351 353 there. In order to access them, please mount this CD and look into 352 '/media/cdrom/sources' and '/media/cdrom/drivers'.354 /media/cdrom/sources and /media/cdrom/drivers. 353 355 354 356 BOOTING FROM ISO IMAGE … … 359 361 Store the ISO image of this CD as a file on a partition formatted with 360 362 one of the following filesystems: 361 'vfat', 'ntfs', 'ext2', 'ext3', 'ext4', 'jfs', 'reiserfs', 'reiser4', 'xfs' 362 363 Copy the 'boot/isolinux/{linux,initramfs_data.cpio.gz}'files from the CD363 vfat, ntfs, ext2, ext3, ext4, jfs, reiserfs, reiser4, xfs 364 365 Copy the boot/isolinux/{linux,initramfs_data.cpio.gz} files from the CD 364 366 to your hard disk 365 367 366 Configure the boot loader to load 'linux'as a kernel image and367 'initramfs_data.cpio.gz'as an initrd. The following parameters have to368 Configure the boot loader to load "linux" as a kernel image and 369 "initramfs_data.cpio.gz" as an initrd. The following parameters have to 368 370 be passed to the kernel: 369 371 370 rw root=iso:/dev/XXX:/path/to/lfslivecd.iso rootfstype=fs_type371 372 where '/dev/XXX'is a partition where you stored the LiveCD image, and373 'fs_type'is the type of the filesystem on that partition. You may374 also want to add 'rootflags=...'option if mounting this partition requires372 rw root=iso:/dev/XXX:/path/to/lfslivecd.iso rootfstype=fs_type 373 374 where /dev/XXX is a partition where you stored the LiveCD image, and 375 fs_type is the type of the filesystem on that partition. You may 376 also want to add "rootflags=..." option if mounting this partition requires 375 377 special flags. 376 378 377 379 If there is only Windows on the target computer, please use grub4dos as a boot 378 loader. It is available from 379 http://sourceforge.net/projects/grub4dos[grub4dos project page]. 380 loader. It is available from <http://sourceforge.net/projects/grub4dos>. 380 381 381 382 MAKING A BOOTABLE USB DRIVE … … 387 388 computer: 388 389 389 * Use the persistent symlink such as '/dev/disk/by-uuid/890C-F46A'to identify390 * Use the persistent symlink such as "/dev/disk/by-uuid/890C-F46A" to identify 390 391 the target partition. 391 392 392 * Add 'rootdelay=20'to the kernel arguments.393 * Add "rootdelay=20" to the kernel arguments. 393 394 394 395 THANKS
