From: Andreas Schwab <schwab@suse.de>
To: Roland Kuhn <rkuhn@e18.physik.tu-muenchen.de>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
hirofumi@mail.parknet.co.jp, linux-kernel@vger.kernel.org
Subject: Re: Long file names in VFAT broken with iocharset=utf8
Date: Mon, 07 May 2007 20:17:15 +0200 [thread overview]
Message-ID: <jebqgwpkgk.fsf@sykes.suse.de> (raw)
In-Reply-To: <60F72760-C801-4F60-BF47-C661B4B5BE26@e18.physik.tu-muenchen.de> (Roland Kuhn's message of "Mon\, 7 May 2007 20\:07\:26 +0200")
Roland Kuhn <rkuhn@e18.physik.tu-muenchen.de> writes:
> PATH_MAX specifically counts _bytes_ not characters, so UTF-8 does not
> matter. ISTR that PATH_MAX was 256 at some point, but I just quickly
> grepped /usr/include and found various mention of 4096, so where's the
> central repository for this configuration item? A hard-
> coded value of 256 somewhere inside the kernel smells like a bug.
There is PATH_MAX and there is NAME_MAX, and only the latter (which is
260 for vfat) matters here.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-05-07 18:17 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 [this message]
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
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=jebqgwpkgk.fsf@sykes.suse.de \
--to=schwab@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox