Changeset 6d4c909 for BOOK/boot


Ignore:
Timestamp:
Feb 21, 2006, 1:56:25 AM (19 years ago)
Author:
Jim Gifford <clfs@…>
Branches:
clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
Children:
ad0c7e6
Parents:
f0ed7ed
Message:

r974@server (orig r972): jim | 2005-12-28 21:29:16 -0800

r1216@server: jim | 2005-12-28 21:26:31 -0800
Text Updates from Chris Staub. Thank you


Location:
BOOK/boot
Files:
3 edited

Legend:

Unmodified
Added
Removed

  • BOOK/boot/common/changingowner.xml

    rf0ed7ed r6d4c909  
    1111  <title>Changing Ownership</title>
    1212
    13   <para os="a">Currently, the <filename class="directory">/tools</filename>
    14   directory is owned by the user <systemitem class="username">lfs</systemitem>,
    15   a user that exists only on the host system. Although the <filename
    16   class="directory">/tools</filename> directory can be deleted once the
    17   LFS system has been finished, it can be retained to build additional
    18   LFS systems. If the <filename class="directory">/tools</filename>
    19   directory is kept as is, the files are owned by a user ID without a
     13  <note os="a">
     14    <para>From now on, all commands in the rest of the book will be run as the <systemitem class="username">root</systemitem> user.</para>
     15  </note>
     16
     17  <para os="b">Currently, the <filename class="directory">/tools</filename>
     18  directory, <filename class="directory">/cross-tools</filename> directory, and
     19  <filename class="directory">$LFS</filename> directory are owned
     20  by the user <systemitem class="username">lfs</systemitem>,
     21  a user that exists only on the host system. For security reasons, the $LFS root directory and all of it subdirectories should be owned by <systemitem class="username">root</systemitem>. Change the ownership for $LFS and its subdirectories by running these commands:</para>
     22
     23<screen><userinput>chown 0:0 ${LFS}
     24chown -R 0:0 $LFS/{bin,boot,dev,etc,home,lib,media,mnt,opt,proc,root,sbin,srv,sys,tmp,usr,var}</userinput></screen>
     25
     26  <para os="c">Optionally, you can do the same with <filename class="directory">/tools</filename> and <filename class="directory">/cross-tools</filename>. Although these directories can be deleted once the
     27  LFS system has been finished, they can be retained to build additional
     28  LFS systems. If the <filename class="directory">/tools</filename> and <filename class="directory">/cross-tools</filename>
     29  directories are kept as is, the files are owned by a user ID without a
    2030  corresponding account. This is dangerous because a user account created
    2131  later could get this same user ID and would own the <filename
    22   class="directory">/tools</filename> directory and all the files therein,
     32  class="directory">/tools</filename> and <filename class="directory">/cross-tools</filename> directories and all the files therein,
    2333  thus exposing these files to possible malicious manipulation.</para>
    2434
    25   <para os="b">To avoid this issue, add the <systemitem
     35  <para os="d">To avoid this issue, add the <systemitem
    2636  class="username">lfs</systemitem> user to the new LFS system later when
    2737  creating the <filename>/etc/passwd</filename> file, taking care to assign
    2838  it the same user and group IDs as on the host system. Alternatively,
    2939  assign the contents of the <filename class="directory">/tools</filename>
    30   directory to user <systemitem class="username">root</systemitem> by running
     40  and <filename class="directory">/cross-tools</filename> directories to user <systemitem class="username">root</systemitem> by running
    3141  the following command:</para>
    3242
    3343<screen><userinput>chown -R 0:0 /tools
    34 chown -R 0:0 ${LFS}</userinput></screen>
     44chown -R 0:0 /cross-tools</userinput></screen>
    3545
    36   <para os="c">The command uses <parameter>0:0</parameter> instead of
     46<para os="e">This book assumes you ran these <command>chown</command> commands.</para>
     47
     48<!--  <para os="c">The command uses <parameter>0:0</parameter> instead of
    3749  <parameter>root:root</parameter>, because <command>chown</command>
    3850  is unable to resolve the name <quote>root</quote> until the password
    3951  file has been created. This book assumes you ran this
    40   <command>chown</command> command.</para>
     52  <command>chown</command> command.</para> -->
    4153
    4254</sect1>

  • BOOK/boot/common/settingenviron.xml

    rf0ed7ed r6d4c909  
    1111  <title>Setting Up the Environment</title>
    1212
    13   <para>The new instance of the shell is a <emphasis>non-login</emphasis>
    14   shell, will read <filename>.bash_profile</filename> file. Create the
     13  <para>The new instance of the shell that will start when the system is booted is a <emphasis>login</emphasis>
     14  shell, which will read <filename>.bash_profile</filename> file. Create the
    1515  <filename>.bash_profile</filename> file now:</para>
    1616

  • BOOK/boot/x86/kernel.xml

    rf0ed7ed r6d4c909  
    2525    <warning os="aa">
    2626      <para>Here a temporary cross-compiled kernel will be built. When
    27       configuring it, select the minimal amount of options required to can
    28       boot the target machine and build the final system. I.e., not support
     27      configuring it, select the minimal amount of options required to
     28      boot the target machine and build the final system. I.e., no support
    2929      for sound, printers, etc. will be needed.</para>
    3030
Note: See TracChangeset for help on using the changeset viewer.