On Fri, Apr 25, 2014 at 8:25 PM, Julian Andres Klode <j...@debian.org> wrote:
> The Debian kernels are configured > CONFIG_FAT_DEFAULT_IOCHARSET="utf8" > which causes iocharset=utf8 to be the default here, rather than > iocharset=ascii. I can now > either work around that in the gummiboot package by one of > > (1) unlink() and then rename() > (2) do a stupid glob() [Bb][Oo][Tt][Xx]64.[Ee][Ff][Ii] (and the same for the > rest of the path) > > I don't think you'd like either of those upstream, so you might want to change > the generator to pass iocharset=ascii. We do not (apart from me) use that > generator, though, so it won't help Debian -- we generate a fstab entry during > system installation instead. Are we sure that this is the expected kernel behaviour? Seems pretty odd to be caused by the charset option: With ascii all is fine: # mount /dev/sda1 /boot -o iocharset=ascii # touch /boot/EFI/A # rm /boot/EFI/a rm: remove regular empty file ‘/boot/EFI/a’? y With UTF8 it breaks: # mount /dev/sda1 /boot -o iocharset=utf8 # touch /boot/EFI/A # rm /boot/EFI/a rm: cannot remove ‘/boot/EFI/a’: No such file or directory And it gets even more weird here: All is fine: [root@lon /]# touch /boot/EFI/a [root@lon /]# touch /boot/EFI/A This fails: [root@lon /]# touch /boot/EFI/A [root@lon /]# touch /boot/EFI/a touch: cannot touch ‘/boot/EFI/a’: File exists -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
