source: chapter06/changingowner.xml@ 148c207

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.0 6.1 6.1.1 6.3 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk v5_0 v5_1 v5_1_1 xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 148c207 was bc82645e, checked in by Gerard Beekmans <gerard@…>, 21 years ago

Integrated Pure LFS - Phase 1

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2490 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 1.6 KB
Line 
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,
6this user account exists only on the host system. Although you may delete
7the <filename class="directory">/stage1</filename> directory once you have
8finished your LFS system, you might want to keep it around, e.g. for
9building more LFS systems. But if you keep the
10<filename class="directory">/stage1</filename> directory you will end up
11with files owned by a user id without a corresponding account. This is
12dangerous because a user account created later could get this user id and
13would suddenly own the <filename class="directory">/stage1</filename>
14directory and all of the files therein. This could open the
15<filename class="directory">/stage1</filename> directory to manipulation by
16an 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
20the <filename>/etc/passwd</filename> file, taking care to assign it the
21same user and group id. Alternatively, you can (and the book will assume
22you 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
29to resolve the name "root" until glibc has been installed.</para>
30
31</sect1>
32
Note: See TracBrowser for help on using the repository browser.