[Clfs-commits] commit: r4337 - in /branches/clfs-sysroot/BOOK: cross-tools/x86/variables.xml final-preps/aboutclfs.xml final-preps/addinguser.xml final-system/common/iproute2.xml partitioning/common/creatingfilesystem.xml
svn at cross-lfs.org
svn at cross-lfs.org
Mon Jan 5 00:45:17 PST 2009
Author: chris at beaker67.com
Date: Mon Jan 5 08:45:16 2009
New Revision: 4337
Log:
CLFS sysroot normally uses DESTDIR anyway
Modified:
branches/clfs-sysroot/BOOK/cross-tools/x86/variables.xml
branches/clfs-sysroot/BOOK/final-preps/aboutclfs.xml
branches/clfs-sysroot/BOOK/final-preps/addinguser.xml
branches/clfs-sysroot/BOOK/final-system/common/iproute2.xml
branches/clfs-sysroot/BOOK/partitioning/common/creatingfilesystem.xml
Modified: branches/clfs-sysroot/BOOK/cross-tools/x86/variables.xml
==============================================================================
--- branches/clfs-sysroot/BOOK/cross-tools/x86/variables.xml (original)
+++ branches/clfs-sysroot/BOOK/cross-tools/x86/variables.xml Mon Jan 5 08:45:16 2009
@@ -24,7 +24,10 @@
href="../arm/variables.xml"
xpointer="xpointer(//*[@os='c'])"/>
-<screen os="d"><userinput>export CLFS_TARGET="{target triplet}"</userinput></screen>
+<screen os="d"><userinput>export CLFS_TARGET="[target triplet]"</userinput></screen>
+
+ <para os="t1">Replace [target triplet] with the appropriate machine triplet
+ using the table at the bottom of the page.</para>
<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
href="../arm/variables.xml"
Modified: branches/clfs-sysroot/BOOK/final-preps/aboutclfs.xml
==============================================================================
--- branches/clfs-sysroot/BOOK/final-preps/aboutclfs.xml (original)
+++ branches/clfs-sysroot/BOOK/final-preps/aboutclfs.xml Mon Jan 5 08:45:16 2009
@@ -5,10 +5,10 @@
%general-entities;
]>
-<sect1 id="ch-final-preps-aboutlfs">
- <?dbhtml filename="aboutlfs.html"?>
+<sect1 id="ch-final-preps-aboutclfs">
+ <?dbhtml filename="aboutclfs.html"?>
- <title>About $CLFS</title>
+ <title>About ${CLFS}</title>
<para>Throughout this book, the environment variable <envar>CLFS</envar> will
be used several times. It is paramount that this variable is always defined.
@@ -25,7 +25,7 @@
<screen><userinput>export CLFS=/mnt/clfs</userinput></screen>
<para>Having this variable set is beneficial in that commands such as
- <command>install -d ${CLFS}/tools</command> can be typed literally. The shell
+ <command>install -dv ${CLFS}/tools</command> can be typed literally. The shell
will automatically replace <quote>${CLFS}</quote> with
<quote>/mnt/clfs</quote> (or whatever the variable was set to) when it
processes the command line.</para>
Modified: branches/clfs-sysroot/BOOK/final-preps/addinguser.xml
==============================================================================
--- branches/clfs-sysroot/BOOK/final-preps/addinguser.xml (original)
+++ branches/clfs-sysroot/BOOK/final-preps/addinguser.xml Mon Jan 5 08:45:16 2009
@@ -21,7 +21,9 @@
issue the following commands to add the new user:</para>
<screen><userinput>groupadd clfs
-useradd -s /bin/bash -g clfs -m -k /dev/null clfs</userinput></screen>
+useradd -s /bin/bash -g clfs -d /home/clfs clfs
+mkdir -pv /home/clfs
+chown -v clfs:clfs /home/clfs</userinput></screen>
<variablelist>
<title>The meaning of the command line options:</title>
@@ -39,23 +41,6 @@
<listitem>
<para>This option adds user <systemitem class="username">clfs</systemitem>
to group <systemitem class="groupname">clfs</systemitem>.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><parameter>-m</parameter></term>
- <listitem>
- <para>This creates a home directory for <systemitem
- class="username">clfs</systemitem>.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><parameter>-k /dev/null</parameter></term>
- <listitem>
- <para>This parameter prevents possible copying of files from a skeleton
- directory (default is <filename class="directory">/etc/skel</filename>)
- by changing the input location to the special null device.</para>
</listitem>
</varlistentry>
Modified: branches/clfs-sysroot/BOOK/final-system/common/iproute2.xml
==============================================================================
--- branches/clfs-sysroot/BOOK/final-system/common/iproute2.xml (original)
+++ branches/clfs-sysroot/BOOK/final-system/common/iproute2.xml Mon Jan 5 08:45:16 2009
@@ -55,22 +55,11 @@
<title>The meaning of the make option:</title>
<varlistentry>
- <term><parameter>DESTDIR=/</parameter></term>
- <listitem>
- <para>This option overrides the default DESTDIR of /usr, so that
- that the IPRoute2 binaries will be installed into
- <filename class="directory">/sbin</filename>. This is the correct
- location according to the FHS, because some of the IPRoute2 binaries
- are used by the CLFS-Bootscripts package.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
<term><parameter>DOCDIR=/usr/share/doc/iproute2 MANDIR=/usr/share/man</parameter></term>
<listitem>
- <para>The DESTDIR=/ parameter would cause documentation to be
- installed into /share/doc and /share/man. These options ensure
- the docs are installed to the correct locations.</para>
+ <para>The DESTDIR=${CLFS} parameter would cause documentation to be
+ installed into /share/doc and /share/man on the CLFS system.
+ These options ensure the docs are installed to the correct locations.</para>
</listitem>
</varlistentry>
</variablelist>
Modified: branches/clfs-sysroot/BOOK/partitioning/common/creatingfilesystem.xml
==============================================================================
--- branches/clfs-sysroot/BOOK/partitioning/common/creatingfilesystem.xml (original)
+++ branches/clfs-sysroot/BOOK/partitioning/common/creatingfilesystem.xml Mon Jan 5 08:45:16 2009
@@ -30,11 +30,11 @@
<note os="e">
<para>Some host distributions use custom features in their filesystem
creation tools (E2fsprogs). This can cause problems when booting into
- your new CLFS, as those features will not be supported by the LFS-installed
- E2fsprogs; you will get an error similar to <computeroutput>unsupported
- filesystem features, upgrade your e2fsprogs</computeroutput>. To check
- if your host system uses custom enhancements, run the following
- command:</para>
+ your new CLFS system, as those features will not be supported by the
+ CLFS-installed E2fsprogs; you will get an error similar to
+ <computeroutput>unsupported filesystem features, upgrade your
+ e2fsprogs</computeroutput>. To check if your host system uses custom
+ enhancements, run the following command:</para>
<screen os="f"><userinput>debugfs -R feature /dev/<replaceable>[xxx]</replaceable></userinput></screen>
More information about the Clfs-commits
mailing list