From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: James Vega <vega_james@lycos.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fat32 all upper-case filename problem
Date: Mon, 05 Apr 2004 22:02:44 +0900 [thread overview]
Message-ID: <87k70utw5n.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <4070910E.7020808@lycos.com>
James Vega <vega_james@lycos.com> writes:
> debil% touch /usbdrive/CASE
> debil% ls /usbdrive
> case
> debil% ls /usbdrive/CASE
> /usbdrive/CASE
> debil% ls /usbdrive/case
> /usbdrive/case
> debil% umount /usbdrive && mount /usbdrive
> debil% ls /usbdrive/case
> /usbdrive/case
> debil% ls /usbdrive/CASE
> ls: /usbdrive/CASE: No such file or directory
Are you using the "iocharset=utf8" or CONFIG_NLS_DEFAULT="utf8"?
If so, it's buggy.
Please don't use it for now.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2004-04-05 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 22:49 fat32 all upper-case filename problem James Vega
2004-04-05 10:30 ` Marco Roeland
2004-04-05 19:40 ` James Vega
2004-04-05 13:02 ` OGAWA Hirofumi [this message]
2004-04-05 19:44 ` James Vega
2004-04-05 21:39 ` James Vega
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=87k70utw5n.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=vega_james@lycos.com \
/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