Date: Sun, 05 Mar 2017 18:02:12 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 217440] FAT32 formatted USB stick with files written by PS4 - Invalid argument, unable to list directory contents Message-ID: <bug-217440-3630-3lXmyGb6Le@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-217440-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-217440-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217440 Warner Losh <imp@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |imp@FreeBSD.org --- Comment #11 from Warner Losh <imp@FreeBSD.org> --- There's no way for the kernel to know the locale. That's purely a userland construct. msdosfs does have a notion of how to decode things, but it has to be done at mount time. And there's likely a bug or two in the translations that's causing the issu= es that you're seeing. These bugs are likely in the MSDOSFS code. I suspect that Conrad's notion of switching to UTF-8 internally is the right way to go, but worry about compatibility. We should ask the folks that set = it to ISO-8859-1 why that specific choice, and if we can shift the interpretat= ion over to UTF-8. Eg, was iso-8859-1 just a placeholder that then got perverted into a format that Windows never produces, or was there a deeper reason... --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217440-3630-3lXmyGb6Le>