From e0a04e86b21514726e2ed072700a2e99022010a6 Mon Sep 17 00:00:00 2001 From: Manuel Canales Esparcia Date: Mon, 20 Dec 2004 18:08:34 +0000 Subject: Removed text in chapter 08. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4436 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter08/fstab.xml | 35 ----------- chapter08/grub.xml | 45 +------------- chapter08/introduction.xml | 5 +- chapter08/kernel.xml | 143 +-------------------------------------------- 4 files changed, 3 insertions(+), 225 deletions(-) (limited to 'chapter08') diff --git a/chapter08/fstab.xml b/chapter08/fstab.xml index c5cc0123b..50cfd8315 100644 --- a/chapter08/fstab.xml +++ b/chapter08/fstab.xml @@ -9,11 +9,6 @@ /etc/fstab -The /etc/fstab file is used by some programs to -determine where file systems are to be mounted by default, which -must be checked and in which order. Create a new file systems table like -this: - cat > /etc/fstab << "EOF" # Begin /etc/fstab @@ -28,34 +23,4 @@ shm /dev/shm tmpfs defaults 0 0 # End /etc/fstab EOF -Of course, replace [xxx], [yyy] -and [fff] with the values appropriate for your system -- -for example hda2, hda5 and -reiserfs. For all the details on the six fields in this -table, see man 5 fstab. - -When using a reiserfs partition, the 1 1 at the -end of the line should be replaced with 0 0, as such a -partition does not need to be dumped or checked - -The /dev/shm mount point for -tmpfs is included to -allow enabling POSIX shared memory. Your kernel must have the required support -built into it for this to work -- more about this in the next section. Please -note that currently very little software actually uses POSIX shared memory. -Therefore you can consider the /dev/shm mount point -optional. For more information, see -Documentation/filesystems/tmpfs.txt in the kernel source -tree. - -There are other lines which you may consider adding to your -fstab file. One example is a line to use if you intend to -use USB devices: - - usbfs /proc/bus/usb usbfs devgid=14,devmode=0660 0 0 - -This option will of course only work if you have the -"Support for Host-side USB" and "USB device filesystem" -compiled into your kernel (not as a module). - diff --git a/chapter08/grub.xml b/chapter08/grub.xml index 57293c359..98a339698 100644 --- a/chapter08/grub.xml +++ b/chapter08/grub.xml @@ -11,23 +11,7 @@ Grub configuring -Your shiny new LFS system is almost complete. One of the last things to -do is ensure you can boot it. The instructions below apply only to computers of -IA-32 architecture, meaning mainstream PCs. Information on boot -loading for other architectures should be available in the usual -resource-specific locations for those architectures. - -Boot loading can be a complex area. First, a few cautionary words. You -really should be familiar with your current boot loader and any other -operating systems present on your hard drive(s) that you might wish to keep -bootable. Please make sure that you have an emergency boot disk ready, so that -you can rescue your computer if, by any chance, your computer becomes unusable -(un-bootable). - -Earlier, we compiled and installed the Grub boot loader software in -preparation for this step. The procedure involves writing some special Grub -files to specific locations on the hard drive. Before we get to that, we -highly recommend that you create a Grub boot floppy diskette just in case. +We highly recommend that you create a Grub boot floppy diskette just in case. Insert a blank floppy diskette and run the following commands: dd if=/boot/grub/stage1 of=/dev/fd0 bs=512 count=1 @@ -38,34 +22,11 @@ dd if=/boot/grub/stage2 of=/dev/fd0 bs=512 seek=1 grub -Grub uses its own naming structure for drives and partitions, in the form -of (hdn,m), where n is the hard drive number, and -m the partition number, both starting from zero. This -means, for instance, that partition hda1 is (hd0,0) to -Grub, and hdb2 is (hd1,1). In contrast to Linux, Grub -doesn't consider CD-ROM drives to be hard drives, so if you have a CD on -hdb, for example, and a second hard drive on -hdc, that second hard drive would still be (hd1). - -Using the above information, determine the appropriate designator for -your root partition (or boot partition, if you use a separate one). For the -following example, we'll assume your root (or separate boot) partition is -hda4. - First, tell Grub where to search for its stage{1,2} files -- you can use the Tab key everywhere to make Grub show the alternatives: root (hd0,3) - -The following command will overwrite your current boot loader. -Don't run the command if this is not what you want. For example, you may be -using a third party boot manager to manage your MBR (Master Boot Record). In -this scenario, it would probably make more sense to install Grub into the -boot sector of the LFS partition, in which case this next command -would become: setup (hd0,3). - - Tell Grub to install itself into the MBR (Master Boot Record) of hda: @@ -116,10 +77,6 @@ rootnoverify (hd0,0) chainloader +1 EOF -If info grub doesn't tell you all you want to -know, you can find more information regarding Grub on its website, located at: -. - The FHS stipulates that Grub's menu.lst file should be symlinked to /etc/grub/menu.lst. To satisfy this requirement, issue the following command: diff --git a/chapter08/introduction.xml b/chapter08/introduction.xml index a879c4a24..b55766f4c 100644 --- a/chapter08/introduction.xml +++ b/chapter08/introduction.xml @@ -7,9 +7,6 @@ Introduction -This chapter will make LFS bootable. This chapter deals with creating a -fstab file, building a -kernel for the new LFS system and installing the Grub bootloader -so that the LFS system can be selected for booting at startup. +See testing diff --git a/chapter08/kernel.xml b/chapter08/kernel.xml index d600342a8..1d41e21b7 100644 --- a/chapter08/kernel.xml +++ b/chapter08/kernel.xml @@ -10,7 +10,6 @@ Linux -<para>The Linux package contains the kernel and the header files.</para> <segmentedlist> <segtitle>&buildtime;</segtitle> @@ -19,30 +18,15 @@ <seg>All default options: 181 MB</seg></seglistitem> </segmentedlist> -<segmentedlist> -<segtitle>Linux installation depends on</segtitle> -<seglistitem><seg>Bash, Binutils, Coreutils, Findutils, -GCC, Glibc, Grep, Gzip, Make, Modutils, Perl, Sed</seg></seglistitem> -</segmentedlist> </sect2> <sect2 role="installation"> <title>Installation of the kernel -Building the kernel involves a few steps: configuration, compilation, and -installation. If you don't like the way this book configures the kernel, view -the README file in the kernel source tree for alternative -methods. - Prepare for compilation by running the following command: make mrproper -This ensures that the kernel tree is absolutely clean. The kernel team -recommends that this command be issued prior to each -kernel compilation. You shouldn't rely on the source tree being clean after -un-tarring. - Also, ensure that the kernel does not attempt to pass hotplugging events to userspace until userspace specifies that it is ready: @@ -54,111 +38,27 @@ to compile the keymap into the kernel, issue the command below: loadkeys -m /usr/share/kbd/keymaps/[path to keymap] > \ [unpacked sources dir]/linux-&linux-version;/drivers/char/defkeymap.c -For example, if you have a Dutch keyboard, you would use -/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz. - Configure the kernel via a menu-driven interface: make menuconfig -make oldconfig may be more appropriate in some -situations. See the README file for more -information. - -If you wish, you may skip kernel configuration by simply copying the -kernel config file, .config, from your host system -(assuming it is available) to the unpacked linux-&linux-version; -directory. However, we -don't recommend this option. You're much better off exploring all the -configuration menus and creating your own kernel configuration from -scratch. - -For POSIX shared memory support, ensure that the kernel config option -Virtual memory file system support is enabled. It resides within -the File systems menu and is normally enabled by default. - -LFS bootscripts make the assumption that you either compile -both Support for Host-side USB and -USB device filesystem directly into the kernel, or don't compile them at -all. Bootscripts will not work properly if it is a module (usbcore.ko). - -NPTL requires the kernel to be compiled with GCC 3.x, in this case -&gcc-version;. Compiling with 2.95.x is known to cause failures in the glibc -testsuite, so do not compile the kernel with gcc 2.95.x -unless you know what you're getting yourself into. - Compile the kernel image and modules: make -If you intend to use kernel modules, you may need an -/etc/modprobe.conf file. Information pertaining -to modules and to kernel configuration in general may be found in the -kernel documentation, which is found in the -linux-&linux-version;/Documentation directory. -The modprobe.conf man page - -may also be of interest to you. - -Be very suspicious while reading other documentation, because it -usually applies to 2.4.x kernels only. As far as the editors know, kernel -configuration issues specific to Hotplug and Udev -are documented nowhere. The problem is that Udev will create a device node -only if Hotplug or a user-written script inserts the corresponding module -into the kernel, and not all modules are detectable by Hotplug. Note -that statements like -alias char-major-XXX some-module -in /etc/modprobe.conf file don't work with -Udev, and other aliases are often unnecessary with Hotplug. - -Because of all those compilcations with Hotplug, Udev and modules, we -strongly recommend you to start with a completely non-modular kernel -configuration, especially if this is the first time you use Udev. - Install the modules, if your kernel configuration uses them: make modules_install -If you have a lot of modules and very little space, you may want to -consider stripping and compressing the modules. For most people such compression -isn't worth the trouble, but if you're really pressed for space, then have a look at -. - -Kernel compilation has finished but more steps are required to complete -the installation. Some files need to be copied to the /boot -directory. - The path to the kernel image may vary depending on the platform you're using. Issue the following command to install the kernel: cp arch/i386/boot/bzImage /boot/lfskernel-&linux-version; -System.map is a symbol file for the kernel. It maps -the function entry points of every function in the kernel API (Application Programming Interface), as well as the -addresses of the kernel data structures for the running kernel. Issue the -following command to install the map file: - cp System.map /boot/System.map-&linux-version; -.config is the kernel configuration file that was -produced by the make menuconfig step above. It contains all -the config selections for the kernel that was just compiled. It's a good idea -to keep this file for future reference: - cp .config /boot/config-&linux-version; -It is important to note that the files in the kernel source directory are -not owned by root. Whenever you unpack a package as user -root (like we did here inside chroot), the files end up -having the user and group IDs of whatever they were on the packager's computer. -This is usually not a problem for any other package you install because you -remove the source tree after the installation. But the Linux source tree is -often kept around for a long time, so there's a chance that whatever user ID -the packager used will be assigned to somebody on your machine and then that -person would have write access to the kernel source. - If you are going to keep the kernel source tree around, you may want to run chown -R 0:0 on the linux-&linux-version; directory to ensure all files are @@ -169,48 +69,7 @@ owned by user root. Contents of Linux - -Installed files -the kernel, the kernel headers, -and the System.map - - -Short descriptions - - -The kernel - -kernel -is the engine of your Linux system. -When switching on your box, the kernel is the first part of your operating -system that gets loaded. It detects and initializes all the components of your -computer's hardware, then makes these components available as a tree of files -to the software, and turns a single CPU into a multi-tasking machine capable -of running scores of programs seemingly at the same time. - - - - -The kernel headers - -kernel headers -define the interface to the -services that the kernel provides. The headers in your system's -include directory should always be -the ones against which Glibc was compiled and should therefore -not be replaced when upgrading the kernel. - - - - -System.map - -/boot/System.map -is a list of addresses and symbols. It maps the entry points and addresses -of all the functions and data structures in the kernel. - - - +See testing -- cgit v1.2.3-54-g00ecf