From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#33999: CP437: Invalid Argument on init Date: Sat, 19 Jan 2019 11:19:24 +0100 Message-ID: <87zhrxq79v.fsf@gnu.org> References: <20190109200804.5619d668@scratchpost.org> <87tvi8vpds.fsf@gnu.org> <20190118235945.19009d9e@scratchpost.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:59297) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gknjP-0001LI-QR for bug-guix@gnu.org; Sat, 19 Jan 2019 05:20:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gknjO-0006h7-TP for bug-guix@gnu.org; Sat, 19 Jan 2019 05:20:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:38033) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gknjO-0006gq-PU for bug-guix@gnu.org; Sat, 19 Jan 2019 05:20:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gknjO-0004wf-H0 for bug-guix@gnu.org; Sat, 19 Jan 2019 05:20:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20190118235945.19009d9e@scratchpost.org> (Danny Milosavljevic's message of "Fri, 18 Jan 2019 23:59:45 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Danny Milosavljevic Cc: 33999@debbugs.gnu.org, Bryan Ferris Hi, Danny Milosavljevic skribis: > On Wed, 16 Jan 2019 12:00:15 +0100 > Ludovic Court=C3=A8s wrote: > >> Glibc has the ability to bring in statically-linked gconv modules, so we >> could in theory build a custom glibc for the statically-linked >> =E2=80=98fsck.fat=E2=80=99, but that doesn=E2=80=99t sound great. >>=20 >> Thoughts? > > Reading the dosfstools source, I found that there is already a fallback > if the codepage conversion does not work, so I don't think we have to > change anything there (see dosfstools-4.1/src/file.c in function > "put_char"). > > But according to Bryan, even mounting *without* checking the UEFI partiti= on > doesn't work. > > There's something else up (I very much doubt that mounting requires iconv= -- > since the mounting happens in the Linux kernel and not in the GNU userland > at runtime). Ah so it must be the charset conversion kernel module that=E2=80=99s missin= g? How can we reproduce the issue? Is there a way to mark the VFAT file system as requiring a specific file name encoding? (I=E2=80=99ve never had troubles mounting my UEFI partition.) Ludo=E2=80=99.