mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-03-06 06:14:47 +00:00
tag + typo fixes
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2432 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
parent
2296bd1cd8
commit
9922b2698c
@ -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>
|
||||
|
||||
|
@ -26,10 +26,11 @@ create devices via the <emphasis>mknod</emphasis> program. Please refer to
|
||||
the man and info pages of <emphasis>mknod</emphasis> if you need more
|
||||
information.</para>
|
||||
|
||||
<para>If you intend to use devpts, pass the
|
||||
<para>If you intend to use <emphasis>devpts</emphasis>, pass the
|
||||
<userinput>generic-nopty</userinput> option to <filename>MAKEDEV</filename>.
|
||||
This creates the same devices as <userinput>generic</userinput>, but it skips
|
||||
the creation of pty devices so that devpts can manage them itself.</para>
|
||||
the creation of <emphasis>pty</emphasis> devices so that
|
||||
<emphasis>devpts<emphasis> can manage those.</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
|
@ -2,8 +2,8 @@
|
||||
<title>Creating the passwd and group files</title>
|
||||
<?dbhtml filename="pwdgroup.html" dir="chapter06"?>
|
||||
|
||||
<para>In order for root to be able to login and for the name "root" to be
|
||||
recognized, there need to be relevant entries in the
|
||||
<para>In order for <emphasis>root</emphasis> to be able to login and for the
|
||||
name "root" to be recognized, there need to be relevant entries in the
|
||||
<filename>/etc/passwd</filename> and
|
||||
<filename>/etc/group</filename> files.</para>
|
||||
|
||||
@ -12,8 +12,8 @@ following command:</para>
|
||||
|
||||
<para><screen><userinput>echo "root:x:0:0:root:/root:/bin/bash" > /etc/passwd</userinput></screen></para>
|
||||
|
||||
<para>The actual password for root (the "x" here is just a placeholder) will
|
||||
be set later.</para>
|
||||
<para>The actual password for <emphasis>root</emphasis> (the "x" here is
|
||||
just a placeholder) will be set later.</para>
|
||||
|
||||
<para>Create the <filename>/etc/group</filename> file by running the
|
||||
following command:</para>
|
||||
@ -35,7 +35,7 @@ audio:x:11:
|
||||
|
||||
<para>The created groups aren't part of any standard -- they are the groups
|
||||
that the MAKEDEV script in the next section uses. Besides the group "root",
|
||||
the LSB (<ulink url="http://www.linuxbase.org"/>) (recommends only a group
|
||||
the LSB (<ulink url="http://www.linuxbase.org"/>) recommends only a group
|
||||
"bin", with a GID of 1, be present. All other group names and GIDs can be
|
||||
chosen freely by the user, as well-written packages don't depend on GID
|
||||
numbers but use the group's name.</para>
|
||||
|
Loading…
Reference in New Issue
Block a user