Ignore:
Timestamp:
Feb 21, 2006, 2:17:51 AM (18 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:
f15e0d6
Parents:
a605458
Message:

r1112@server (orig r1110): chris | 2006-01-30 11:07:11 -0800
Moved note in boot section about running the rest of the book as root to populating LFS/dev since the devices must be created as root.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • BOOK/boot/common/changingowner.xml

    ra605458 rbf3dcb3f  
    1111  <title>Changing Ownership</title>
    1212
    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>
     13  <para os="a">Currently, the <filename class="directory">/tools</filename>
    1814  directory, <filename class="directory">/cross-tools</filename> directory, and
    1915  <filename class="directory">$LFS</filename> directory are owned
    2016  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>
     17  a user that exists only on the host system. For security reasons, the
     18  $LFS root directory and all of it subdirectories should be owned by
     19  <systemitem class="username">root</systemitem>. Change the ownership for $LFS and its subdirectories by running these commands:</para>
    2220
    2321<screen><userinput>chown root:root ${LFS}
    2422chown -R root:root $LFS/{bin,boot,dev,etc,home,lib,media,mnt,opt,proc,root,sbin,srv,sys,tmp,usr,var}</userinput></screen>
    2523
    26   <para os="c">The same issue also exists with <filename class="directory">/tools</filename> and <filename class="directory">/cross-tools</filename>. Although these directories can be deleted once the
     24  <para os="b">The same issue also exists with <filename class="directory">/tools</filename> and <filename class="directory">/cross-tools</filename>. Although these directories can be deleted once the
    2725  LFS system has been finished, they can be retained to build additional
    2826  LFS systems. If the <filename class="directory">/tools</filename> and <filename class="directory">/cross-tools</filename>
     
    3331  thus exposing these files to possible malicious manipulation.</para>
    3432
    35   <para os="d">To avoid this issue, add the <systemitem
     33  <para os="c">To avoid this issue, add the <systemitem
    3634  class="username">lfs</systemitem> user to the new LFS system later when
    3735  creating the <filename>/etc/passwd</filename> file, taking care to assign
Note: See TracChangeset for help on using the changeset viewer.