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 /stage1 directory is owned by the lfs user. However,
  5. this user account exists only on the host system. Although you may delete
  6. the <filename class="directory">/stage1</filename> directory once you have
  7. finished your LFS system, you might want to keep it around, e.g. for
  8. building more LFS systems. But if you keep the
  9. <filename class="directory">/stage1</filename> directory you will end up
  10. with files owned by a user id without a corresponding account. This is
  11. dangerous because a user account created later could get this user id and
  12. would suddenly own the <filename class="directory">/stage1</filename>
  13. directory and all of the files therein. This could open the
  14. <filename class="directory">/stage1</filename> directory to manipulation by
  15. an untrusted user.</para>
  16. <para>To avoid this issue, you can add the
  17. <emphasis>lfs</emphasis> user to the new LFS system later when creating
  18. the <filename>/etc/passwd</filename> file, taking care to assign it the
  19. same user and group id. Alternatively, you can (and the book will assume
  20. you do) run the following command now, to assign the contents of the
  21. <filename class="directory">/stage1</filename> directory to user
  22. <emphasis>root</emphasis> by running the following command:</para>
  23. <para><screen><userinput>chown -R 0:0 /stage1</userinput></screen></para>
  24. <para>The command uses "0:0" instead of "root:root", because chown is unable
  25. to resolve the name "root" until glibc has been installed.</para>
  26. </sect1>