mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-03-06 06:14:47 +00:00
added make mandocs
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2250 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
parent
1986f02dba
commit
14d5c7f1fc
@ -1,12 +1,27 @@
|
||||
<sect2>
|
||||
<title>Installation of the kernel headers</title>
|
||||
<title>Installation of the kernel headers and man pages</title>
|
||||
|
||||
<para>We won't be compiling a new kernel yet -- we'll do that when we have
|
||||
finished the installation of all the packages. But as some packages need the
|
||||
kernel header files, we're going to unpack the kernel archive now, set it up,
|
||||
and copy the header files to where they will be found by these packages.</para>
|
||||
|
||||
<para>The kernel headers are copied by running the following commands:</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
|
||||
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 whatever userid was used will
|
||||
be assigned to somebody on your machine, and that person would get write
|
||||
access to the kernel source.</para>
|
||||
|
||||
<para>In light of this, you might want to run <userinput>chown
|
||||
0.0</userinput> on the linux-&kernel-version; directory to ensure all files
|
||||
are owned by user <emphasis>root</emphasis>.</para>
|
||||
|
||||
<para>The kernel headers and man pages are installed by running the following
|
||||
commands:</para>
|
||||
|
||||
<para><screen><userinput>ln -s /static/bin/pwd /bin/pwd &&
|
||||
make mrproper &&
|
||||
|
Loading…
Reference in New Issue
Block a user