| 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
| ||
|
Date: Tue, 8 May 2007 00:43:24 -0400 From: "Albert Cahalan" <acahalan@...il.com> To: 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 Andrey Borzenkov writes: > This was posted in one of Russian forums. It was not possible to > archive (under Linux, using tar) vfat directory where files had > long Russian names (really long - over 150 - 170 characters) - tar > returned stat failure. When looking with plain ls, file names > appeared truncated. I have an idea to deal with this, but first a rant... At two bytes per character, you get 127 characters in a filename. That's wider than the standard 80-column display, and far wider than the 28 or 29 characters that an "ls -l" has room for. In a GUI file manager or file dialog box, you'll have to scroll sideways. In a web browser directory listing, you'll almost certainly have to scroll sideways. Must of this even applies to Windows tools. In other words, this is user error. Somebody thought that a filename was a place to store a document, probably a README file. What next, shall we MIME-encode an icon into the filename? Fix: the vfat driver should use the 8.3 name for such files. - 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/
Powered by blists - more mailing lists