public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nerijus Baliunas <nerijus@users.sourceforge.net>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	linux-kernel@vger.kernel.org
Subject: Re[2]: [PATCH] vfat write wrong value into lcase flag
Date: Fri, 10 Aug 2001 16:09:06 +0200 (EET)	[thread overview]
Message-ID: <200108101425.QAA1285141@mail.takas.lt> (raw)
In-Reply-To: <87wv4er2kt.fsf@devron.myhome.or.jp> <200108082020.WAA1347968@mail.takas.lt> <874rrhf69p.fsf@devron.myhome.or.jp>
In-Reply-To: <874rrhf69p.fsf@devron.myhome.or.jp>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1586 bytes --]

On 10 Aug 2001 03:16:34 +0900 OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> wrote:

OH> Nerijus Baliunas <nerijus@users.sourceforge.net> writes:
OH> 
OH> > On 09 Aug 2001 00:30:58 +0900 OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> wrote:
OH> > 
OH> > OH> The current vfat is writeing wrong value into lcase flag.  It is
OH> > OH> writing the lowercase flag, although filename is uppercase.
OH> > 
OH> > Hello,
OH> > 
OH> > In December 1999 I sent my investigation about short filenames in vfat:
OH> 
OH> [...]
OH> 
OH> > I think Linux should create files like win98
OH> > (because NT shows them correctly) and show like NT.
OH> 
OH> The _current vfat_ uses the following rule.
OH> 
OH>   name                   attribute                         used direntry
OH> -----------------------------------------------------------------------------
OH> foo.txt  LONG_FILENAME, CASE_LOWER_BASE | CASE_LOWER_EXT         2
OH> foo.TXT  LONG_FILENAME, CASE_LOWER_BASE | CASE_LOWER_EXT         2
OH> FOO.txt  LONG_FILENAME, CASE_LOWER_BASE | CASE_LOWER_EXT         2
OH> FOO.TXT               , CASE_LOWER_BASE | CASE_LOWER_EXT         1
OH> Foo.TXT  LONG_FILENAME, CASE_LOWER_BASE | CASE_LOWER_EXT         2
OH> FOO.Txt  LONG_FILENAME, CASE_LOWER_BASE | CASE_LOWER_EXT         2
OH> 
OH> I missed something?

I don't know. Sorry, I didn't look at the code, but current (2.4.7) kernel still shows
filenames as I wrote in 1999. I am talking about filenames _without_ long entries.
Didn't test what current kernel writes, though.
I'm attaching floppy image, ungzip and loop mount it.

Regards,
Nerijus

[-- Attachment #2: fdd_vfat.gz --]
[-- Type: APPLICATION/X-GZIP, Size: 1961 bytes --]

  reply	other threads:[~2001-08-10 14:25 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
2001-08-10 14:09     ` Nerijus Baliunas [this message]
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=200108101425.QAA1285141@mail.takas.lt \
    --to=nerijus@users.sourceforge.net \
    --cc=hirofumi@mail.parknet.co.jp \
    --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