From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Erik Mouw <erik@harddisk-recovery.com>, aia21@cantab.net
Cc: walt <wa1ter@myrealbox.com>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.8-rc2-bk] New read/write bug in FAT fs
Date: Wed, 04 Aug 2004 23:17:28 +0900 [thread overview]
Message-ID: <87oelrj8cn.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20040804134549.GD25969@harddisk-recovery.com>
Erik Mouw <erik@harddisk-recovery.com> writes:
> To minimise confusion, is it an idea that NTFS and FAT use the same
> mount options? Right now NTFS uses "nls" and VFAT "iocharset".
"nls" option is used by only NTFS. Other filesystems is using "iocharset".
Umm.. Why was "iocharset" option deprecated?
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2004-08-04 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 11:57 [2.6.8-rc2-bk] New read/write bug in FAT fs walt
2004-08-04 12:23 ` walt
2004-08-04 13:19 ` Tomasz Torcz
2004-08-04 13:31 ` OGAWA Hirofumi
2004-08-04 13:45 ` Erik Mouw
2004-08-04 14:17 ` 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=87oelrj8cn.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=aia21@cantab.net \
--cc=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wa1ter@myrealbox.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