mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ioe-lkml@rameria.de>
To: linux-kernel@vger.kernel.org
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	Horms <horms@verge.net.au>,
	333776@bugs.debian.org
Subject: Re: Bug#333776: linux-2.6: vfat driver in 2.6.12 is not properly case-insensitive
Date: Sat, 29 Oct 2005 16:45:02 +0200	[thread overview]
Message-ID: <200510291645.08872.ioe-lkml@rameria.de> (raw)
In-Reply-To: <874q71wv2b.fsf@devron.myhome.or.jp>

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

Hi,

On Friday 28 October 2005 16:54, OGAWA Hirofumi wrote:
> Horms <horms@verge.net.au> writes:
> > I guess it is charset2lower or charset2upper that vfat is calling,
> > which make no conversion, thus leading to the problem I outlined above.
> >
> > My question is: Is this behaviour correct, or is it a bug?
> 
> This is known bug. For fixing this bug cleanly, we will need to much
> change the both of nls and filesystems.

Using per locale collation sequences? :-)

Do you know, how Windows handles the problem of differing collation 
sequences on the file system? Or is the file system always dependend 
on the locale of the Windows version, which created the file system?

I'm so happy, that Unix is not case insensitive :-)


Regards

Ingo Oeser


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-10-29 14:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051013165529.GA2472@tennyson.dodds.net>
     [not found] ` <20051014023216.GJ8848@verge.net.au>
     [not found]   ` <20051015003549.GB11040@tennyson.dodds.net>
2005-10-28  8:22     ` Horms
2005-10-28 14:54       ` OGAWA Hirofumi
2005-10-28 15:07         ` OGAWA Hirofumi
2005-10-29  3:45           ` Simon Horman [Horms]
2005-10-29 14:45         ` Ingo Oeser [this message]
2005-10-29 16:28           ` OGAWA Hirofumi
2005-10-29 18:44             ` Anton Altaparmakov
2005-10-29 20:07               ` 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=200510291645.08872.ioe-lkml@rameria.de \
    --to=ioe-lkml@rameria.de \
    --cc=333776@bugs.debian.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=horms@verge.net.au \
    --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®