From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Nerijus Baliunas <nerijus@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vfat write wrong value into lcase flag
Date: 10 Aug 2001 03:16:34 +0900 [thread overview]
Message-ID: <874rrhf69p.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <87wv4er2kt.fsf@devron.myhome.or.jp> <200108082020.WAA1347968@mail.takas.lt>
In-Reply-To: <200108082020.WAA1347968@mail.takas.lt>
Nerijus Baliunas <nerijus@users.sourceforge.net> writes:
> On 09 Aug 2001 00:30:58 +0900 OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> wrote:
>
> OH> The current vfat is writeing wrong value into lcase flag. It is
> OH> writing the lowercase flag, although filename is uppercase.
>
> Hello,
>
> In December 1999 I sent my investigation about short filenames in vfat:
[...]
>
> I think Linux should create files like win98
> (because NT shows them correctly) and show like NT.
The _current vfat_ uses the following rule.
name attribute used direntry
-----------------------------------------------------------------------------
foo.txt LONG_FILENAME, CASE_LOWER_BASE | CASE_LOWER_EXT 2
foo.TXT LONG_FILENAME, CASE_LOWER_BASE | CASE_LOWER_EXT 2
FOO.txt LONG_FILENAME, CASE_LOWER_BASE | CASE_LOWER_EXT 2
FOO.TXT , CASE_LOWER_BASE | CASE_LOWER_EXT 1
Foo.TXT LONG_FILENAME, CASE_LOWER_BASE | CASE_LOWER_EXT 2
FOO.Txt LONG_FILENAME, CASE_LOWER_BASE | CASE_LOWER_EXT 2
I missed something?
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2001-08-09 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 15:30 [PATCH] vfat write wrong value into lcase flag OGAWA Hirofumi
2001-08-08 20:14 ` Nerijus Baliunas
2001-08-09 18:16 ` OGAWA Hirofumi [this message]
2001-08-10 14:09 ` Re[2]: " Nerijus Baliunas
2001-08-10 16:56 ` OGAWA Hirofumi
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=874rrhf69p.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=nerijus@users.sourceforge.net \
/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