From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-fsdevel@vger.kernel.org
Subject: Re: FAT-filesystem EOF marker problem
Date: 24 Sep 2002 12:36:16 -0700 [thread overview]
Message-ID: <amqerg$cn5$1@cesium.transmeta.com> (raw)
In-Reply-To: Pine.LNX.4.33L2.0209231103021.22676-100000@dragon.pdx.osdl.net
Followup to: <Pine.LNX.4.33L2.0209231103021.22676-100000@dragon.pdx.osdl.net>
By author: "Randy.Dunlap" <rddunlap@osdl.org>
In newsgroup: linux.dev.fs.devel
>
> Um, I guess we can say that Windows ME uses 0xfff always, at least
> one version of it. Don't know about Windows 98 or 98 SE or 2000
> or XP etc. But since FAT entry 1 tells the FAT filesystem what
> the EOF value is, it shouldn't matter if it changes from one
> filesystem to another, should it? I don't see a problem with
> using the value in fat_entry[1]. Just make sure that it's valid
> (0xff8 - 0xfff for FAT12).
>
ALL versions of DOS since 1.0 uses all ones for the EOC mark.
Under the principle "be liberal in what you receive, conservative in
what you send" we should recognize anything >= -8 as EOC, but write
-1.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-09-24 19:36 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 [this message]
2002-09-24 21:36 ` Randy.Dunlap
2002-09-24 19:34 ` H. Peter Anvin
2002-09-24 21:08 ` Andries Brouwer
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='amqerg$cn5$1@cesium.transmeta.com' \
--to=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).