Re: Long file names in VFAT broken with iocharset=utf8

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Andrey Borzenkov <[email protected]> writes:

> On Monday 07 May 2007, Andreas Schwab wrote:
>> Roland Kuhn <[email protected]> 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.
>>
>
> Do you imply that Linux is unable to represent full VFAT names (255 UCS2 
> charaters) by design? Hmm ... testing ... looks like it,

Yes. But I think it's not design, and it should be fixed.
-- 
OGAWA Hirofumi <[email protected]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux