Changeset a4495da


Ignore:
Timestamp:
04/17/2005 11:03:59 PM (19 years ago)
Author:
Jim Gifford <jim@…>
Children:
af9b59e
Parents:
a2d4711a
Message:

Text updates from Matt

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/branches/multi-arch/BOOK@4993 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:
6 edited

Legend:

Unmodified
Added
Removed

  • chapter01/changelog.xml

    ra2d4711a ra4495da  
    8585
    8686<itemizedlist>
    87 <listitem><para>April 12, 2005 [manuel]</para>
     87<listitem><para>April 17, 2005 [manuel]</para>
    8888<itemizedlist>
    8989<listitem><para>Updated: Arch: All - Updated the stylesheets to use
    9090DocBook-XSL 1.68.1.</para></listitem>
     91</itemizedlist>
     92</listitem>
     93</itemizedlist>
     94
     95<itemizedlist>
     96<listitem><para>April 16, 2005 [matt]</para>
     97<itemizedlist>
     98<listitem><para>Updated: Arch: All - Updated documentation. Contributed by
     99Ken Moffat, Alexander Patrakov, Andrew Benton, Allard Welter, and Peter Ennis</para></listitem>
    91100</itemizedlist>
    92101</listitem>

  • chapter01/how.xml

    ra2d4711a ra4495da  
    3838to build a first pass of the toolchain, including Binutils and GCC
    3939(first pass basically means these two core packages will be
    40 re-installed a second time). The programs from these packages will be
    41 linked statically in order to be used independently of the host
    42 system. The next step is to build Glibc, the C library. Glibc will be
    43 compiled by the toolchain programs built in the first pass. Then, a
    44 second pass of the toolchain will be built. This time, the toolchain
    45 will be dynamically linked against the newly built Glibc. The
    46 remaining <xref linkend="chapter-temporary-tools"/> packages are built
    47 using this second pass toolchain. When this is done, the LFS
    48 installation process will no longer depend on the host distribution,
    49 with the exception of the running kernel.</para>
     40re-installed a second time). The next step is to build Glibc, the C library.
     41Glibc will be compiled by the toolchain programs built in the first pass. Then,
     42a second pass of the toolchain will be built. This time, the toolchain will be
     43dynamically linked against the newly built Glibc. The remaining
     44<xref linkend="chapter-temporary-tools"/> packages are built using this second
     45pass toolchain. When this is done, the LFS installation process will no longer
     46depend on the host distribution, with the exception of the running kernel.
     47</para>
    5048
    5149<para>While this may initially seem like a lot of work to get away
    5250from a host distribution, a full technical explanation is provided at
    53 the beginning of <xref linkend="chapter-temporary-tools"/>,
    54 including notes on the differences between
    55 statically and dynamically-linked programs.</para>
     51the beginning of <xref linkend="chapter-temporary-tools"/>.</para>
    5652
    5753<para>In <xref linkend="chapter-building-system"/>, the full LFS system is

  • chapter06/hotplug.xml

    ra2d4711a ra4495da  
    4747
    4848<screen><userinput>rm -f /etc/hotplug/net.agent</userinput></screen>
    49 
    50 <para>Create a file that is necessary for the logging of hotplug events:</para>
    51 
    52 <screen><userinput>touch /var/log/hotplug/events</userinput></screen>
    5349
    5450<para>Create a directory for storing firmware that can be loaded by

  • chapter07/profile.xml

    ra2d4711a ra4495da  
    6262two-letter code for the desired language (e.g., <quote>en</quote>) and
    6363<replaceable>[CC]</replaceable> with the two-letter code for the
    64 appropriate country (e.g., <quote>GB</quote>). It may also be
    65 necessary to specify (and this is actually the preferred form) the
    66 character encoding (e.g.  <quote>iso8859-1</quote>) after a dot (so
    67 that the result is <quote>en_GB.iso8859-1</quote>).  Issue the
    68 following command for more information:</para>
    69 
    70 <screen><userinput>man 3 setlocale</userinput></screen>
     64appropriate country (e.g., <quote>GB</quote>).
     65<replaceable>[charmap]</replaceable> should be replaced with the
     66canonical charmap for your chosen locale.</para>
    7167
    7268<para>The list of all locales supported by Glibc can be obtained by running
    … …  
    7470
    7571<screen><userinput>locale -a</userinput></screen>
     72
     73<para>Locales can have a number of synonyms, e.g. <quote>ISO-8859-1</quote> is
     74also referred to as <quote>iso8859-1</quote> and <quote>iso88591</quote>.
     75Some applications cannot handle the various synonyms correctly, so it is safest
     76to choose the canonical name for a particular locale.  To determine the
     77canonical name, run the following command, where
     78<replaceable>[locale name]</replaceable> is the output given by
     79<command>locale -a</command> for your preferred locale
     80(<quote>en_GB.iso88591</quote> in our example).</para>
     81
     82<screen><userinput>LC_ALL=<replaceable>[locale name]</replaceable> locale charmap</userinput></screen>
     83
     84<para>For the <quote>en_GB.iso88591</quote> locale, the above command
     85will print:</para>
     86
     87<screen>ISO-8859-1</screen>
     88
     89<para>This results in in a final locale setting of <quote>en_GB.ISO-8859-1</quote>.</para>
    7690
    7791<para>Once the proper locale settings have been determined, create the
    … …  
    8195<literal># Begin /etc/profile
    8296
    83 export LC_ALL=<replaceable>[ll]</replaceable>_<replaceable>[CC]</replaceable>
    84 export LANG=<replaceable>[ll]</replaceable>_<replaceable>[CC]</replaceable>
     97export LANG=<replaceable>[ll]</replaceable>_<replaceable>[CC]</replaceable>.<replaceable>[charmap]</replaceable>
    8598export INPUTRC=/etc/inputrc
    8699

  • chapter07/udev.xml

    ra2d4711a ra4495da  
    3131resides entirely in memory and does not take up any disk space).
    3232Device nodes do not require much disk space, so the memory that is
    33 used in negligable.</para>
     33used is negligible.</para>
    3434
    3535<sect2>
    … …  
    153153<title>Handling Hotpluggable/Dynamic Devices</title>
    154154
    155 <para>When you plug in a device, such a Universal Serial Bus (USB) MP3 player, the kernel
     155<para>When you plug in a device, such as a Universal Serial Bus (USB) MP3 player, the kernel
    156156recognizes that the device is now connected and generates a hotplug
    157157event. If the driver is already loaded (either because it was compiled
    … …  
    160160be called upon to create the relevant device node(s) according to the
    161161<systemitem class="filesystem">sysfs</systemitem> data available in
    162 <filename class="directory">/sys</filename>.  If the driver for the
    163 just plugged in device is available as a module but currently unloaded,
    164 then attaching the device to the system will only cause the kernel's
    165 bus driver to generate a hotplug event that notifies userspace of the
    166 new device connection and it not being attached to a driver. In
    167 effect, nothing happens and the device itself is not usable
    168 yet.</para>
    169 
    170 <para>If building a system that has a lot of drivers compiled as
    171 modules rather than directly built into the kernel, using the
    172 <command>S05modules</command> may not be practical. The Hotplug
    173 package (see <ulink url="http://linux-hotplug.sourceforge.net/"/>) can
    174 be beneficial in these cases. When the Hotplug package is installed,
    175 it will respond to the aforementioned kernel's bus driver hotplug
    176 events. The Hotplug package will load the appropriate module and make
    177 this device available by creating the device node(s) for it.</para>
     162<filename class="directory">/sys</filename>.</para>
     163
     164<para>If the driver for the just plugged in device is available as a module but
     165currently unloaded, the Hotplug package will load the appropriate module
     166and make this device available by creating the device node(s) for it.</para>
    178167</sect2>
    179168

  • prologue/foreword.xml

    ra2d4711a ra4495da  
    88<?dbhtml filename="foreword.html"?>
    99
    10 <para>My adventures in Linux began six years ago when I downloaded and
     10<para>My adventures in Linux began in 1998 when I downloaded and
    1111installed my first distribution. After working with it for awhile, I
    1212discovered issues I definitely would have liked to see improved upon.
    … …  
    3838Linux community, it became apparent that there was sustained interest
    3939in the ideas set forth in my Linux adventures. Such custom-built LFS
    40 systems not only to meet user specifications and requirements, but
     40systems serve not only to meet user specifications and requirements, but
    4141also serve as an ideal learning opportunity for programmers and system
    4242administrators to enhance their Linux skills. Out of this broadened
Note: See TracChangeset for help on using the changeset viewer.