From: walt <wa1ter@myrealbox.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, hirofumi@mail.parknet.co.jp
Subject: Re: [2.6.8-rc2-bk] New read/write bug in FAT fs
Date: Wed, 04 Aug 2004 05:23:05 -0700 [thread overview]
Message-ID: <4110D529.4000605@myrealbox.com> (raw)
In-Reply-To: <4110CF29.8060401@myrealbox.com>
walt wrote:
> Even when a fat32 fs is mounted read-write I now get error
> messages claiming the fs is 'read-only' when I try to write
> to it.
Okay, I've now found the comments about specifying values
for iocharset and codepage, and read-write works again.
However, IMHO the 'mount' command should simply refuse to
mount a FATfs read/write unless iocharset and codepage are
specified. As things stand now, 'mount' reports the fs is
mounted rw when it simply is not true.
next prev parent reply other threads:[~2004-08-04 13:23 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 [this message]
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
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=4110D529.4000605@myrealbox.com \
--to=wa1ter@myrealbox.com \
--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