public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: 11 Aug 2001 01:56:26 +0900	[thread overview]
Message-ID: <87vgjvyhtx.fsf_-_@devron.myhome.or.jp> (raw)
In-Reply-To: <87wv4er2kt.fsf@devron.myhome.or.jp> <200108082020.WAA1347968@mail.takas.lt> <874rrhf69p.fsf@devron.myhome.or.jp> <200108101425.QAA1285141@mail.takas.lt>
In-Reply-To: <200108101425.QAA1285141@mail.takas.lt>

[-- Attachment #1: Type: text/plain, Size: 2161 bytes --]

Nerijus Baliunas <nerijus@users.sourceforge.net> writes:

> 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.

Thanks for sending floppy image.

This floppy image contains following directory entry:
(this floppy image forgot testing extension name)

  name                   attribute                         used direntry
-----------------------------------------------------------------------------
LINUP    LONG_FILENAME, CASE_LOWER_BASE | CASE_LOWER_EXT         2
LINLOW                , CASE_LOWER_BASE | CASE_LOWER_EXT         1
DOSUP                 ,                                          1
DOSLOW                ,                                          1
98UP                  ,                                          1
98low    LONG_FILENAME,                                          2
W2KUP                 ,                                          1
W2KLOW                , CASE_LOWER_BASE                          1
NTUP                  ,                                          1
NTLOW                 , CASE_LOWER_BASE                          1

linux-2.4.8-pre8:
-----------------------------------------------------------------------------
LINUP                 , CASE_LOWER_BASE | CASE_LOWER_EXT         1
linlow   LONG_FILENAME, CASE_LOWER_BASE | CASE_LOWER_EXT         2

default, convert the shortname to lowercase:
  $ mount -t vfat fdd_vfat /mnt -o loop
  $ ls /mnt
  98low  98up  LINUP  doslow  dosup  linlow  ntlow  ntup  w2klow  w2kup

nocase option, use the win9x rule for display (doesn't support CASE_* flags):
  $ mount -t vfat fdd_vfat /mnt -o loop,nocase
  $ ls /mnt
  98UP  98low  DOSLOW  DOSUP  LINLOW  LINUP  NTLOW  NTUP  W2KLOW  W2KUP

2.4.8-pre8 is useing the win9x rule for create. But attribute must
change to 0.

Now, I writing the lower/win95/winnt/mixed rule on -ac tree.
Please help to test the following patch, if you interests.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

[-- Attachment #2: vfat_shortname-2.4.7-ac10.diff.gz --]
[-- Type: application/octet-stream, Size: 6655 bytes --]

      reply	other threads:[~2001-08-10 16:57 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     ` Re[2]: " Nerijus Baliunas
2001-08-10 16:56       ` OGAWA Hirofumi [this message]

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=87vgjvyhtx.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