aboutsummaryrefslogtreecommitdiffstats
path: root/chapter06/kernel-inst.xml
diff options
context:
space:
mode:
authorGerard Beekmans <gerard@linuxfromscratch.org>2003-02-06 00:01:40 +0000
committerGerard Beekmans <gerard@linuxfromscratch.org>2003-02-06 00:01:40 +0000
commit9922b2698cdc90aeab540a995d4e698d63121c4d (patch)
treea0b2e7f1d2de44c7e604c6062394346969c68132 /chapter06/kernel-inst.xml
parent2296bd1cd886ce6d8fe4dcdff99989c05930a42f (diff)
tag + typo fixes
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2432 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter06/kernel-inst.xml')
-rw-r--r--chapter06/kernel-inst.xml20
1 files changed, 11 insertions, 9 deletions
diff --git a/chapter06/kernel-inst.xml b/chapter06/kernel-inst.xml
index 55f1482e5..2b02a202b 100644
--- a/chapter06/kernel-inst.xml
+++ b/chapter06/kernel-inst.xml
@@ -9,21 +9,23 @@ kernel header files, we're going to unpack the kernel archive now, set it up
and copy the header files so they can be found by these packages.</para>
<para>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
-do here inside chroot), the files end up having the user and group ID's of
-whatever they were on the packager's computer. This is usually not a
+are not owned by <emphasis>root</emphasis>. Whenever you unpack a package as
+user <emphasis>root</emphasis> (like we do 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 kernel source tree is often kept
-around for a long time, so there's a chance that whatever userid was used will
-be assigned to somebody on your machine and that person would have write
-access to the kernel source.</para>
+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.</para>
<para>In light of this, you might want to run <userinput>chown -R 0:0</userinput>
on the <filename>linux-&kernel-version;</filename> directory
to ensure all files are owned by user <emphasis>root</emphasis>.</para>
-<para>Kernel header installation requires the <emphasis>pwd</emphasis> program.
-In the kernel source, the path to the pwd program is hard-wired as /bin/pwd.
+<para>Kernel header installation requires the <filename>pwd</filename> program.
+In the kernel source the path to the <filename>pwd</filename> program is
+hard-wired as <filename>/bin/pwd</filename>.
Create a symlink to account for that:</para>
<para><screen><userinput>ln -s /static/bin/pwd /bin/pwd</userinput></screen></para>
@@ -58,7 +60,7 @@ cp -R include/asm-generic /usr/include</userinput></screen></para>
<para>There are a few kernel header files which make use of the
<filename>autoconf.h</filename> header file. Since we do not yet configure the
kernel, we need to create this file ourselves in order to avoid compilation
-failures. Create an empty autoconf.h file:</para>
+failures. Create an empty <filename>autoconf.h</filename> file:</para>
<para><screen><userinput>touch /usr/include/linux/autoconf.h</userinput></screen></para>