- Timestamp:
- 08/08/2004 02:11:37 AM (20 years ago)
- Branches:
- 6.0
- Children:
- dbc195c
- Parents:
- 5ba3d1d
- Location:
- chapter08
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/fstab.xml
r5ba3d1d r1dc34de7 10 10 <indexterm zone="ch-bootable-fstab"><primary sortas="e-/etc/fstab">/etc/fstab</primary></indexterm> 11 11 12 <para>The <filename>/etc/fstab</filename> file is used by some programs to13 determine where file systems are to be mounted by default, which 14 must be checked and in which order. Create a new file systems table like 15 t his:</para>12 <para>The <filename>/etc/fstab</filename> file is used by some 13 programs to determine where file systems are to be mounted by default, 14 which must be checked, and in which order. Create a new file systems 15 table like this:</para> 16 16 17 17 <screen><userinput>cat > /etc/fstab << "EOF" … … 29 29 EOF</userinput></screen> 30 30 31 <para>Of course, replace <replaceable>[xxx]</replaceable>, <replaceable>[yyy]</replaceable> 32 and <replaceable>[fff]</replaceable> with the values appropriate for your system -- 33 for example <filename class="partition">hda2</filename>, <filename class="partition">hda5</filename> and 34 <systemitem class="filesystem">reiserfs</systemitem>. For all the details on the six fields in this 35 table, see <command>man 5 fstab</command>.</para> 31 <para>Replace <replaceable>[xxx]</replaceable>, 32 <replaceable>[yyy]</replaceable> and <replaceable>[fff]</replaceable> 33 with the values appropriate for the system. For example, <filename 34 class="partition">hda2</filename>, <filename 35 class="partition">hda5</filename>, and <systemitem 36 class="filesystem">reiserfs</systemitem>. For details on the six 37 fields in this file, see <command>man 5 fstab</command>.</para> 36 38 37 <para>When using a reiserfs partition, the <parameter>1 1</parameter> at the 38 end of the line should be replaced with <parameter>0 0</parameter>, as such a 39 partition does not need to be dumped or checked</para> 39 <para>When using a reiserfs partition, the <parameter>1 1</parameter> 40 at the end of the line should be replaced with <parameter>0 41 0</parameter> because such a partition does not need to be dumped or 42 checked.</para> 40 43 41 <para>The <filename class="directory">/dev/shm</filename> mount point for 42 <systemitem class="filesystem">tmpfs</systemitem> is included to 43 allow enabling POSIX shared memory. Your kernel must have the required support 44 built into it for this to work -- more about this in the next section. Please 45 note that currently very little software actually uses POSIX shared memory. 46 Therefore you can consider the <filename class="directory">/dev/shm</filename> mount point 47 optional. For more information, see 48 <filename>Documentation/filesystems/tmpfs.txt</filename> in the kernel source 49 tree.</para> 44 <para>The <filename class="directory">/dev/shm</filename> mount point 45 for <systemitem class="filesystem">tmpfs</systemitem> is included to 46 allow enabling POSIX shared memory. The kernel must have the required 47 support built into it for this to work (more about this in the next 48 section). Please note that very little software currently uses POSIX 49 shared memory. Therefore, consider the <filename 50 class="directory">/dev/shm</filename> mount point optional. For more 51 information, see 52 <filename>Documentation/filesystems/tmpfs.txt</filename> in the kernel 53 source tree.</para> 50 54 51 <para>There are other lines which you may consider adding to your52 <filename> fstab</filename> file. One example is a line to use if you intend to53 use USBdevices:</para>55 <para>There are other lines which may be added to the 56 <filename>/etc/fstab</filename> file. One example is a line for USB 57 devices:</para> 54 58 55 59 <screen> usbfs /proc/bus/usb usbfs devgid=14,devmode=0660 0 0 </screen> 56 60 57 <para>This option will o f course only work if you have the58 "Support for Host-side USB" and "USB device filesystem" 59 compiled into yourkernel (not as a module).</para>61 <para>This option will only work if the <quote>Support for Host-side 62 USB</quote> and <quote>USB device filesystem</quote> are compiled into 63 the kernel (not as a module).</para> 60 64 61 65 </sect1> 66 -
chapter08/grub.xml
r5ba3d1d r1dc34de7 12 12 <secondary>configuring</secondary></indexterm> 13 13 14 <para>Your shiny new LFS system is almost complete. One of the last things to 15 do is ensure you can boot it. The instructions below apply only to computers of 16 IA-32 architecture, meaning mainstream PCs. Information on <quote>boot 17 loading</quote> for other architectures should be available in the usual 18 resource-specific locations for those architectures.</para> 14 <para>Your shiny new LFS system is almost complete. One of the last 15 things to do is ensure that it can be properly booted. The 16 instructions below apply only to computers of IA-32 architecture, 17 meaning mainstream PCs. Information on <quote>boot loading</quote> for 18 other architectures should be available in the usual resource-specific 19 locations for those architectures.</para> 19 20 20 <para>Boot loading can be a complex area. First, a few cautionary words. You21 really should be familiar with yourcurrent boot loader and any other22 operating systems present on your hard drive(s) that you might wish to keep23 bootable. Please make sure that you have an emergency boot disk ready, so that24 you can rescue your computer if, by any chance, your computer becomes unusable 25 (un-bootable).</para>21 <para>Boot loading can be a complex area. First, a few cautionary 22 words. Be familiar with the current boot loader and any other 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 to 25 <quote>rescue</quote> the computer if, by chance, the computer becomes 26 unusable (un-bootable).</para> 26 27 27 <para>Earlier, we compiled and installed the Grub boot loader software in28 preparation for this step. The procedure involves writing some special Grub 29 files to specific locations on the hard drive. Before we get to that, we 30 highly recommend that you create a Grub boot floppy diskette just in case. 31 Insert ablank floppy diskette and run the following commands:</para>28 <para>Earlier, we compiled and installed the Grub boot loader software 29 in preparation for this step. The procedure involves writing some 30 special Grub files to specific locations on the hard drive. We highly 31 recommend a Grub boot floppy diskette be created as a backup. Insert a 32 blank floppy diskette and run the following commands:</para> 32 33 33 34 <screen><userinput>dd if=/boot/grub/stage1 of=/dev/fd0 bs=512 count=1 34 35 dd if=/boot/grub/stage2 of=/dev/fd0 bs=512 seek=1</userinput></screen> 35 36 36 <para>Remove the diskette and store it somewhere safe. Now we'llrun the37 <para>Remove the diskette and store it somewhere safe. Now, run the 37 38 <command>grub</command> shell:</para> 38 39 39 40 <screen><userinput>grub</userinput></screen> 40 41 41 <para>Grub uses its own naming structure for drives and partitions, in the form 42 of (hdn,m), where <emphasis>n</emphasis> is the hard drive number, and 43 <emphasis>m</emphasis> the partition number, both starting from zero. This 44 means, for instance, that partition <filename class="partition">hda1</filename> is (hd0,0) to 45 Grub, and <filename class="partition">hdb2</filename> is (hd1,1). In contrast to Linux, Grub 46 doesn't consider CD-ROM drives to be hard drives, so if you have a CD on 47 <filename class="partition">hdb</filename>, for example, and a second hard drive on 48 <filename class="partition">hdc</filename>, that second hard drive would still be (hd1).</para> 42 <para>Grub uses its own naming structure for drives and partitions, in 43 the form of <emphasis>(hdn,m)</emphasis>, where <emphasis>n</emphasis> 44 is the hard drive number and <emphasis>m</emphasis> is the partition 45 number, both starting from zero. For example, partition <filename 46 class="partition">hda1</filename> is <emphasis>(hd0,0)</emphasis> to 47 Grub, and <filename class="partition">hdb3</filename> is 48 <emphasis>(hd1,2)</emphasis>. In contrast to Linux, Grub does not 49 consider CD-ROM drives to be hard drives. For example, if using a CD 50 on <filename class="partition">hdb</filename> and a second hard drive 51 on <filename class="partition">hdc</filename>, that second hard drive 52 would still be <emphasis>(hd1)</emphasis>.</para> 49 53 50 <para>Using the above information, determine the appropriate designator for 51 your root partition (or boot partition, if you use a separate one). For the 52 following example, we'll assume your root (or separate boot) partition is 53 <filename class="partition">hda4</filename>.</para> 54 <para>Using the above information, determine the appropriate 55 designator for the root partition (or boot partition, if a separate 56 one is used). For the following example, it is assumed that the root 57 (or separate boot) partition is <filename 58 class="partition">hda4</filename>.</para> 54 59 55 <para>First, tell Grub where to search for its <filename>stage{1,2}</filename> 56 files -- you can use the Tab key everywhere to make Grub show the alternatives:</para> 60 <para>First, tell Grub where to search for its 61 <filename>stage{1,2}</filename> files. The Tab key can be used 62 everywhere to make Grub show the alternatives:</para> 57 63 58 64 <screen><userinput>root (hd0,3)</userinput></screen> 59 65 60 61 <warning><para>The following command will overwrite your current boot loader. 62 Don't run the command if this is not what you want. For example, you may be 63 using a third party boot manager to manage your MBR (Master Boot Record). In 64 this scenario, it would probably make more sense to install Grub into the 65 <quote>boot sector</quote> of the LFS partition, in which case this next command 66 would become: <userinput>setup (hd0,3)</userinput>.</para></warning> 67 66 <warning><para>The following command will overwrite the current boot 67 loader. Do not run the command if this is not desired, for example, if 68 using a third party boot manager to manage the Master Boot Record 69 (MBR). In this scenario, it would probably make more sense to install 70 Grub into the <quote>boot sector</quote> of the LFS partition. In this 71 case, this next command would become: <userinput>setup 72 (hd0,3)</userinput>.</para></warning> 68 73 69 74 <para>Tell Grub to install itself into the MBR (Master Boot Record) of … … 72 77 <screen><userinput>setup (hd0)</userinput></screen> 73 78 74 <para>If all is well, Grub will have reported finding its files in 75 <filename class="directory">/boot/grub</filename>. That's all there is to it:</para> 79 <para>If all went well, Grub will have reported finding its files in 80 <filename class="directory">/boot/grub</filename>. That's all there is 81 to it. Quit the <command>grub</command> shell:</para> 76 82 77 83 <screen><userinput>quit</userinput></screen> 78 84 79 <para>Now we need to create a <quote>menu list</quote> file, defining Grub's 80 boot menu:</para> 85 <para>Create a <quote>menu list</quote> file defining Grub's boot menu:</para> 81 86 82 87 <screen><userinput>cat > /boot/grub/menu.lst << "EOF" … … 98 103 EOF</userinput></screen> 99 104 100 <para> You may want to add an entry for your host distribution. It might look105 <para>Add an entry for the host distribution if desired. It might look 101 106 like this:</para> 102 107 … … 108 113 EOF</userinput></screen> 109 114 110 <para>Also, if you happen to dual-boot Windows, the following entry should111 allowbooting it:</para>115 <para>Also, if dual-booting Windows, the following entry will allow 116 booting it:</para> 112 117 113 118 <screen><userinput>cat >> /boot/grub/menu.lst << "EOF" … … 117 122 EOF</userinput></screen> 118 123 119 <para>If <command>info grub</command> does n't tell you all you want to120 know, you can find more information regarding Grub on its website, locatedat:124 <para>If <command>info grub</command> does not provide all necessary material, additional 125 information regarding Grub is located on its website at: 121 126 <ulink url="http://www.gnu.org/software/grub/"/>.</para> 122 127 123 128 </sect1> 129 -
chapter08/introduction.xml
r5ba3d1d r1dc34de7 8 8 <?dbhtml filename="introduction.html"?> 9 9 10 <para>This chapter will make LFS bootable. This chapter deals with creating a11 <filename>fstab</filename> file, building a12 kernel for the new LFS system and installing the Grub bootloader13 sothat the LFS system can be selected for booting at startup.</para>10 <para>This chapter will make the LFS system bootable. This chapter 11 discusses creating an <filename>fstab</filename> file, building a 12 kernel for the new LFS system, and installing the Grub bootloader so 13 that the LFS system can be selected for booting at startup.</para> 14 14 15 15 </sect1> 16 -
chapter08/kernel.xml
r5ba3d1d r1dc34de7 30 30 <title>Installation of the kernel</title> 31 31 32 <para>Building the kernel involves a few steps : configuration, compilation, and33 installation. If you don't like the way this book configures the kernel, view 34 the <filename>README</filename> file in the kernel source tree for alternative 35 methods.</para>32 <para>Building the kernel involves a few steps -- configuration, 33 compilation, and installation. Read the <filename>README</filename> 34 file in the kernel source tree for alternative methods to the way this 35 book configures the kernel.</para> 36 36 37 37 <para>Prepare for compilation by running the following command:</para> … … 39 39 <screen><userinput>make mrproper</userinput></screen> 40 40 41 <para>This ensures that the kernel tree is absolutely clean. The kernel team42 recommends that this command be issued prior to <emphasis>each</emphasis> 43 kernel compilation. You shouldn't rely on the source tree being clean after41 <para>This ensures that the kernel tree is absolutely clean. The 42 kernel team recommends that this command be issued prior to each 43 kernel compilation. Do not rely on the source tree being clean after 44 44 un-tarring.</para> 45 45 46 <para>Also, ensure that the kernel does not attempt to pass hotplugging events 47 to userspace until userspace specifies that it is ready:</para> 46 <para>Also, ensure that the kernel does not attempt to pass 47 hotplugging events to userspace until userspace specifies that it is 48 ready:</para> 48 49 49 50 <screen><userinput>sed -i 's@/sbin/hotplug@/bin/true@' kernel/kmod.c</userinput></screen> 50 51 51 <para>If, in <xref linkend="ch-scripts-console"/>, you decided you want52 tocompile the keymap into the kernel, issue the command below:</para>52 <para>If, in <xref linkend="ch-scripts-console"/>, you decided to 53 compile the keymap into the kernel, issue the command below:</para> 53 54 54 55 <screen><userinput>loadkeys -m /usr/share/kbd/keymaps/<replaceable>[path to keymap]</replaceable> > \ 55 56 <replaceable>[unpacked sources dir]</replaceable>/linux-&linux-version;/drivers/char/defkeymap.c</userinput></screen> 56 57 57 <para>For example, if you have a Dutch keyboard, you woulduse58 <para>For example, if using a Dutch keyboard, use 58 59 <filename>/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz</filename>.</para> 59 60 … … 66 67 information.</para> 67 68 68 <para>If you wish, you may skip kernel configuration by simply copying the 69 kernel config file, <filename>.config</filename>, from your host system 70 (assuming it is available) to the unpacked <filename class="directory">linux-&linux-version;</filename> 71 directory. However, we 72 don't recommend this option. You're much better off exploring all the 73 configuration menus and creating your own kernel configuration from 69 <note><para>When you configure the kernel, be sure to enable the 70 <quote>Support for hot-pluggable devices</quote> option under the 71 <quote>General Setup</quote> menu. This enables hotplug events that 72 are used by <command>udev</command> to populate the <filename 73 class="directory">/dev</filename> directory with device 74 nodes.</para></note> 75 76 <para>If desired, skip kernel configuration by copying the kernel 77 config file, <filename>.config</filename>, from the host system 78 (assuming it is available) to the unpacked <filename 79 class="directory">linux-&linux-version;</filename> directory. However, 80 we do not recommend this option. It is often better to explore all the 81 configuration menus and creating the kernel configuration from 74 82 scratch.</para> 75 83 76 <para>For POSIX shared memory support, ensure that the kernel config option 77 <quote>Virtual memory file system support</quote> is enabled. It resides within 78 the <quote>File systems</quote> menu and is normally enabled by default.</para> 79 80 <para>LFS bootscripts make the assumption that you either compile 81 both <quote>Support for Host-side USB</quote> and 82 <quote>USB device filesystem</quote> directly into the kernel, or don't compile them at 83 all. Bootscripts will not work properly if it is a module (<filename>usbcore.ko</filename>).</para> 84 85 <note><para>NPTL requires the kernel to be compiled with GCC 3.x, in this case 86 &gcc-version;. Compiling with 2.95.x is known to cause failures in the glibc 87 testsuite, so do <emphasis>not</emphasis> compile the kernel with gcc 2.95.x 88 unless you know what you're getting yourself into.</para></note> 84 <para>For POSIX shared memory support, ensure that the kernel config 85 option <quote>Virtual memory file system support</quote> is enabled. 86 It resides within the <quote>File systems</quote> menu and is normally 87 enabled by default.</para> 88 89 <para>LFS bootscripts make the assumption that either both 90 <quote>Support for Host-side USB</quote> and <quote>USB device 91 filesystem</quote> have been compiled directly into the kernel, or 92 that neither is compiled at all. Bootscripts will not work properly 93 if it is a module (usbcore.ko).</para> 94 95 <note><para>NPTL requires the kernel to be compiled with GCC 3.x, in 96 this case &gcc-version;. Compiling with 2.95.x is known to cause failures in 97 the glibc testsuite, so it is not recommended to compile the kernel 98 with gcc 2.95.x.</para></note> 89 99 90 100 <para>Compile the kernel image and modules:</para> … … 92 102 <screen><userinput>make</userinput></screen> 93 103 94 <para>If you intend to use kernel modules, you may need an 95 <filename>/etc/modprobe.conf</filename> file. Information pertaining 96 to modules and to kernel configuration in general may be found in the 97 kernel documentation, which is found in the 98 <filename class="directory">linux-&linux-version;/Documentation</filename> directory. 99 The modprobe.conf man page 100 <!-- removed for review from tldp.org 101 and the kernel HOWTO at 102 <ulink url="http://www.tldp.org/HOWTO/Kernel-HOWTO.html"/> --> 103 may also be of interest to you.</para> 104 105 <para>Be very suspicious while reading other documentation, because it 106 usually applies to 2.4.x kernels only. As far as the editors know, kernel 107 configuration issues specific to Hotplug and Udev 108 are documented nowhere. The problem is that Udev will create a device node 109 only if Hotplug or a user-written script inserts the corresponding module 110 into the kernel, and not all modules are detectable by Hotplug. Note 111 that statements like 112 <screen>alias char-major-XXX some-module</screen> 113 in <filename>/etc/modprobe.conf</filename> file don't work with 104 <para>If using kernel modules, an 105 <filename>/etc/modprobe.conf</filename> file may be needed. 106 Information pertaining to modules and to kernel configuration is 107 located in the kernel documentation in the <filename 108 class="directory">linux-&linux-version;/Documentation</filename> 109 directory. The <emphasis>modprobe.conf</emphasis> man page may also be 110 of interest.</para> 111 112 <para>Be very careful when reading other documentation, because it 113 usually applies to 2.4.x kernels only. As far as we know, kernel 114 configuration issues specific to Hotplug and Udev are not documented. 115 The problem is that Udev will create a device node only if Hotplug or 116 a user-written script inserts the corresponding module into the 117 kernel, and not all modules are detectable by Hotplug. Note that 118 statements like <screen>alias char-major-XXX some-module</screen> in 119 the <filename>/etc/modprobe.conf</filename> file do not work with 114 120 Udev, and other aliases are often unnecessary with Hotplug.</para> 115 121 116 <para>Because of all those compilcations with Hotplug, Udevand modules, we117 strongly recommend you to startwith a completely non-modular kernel118 configuration, especially if this is the first time you useUdev.</para>122 <para>Because of the complications with Hotplug, Udev, and modules, we 123 strongly recommend starting with a completely non-modular kernel 124 configuration, especially if this is the first time using Udev.</para> 119 125 120 126 <para>Install the modules, if your kernel configuration uses them:</para> … … 122 128 <screen><userinput>make modules_install</userinput></screen> 123 129 124 <para>If you have a lot of modules and very little space, you may want to 125 consider stripping and compressing the modules. For most people such compression 126 isn't worth the trouble, but if you're really pressed for space, then have a look at 127 <ulink url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para> 128 129 <para>Kernel compilation has finished but more steps are required to complete 130 the installation. Some files need to be copied to the <filename class="directory">/boot</filename> 131 directory.</para> 132 133 <para>The path to the kernel image may vary depending on the platform you're 134 using. Issue the following command to install the kernel:</para> 130 <para>If there are many modules and very little space, consider 131 stripping and compressing the modules. For most users, such 132 compression is not worth the time, but if the system is pressed for 133 space, see <ulink 134 url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para> 135 136 <para>After kernel compilation is complete, additional steps are 137 required to complete the installation. Some files need to be copied to 138 the <filename class="directory">/boot</filename> directory.</para> 139 140 <para>The path to the kernel image may vary depending on the platform 141 being used. Issue the following command to install the kernel:</para> 135 142 136 143 <screen><userinput>cp arch/i386/boot/bzImage /boot/lfskernel-&linux-version;</userinput></screen> 137 144 138 <para><filename>System.map</filename> is a symbol file for the kernel. It maps139 the function entry points of every function in the kernel API (Application Programming Interface), as well as the 140 a ddresses of the kernel data structures for the running kernel. Issue the141 following command to install the map file:</para>145 <para><filename>System.map</filename> is a symbol file for the kernel. 146 It maps the function entry points of every function in the kernel API, 147 as well as the addresses of the kernel data structures for the running 148 kernel. Issue the following command to install the map file:</para> 142 149 143 150 <screen><userinput>cp System.map /boot/System.map-&linux-version;</userinput></screen> 144 151 145 <para><filename>.config</filename> is the kernel configuration file that was 146 produced by the <command>make menuconfig</command> step above. It contains all 147 the config selections for the kernel that was just compiled. It's a good idea 148 to keep this file for future reference:</para> 152 <para><filename>.config</filename> is the kernel's configuration file 153 that was produced by the <command>make menuconfig</command> step 154 above. It contains all the configuration selections for the kernel 155 that was just compiled. It is a good idea to keep this file for future 156 reference:</para> 149 157 150 158 <screen><userinput>cp .config /boot/config-&linux-version;</userinput></screen> 151 159 152 <para>It is important to note that the files in the kernel source directory are 153 not owned by <emphasis>root</emphasis>. Whenever you unpack a package as user 154 <emphasis>root</emphasis> (like we did here inside chroot), the files end up 155 having the user and group IDs of whatever they were on the packager's computer. 156 This is usually not a problem for any other package you install because you 157 remove the source tree after the installation. But the Linux source tree is 158 often kept around for a long time, so there's a chance that whatever user ID 159 the packager used will be assigned to somebody on your machine and then that 160 person would have write access to the kernel source.</para> 161 162 <para>If you are going to keep the kernel source tree around, you may want to 163 run <command>chown -R 0:0</command> on the 164 <filename class="directory">linux-&linux-version;</filename> directory to ensure all files are 165 owned by user <emphasis>root</emphasis>.</para> 166 160 <para>It is important to note that the files in the kernel source 161 directory are not owned by <emphasis>root</emphasis>. Whenever a 162 package is unpacked as user <emphasis>root</emphasis> (like we did 163 here inside chroot), the files have the user and group IDs of whatever 164 they were on the packager's computer. This is usually not a problem 165 for any other package to be installed because the source tree is 166 removed after the installation. However, the Linux source tree is 167 often retained for a long time. Because of this, there is a chance 168 that whatever user ID the packager used will be assigned to somebody 169 on the machine. That person would then have write access to the kernel 170 source.</para> 171 172 <para>If the kernel source tree is going to retained, run 173 <command>chown -R 0:0</command> on the <filename 174 class="directory">linux-&linux-version;</filename> directory to ensure 175 all files are owned by user <emphasis>root</emphasis>.</para> 167 176 </sect2> 168 177 … … 182 191 <listitem> 183 192 <indexterm zone="ch-bootable-kernel kernel"><primary sortas="b-kernel">kernel</primary></indexterm> 184 <para> is the engine of your Linux system.185 When switching on your box, the kernel is the first part of your operating 186 system that gets loaded. It detects and initializes all the components of your 187 computer's hardware, then makes these components available as a tree of files 188 to the software, and turns a single CPU into a multi-tasking machine capable193 <para>the engine of the Linux system. When turning on your computer, 194 the kernel is the first part of the operating system that gets loaded. 195 It detects and initializes all components of the computer's hardware, 196 then makes these components available as a tree of files to the 197 software, and turns a single CPU into a multitasking machine capable 189 198 of running scores of programs seemingly at the same time.</para> 190 199 </listitem> … … 195 204 <listitem> 196 205 <indexterm zone="ch-bootable-kernel kernel-headers"><primary sortas="e-kernel-headers">kernel headers</primary></indexterm> 197 <para>define the interface to the 198 services that the kernel provides. The headers in your system's 199 <filename class="directory">include</filename> directory should <emphasis>always</emphasis> be 200 the ones against which Glibc was compiled and should therefore 201 <emphasis>not</emphasis> be replaced when upgrading the kernel.</para> 206 <para>defines the interface to the services that the kernel provides. 207 The headers in your system's <filename 208 class="directory">include</filename> directory should 209 <emphasis>always</emphasis> be the ones against which Glibc was 210 compiled and therefore, should <emphasis>not</emphasis> be replaced 211 when upgrading the kernel.</para> 202 212 </listitem> 203 213 </varlistentry> … … 207 217 <listitem> 208 218 <indexterm zone="ch-bootable-kernel System.map"><primary sortas="e-/boot/System.map">/boot/System.map</primary></indexterm> 209 <para>is a list of addresses and symbols. It maps the entry points and addresses 210 of all the functions and data structures in the kernel.</para> 219 <para>is a list of addresses and symbols. It maps the entry points and 220 addresses of all the functions and data structures in the 221 kernel.</para> 211 222 </listitem> 212 223 </varlistentry> … … 216 227 217 228 </sect1> 229
Note:
See TracChangeset
for help on using the changeset viewer.