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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0705101654480.24536@yvahk01.tjqt.qr>
Date:	Thu, 10 May 2007 16:59:44 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Bodo Eggert <7eggert@....de>
cc:	Albert Cahalan <acahalan@...il.com>,
	Andrey Borzenkov <arvidjaar@...l.ru>,
	hirofumi@...l.parknet.co.jp, linux-kernel@...r.kernel.org,
	hpa@...or.com
Subject: Re: Long file names in VFAT broken with iocharset=utf8


On May 10 2007 16:49, Bodo Eggert wrote:
>
>Just because you limit yourself to 80 chars minus "ls -l"-clutter, this is
>no reason why I shouldn't use long filenames. If I need to handle these
>filenames, I can enlarge the terminal window or read the next line.
>
>E.g.: I have a music file named "artist - title.ext", where the artist
>name is 103 characters long, using abbreviations. In order to enter that
>name, I have to press seven keys, including the escape character.
>There is nothing unreasonable in using that name.

What name would that be? I cannot dream up any IME that outputs _that_
many characters for that few keystrokes. Even with CJ(K), 7 keystrokes can
make at most 21 bytes if I had to take a good guess.


	Jan
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/