changingowner.xml 1.6 KB

1234567891011121314151617181920212223242526272829303132
  1. <sect1 id="ch06-changingowner">
  2. <title>Changing ownership</title>
  3. <?dbhtml filename="changingowner.html" dir="chapter06"?>
  4. <para>Right now the <filename class="directory">/tools</filename> directory
  5. is owned by the user <emphasis>lfs</emphasis>, a user that exists only on your
  6. host system. Although you will probably want to delete the
  7. <filename class="directory">/tools</filename> directory once you have
  8. finished your LFS system, you may want to keep it around, for example to
  9. build more LFS systems. But if you keep the
  10. <filename class="directory">/tools</filename> directory as it is, you end up
  11. with files owned by a user ID without a corresponding account. This is
  12. dangerous because a user account created later on could get this same user ID
  13. and would suddenly own the <filename class="directory">/tools</filename>
  14. directory and all the files therein, thus exposing these files to possible
  15. malicious manipulation.</para>
  16. <para>To avoid this issue, you could add the <emphasis>lfs</emphasis> user to
  17. your new LFS system later on when creating the <filename>/etc/passwd</filename>
  18. file, taking care to assign it the same user and group IDs as on your host
  19. system. Alternatively, you can (and the book assumes you do) assign the
  20. contents of the <filename class="directory">/tools</filename> directory to
  21. user <emphasis>root</emphasis> by running the following command:</para>
  22. <screen><userinput>chown -R 0:0 /tools</userinput></screen>
  23. <para>The command uses "0:0" instead of "root:root", because
  24. <userinput>chown</userinput> is unable to resolve the name "root" until the
  25. password file has been created.</para>
  26. </sect1>