[lfs] branch trunk updated: fstab: drop a stale para and fix the desc for iocharset

"Git Owner" ([email protected] via lfs-book Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.book
Message-ID <177558375272.28714.10997534868286984224@rivendell.linuxfromscratch.org>
This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch trunk
in repository lfs.

The following commit(s) were added to refs/heads/trunk by this push:
     new 45fd83b87 fstab: drop a stale para and fix the desc for iocharset
45fd83b87 is described below

commit 45fd83b871a86784a601bffb1f5edbc37fab7ca0
Author: Xi Ruoyao <[email protected]>
AuthorDate: Wed Apr 8 01:34:37 2026 +0800

    fstab: drop a stale para and fix the desc for iocharset
    
    The iocharset option has nothing to do with what the firmware will see.
    It only changes the way the kernel reports the file names to the
    user-space.  So techincally it should match the locale, we're lucky here
    because most common locales treat 7-bit ASCII in the same way.
    
    P.S. the UEFI spec says the file names stored onto the ESP (controlled
    by codepage instead of iocharset) must be either (7-bit) ASCII or UCS-2.
    CP437 actually has more characters than ASCII (it's "DOS extended 8-bit
    ASCII") so if you create a file with 8-bit name in ESP you may wreck
    havoc.  UCS-2 is a subset of UTF-16 which is CP1200, but Linux does not
    support CP1200 (yet) and even if we can use CP1200 it still contains
    more characters than UCS-2 so the issue will still exist.  We can only
    trust the boot loader installers (like grub-install) and the user for
    avoiding 8-bit file names.
---
 chapter10/fstab.xml | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/chapter10/fstab.xml b/chapter10/fstab.xml
index c5128ebbd..43822d8c2 100644
--- a/chapter10/fstab.xml
+++ b/chapter10/fstab.xml
@@ -99,10 +99,14 @@ EOF</userinput></screen>
 EOF</userinput></screen>
 
   <para>
-    The <literal>iso8859-1</literal> IO charset is used here since UEFI
-    firmware implementations search for <filename
-    class="directory">\EFI\BOOT\BOOT...EFI</filename>, which in a
-    case-sensitive environment would not be satisfied. 
+    The <literal>iso8859-1</literal> IO charset is used here as we'll
+    enable it as a part of the kernel UEFI configuration in
+    <xref linkend='ch-bootable-kernel'/>.  Technically the IO charset should
+    match your locale as we've discussed above.  However the name of all the
+    files in the ESP only contains 7-bit ASCII characters, so things will
+    be OK as long as the character set for your locale treats 7-bit ASCII
+    characters in the same way as ISO-8859-1.  For example, UTF-8 is such
+    a character set.
   </para>
 
   <note>
@@ -115,9 +119,9 @@ EOF</userinput></screen>
     </para>
   </note>
 
-    <para>In the latter case, the kernel emits the following message:</para>
+<!--<para>In the latter case, the kernel emits the following message:</para>
 
-<!--  <note>
+    <note>
 <screen><computeroutput>FAT: utf8 is not a recommended IO charset for FAT filesystems,
     filesystem will be case sensitive!</computeroutput></screen>
 

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-book
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.