From: "H. Peter Anvin" <hpa@zytor.com>
To: Roland Kuhn <rkuhn@e18.physik.tu-muenchen.de>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Andrey Borzenkov <arvidjaar@mail.ru>,
linux-kernel@vger.kernel.org
Subject: Re: Long file names in VFAT broken with iocharset=utf8
Date: Mon, 07 May 2007 14:12:32 -0700 [thread overview]
Message-ID: <463F9640.4080003@zytor.com> (raw)
In-Reply-To: <BD281C0E-5278-4944-ABF0-AF692325945C@e18.physik.tu-muenchen.de>
Roland Kuhn wrote:
>
> No, we don't. At least not when looking at the POSIX spec, which
> explicitly mentions _bytes_ and _not_ unicode characters. So, to be on
> the safe side, FAT filesystems would need to support a NAME_MAX of
> roughly 6*255+3=1533 bytes (not to mention the hassles of forbidden
> sequences, etc.; do we need to count zero-width characters?) and report
> it through pathconf() to userspace, then userspace could do with that
> whatever it liked.
>
> What happened to: "file names are just sequences of octets, excluding
> '/' and NUL"? Adding unicode parsing to the kernel is completely useless
> _and_ a big trouble maker.
>
"Filenames are just octets" have never applied to alien filesystems like
VFAT.
-hpa
next prev parent reply other threads:[~2007-05-07 21:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 17:51 Long file names in VFAT broken with iocharset=utf8 Andrey Borzenkov
2007-05-07 18:07 ` Roland Kuhn
2007-05-07 18:17 ` Andreas Schwab
2007-05-07 18:43 ` Andrey Borzenkov
2007-05-07 18:52 ` OGAWA Hirofumi
2007-05-07 18:27 ` OGAWA Hirofumi
2007-05-07 19:34 ` H. Peter Anvin
2007-05-07 19:59 ` Roland Kuhn
2007-05-07 21:01 ` OGAWA Hirofumi
2007-05-07 21:12 ` H. Peter Anvin [this message]
2007-05-09 10:27 ` Andrey Borzenkov
-- strict thread matches above, loose matches on Subject: below --
2007-05-08 4:43 Albert Cahalan
2007-05-08 8:38 ` Jan Engelhardt
2007-05-09 15:34 ` Albert Cahalan
2007-05-09 15:57 ` Andrey Borzenkov
2007-05-09 23:49 ` Albert Cahalan
[not found] <8ipOe-5KI-3@gated-at.bofh.it>
2007-05-08 16:21 ` Bodo Eggert
[not found] ` <8ityz-2Xz-31@gated-at.bofh.it>
[not found] ` <8iWqS-5Ba-15@gated-at.bofh.it>
[not found] ` <8iWKp-619-29@gated-at.bofh.it>
[not found] ` <8j4eK-QR-13@gated-at.bofh.it>
2007-05-10 14:49 ` Bodo Eggert
2007-05-10 14:59 ` Jan Engelhardt
2007-05-10 16:14 ` John Anthony Kazos Jr.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=463F9640.4080003@zytor.com \
--to=hpa@zytor.com \
--cc=arvidjaar@mail.ru \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=rkuhn@e18.physik.tu-muenchen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.