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