From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andries Brouwer Subject: Re: FAT-filesystem EOF marker problem Date: Tue, 24 Sep 2002 23:08:07 +0200 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20020924210807.GA16695@win.tue.nl> References: <20020923031804.GA16248@win.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org Return-path: To: "H. Peter Anvin" Content-Disposition: inline In-Reply-To: List-Id: linux-fsdevel.vger.kernel.org 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.