|
|
Log in / Subscribe / Register

File name encoding issues in /boot

File name encoding issues in /boot

Posted Jan 30, 2012 19:09 UTC (Mon) by gbrun (guest, #82611)
Parent article: The case for the /usr merge

Another point why it might be a good idea to put /boot and the main system on different partitions.

GRUB2 and other boot loaders which "understand" file systems must make assumptions about the character set encoding in file systems which do not store file names in UTF8/UNICODE, such as AFFS, SFS or HFS.

OK, I admit that I see little purpose to assign non-ASCII names to files relevant to the boot loader.

Nevertheless, separating /boot from / allows to use an ASCII/UNICODE-friendly encoding in /boot which Bootloaders will support in any case, and to use a filesystem with the weirdest possible LC_CTYPE encoding on / if one desires.

to post comments

File name encoding issues in /boot

Posted Jan 31, 2012 10:34 UTC (Tue) by mpr22 (subscriber, #60784) [Link] (1 responses)

OK, I admit that I see little purpose to assign non-ASCII names to files relevant to the boot loader.

Being able to label the files in one's native language seems perfectly reasonable to me, and shouldn't be restricted to people whose native language can be written acceptably in ASCII :)

File name encoding issues in /boot

Posted Jan 31, 2012 12:28 UTC (Tue) by Cyberax (✭ supporter ✭, #52523) [Link]

Well, my native language is not written using ASCII and I can't say I ever wanted to name kernel images in my native language.

Now, menu entries in GRUB are another matter but GRUB2 supports non-ASCII for menus just fine.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds