mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-01-19 13:37:39 +00:00
bc82645e95
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2490 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
33 lines
1.6 KiB
XML
33 lines
1.6 KiB
XML
<sect1 id="ch06-changingowner">
|
|
<title>Changing ownership</title>
|
|
<?dbhtml filename="changingowner.html" dir="chapter06"?>
|
|
|
|
<para>Right now the /stage1 directory is owned by the lfs user. However,
|
|
this user account exists only on the host system. Although you may delete
|
|
the <filename class="directory">/stage1</filename> directory once you have
|
|
finished your LFS system, you might want to keep it around, e.g. for
|
|
building more LFS systems. But if you keep the
|
|
<filename class="directory">/stage1</filename> directory you will end up
|
|
with files owned by a user id without a corresponding account. This is
|
|
dangerous because a user account created later could get this user id and
|
|
would suddenly own the <filename class="directory">/stage1</filename>
|
|
directory and all of the files therein. This could open the
|
|
<filename class="directory">/stage1</filename> directory to manipulation by
|
|
an untrusted user.</para>
|
|
|
|
<para>To avoid this issue, you can add the
|
|
<emphasis>lfs</emphasis> user to the new LFS system later when creating
|
|
the <filename>/etc/passwd</filename> file, taking care to assign it the
|
|
same user and group id. Alternatively, you can (and the book will assume
|
|
you do) run the following command now, to assign the contents of the
|
|
<filename class="directory">/stage1</filename> directory to user
|
|
<emphasis>root</emphasis> by running the following command:</para>
|
|
|
|
<para><screen><userinput>chown -R 0:0 /stage1</userinput></screen></para>
|
|
|
|
<para>The command uses "0:0" instead of "root:root", because chown is unable
|
|
to resolve the name "root" until glibc has been installed.</para>
|
|
|
|
</sect1>
|
|
|