From: Erik Mouw <erik@harddisk-recovery.com>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
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, 4 Aug 2004 15:45:49 +0200 [thread overview]
Message-ID: <20040804134549.GD25969@harddisk-recovery.com> (raw)
In-Reply-To: <87657zkp21.fsf@devron.myhome.or.jp>
On Wed, Aug 04, 2004 at 10:31:18PM +0900, OGAWA Hirofumi wrote:
> This is intention.
>
> The default codepage/iocharset which is easy to cause a mistake and
> unclear was deleted from fatfs. So default is mounted as read only.
>
> You need to explicitly specify the "codepage" and "iocharset" options.
To minimise confusion, is it an idea that NTFS and FAT use the same
mount options? Right now NTFS uses "nls" and VFAT "iocharset".
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2004-08-04 13:46 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 [this message]
2004-08-04 14:17 ` 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=20040804134549.GD25969@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=hirofumi@mail.parknet.co.jp \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.