Changeset 8eeb6bc
- Timestamp:
- 09/30/2004 10:33:31 PM (20 years ago)
- Branches:
- 6.0
- Children:
- 0ffc1a4
- Parents:
- 343c80b
- Files:
-
- 10 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/adjusting.xml
r343c80b r8eeb6bc 51 51 <para>Be sure to visually inspect the specs file in order to verify the 52 52 intended changes have been made.</para> 53 54 <beginpage/> 53 55 54 56 <important><para>If working on a platform where the name of the -
chapter05/gcc-pass1.xml
r343c80b r8eeb6bc 58 58 from <command>gcc</command>'s include search path. This is not absolutely 59 59 essential, however, it helps to minimize the influence of the host 60 system.</para></listitem> 60 system.</para> 61 <beginpage/> 62 </listitem> 61 63 </varlistentry> 62 64 -
chapter05/introduction.xml
r343c80b r8eeb6bc 55 55 reminders.</para> 56 56 57 <beginpage/> 58 57 59 <para>Check one last time that the <envar>LFS</envar> environment 58 60 variable is set up properly:</para> -
chapter05/toolchaintechnotes.xml
r343c80b r8eeb6bc 104 104 checking what linker to use... /tools/i686-pc-linux-gnu/bin/ld</computeroutput></screen> 105 105 106 <beginpage/>107 106 <para>This is important for the reasons mentioned above. It also 108 107 demonstrates that GCC's configure script does not search the PATH … … 169 168 class="directory">/tools</filename>.</para> 170 169 171 <beginpage/>172 170 <para>Upon entering the chroot environment in <xref 173 171 linkend="chapter-building-system"/>, the first major package to be … … 177 175 toolchain defaults, then proceed in building the rest of the target 178 176 LFS system.</para> 177 178 <beginpage/> 179 179 180 180 <sect2> -
chapter06/devices.xml
r343c80b r8eeb6bc 61 61 62 62 <para>The <command>mount</command> commands executed above may result 63 in the following warning message: <computeroutput>can't open /etc/fstab: No 64 such file or directory</computeroutput>. This 65 file—<filename>/etc/fstab</filename>—has 66 not been created yet but is also not required for the file systems to 67 be properly mounted. As such, the warning can be safely ignored.</para> 63 in the following warning message:</para> 64 65 <para><blockquote><computeroutput>can't open /etc/fstab: No 66 such file or directory.</computeroutput></blockquote></para> 67 68 <para>This file—<filename>/etc/fstab</filename>—has not 69 been created yet but is also not required for the file systems to be 70 properly mounted. As such, the warning can be safely ignored.</para> 68 71 </sect2> 69 72 -
chapter06/udev.xml
r343c80b r8eeb6bc 73 73 in LFS) in response to hotplug events.</para> 74 74 <indexterm zone="ch-system-udev udev"><primary sortas="b-udev">udev</primary></indexterm> 75 < /listitem></varlistentry>75 <beginpage/></listitem></varlistentry> 76 76 77 77 <varlistentry id="udevd"> -
chapter07/profile.xml
r343c80b r8eeb6bc 58 58 <filename>/etc/inputrc</filename> file created earlier.</para> 59 59 60 <beginpage/>61 60 <para>Replace <replaceable>[ll]</replaceable> below with the 62 61 two-letter code for the desired language (e.g., <quote>en</quote>) and -
chapter07/udev.xml
r343c80b r8eeb6bc 65 65 realistic.</para> 66 66 </sect2> 67 68 <beginpage/> 67 69 68 70 <sect2> … … 125 127 class="directory">/dev</filename> entry for it.</para> 126 128 127 <beginpage/>128 129 <para>This brings us to one problem that exists with 129 130 <command>udev</command>, and likewise with <systemitem -
chapter07/usage.xml
r343c80b r8eeb6bc 57 57 appropriate services get killed and others get started.</para> 58 58 59 <beginpage/>60 59 <para>The real scripts are in <filename 61 60 class="directory">/etc/rc.d/init.d</filename>. They do the actual -
prologue/audience.xml
r343c80b r8eeb6bc 54 54 it, or barbecue it.</para> 55 55 56 <beginpage/> 57 56 58 <para>Another analogy that we can use is that of comparing LFS with a 57 59 finished house. LFS provides the skeletal plan of a house, but it is up
Note:
See TracChangeset
for help on using the changeset viewer.