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