From: "Albert Cahalan" <acahalan@gmail.com>
To: arvidjaar@mail.ru, hirofumi@mail.parknet.co.jp,
linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: Re: Long file names in VFAT broken with iocharset=utf8
Date: Tue, 8 May 2007 00:43:24 -0400 [thread overview]
Message-ID: <787b0d920705072143q63e56f23j18c6b0dbfb270883@mail.gmail.com> (raw)
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.
next reply other threads:[~2007-05-08 4:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 4:43 Albert Cahalan [this message]
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.
-- strict thread matches above, loose matches on Subject: below --
2007-05-07 17:51 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
2007-05-09 10:27 ` Andrey Borzenkov
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=787b0d920705072143q63e56f23j18c6b0dbfb270883@mail.gmail.com \
--to=acahalan@gmail.com \
--cc=arvidjaar@mail.ru \
--cc=hirofumi@mail.parknet.co.jp \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®