From: Andries Brouwer <aebr@win.tue.nl>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: FAT-filesystem EOF marker problem
Date: Tue, 24 Sep 2002 23:08:07 +0200 [thread overview]
Message-ID: <20020924210807.GA16695@win.tue.nl> (raw)
In-Reply-To: <amqenu$cic$1@cesium.transmeta.com>
On Tue, Sep 24, 2002 at 12:34:22PM -0700, H. Peter Anvin wrote:
> > | My docs say: FAT entry 0 contains the media descriptor byte.
> > | FAT entry 1 contains the EOF marker, except that the high order two
> > | bits can be used for other purposes.
> >
> > And the value that I see there is 0xfff.
>
> Fat entry 0 contains the media descriptor byte, and fat entry 1 *used*
> to contain the EOC mark, but has been retconned as the volume dirty bit
Yes, I know.
(As I see it, it still holds the EOC mark, but only the low order bits
are of interest, so the top two bits have a different meaning now.)
Let me mention
http://www.win.tue.nl/~aeb/linux/fs/fat/fat.html
(my notes on the FAT filesystem).
If anyone has corrections or additions I'd like to hear.
Andries
P.S. I checked some old stuff but did not find anything with a EOC
other than 0x*fff. I would be interested in hearing about which
non-Linux programs used other values.
next prev parent reply other threads:[~2002-09-24 21:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-22 5:30 FAT-filesystem EOF marker problem Randy.Dunlap
2002-09-22 18:18 ` OGAWA Hirofumi
2002-09-22 18:53 ` Randy.Dunlap
2002-09-23 3:18 ` Andries Brouwer
2002-09-23 6:24 ` Randy.Dunlap
2002-09-23 7:59 ` OGAWA Hirofumi
2002-09-23 18:08 ` Randy.Dunlap
2002-09-24 19:36 ` H. Peter Anvin
2002-09-24 21:36 ` Randy.Dunlap
2002-09-24 19:34 ` H. Peter Anvin
2002-09-24 21:08 ` Andries Brouwer [this message]
2002-09-24 19:27 ` H. Peter Anvin
2002-09-24 19:40 ` H. Peter Anvin
2002-09-24 21:11 ` Andries Brouwer
2002-09-24 21:40 ` H. Peter Anvin
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=20020924210807.GA16695@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=hpa@zytor.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).