Changeset fa21b3d for chapter08

Timestamp:

01/06/2006 01:59:08 AM (18 years ago)

Author:

Jeremy Huntwork <jhuntwork@…>

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, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, 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:

abf1f62

Parents:

60e34b5

Message:

Initial support of UTF-8. Thanks Alexander Patrakov.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7245 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Location:

chapter08

Files:

• fstab.xml (modified) (1 diff)
• kernel.xml (modified) (2 diffs)

chapter08/fstab.xml

@@ -66 +66 @@
   <filename>/etc/sysconfig/modules</filename>.</para>
 
+  <para>Filesystems with MS-DOS or Windows origin (i.e.: vfat, ntfs, smbfs, cifs,
+  iso9660, udf) need the <quote>iocharset</quote> mount option in order for
+  non-ASCII characters in file names to be interpreted properly. The value
+  of this option should be the same as the character set of your locale,
+  adjusted in such a way that the kernel understands it. This works if the
+  relevant character set definition (found under File systems -&gt;
+  Native Language Support) has been compiled into the kernel
+  or built as a module. The <quote>codepage</quote> option is also needed for
+  vfat and smbfs filesystems. It
+  should be set to the codepage number used under MS-DOS in your country. E.g.,
+  in order to mount USB flash drives, a ru_RU.KOI8-R user would need the
+  following line in <filename>/etc/fstab</filename>:</para>
+
+<screen>/dev/sda1    /media/flash vfat noauto,user,quiet,showexec,iocharset=koi8r,codepage=866 0 0</screen>
+
+  <para>The corresponding line for ru_RU.UTF-8 users is:</para>
+
+<screen>/dev/sda1    /media/flash vfat noauto,user,quiet,showexec,iocharset=utf8,codepage=866 0 0</screen>
+
+  <note><para>In the latter case, the kernel emits the following message:</para>
+
+<screen><computeroutput>FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!</computeroutput></screen>
+
+  <para>This negative recommendation should be ignored, since all other values
+  of the <quote>iocharset</quote> option result in wrong display of filenames in
+  UTF-8 locales.</para></note>
+
+  <para>It is also possible to specify default codepage and iocharset values for
+  some filesystems during kernel configuration. The relevant parameters
+  are named
+  <quote>Default NLS Option</quote> (CONFIG_NLS_DEFAULT),
+  <quote>Default Remote NLS Option</quote> (CONFIG_SMB_NLS_DEFAULT),
+  <quote>Default codepage for FAT</quote> (CONFIG_FAT_DEFAULT_CODEPAGE), and
+  <quote>Default iocharset for FAT</quote> (CONFIG_FAT_DEFAULT_IOCHARSET).
+  There is no way to specify these settings for the
+  ntfs filesystem at kernel compilation time.</para>
+  <!-- Personally, I find it more foolproof to always specify the iocharset and
+  codepage in /etc/fstab for MS-based filesystems - Alexander E. Patrakov -->
+
 </sect1>

chapter08/kernel.xml

@@ -49 +49 @@
     configures the kernel.</para>
 
+    <para>By default, the Linux kernel generates wrong sequences of bytes when
+    dead keys are used in UTF-8 keyboard mode. Also, one cannot copy and paste
+    non-ASCII characters when UTF-8 mode is active. Fix these issues with the
+    patch:</para>
+
+<screen><userinput>patch -Np1 -i ../&linux-utf8-patch;</userinput></screen>
+
     <para>Prepare for compilation by running the following command:</para>
 
@@ -58 +65 @@
     un-tarring.</para>
 
-    <para>If, in <xref linkend="ch-scripts-console" role=","/> it was decided to
-    compile the keymap into the kernel, issue the command below:</para>
-
-<screen role="nodump"><userinput>loadkeys -m /usr/share/kbd/keymaps/<replaceable>[path to  keymap]</replaceable> &gt; \
-    drivers/char/defkeymap.c</userinput></screen>
-
-    <para>For example, if using a Dutch keyboard, use
-    <filename>/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz</filename>.</para>
+    <!-- Support for compiling a keymap into the kernel is deliberately removed -->
 
     <para>Configure the kernel via a menu-driven interface. BLFS has some