Changeset 9922b26


Ignore:
Timestamp:
02/06/2003 12:01:40 AM (21 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
5384d51
Parents:
2296bd1
Message:

tag + typo fixes

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

Location:
chapter06
Files:
3 edited

Legend:

Unmodified
Added
Removed

  • chapter06/kernel-inst.xml

    r2296bd1 r9922b26  
    1010
    1111<para>It is important to note that the files in the kernel source directory
    12 are not owned by root. Whenever you unpack a package as user root (like we
    13 do here inside chroot), the files end up having the user and group ID's of
    14 whatever they were on the packager's computer. This is usually not a
     12are not owned by <emphasis>root</emphasis>. Whenever you unpack a package as
     13user <emphasis>root</emphasis> (like we do here inside chroot), the files end
     14up having the user and group IDs of whatever they were on the packager's
     15computer. This is usually not a
    1516problem for any other package you install because you remove the source
    1617tree after the installation. But the Linux kernel source tree is often kept
    17 around for a long time, so there's a chance that whatever userid was used will
    18 be assigned to somebody on your machine and that person would have write
    19 access to the kernel source.</para>
     18around for a long time, so there's a chance that whatever user ID the packager
     19used will be assigned to somebody on your machine and then that person would
     20have write access to the kernel source.</para>
    2021
    2122<para>In light of this, you might want to run <userinput>chown -R 0:0</userinput>
    … …  
    2324to ensure all files are owned by user <emphasis>root</emphasis>.</para>
    2425
    25 <para>Kernel header installation requires the <emphasis>pwd</emphasis> program.
    26 In the kernel source, the path to the pwd program is hard-wired as /bin/pwd.
     26<para>Kernel header installation requires the <filename>pwd</filename> program.
     27In the kernel source the path to the <filename>pwd</filename> program is
     28hard-wired as <filename>/bin/pwd</filename>.
    2729Create a symlink to account for that:</para>
    2830
    … …  
    5961<filename>autoconf.h</filename> header file. Since we do not yet configure the
    6062kernel, we need to create this file ourselves in order to avoid compilation
    61 failures. Create an empty autoconf.h file:</para>
     63failures. Create an empty <filename>autoconf.h</filename> file:</para>
    6264
    6365<para><screen><userinput>touch /usr/include/linux/autoconf.h</userinput></screen></para>

  • chapter06/makedev-inst.xml

    r2296bd1 r9922b26  
    2727information.</para>
    2828
    29 <para>If you intend to use devpts, pass the
     29<para>If you intend to use <emphasis>devpts</emphasis>, pass the
    3030<userinput>generic-nopty</userinput> option to <filename>MAKEDEV</filename>.
    3131This creates the same devices as <userinput>generic</userinput>, but it skips
    32 the creation of pty devices so that devpts can manage them itself.</para>
     32the creation of <emphasis>pty</emphasis> devices so that
     33<emphasis>devpts<emphasis> can manage those.</para>
    3334
    3435</sect2>

  • chapter06/pwdgroup.xml

    r2296bd1 r9922b26  
    33<?dbhtml filename="pwdgroup.html" dir="chapter06"?>
    44
    5 <para>In order for root to be able to login and for the name "root" to be
    6 recognized, there need to be relevant entries in the
     5<para>In order for <emphasis>root</emphasis> to be able to login and for the
     6name "root" to be recognized, there need to be relevant entries in the
    77<filename>/etc/passwd</filename> and
    88<filename>/etc/group</filename> files.</para>
    … …  
    1313<para><screen><userinput>echo "root:x:0:0:root:/root:/bin/bash" &gt; /etc/passwd</userinput></screen></para>
    1414
    15 <para>The actual password for root (the "x" here is just a placeholder) will
    16 be set later.</para>
     15<para>The actual password for <emphasis>root</emphasis> (the "x" here is
     16just a placeholder) will be set later.</para>
    1717
    1818<para>Create the <filename>/etc/group</filename> file by running the
    … …  
    3636<para>The created groups aren't part of any standard -- they are the groups
    3737that the MAKEDEV script in the next section uses. Besides the group "root",
    38 the LSB (<ulink url="http://www.linuxbase.org"/>) (recommends only a group
     38the LSB (<ulink url="http://www.linuxbase.org"/>) recommends only a group
    3939"bin", with a GID of 1, be present. All other group names and GIDs can be
    4040chosen freely by the user, as well-written packages don't depend on GID
Note: See TracChangeset for help on using the changeset viewer.