Changeset 76c3eca in clfs-sysroot
- Timestamp:
- Jan 5, 2009, 12:45:16 AM (16 years ago)
- Branches:
- master
- Children:
- 7400ff8
- Parents:
- 9da6c48
- Location:
- BOOK
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
BOOK/cross-tools/x86/variables.xml
r9da6c48 r76c3eca 25 25 xpointer="xpointer(//*[@os='c'])"/> 26 26 27 <screen os="d"><userinput>export CLFS_TARGET="{target triplet}"</userinput></screen> 27 <screen os="d"><userinput>export CLFS_TARGET="[target triplet]"</userinput></screen> 28 29 <para os="t1">Replace [target triplet] with the appropriate machine triplet 30 using the table at the bottom of the page.</para> 28 31 29 32 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" -
BOOK/final-preps/aboutclfs.xml
r9da6c48 r76c3eca 6 6 ]> 7 7 8 <sect1 id="ch-final-preps-about lfs">9 <?dbhtml filename="about lfs.html"?>8 <sect1 id="ch-final-preps-aboutclfs"> 9 <?dbhtml filename="aboutclfs.html"?> 10 10 11 <title>About $ CLFS</title>11 <title>About ${CLFS}</title> 12 12 13 13 <para>Throughout this book, the environment variable <envar>CLFS</envar> will … … 26 26 27 27 <para>Having this variable set is beneficial in that commands such as 28 <command>install -d ${CLFS}/tools</command> can be typed literally. The shell28 <command>install -dv ${CLFS}/tools</command> can be typed literally. The shell 29 29 will automatically replace <quote>${CLFS}</quote> with 30 30 <quote>/mnt/clfs</quote> (or whatever the variable was set to) when it -
BOOK/final-preps/addinguser.xml
r9da6c48 r76c3eca 22 22 23 23 <screen><userinput>groupadd clfs 24 useradd -s /bin/bash -g clfs -m -k /dev/null clfs</userinput></screen> 24 useradd -s /bin/bash -g clfs -d /home/clfs clfs 25 mkdir -pv /home/clfs 26 chown -v clfs:clfs /home/clfs</userinput></screen> 25 27 26 28 <variablelist> … … 40 42 <para>This option adds user <systemitem class="username">clfs</systemitem> 41 43 to group <systemitem class="groupname">clfs</systemitem>.</para> 42 </listitem>43 </varlistentry>44 45 <varlistentry>46 <term><parameter>-m</parameter></term>47 <listitem>48 <para>This creates a home directory for <systemitem49 class="username">clfs</systemitem>.</para>50 </listitem>51 </varlistentry>52 53 <varlistentry>54 <term><parameter>-k /dev/null</parameter></term>55 <listitem>56 <para>This parameter prevents possible copying of files from a skeleton57 directory (default is <filename class="directory">/etc/skel</filename>)58 by changing the input location to the special null device.</para>59 44 </listitem> 60 45 </varlistentry> -
BOOK/final-system/common/iproute2.xml
r9da6c48 r76c3eca 56 56 57 57 <varlistentry> 58 <term><parameter>DESTDIR=/</parameter></term>59 <listitem>60 <para>This option overrides the default DESTDIR of /usr, so that61 that the IPRoute2 binaries will be installed into62 <filename class="directory">/sbin</filename>. This is the correct63 location according to the FHS, because some of the IPRoute2 binaries64 are used by the CLFS-Bootscripts package.</para>65 </listitem>66 </varlistentry>67 68 <varlistentry>69 58 <term><parameter>DOCDIR=/usr/share/doc/iproute2 MANDIR=/usr/share/man</parameter></term> 70 59 <listitem> 71 <para>The DESTDIR= /parameter would cause documentation to be72 installed into /share/doc and /share/man . These options ensure73 the docs are installed to the correct locations.</para>60 <para>The DESTDIR=${CLFS} parameter would cause documentation to be 61 installed into /share/doc and /share/man on the CLFS system. 62 These options ensure the docs are installed to the correct locations.</para> 74 63 </listitem> 75 64 </varlistentry> -
BOOK/partitioning/common/creatingfilesystem.xml
r9da6c48 r76c3eca 31 31 <para>Some host distributions use custom features in their filesystem 32 32 creation tools (E2fsprogs). This can cause problems when booting into 33 your new CLFS , as those features will not be supported by the LFS-installed34 E2fsprogs; you will get an error similar to <computeroutput>unsupported35 filesystem features, upgrade your e2fsprogs</computeroutput>. To check36 if your host system uses custom enhancements, run the following37 command:</para>33 your new CLFS system, as those features will not be supported by the 34 CLFS-installed E2fsprogs; you will get an error similar to 35 <computeroutput>unsupported filesystem features, upgrade your 36 e2fsprogs</computeroutput>. To check if your host system uses custom 37 enhancements, run the following command:</para> 38 38 39 39 <screen os="f"><userinput>debugfs -R feature /dev/<replaceable>[xxx]</replaceable></userinput></screen>
Note:
See TracChangeset
for help on using the changeset viewer.