- Timestamp:
- 06/12/2020 08:42:32 PM (4 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 9e7475a
- Parents:
- 96f04d7
- Location:
- chapter09
- Files:
-
- 8 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter09/etcshells.xml
r96f04d7 ra3d0817 24 24 login shells on the system. Applications use this file to determine 25 25 whether a shell is valid. For each shell a single line should be 26 present, consisting of the shell's path ,relative to the root of the26 present, consisting of the shell's path relative to the root of the 27 27 directory structure (/).</para> 28 28 -
chapter09/inputrc.xml
r96f04d7 ra3d0817 16 16 17 17 <para>The <filename>inputrc</filename> file is the configuration file for 18 the Readline library, which provides editing capabilities while the user is18 the readline library, which provides editing capabilities while the user is 19 19 entering a line from the terminal. It works by translating keyboard inputs 20 into specific actions. Readline is used by Bash and most other shells as20 into specific actions. Readline is used by bash and most other shells as 21 21 well as many other applications.</para> 22 22 23 23 <para>Most people do not need user-specific functionality so the command 24 24 below creates a global <filename>/etc/inputrc</filename> used by everyone who 25 logs in. If you later decide you need to override the defaults on a per -user25 logs in. If you later decide you need to override the defaults on a per user 26 26 basis, you can create a <filename>.inputrc</filename> file in the user's home 27 27 directory with the modified mappings.</para> -
chapter09/introduction.xml
r96f04d7 ra3d0817 19 19 order but, at the same time, be executed as fast as possible.</para> 20 20 21 <!-- <para>In the packages that were installed in Chapter 6, there were two22 different boot systems installed. LFS provides the ability to easily23 select which system the user wants to use and to compare and contrast the24 two systems by actually running each system on the local computer. The25 advantages and disadvantages of these systems is presented below.</para>-->26 27 21 <sect2 id='sysv-desc'> 28 22 <title>System V</title> … … 40 34 can be run by the user:</para> 41 35 42 <literallayout> 43 0 — halt 36 <literallayout>0 — halt 44 37 1 — Single user mode 45 38 2 — Multiuser, without networking … … 47 40 4 — User definable 48 41 5 — Full multiuser mode with display manager 49 6 — reboot 50 </literallayout> 42 6 — reboot</literallayout> 51 43 52 44 <para>The usual default run level is 3 or 5.</para> … … 70 62 <itemizedlist> 71 63 <listitem> 72 <para> Slower to boot. A medium speed base LFS system64 <para>May be slower to boot. A medium speed base LFS system 73 65 takes 8-12 seconds where the boot time is measured from the 74 66 first kernel message to the login prompt. Network … … 95 87 96 88 </sect2> 97 <!--98 <sect2 id='sysd-desc'>99 <title>Systemd</title>100 89 101 <para>Systemd is a group of interconnected programs that handles system and 102 individual process requests. It provides a dependency system between 103 various entities called "units". It automatically addresses dependencies 104 between units and can execute several startup tasks in parallel. It 105 provides login, inetd, logging, time, and networking services. </para> 90 </sect1> 106 91 107 <bridgehead renderas="sect3">Advantages</bridgehead>108 109 <itemizedlist>110 <listitem>111 <para>Used on many established distributions by default.</para>112 </listitem>113 114 <listitem>115 <para>There is extensive documentation.116 See <ulink url="http://www.freedesktop.org/wiki/Software/systemd/"/>.</para>117 </listitem>118 119 <listitem>120 <para>Parallel execution of boot processes. A medium speed121 base LFS system takes 6-10 seconds from kernel start to a122 login prompt. Network connectivity is typically established123 about 2 seconds after the login prompt. More complex startup124 procedures may show a greater speedup when compared to System V.</para>125 </listitem>126 127 <listitem>128 <para>Implements advanced features such as control groups to129 manage related processes.</para>130 </listitem>131 132 <listitem>133 <para>Maintains backward compatibility with System V programs134 and scripts.</para>135 </listitem>136 </itemizedlist>137 138 <bridgehead renderas="sect3">Disadvantages</bridgehead>139 140 <itemizedlist>141 <listitem>142 <para>There is a substantial learning curve.</para>143 </listitem>144 145 <listitem>146 <para>Some advanced features such as dbus or cgroups cannot be147 disabled if they are not otherwise needed.</para>148 </listitem>149 150 <listitem>151 <para>Although implemented as several executable programs152 the user cannot choose to implement only the portions desired.</para>153 </listitem>154 155 <listitem>156 <para>Due to the nature of using compiled programs, systemd is157 more difficult to debug.</para>158 </listitem>159 160 <listitem>161 <para>Logging is done in a binary format. Extra tools must162 be used to process logs or additional processes must be implemented163 to duplicate traditional logging programs.</para>164 </listitem>165 166 </itemizedlist>167 168 </sect2>169 -->170 <!--171 <sect2 id='sysv'>172 <title>Selecting a Boot Method</title>173 174 <para>Selecting a boot method in LFS is relatively easy.175 Both systems are installed side-by-side. The only task needed is to176 ensure the files that are needed by the system have the correct names.177 The following scripts do that.</para>178 179 <screen><userinput remap="install">cat > /usr/sbin/set-systemd << "EOF"180 #! /bin/bash181 182 ln -svfn init-systemd /sbin/init183 ln -svfn init.d-systemd /etc/init.d184 185 for tool in halt poweroff reboot runlevel shutdown telinit; do186 ln -sfvn ${tool}-systemd /sbin/${tool}187 ln -svfn ${tool}-systemd.8 /usr/share/man/man8/${tool}.8188 done189 190 echo "Now reboot with /sbin/reboot-sysv"191 EOF192 193 chmod 0744 /usr/sbin/set-systemd194 195 cat > /usr/sbin/set-sysv << "EOF"196 #! /bin/bash197 198 ln -sfvn init-sysv /sbin/init199 ln -svfn init.d-sysv /etc/init.d200 201 for tool in halt poweroff reboot runlevel shutdown telinit; do202 ln -sfvn ${tool}-sysv /sbin/${tool}203 ln -svfn ${tool}-sysv.8 /usr/share/man/man8/${tool}.8204 done205 206 echo "Now reboot with /sbin/reboot-systemd"207 EOF208 209 chmod 0744 /usr/sbin/set-sysv</userinput></screen>210 211 <note><para>The comment about the correct command to reboot in the212 above scripts is correct. The reboot command for the current boot213 system must be used after the script changes the default reboot command.214 </para></note>215 216 <para>Now set the desired boot system. The default is System V:</para>217 218 <screen><userinput remap="install">/usr/sbin/set-sysv</userinput></screen>219 220 <para>Changing the boot system can be done at any time by running the221 appropriate script above and rebooting.</para>222 223 </sect2>224 -->225 </sect1> -
chapter09/network.xml
r96f04d7 ra3d0817 14 14 <primary sortas="d-network">network</primary> 15 15 <secondary>configuring</secondary></indexterm> 16 <!-- 17 <para>This section only applies if a network card is to be 18 configured.</para> 19 20 <para>If a network card will not be used, there is likely no need to create 21 any configuration files relating to network cards. If that is the case, you 22 will need to remove the <filename class="symlink">network</filename> symlinks 23 from all run-level directories (<filename 24 class="directory">/etc/rc.d/rc*.d</filename>) after the bootscripts are 25 installed in <xref linkend="ch-config-bootscripts"/>.</para> 26 --> 16 27 17 <sect2> 28 18 <title>Creating Network Interface Configuration Files</title> … … 38 28 the filename be <emphasis>ifconfig</emphasis>.</para> 39 29 40 <note><para>If the procedure in the previous section was not used, Udev30 <note><para>If the procedure in the previous section was not used, udev 41 31 will assign network card interface names based on system physical 42 32 characteristics such as enp2s1. If you are not sure what your interface … … 65 55 <para>If the <envar>ONBOOT</envar> variable is set to <quote>yes</quote> the 66 56 System V network script will bring up the Network Interface Card (NIC) during 67 booting of the system. If set to anything but <quote>yes</quote> the NIC57 the system boot process. If set to anything but <quote>yes</quote> the NIC 68 58 will be ignored by the network script and not be automatically brought up. 69 59 The interface can be manually started or stopped with the -
chapter09/profile.xml
r96f04d7 ra3d0817 104 104 before the telephone number in order to get into the country. If any of the 105 105 commands above fail with a message similar to the one shown below, this means 106 that your locale was either not installed in Chapter 6 or is not supported by107 the default installation of Glibc.</para>106 that your locale was either not installed in <xref linkend="ch-system-glibc"/> 107 or is not supported by the default installation of Glibc.</para> 108 108 109 109 <screen><computeroutput>locale: Cannot set LC_* to default locale: No such file or directory</computeroutput></screen> … … 115 115 116 116 <!-- FIXME: the xlib example will became obsolete real soon --> 117 < para>Some packages beyond LFS may also lack support for your chosen locale. One117 <!--<para>Some packages beyond LFS may also lack support for your chosen locale. One 118 118 example is the X library (part of the X Window System), which outputs the 119 119 following error message if the locale does not exactly match one of the character … … 129 129 For example, one would have to change "de_DE.ISO-8859-15@euro" to 130 130 "de_DE@euro" in order to get this locale recognized by Xlib.</para> 131 131 --> 132 132 <para>Other packages can also function incorrectly (but may not necessarily 133 133 display any error messages) if the locale name does not meet their expectations. … … 146 146 EOF</userinput></screen> 147 147 148 <para>The <quote>C</quote> (default) and <quote>en_US </quote> (the recommended148 <para>The <quote>C</quote> (default) and <quote>en_US.utf8</quote> (the recommended 149 149 one for United States English users) locales are different. <quote>C</quote> 150 150 uses the US-ASCII 7-bit character set, and treats bytes with the high bit set -
chapter09/symlinks.xml
r96f04d7 ra3d0817 22 22 Intel and Realtek, the network card manufactured by Intel may become eth0 23 23 and the Realtek card becomes eth1. In some cases, after a reboot the cards 24 get renumbered the other way around.</para>24 could get renumbered the other way around.</para> 25 25 26 26 <para>In the new naming scheme, typical network device names would then … … 45 45 <title>Creating Custom Udev Rules</title> 46 46 47 <para>The naming scheme can be customized by creating custom Udev47 <para>The naming scheme can be customized by creating custom udev 48 48 rules. A script has been included that generates the initial rules. 49 49 Generate these rules by running:</para> … … 69 69 the hardware ID nor the driver is used to determine which name to give an 70 70 interface; this information is only for reference. The second line is the 71 Udev rule that matches this NIC and actually assigns it a name.</para>72 73 <para>All Udev rules are made up of several keys, separated by commas and71 udev rule that matches this NIC and actually assigns it a name.</para> 72 73 <para>All udev rules are made up of several keys, separated by commas and 74 74 optional whitespace. This rule's keys and an explanation of each of them 75 75 are as follows:</para> … … 77 77 <itemizedlist> 78 78 <listitem> 79 <para><literal>SUBSYSTEM=="net"</literal> - This tells Udev to ignore79 <para><literal>SUBSYSTEM=="net"</literal> - This tells udev to ignore 80 80 devices that are not network cards.</para> 81 81 </listitem> 82 82 <listitem> 83 <para><literal>ACTION=="add"</literal> - This tells Udev to ignore this83 <para><literal>ACTION=="add"</literal> - This tells udev to ignore this 84 84 rule for a uevent that isn't an add ("remove" and "change" uevents also 85 85 happen, but don't need to rename network interfaces).</para> 86 86 </listitem> 87 87 <listitem> 88 <para><literal>DRIVERS=="?*"</literal> - This exists so that Udev will88 <para><literal>DRIVERS=="?*"</literal> - This exists so that udev will 89 89 ignore VLAN or bridge sub-interfaces (because these sub-interfaces do 90 90 not have drivers). These sub-interfaces are skipped because the name … … 97 97 <listitem> 98 98 <para><literal>ATTR{type}=="1"</literal> - This ensures the rule only 99 matches the primary interface in the case of certain wireless drivers ,99 matches the primary interface in the case of certain wireless drivers 100 100 which create multiple virtual interfaces. The secondary interfaces are 101 101 skipped for the same reason that VLAN and bridge sub-interfaces are … … 104 104 <listitem> 105 105 <para><literal>NAME</literal> - The value of this key is the name that 106 Udev will assign to this interface.</para>106 udev will assign to this interface.</para> 107 107 </listitem> 108 108 </itemizedlist> … … 134 134 the physical path to the CD or DVD device. Second, it can operate in 135 135 <quote>by-id</quote> mode (default for IDE and SCSI devices), where the 136 rules it creates depend on identification strings stored in the CD or DVD137 device itself. The path is determined by Udev's <command>path_id</command>136 rules it creates depend on identification strings stored on the CD or DVD 137 device itself. The path is determined by udev's <command>path_id</command> 138 138 script, and the identification strings are read from the hardware by its 139 139 <command>ata_id</command> or <command>scsi_id</command> programs, depending … … 160 160 should not use by-path persistence, because each time the device is plugged 161 161 into a new external port, its physical path will change. All 162 externally-connected devices will have this problem if you write Udev rules162 externally-connected devices will have this problem if you write udev rules 163 163 to recognize them by their physical path; the problem is not limited to CD 164 164 and DVD drives.</para></important> 165 165 166 <para>If you wish to see the values that the Udev scripts will use, then166 <para>If you wish to see the values that the udev scripts will use, then 167 167 for the appropriate CD-ROM device, find the corresponding directory under 168 168 <filename class="directory">/sys</filename> (e.g., this can be … … 183 183 <quote>by-id</quote> or <quote>by-path</quote>):</para> 184 184 185 <screen role="nodump"><userinput>sed - i -e 's/"write_cd_rules"/"write_cd_rules <replaceable>mode</replaceable>"/' \186 /etc/udev/rules.d/83-cdrom-symlinks.rules</userinput></screen>185 <screen role="nodump"><userinput>sed -e 's/"write_cd_rules"/"write_cd_rules <replaceable>mode</replaceable>"/' \ 186 -i /etc/udev/rules.d/83-cdrom-symlinks.rules</userinput></screen> 187 187 188 188 <para>Note that it is not necessary to create the rules files or symlinks 189 at this time ,because you have bind-mounted the host's190 <filename class="directory">/dev</filename> directory into the LFS system ,189 at this time because you have bind-mounted the host's 190 <filename class="directory">/dev</filename> directory into the LFS system 191 191 and we assume the symlinks exist on the host. The rules and symlinks will 192 192 be created the first time you boot your LFS system.</para> … … 194 194 <para>However, if you have multiple CD-ROM devices, then the symlinks 195 195 generated at that time may point to different devices than they point to on 196 your host ,because devices are not discovered in a predictable order. The196 your host because devices are not discovered in a predictable order. The 197 197 assignments created when you first boot the LFS system will be stable, so 198 198 this is only an issue if you need the symlinks on both systems to point to … … 213 213 <filename>/dev/video0</filename> refers to the camera and 214 214 <filename>/dev/video1</filename> refers to the tuner, and sometimes 215 after a reboot the order changes to the opposite one.215 after a reboot the order changes. 216 216 For all classes of hardware except sound cards and network cards, this is 217 fixable by creating Udev rules for custom persistent symlinks.217 fixable by creating udev rules for custom persistent symlinks. 218 218 The case of network cards is covered separately in 219 219 <xref linkend="ch-config-network"/>, and sound card configuration can … … 238 238 <literal> 239 239 # Persistent symlinks for webcam and tuner 240 KERNEL=="video*", ATTRS{idProduct}=="1910", ATTRS{idVendor}=="0d81", \ 241 SYMLINK+="webcam" 242 KERNEL=="video*", ATTRS{device}=="0x036f", ATTRS{vendor}=="0x109e", \ 243 SYMLINK+="tvtuner" 240 KERNEL=="video*", ATTRS{idProduct}=="1910", ATTRS{idVendor}=="0d81", SYMLINK+="webcam" 241 KERNEL=="video*", ATTRS{device}=="0x036f", ATTRS{vendor}=="0x109e", SYMLINK+="tvtuner" 244 242 </literal> 245 243 EOF</userinput></screen> -
chapter09/udev.xml
r96f04d7 ra3d0817 16 16 </indexterm> 17 17 18 <para>In <xref linkend="chapter-building-system"/>, we installed the Udev18 <para>In <xref linkend="chapter-building-system"/>, we installed the udev 19 19 package when <phrase revision="sysv">eudev</phrase> 20 20 <phrase revision="systemd">systemd</phrase> was built. Before we go into the … … 31 31 the world.</para> 32 32 33 <para>Using the Udev method, only those devices which are detected by the33 <para>Using the udev method, only those devices which are detected by the 34 34 kernel get device nodes created for them. Because these device nodes will be 35 35 created each time the system boots, they will be stored on a <systemitem … … 136 136 might contain the string 137 137 <quote>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</quote>. 138 The default rules provided with Udev will cause <command>udevd</command>138 The default rules provided with udev will cause <command>udevd</command> 139 139 to call out to <command>/sbin/modprobe</command> with the contents of the 140 140 <envar>MODALIAS</envar> uevent environment variable (which should be the … … 150 150 151 151 <para>The kernel itself is also able to load modules for network 152 protocols, filesystems and NLS support on demand.</para>152 protocols, filesystems, and NLS support on demand.</para> 153 153 154 154 </sect3> … … 178 178 bus driver properly exports the necessary aliases to <systemitem 179 179 class="filesystem">sysfs</systemitem>. In other cases, one should 180 arrange module loading by other means. With Linux-&linux-version;, Udev is180 arrange module loading by other means. With Linux-&linux-version;, udev is 181 181 known to load properly-written drivers for INPUT, IDE, PCI, USB, SCSI, 182 182 SERIO, and FireWire devices.</para> 183 183 184 184 <para>To determine if the device driver you require has the necessary 185 support for Udev, run <command>modinfo</command> with the module name as185 support for udev, run <command>modinfo</command> with the module name as 186 186 the argument. Now try locating the device directory under 187 187 <filename class="directory">/sys/bus</filename> and check whether there is … … 191 191 class="filesystem">sysfs</systemitem>, the driver supports the device and 192 192 can talk to it directly, but doesn't have the alias, it is a bug in the 193 driver. Load the driver without the help from Udev and expect the issue193 driver. Load the driver without the help from udev and expect the issue 194 194 to be fixed later.</para> 195 195 … … 207 207 208 208 <sect3> 209 <title>A kernel module is not loaded automatically, and Udev is not209 <title>A kernel module is not loaded automatically, and udev is not 210 210 intended to load it</title> 211 211 … … 215 215 <emphasis>snd-pcm</emphasis> by making the sound cards available to OSS 216 216 applications), configure <command>modprobe</command> to load the wrapper 217 after Udev loads the wrapped module. To do this, add a217 after udev loads the wrapped module. To do this, add a 218 218 <quote>softdep</quote> line to the corresponding 219 219 <filename>/etc/modprobe.d/<replaceable><filename></replaceable>.conf</filename> … … 280 280 <para>Further text assumes that the driver is built statically into the 281 281 kernel or already loaded as a module, and that you have already checked 282 that Udev doesn't create a misnamed device.</para>282 that udev doesn't create a misnamed device.</para> 283 283 284 284 <para>Udev has no information needed to create a device node if a kernel … … 298 298 <title>Device naming order changes randomly after rebooting</title> 299 299 300 <para>This is due to the fact that Udev, by design, handles uevents and300 <para>This is due to the fact that udev, by design, handles uevents and 301 301 loads modules in parallel, and thus in an unpredictable order. This will 302 302 never be <quote>fixed</quote>. You should not rely upon the kernel device 303 303 names being stable. Instead, create your own rules that make symlinks with 304 304 stable names based on some stable attributes of the device, such as a 305 serial number or the output of various *_id utilities installed by Udev.305 serial number or the output of various *_id utilities installed by udev. 306 306 See <xref linkend="ch-config-symlinks"/> and 307 307 <xref linkend="ch-config-network"/> for examples.</para> -
chapter09/usage.xml
r96f04d7 ra3d0817 236 236 <para>For information on kernel module loading and udev, see 237 237 <xref linkend="module-loading"/>.</para> 238 <!--239 <sect3>240 <title>Module Loading</title>241 242 <para>Device drivers compiled as modules may have aliases built into them.243 Aliases are visible in the output of the <command>modinfo</command>244 program and are usually related to the bus-specific identifiers of devices245 supported by a module. For example, the <emphasis>snd-fm801</emphasis>246 driver supports PCI devices with vendor ID 0x1319 and device ID 0x0801,247 and has an alias of <quote>pci:v00001319d00000801sv*sd*bc04sc01i*</quote>.248 For most devices, the bus driver exports the alias of the driver that249 would handle the device via <systemitem250 class="filesystem">sysfs</systemitem>. E.g., the251 <filename>/sys/bus/pci/devices/0000:00:0d.0/modalias</filename> file252 might contain the string253 <quote>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</quote>.254 The default rules provided with Udev will cause <command>udevd</command>255 to call out to <command>/sbin/modprobe</command> with the contents of the256 <envar>MODALIAS</envar> uevent environment variable (which should be the257 same as the contents of the <filename>modalias</filename> file in sysfs),258 thus loading all modules whose aliases match this string after wildcard259 expansion.</para>260 261 <para>In this example, this means that, in addition to262 <emphasis>snd-fm801</emphasis>, the obsolete (and unwanted)263 <emphasis>forte</emphasis> driver will be loaded if it is264 available. See below for ways in which the loading of unwanted drivers can265 be prevented.</para>266 267 <para>The kernel itself is also able to load modules for network268 protocols, filesystems and NLS support on demand.</para>269 270 </sect3>271 272 <sect3>273 <title>Handling Hotpluggable/Dynamic Devices</title>274 275 <para>When you plug in a device, such as a Universal Serial Bus (USB) MP3276 player, the kernel recognizes that the device is now connected and277 generates a uevent. This uevent is then handled by278 <command>udevd</command> as described above.</para>279 280 </sect3>281 -->282 238 </sect2> 283 239 … … 294 250 hardware clock's time to the local time using the 295 251 <filename>/etc/localtime</filename> file (which tells the 296 <command>hwclock</command> program which timezone t he user is in). There is no252 <command>hwclock</command> program which timezone to use). There is no 297 253 way to detect whether or not the hardware clock is set to UTC, so this 298 254 needs to be configured manually.</para> 299 255 300 <para>The <command>setclock</command> is run via256 <para>The <command>setclock</command> program is run via 301 257 <application>udev</application> when the kernel detects the hardware 302 258 capability upon boot. It can also be run manually with the stop parameter to … … 316 272 <para>Change the value of the <envar>UTC</envar> variable below 317 273 to a value of <parameter>0</parameter> (zero) if the hardware clock 318 is <emphasis> not</emphasis> set to UTC time.</para>274 is <emphasis>NOT</emphasis> set to UTC time.</para> 319 275 320 276 <para>Create a new file <filename>/etc/sysconfig/clock</filename> by running … … 337 293 time zones, UTC, and the <envar>TZ</envar> environment variable.</para> 338 294 339 <note><para>The CLOCKPARAMS and UTC paramaters may be alternativelyset295 <note><para>The CLOCKPARAMS and UTC paramaters may also be set 340 296 in the <filename>/etc/sysconfig/rc.site</filename> file.</para></note> 341 297 … … 353 309 354 310 <para>This section discusses how to configure the <command>console</command> 355 bootscript that sets up the keyboard map, console font and console kernel log311 bootscript that sets up the keyboard map, console font, and console kernel log 356 312 level. If non-ASCII characters (e.g., the copyright sign, the British pound 357 313 sign and Euro symbol) will not be used and the keyboard is a U.S. one, much … … 506 462 <para>Due to the use of a 512-glyph LatArCyrHeb-16 font in the previous 507 463 example, bright colors are no longer available on the Linux console unless 508 a framebuffer is used. If one wants to have bright colors without 464 a framebuffer is used. If one wants to have bright colors without a 509 465 framebuffer and can live without characters not belonging to his language, 510 466 it is still possible to use a language-specific 256-glyph font, as … … 549 505 languages, because there accents are added to unaccented ASCII 550 506 characters, or two ASCII characters are composed together. However, in 551 UTF-8 mode it is a problem ,e.g., for the Greek language, where one507 UTF-8 mode it is a problem; e.g., for the Greek language, where one 552 508 sometimes needs to put an accent on the letter <quote>alpha</quote>. 553 509 The solution is either to avoid the use of UTF-8, or to install the … … 557 513 558 514 <listitem> 559 <para>For Chinese, Japanese, Korean and some other languages, the Linux515 <para>For Chinese, Japanese, Korean, and some other languages, the Linux 560 516 console cannot be configured to display the needed characters. Users 561 517 who need such languages should install the X Window System, fonts that 562 518 cover the necessary character ranges, and the proper input method (e.g., 563 SCIM, itsupports a wide variety of languages).</para>519 SCIM, supports a wide variety of languages).</para> 564 520 </listitem> 565 521 … … 572 528 the Linux text console localization. It has nothing to do with setting 573 529 the proper keyboard layout and terminal fonts in the X Window System, with 574 ssh sessions or with a serial console. In such situations, limitations530 ssh sessions, or with a serial console. In such situations, limitations 575 531 mentioned in the last two list items above do not apply.</para> 576 532 </note> … … 586 542 </indexterm> 587 543 588 <para>At times, it is desir edto create files at boot time. For instance,544 <para>At times, it is desirable to create files at boot time. For instance, 589 545 the <filename class="directory">/tmp/.ICE-unix</filename> directory 590 may be desired. This can be done by creating an entry in the546 is often needed. This can be done by creating an entry in the 591 547 <filename>/etc/sysconfig/createfiles</filename> configuration script. 592 548 The format of this file is embedded in the comments of the default
Note:
See TracChangeset
for help on using the changeset viewer.