Context Navigation

r9fcb5e4	rb71fa50
27	27	url="http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>. A pre-made
28	28	<filename>/etc/sysconfig/console</filename> file with known settings for
29		several countries was installed with the LFS-Bootscripts package, so the
	29	several countries was installed with the CLFS-Bootscripts package, so the
30	30	relevant section can be uncommented if the country is supported. If still
31	31	in doubt, look in the <filename class="directory">/usr/share/kbd</filename>

bootscripts/common/introduction.xml

r9fcb5e4	rb71fa50
11	11	<title>Introduction</title>
12	12
13		<para>This chapter details how to install and configure the LFS-Bootscripts
	13	<para>This chapter details how to install and configure the CLFS-Bootscripts
14	14	package. Most of these scripts will work without modification, but a few
15	15	require additional configuration files because they deal with

r9fcb5e4	rb71fa50
58	58
59	59	<para>The <envar>SERVICE</envar> variable defines the method used for
60		obtaining the IP address. The LFS-Bootscripts package has a modular IP
	60	obtaining the IP address. The CLFS-Bootscripts package has a modular IP
61	61	assignment format, and creating additional files in the <filename
62	62	class="directory">/etc/sysconfig/network-devices/services</filename>

-              r9fcb5e4
+              rb71fa50
   from Glibc.</para>
   <para>Some packages beyond LFS may also lack support for your chosen locale.
+  <para>Some packages beyond CLFS may also lack support for your chosen locale.
   One example is the X library (part of the X Window System), which outputs
   the following error message:</para>
 …
   require additional steps and additional patches because many applications
   tend to not work properly under such conditions. These steps and patches
   are not included in the LFS book and such locales are not yet supported
   by LFS.</para>
+  are not included in the CLFS book and such locales are not yet supported
+  by CLFS.</para>
 </sect1>

-              r9fcb5e4
+              rb71fa50
   <?dbhtml filename="udev.html"?>
   <title>Device and Module Handling on an LFS System</title>
+  <title>Device and Module Handling on a CLFS System</title>
   <indexterm zone="ch-scripts-udev">
 …
     the rules specified in the files within the <filename
     class="directory">/etc/udev/rules.d/</filename> directory. These are
     numbered in a similar fashion to the LFS-Bootscripts package. If
+    numbered in a similar fashion to the CLFS-Bootscripts package. If
     <command>udev</command> can't find a rule for the device it is creating,
     it will default permissions to <emphasis>660</emphasis> and ownership to
 …
     this method will not work because the device node does not exist until
     the module is loaded. To solve this, the <command>S05modules</command>
     bootscript was added to the LFS-Bootscripts package, along with the
+    bootscript was added to the CLFS-Bootscripts package, along with the
     <filename>/etc/sysconfig/modules</filename> file. By adding module
     names to the <filename>modules</filename> file, these modules will be

-              r9fcb5e4
+              rb71fa50
   different from one system to another, so it cannot be assumed that
   because things worked in one particular Linux distribution, they should work
   the same in LFS too. LFS has its own way of doing things, but it
+  the same in CLFS too. CLFS has its own way of doing things, but it
   respects generally accepted standards.</para>
 …
   <para>Feel free to modify the way the boot process works (after all,
   it is your own LFS system). The files given here are an example of how
+  it is your own CLFS system). The files given here are an example of how
   it can be done.</para>

Note: See TracChangeset for help on using the changeset viewer.