gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 06:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fixed command to change /tools ownewrship. Resolves ticket #1780.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7565 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Manuel Canales Esparcia 2006-04-23 09:00:37 +00:00
parent 830492e984
commit 07e8db25bd
3 changed files with 22 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
chapter01/changelog.xml
View File

@ -36,12 +36,23 @@
</listitem>
-->
<listitem>
<para>April 23, 2006</para>
<itemizedlist>
<listitem>
<para>[manuel] - Fixed command to change $LFS/tools
ownewrship. Resolves ticket #1780.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>April 22, 2006</para>
<itemizedlist>
<listitem>
<para>[manuel] - Revised again the Host System Requirements page
wording and look. Thanks to Bruce Dubbs for the patch.</para>
wording and look. Thanks to Bruce Dubbs for the patch. Resolves
ticket #1779.</para>
</listitem>
</itemizedlist>
</listitem>

16
chapter05/changingowner.xml
View File

@ -18,29 +18,29 @@
class="username">root</systemitem>'s environment.</para>
</note>
<para>Currently, the <filename class="directory">/tools</filename> directory
<para>Currently, the <filename class="directory">$LFS/tools</filename> directory
is owned by the user <systemitem class="username">lfs</systemitem>, a user
that exists only on the host system. If the <filename
class="directory">/tools</filename> directory is kept as is, the files are
class="directory">$LFS/tools</filename> directory is kept as is, the files are
owned by a user ID without a corresponding account. This is dangerous because
a user account created later could get this same user ID and would own the
<filename class="directory">/tools</filename> directory and all the files
<filename class="directory">$LFS/tools</filename> directory and all the files
therein, thus exposing these files to possible malicious manipulation.</para>
<para>To avoid this issue, you could add the <systemitem
class="username">lfs</systemitem> 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 IDs as on the host system. Better yet, change the
ownership of the <filename class="directory">/tools</filename> directory to
ownership of the <filename class="directory">$LFS/tools</filename> directory to
user <systemitem class="username">root</systemitem> by running the following
command:</para>
<screen><userinput>chown -R root:root /tools</userinput></screen>
<screen><userinput>chown -R root:root $LFS/tools</userinput></screen>
<para>Although the <filename class="directory">/tools</filename> directory can
be deleted once the LFS system has been finished, it can be retained to build
<para>Although the <filename class="directory">$LFS/tools</filename> directory
can be deleted once the LFS system has been finished, it can be retained to build
additional LFS systems <emphasis>of the same book version</emphasis>. How best
to backup <filename class="directory">/tools</filename> is a matter of
to backup <filename class="directory">$LFS/tools</filename> is a matter of
personal preference and is left as an exercise for the reader.</para>
</sect1>

4
general.ent
View File

@ -1,6 +1,6 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<!ENTITY version "SVN-20060422">
<!ENTITY releasedate "April 22, 2006">
<!ENTITY version "SVN-20060423">
<!ENTITY releasedate "April 23, 2006">
<!ENTITY milestone "6.2">
<!ENTITY generic-version "development"> <!-- Use "development", "testing", or "x.y[-pre{x}]" -->