To: linux-kernel@vger.kernel.org
From: "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: PATCH to access old-style FAT fs
Date: Sat, 31 Jan 2004 02:19:16 +0000 (UTC)
Organization: Mostly alphabetical, except Q, with we do not fancy
Message-ID: <bvf3b3$6pr$2@terminus.zytor.com>
References: <20040126173949.GA788@frodo.local> <20040128202443.GA9246@frodo.local> <87bron7ppd.fsf@devron.myhome.or.jp> <20040129105624.GA1072@frodo.local>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
NNTP-Posting-Date: Sat, 31 Jan 2004 02:19:16 +0000 (UTC)
Originator: hpa@smyrno.(none) (H. Peter Anvin)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1171
Lines: 31

Followup to:  <20040129105624.GA1072@frodo.local>
By author:    Frodo Looijaard <frodol@dds.nl>
In newsgroup: linux.dev.kernel
> 
> I have run a small test in MS-DOS 5.00:
> 
>   1) Create a new directory
>   2) Create five files in it
>   3) Change the first character of the second filename to 0x00 with an editor
>   4) Do a DIR listing: only one file is seen
>      Linux shows four files!
>   5) Create a new file
>   6) Do a DIR listing: there are five files
> 
> So MS-DOS 5.00 at least does stop when a 0x00 marker is found, but does
> not write new 0x00 markers when a 0x00 marker is overwritten. 
> 

This is of course dangerous, since it could create conflicts.

Thus, I suggest we do write new 0x00 markers; even though it's not
required (it only matters if the filesystem is out of spec and
therefore by definition corrupt), it would help the Psion, and
wouldn't cause any problems for in-spec filesystems.

	-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/