- Timestamp:
- 08/29/2004 06:36:34 PM (20 years ago)
- Branches:
- 6.0
- Children:
- 8b320e7
- Parents:
- ec0a37e6
- Location:
- chapter08
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/chapter08.xml
rec0a37e6 r69993f4 6 6 <chapter id="chapter-bootable" xreflabel="Chapter 8"> 7 7 <?dbhtml dir="chapter08"?> 8 <title>Making the LFS system bootable</title>8 <title>Making the LFS System Bootable</title> 9 9 <?dbhtml filename="chapter08.html"?> 10 10 -
chapter08/fstab.xml
rec0a37e6 r69993f4 5 5 ]> 6 6 <sect1 id="ch-bootable-fstab"> 7 <title>Creating the /etc/fstab file</title>7 <title>Creating the /etc/fstab File</title> 8 8 <?dbhtml filename="fstab.html"?> 9 9 … … 30 30 31 31 <para>Replace <replaceable>[xxx]</replaceable>, 32 <replaceable>[yyy]</replaceable> and <replaceable>[fff]</replaceable>33 with the values appropriate for the system . For example, <filename32 <replaceable>[yyy]</replaceable>, and <replaceable>[fff]</replaceable> 33 with the values appropriate for the system, for example, <filename 34 34 class="partition">hda2</filename>, <filename 35 35 class="partition">hda5</filename>, and <systemitem … … 44 44 <para>The <filename class="directory">/dev/shm</filename> mount point 45 45 for <systemitem class="filesystem">tmpfs</systemitem> is included to 46 allow enabling POSIX 47 support built into it for this to work (more about this i n the next48 section). Please note that very little software currently uses POSIX49 shared memory. Therefore, consider the <filename46 allow enabling POSIX-shared memory. The kernel must have the required 47 support built into it for this to work (more about this is in the next 48 section). Please note that very little software currently uses 49 POSIX-shared memory. Therefore, consider the <filename 50 50 class="directory">/dev/shm</filename> mount point optional. For more 51 51 information, see … … 59 59 <screen> usbfs /proc/bus/usb usbfs devgid=14,devmode=0660 0 0 </screen> 60 60 61 <para>This option will only work if the<quote>Support for Host-side61 <para>This option will only work if <quote>Support for Host-side 62 62 USB</quote> and <quote>USB device filesystem</quote> are compiled into 63 63 the kernel (not as a module).</para> -
chapter08/grub.xml
rec0a37e6 r69993f4 5 5 ]> 6 6 <sect1 id="ch-bootable-grub"> 7 <title>Making the LFS system bootable</title>7 <title>Making the LFS System Bootable</title> 8 8 <?dbhtml filename="grub.html"?> 9 9 … … 13 13 14 14 <para>Your shiny new LFS system is almost complete. One of the last 15 things to do is ensure that itcan be properly booted. The15 things to do is to ensure that the system can be properly booted. The 16 16 instructions below apply only to computers of IA-32 architecture, 17 17 meaning mainstream PCs. Information on <quote>boot loading</quote> for … … 19 19 locations for those architectures.</para> 20 20 21 <para>Boot loading can be a complex area . First,a few cautionary22 words . Be familiar with the current boot loader and any other21 <para>Boot loading can be a complex area, so a few cautionary 22 words are in order. Be familiar with the current boot loader and any other 23 23 operating systems present on the hard drive(s) that need to be 24 bootable. Please make sure that an emergency boot disk is ready to25 <quote>rescue</quote> the computer if , by chance,the computer becomes24 bootable. Make sure that an emergency boot disk is ready to 25 <quote>rescue</quote> the computer if the computer becomes 26 26 unusable (un-bootable).</para> 27 27 … … 29 29 in preparation for this step. The procedure involves writing some 30 30 special Grub files to specific locations on the hard drive. We highly 31 recommend a Grub boot floppy diskette be createdas a backup. Insert a31 recommend creating a Grub boot floppy diskette as a backup. Insert a 32 32 blank floppy diskette and run the following commands:</para> 33 33 … … 40 40 <screen><userinput>grub</userinput></screen> 41 41 42 <para>Grub uses its own naming structure for drives and partitions ,in42 <para>Grub uses its own naming structure for drives and partitions in 43 43 the form of <emphasis>(hdn,m)</emphasis>, where <emphasis>n</emphasis> 44 44 is the hard drive number and <emphasis>m</emphasis> is the partition 45 45 number, both starting from zero. For example, partition <filename 46 46 class="partition">hda1</filename> is <emphasis>(hd0,0)</emphasis> to 47 Grub ,and <filename class="partition">hdb3</filename> is47 Grub and <filename class="partition">hdb3</filename> is 48 48 <emphasis>(hd1,2)</emphasis>. In contrast to Linux, Grub does not 49 49 consider CD-ROM drives to be hard drives. For example, if using a CD … … 58 58 class="partition">hda4</filename>.</para> 59 59 60 <para> First, tell Grub where to search for its60 <para>Tell Grub where to search for its 61 61 <filename>stage{1,2}</filename> files. The Tab key can be used 62 62 everywhere to make Grub show the alternatives:</para> … … 67 67 loader. Do not run the command if this is not desired, for example, if 68 68 using a third party boot manager to manage the Master Boot Record 69 (MBR). In this scenario, it would probablymake more sense to install69 (MBR). In this scenario, it would make more sense to install 70 70 Grub into the <quote>boot sector</quote> of the LFS partition. In this 71 71 case, this next command would become: <userinput>setup 72 72 (hd0,3)</userinput>.</para></warning> 73 73 74 <para>Tell Grub to install itself into the MBR (Master Boot Record)of74 <para>Tell Grub to install itself into the MBR of 75 75 <filename class="partition">hda</filename>:</para> 76 76 … … 113 113 EOF</userinput></screen> 114 114 115 <para> Also, if dual-booting Windows, the following entry will allow115 <para>If dual-booting Windows, the following entry will allow 116 116 booting it:</para> 117 117 -
chapter08/introduction.xml
rec0a37e6 r69993f4 8 8 <?dbhtml filename="introduction.html"?> 9 9 10 <para> This chapter willmake the LFS system bootable. This chapter10 <para>It is time to make the LFS system bootable. This chapter 11 11 discusses creating an <filename>fstab</filename> file, building a 12 12 kernel for the new LFS system, and installing the Grub bootloader so -
chapter08/kernel.xml
rec0a37e6 r69993f4 16 16 <segtitle>&buildtime;</segtitle> 17 17 <segtitle>&diskspace;</segtitle> 18 <seglistitem><seg> All default options:4.20 SBU</seg>19 <seg> All default options:181 MB</seg></seglistitem>18 <seglistitem><seg>4.20 SBU</seg> 19 <seg>181 MB</seg></seglistitem> 20 20 </segmentedlist> 21 21 … … 23 23 <segtitle>Linux installation depends on</segtitle> 24 24 <seglistitem><seg>Bash, Binutils, Coreutils, Findutils, 25 GCC, Glibc, Grep, Gzip, Make, Modutils, Perl, Sed</seg></seglistitem>25 GCC, Glibc, Grep, Gzip, Make, Modutils, Perl, and Sed</seg></seglistitem> 26 26 </segmentedlist> 27 27 </sect2> … … 30 30 <title>Installation of the kernel</title> 31 31 32 <para>Building the kernel involves a few steps --configuration,32 <para>Building the kernel involves a few steps—configuration, 33 33 compilation, and installation. Read the <filename>README</filename> 34 34 file in the kernel source tree for alternative methods to the way this … … 50 50 <screen><userinput>sed -i 's@/sbin/hotplug@/bin/true@' kernel/kmod.c</userinput></screen> 51 51 52 <para>If, in <xref linkend="ch-scripts-console"/> , you decided to53 compile the keymapinto the kernel, issue the command below:</para>52 <para>If, in <xref linkend="ch-scripts-console"/> the keymap was 53 compiled into the kernel, issue the command below:</para> 54 54 55 55 <screen><userinput>loadkeys -m /usr/share/kbd/keymaps/<replaceable>[path to keymap]</replaceable> > \ … … 67 67 information.</para> 68 68 69 <note><para>When you configurethe kernel, be sure to enable the69 <note><para>When configuring the kernel, be sure to enable the 70 70 <quote>Support for hot-pluggable devices</quote> option under the 71 71 <quote>General Setup</quote> menu. This enables hotplug events that … … 79 79 class="directory">linux-&linux-version;</filename> directory. However, 80 80 we do not recommend this option. It is often better to explore all the 81 configuration menus and creat ingthe kernel configuration from81 configuration menus and create the kernel configuration from 82 82 scratch.</para> 83 83 84 <para>For POSIX 84 <para>For POSIX-shared memory support, ensure that the kernel config 85 85 option <quote>Virtual memory file system support</quote> is enabled. 86 86 It resides within the <quote>File systems</quote> menu and is normally … … 95 95 <note><para>NPTL requires the kernel to be compiled with GCC 3.x, in 96 96 this case &gcc-version;. Compiling with 2.95.x is known to cause failures in 97 the glibc test suite, so it is not recommended to compile the kernel97 the glibc test suite, so it is not recommended to compile the kernel 98 98 with gcc 2.95.x.</para></note> 99 99 … … 104 104 <para>If using kernel modules, an 105 105 <filename>/etc/modprobe.conf</filename> file may be needed. 106 Information pertaining to modules and tokernel configuration is106 Information pertaining to modules and kernel configuration is 107 107 located in the kernel documentation in the <filename 108 108 class="directory">linux-&linux-version;/Documentation</filename> … … 110 110 of interest.</para> 111 111 112 <para>Be very careful when reading other documentation ,because it112 <para>Be very careful when reading other documentation because it 113 113 usually applies to 2.4.x kernels only. As far as we know, kernel 114 114 configuration issues specific to Hotplug and Udev are not documented. … … 124 124 configuration, especially if this is the first time using Udev.</para> 125 125 126 <para>Install the modules, if yourkernel configuration uses them:</para>126 <para>Install the modules, if the kernel configuration uses them:</para> 127 127 128 128 <screen><userinput>make modules_install</userinput></screen> … … 161 161 directory are not owned by <emphasis>root</emphasis>. Whenever a 162 162 package is unpacked as user <emphasis>root</emphasis> (like we did 163 hereinside chroot), the files have the user and group IDs of whatever163 inside chroot), the files have the user and group IDs of whatever 164 164 they were on the packager's computer. This is usually not a problem 165 165 for any other package to be installed because the source tree is … … 181 181 <segmentedlist> 182 182 <segtitle>Installed files</segtitle> 183 <seglistitem><seg> the kernel, thekernel headers,184 and theSystem.map</seg></seglistitem>183 <seglistitem><seg>kernel, kernel headers, 184 and System.map</seg></seglistitem> 185 185 </segmentedlist> 186 186 … … 189 189 190 190 <varlistentry id="kernel"> 191 <term> The <emphasis>kernel</emphasis></term>191 <term><command>kernel</command></term> 192 192 <listitem> 193 <para>the engine of the Linux system. When turning on yourcomputer,193 <para>the engine of the Linux system. When turning on the computer, 194 194 the kernel is the first part of the operating system that gets loaded. 195 195 It detects and initializes all components of the computer's hardware, 196 196 then makes these components available as a tree of files to the 197 software ,and turns a single CPU into a multitasking machine capable197 software and turns a single CPU into a multitasking machine capable 198 198 of running scores of programs seemingly at the same time.</para> 199 199 <indexterm zone="ch-bootable-kernel kernel"><primary sortas="b-kernel">kernel</primary></indexterm> … … 202 202 203 203 <varlistentry id="kernel-headers"> 204 <term> The <emphasis>kernel headers</emphasis></term>204 <term><command>kernel headers</command></term> 205 205 <listitem> 206 206 <para>defines the interface to the services that the kernel provides. 207 The headers in yoursystem's <filename207 The headers in the system's <filename 208 208 class="directory">include</filename> directory should 209 209 <emphasis>always</emphasis> be the ones against which Glibc was … … 217 217 <term><filename>System.map</filename></term> 218 218 <listitem> 219 <para> isa list of addresses and symbols. It maps the entry points and219 <para>a list of addresses and symbols. It maps the entry points and 220 220 addresses of all the functions and data structures in the 221 221 kernel.</para>
Note:
See TracChangeset
for help on using the changeset viewer.