Changeset 1dc34de7


Ignore:
Timestamp:
08/08/2004 02:11:37 AM (20 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
6.0
Children:
dbc195c
Parents:
5ba3d1d
Message:

Completed global edits for upcoming 6.0 release

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/branches/testing/BOOK@4002 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Location:
chapter08
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • chapter08/fstab.xml

    r5ba3d1d r1dc34de7  
    1010<indexterm zone="ch-bootable-fstab"><primary sortas="e-/etc/fstab">/etc/fstab</primary></indexterm>
    1111
    12 <para>The <filename>/etc/fstab</filename> file is used by some programs to
    13 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 this:</para>
     12<para>The <filename>/etc/fstab</filename> file is used by some
     13programs to determine where file systems are to be mounted by default,
     14which must be checked, and in which order. Create a new file systems
     15table like this:</para>
    1616
    1717<screen><userinput>cat &gt; /etc/fstab &lt;&lt; "EOF"
    … …  
    2929EOF</userinput></screen>
    3030
    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>
     33with the values appropriate for the system. For example, <filename
     34class="partition">hda2</filename>, <filename
     35class="partition">hda5</filename>, and <systemitem
     36class="filesystem">reiserfs</systemitem>. For details on the six
     37fields in this file, see <command>man 5 fstab</command>.</para>
    3638
    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>
     40at the end of the line should be replaced with <parameter>0
     410</parameter> because such a partition does not need to be dumped or
     42checked.</para>
    4043
    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
     45for <systemitem class="filesystem">tmpfs</systemitem> is included to
     46allow enabling POSIX shared memory. The kernel must have the required
     47support built into it for this to work (more about this in the next
     48section). Please note that very little software currently uses POSIX
     49shared memory.  Therefore, consider the <filename
     50class="directory">/dev/shm</filename> mount point optional. For more
     51information, see
     52<filename>Documentation/filesystems/tmpfs.txt</filename> in the kernel
     53source tree.</para>
    5054
    51 <para>There are other lines which you may consider adding to your
    52 <filename>fstab</filename> file. One example is a line to use if you intend to
    53 use USB devices:</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
     57devices:</para>
    5458
    5559<screen> usbfs         /proc/bus/usb usbfs   devgid=14,devmode=0660 0 0 </screen>
    5660
    57 <para>This option will of course only work if you have the
    58 "Support for Host-side USB" and "USB device filesystem"
    59 compiled into your kernel (not as a module).</para>
     61<para>This option will only work if the <quote>Support for Host-side
     62USB</quote> and <quote>USB device filesystem</quote> are compiled into
     63the kernel (not as a module).</para>
    6064
    6165</sect1>
     66

  • chapter08/grub.xml

    r5ba3d1d r1dc34de7  
    1212<secondary>configuring</secondary></indexterm>
    1313
    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
     15things to do is ensure that it can be properly booted. The
     16instructions below apply only to computers of IA-32 architecture,
     17meaning mainstream PCs. Information on <quote>boot loading</quote> for
     18other architectures should be available in the usual resource-specific
     19locations for those architectures.</para>
    1920
    20 <para>Boot loading can be a complex area. First, a few cautionary words. You
    21 really should be familiar with your current boot loader and any other
    22 operating systems present on your hard drive(s) that you might wish to keep
    23 bootable. Please make sure that you have an emergency boot disk ready, so that
    24 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
     22words. Be familiar with the current boot loader and any other
     23operating systems present on the hard drive(s) that need to be
     24bootable. Please make sure that an emergency boot disk is ready to
     25<quote>rescue</quote> the computer if, by chance, the computer becomes
     26unusable (un-bootable).</para>
    2627
    27 <para>Earlier, we compiled and installed the Grub boot loader software in
    28 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 a blank floppy diskette and run the following commands:</para>
     28<para>Earlier, we compiled and installed the Grub boot loader software
     29in preparation for this step. The procedure involves writing some
     30special Grub files to specific locations on the hard drive. We highly
     31recommend a Grub boot floppy diskette be created as a backup. Insert a
     32blank floppy diskette and run the following commands:</para>
    3233
    3334<screen><userinput>dd if=/boot/grub/stage1 of=/dev/fd0 bs=512 count=1
    3435dd if=/boot/grub/stage2 of=/dev/fd0 bs=512 seek=1</userinput></screen>
    3536
    36 <para>Remove the diskette and store it somewhere safe. Now we'll run the
     37<para>Remove the diskette and store it somewhere safe. Now, run the
    3738<command>grub</command> shell:</para>
    3839
    3940<screen><userinput>grub</userinput></screen>
    4041
    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
     43the form of <emphasis>(hdn,m)</emphasis>, where <emphasis>n</emphasis>
     44is the hard drive number and <emphasis>m</emphasis> is the partition
     45number, both starting from zero. For example, partition <filename
     46class="partition">hda1</filename> is <emphasis>(hd0,0)</emphasis> to
     47Grub, and <filename class="partition">hdb3</filename> is
     48<emphasis>(hd1,2)</emphasis>. In contrast to Linux, Grub does not
     49consider CD-ROM drives to be hard drives. For example, if using a CD
     50on <filename class="partition">hdb</filename> and a second hard drive
     51on <filename class="partition">hdc</filename>, that second hard drive
     52would still be <emphasis>(hd1)</emphasis>.</para>
    4953
    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
     55designator for the root partition (or boot partition, if a separate
     56one is used). For the following example, it is assumed that the root
     57(or separate boot) partition is <filename
     58class="partition">hda4</filename>.</para>
    5459
    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
     62everywhere to make Grub show the alternatives:</para>
    5763
    5864<screen><userinput>root (hd0,3)</userinput></screen>
    5965
    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
     67loader. Do not run the command if this is not desired, for example, if
     68using a third party boot manager to manage the Master Boot Record
     69(MBR). In this scenario, it would probably make more sense to install
     70Grub into the <quote>boot sector</quote> of the LFS partition. In this
     71case, this next command would become: <userinput>setup
     72(hd0,3)</userinput>.</para></warning>
    6873
    6974<para>Tell Grub to install itself into the MBR (Master Boot Record) of
    … …  
    7277<screen><userinput>setup (hd0)</userinput></screen>
    7378
    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
     81to it. Quit the <command>grub</command> shell:</para>
    7682
    7783<screen><userinput>quit</userinput></screen>
    7884
    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>
    8186
    8287<screen><userinput>cat &gt; /boot/grub/menu.lst &lt;&lt; "EOF"
    … …  
    98103EOF</userinput></screen>
    99104
    100 <para>You may want to add an entry for your host distribution. It might look
     105<para>Add an entry for the host distribution if desired. It might look
    101106like this:</para>
    102107
    … …  
    108113EOF</userinput></screen>
    109114
    110 <para>Also, if you happen to dual-boot Windows, the following entry should
    111 allow booting it:</para>
     115<para>Also, if dual-booting Windows, the following entry will allow
     116booting it:</para>
    112117
    113118<screen><userinput>cat &gt;&gt; /boot/grub/menu.lst &lt;&lt; "EOF"
    … …  
    117122EOF</userinput></screen>
    118123
    119 <para>If <command>info grub</command> doesn't tell you all you want to
    120 know, you can find more information regarding Grub on its website, located at:
     124<para>If <command>info grub</command> does not provide all necessary material, additional
     125information regarding Grub is located on its website at:
    121126<ulink url="http://www.gnu.org/software/grub/"/>.</para>
    122127
    123128</sect1>
     129

  • chapter08/introduction.xml

    r5ba3d1d r1dc34de7  
    88<?dbhtml filename="introduction.html"?>
    99
    10 <para>This chapter will make LFS bootable. This chapter deals with creating a
    11 <filename>fstab</filename> file, building a
    12 kernel for the new LFS system and installing the Grub bootloader
    13 so that the LFS system can be selected for booting at startup.</para>
     10<para>This chapter will make the LFS system bootable. This chapter
     11discusses creating an <filename>fstab</filename> file, building a
     12kernel for the new LFS system, and installing the Grub bootloader so
     13that the LFS system can be selected for booting at startup.</para>
    1414
    1515</sect1>
     16

  • chapter08/kernel.xml

    r5ba3d1d r1dc34de7  
    3030<title>Installation of the kernel</title>
    3131
    32 <para>Building the kernel involves a few steps: configuration, compilation, and
    33 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,
     33compilation, and installation. Read the <filename>README</filename>
     34file in the kernel source tree for alternative methods to the way this
     35book configures the kernel.</para>
    3636
    3737<para>Prepare for compilation by running the following command:</para>
    … …  
    3939<screen><userinput>make mrproper</userinput></screen>
    4040
    41 <para>This ensures that the kernel tree is absolutely clean. The kernel team
    42 recommends that this command be issued prior to <emphasis>each</emphasis>
    43 kernel compilation. You shouldn't rely on the source tree being clean after
     41<para>This ensures that the kernel tree is absolutely clean. The
     42kernel team recommends that this command be issued prior to each
     43kernel compilation. Do not rely on the source tree being clean after
    4444un-tarring.</para>
    4545
    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
     47hotplugging events to userspace until userspace specifies that it is
     48ready:</para>
    4849
    4950<screen><userinput>sed -i 's@/sbin/hotplug@/bin/true@' kernel/kmod.c</userinput></screen>
    5051
    51 <para>If, in <xref linkend="ch-scripts-console"/>, you decided you want
    52 to compile the keymap into the kernel, issue the command below:</para>
     52<para>If, in <xref linkend="ch-scripts-console"/>, you decided to
     53compile the keymap into the kernel, issue the command below:</para>
    5354
    5455<screen><userinput>loadkeys -m /usr/share/kbd/keymaps/<replaceable>[path to  keymap]</replaceable> &gt; \
    5556    <replaceable>[unpacked sources dir]</replaceable>/linux-&linux-version;/drivers/char/defkeymap.c</userinput></screen>
    5657
    57 <para>For example, if you have a Dutch keyboard, you would use
     58<para>For example, if using a Dutch keyboard, use
    5859<filename>/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz</filename>.</para>
    5960
    … …  
    6667information.</para>
    6768
    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
     72are used by <command>udev</command> to populate the <filename
     73class="directory">/dev</filename> directory with device
     74nodes.</para></note>
     75
     76<para>If desired, skip kernel configuration by copying the kernel
     77config file, <filename>.config</filename>, from the host system
     78(assuming it is available) to the unpacked <filename
     79class="directory">linux-&linux-version;</filename> directory. However,
     80we do not recommend this option. It is often better to explore all the
     81configuration menus and creating the kernel configuration from
    7482scratch.</para>
    7583
    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
     85option <quote>Virtual memory file system support</quote> is enabled.
     86It resides within the <quote>File systems</quote> menu and is normally
     87enabled 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
     91filesystem</quote> have been compiled directly into the kernel, or
     92that neither is compiled at all.  Bootscripts will not work properly
     93if it is a module (usbcore.ko).</para>
     94
     95<note><para>NPTL requires the kernel to be compiled with GCC 3.x, in
     96this case &gcc-version;. Compiling with 2.95.x is known to cause failures in
     97the glibc testsuite, so it is not recommended to compile the kernel
     98with gcc 2.95.x.</para></note>
    8999
    90100<para>Compile the kernel image and modules:</para>
    … …  
    92102<screen><userinput>make</userinput></screen>
    93103
    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.
     106Information pertaining to modules and to kernel configuration is
     107located in the kernel documentation in the <filename
     108class="directory">linux-&linux-version;/Documentation</filename>
     109directory. The <emphasis>modprobe.conf</emphasis> man page may also be
     110of interest.</para>
     111
     112<para>Be very careful when reading other documentation, because it
     113usually applies to 2.4.x kernels only. As far as we know, kernel
     114configuration issues specific to Hotplug and Udev are not documented.
     115The problem is that Udev will create a device node only if Hotplug or
     116a user-written script inserts the corresponding module into the
     117kernel, and not all modules are detectable by Hotplug. Note that
     118statements like <screen>alias char-major-XXX some-module</screen> in
     119the <filename>/etc/modprobe.conf</filename> file do not work with
    114120Udev, and other aliases are often unnecessary with Hotplug.</para>
    115121
    116 <para>Because of all those compilcations with Hotplug, Udev and modules, we
    117 strongly recommend you to start with a completely non-modular kernel
    118 configuration, especially if this is the first time you use Udev.</para>
     122<para>Because of the complications with Hotplug, Udev, and modules, we
     123strongly recommend starting with a completely non-modular kernel
     124configuration, especially if this is the first time using Udev.</para>
    119125
    120126<para>Install the modules, if your kernel configuration uses them:</para>
    … …  
    122128<screen><userinput>make modules_install</userinput></screen>
    123129
    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
     131stripping and compressing the modules. For most users, such
     132compression is not worth the time, but if the system is pressed for
     133space, see <ulink
     134url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para>
     135
     136<para>After kernel compilation is complete, additional steps are
     137required to complete the installation. Some files need to be copied to
     138the <filename class="directory">/boot</filename> directory.</para>
     139
     140<para>The path to the kernel image may vary depending on the platform
     141being used. Issue the following command to install the kernel:</para>
    135142
    136143<screen><userinput>cp arch/i386/boot/bzImage /boot/lfskernel-&linux-version;</userinput></screen>
    137144
    138 <para><filename>System.map</filename> is a symbol file for the kernel. It maps
    139 the function entry points of every function in the kernel API (Application Programming Interface), as well as the
    140 addresses of the kernel data structures for the running kernel. Issue the
    141 following command to install the map file:</para>
     145<para><filename>System.map</filename> is a symbol file for the kernel.
     146It maps the function entry points of every function in the kernel API,
     147as well as the addresses of the kernel data structures for the running
     148kernel. Issue the following command to install the map file:</para>
    142149
    143150<screen><userinput>cp System.map /boot/System.map-&linux-version;</userinput></screen>
    144151
    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
     153that was produced by the <command>make menuconfig</command> step
     154above. It contains all the configuration selections for the kernel
     155that was just compiled. It is a good idea to keep this file for future
     156reference:</para>
    149157
    150158<screen><userinput>cp .config /boot/config-&linux-version;</userinput></screen>
    151159
    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
     161directory are not owned by <emphasis>root</emphasis>. Whenever a
     162package is unpacked as user <emphasis>root</emphasis> (like we did
     163here inside chroot), the files have the user and group IDs of whatever
     164they were on the packager's computer. This is usually not a problem
     165for any other package to be installed because the source tree is
     166removed after the installation. However, the Linux source tree is
     167often retained for a long time.  Because of this, there is a chance
     168that whatever user ID the packager used will be assigned to somebody
     169on the machine. That person would then have write access to the kernel
     170source.</para>
     171
     172<para>If the kernel source tree is going to retained, run
     173<command>chown -R 0:0</command> on the <filename
     174class="directory">linux-&linux-version;</filename> directory to ensure
     175all files are owned by user <emphasis>root</emphasis>.</para>
    167176</sect2>
    168177
    … …  
    182191<listitem>
    183192<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 capable
     193<para>the engine of the Linux system. When turning on your computer,
     194the kernel is the first part of the operating system that gets loaded.
     195It detects and initializes all components of the computer's hardware,
     196then makes these components available as a tree of files to the
     197software, and turns a single CPU into a multitasking machine capable
    189198of running scores of programs seemingly at the same time.</para>
    190199</listitem>
    … …  
    195204<listitem>
    196205<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.
     207The headers in your system's <filename
     208class="directory">include</filename> directory should
     209<emphasis>always</emphasis> be the ones against which Glibc was
     210compiled and therefore, should <emphasis>not</emphasis> be replaced
     211when upgrading the kernel.</para>
    202212</listitem>
    203213</varlistentry>
    … …  
    207217<listitem>
    208218<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
     220addresses of all the functions and data structures in the
     221kernel.</para>
    211222</listitem>
    212223</varlistentry>
    … …  
    216227
    217228</sect1>
     229
Note: See TracChangeset for help on using the changeset viewer.