From owner-freebsd-questions@FreeBSD.ORG Tue Sep 27 14:56:12 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E5CF16A41F for ; Tue, 27 Sep 2005 14:56:12 +0000 (GMT) (envelope-from micahjon@ywave.com) Received: from smtpout1.ywave.com (ycomradius.yelmtel.com [216.227.100.60]) by mx1.FreeBSD.org (Postfix) with SMTP id 1111243D48 for ; Tue, 27 Sep 2005 14:56:11 +0000 (GMT) (envelope-from micahjon@ywave.com) Received: (qmail 29716 invoked by uid 502); 27 Sep 2005 14:56:10 -0000 Received: from dsl-12-178-99-132.ywave.com (HELO ?192.168.1.65?) (micahjon@ywave.com@12.178.99.132) by 0 with SMTP; 27 Sep 2005 14:56:10 -0000 X-CLIENT-IP: 12.178.99.132 X-CLIENT-HOST: dsl-12-178-99-132.ywave.com Message-ID: <43395D89.8080208@ywave.com> Date: Tue, 27 Sep 2005 07:56:09 -0700 From: Micah User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050924) X-Accept-Language: en-us, en MIME-Version: 1.0 To: RW References: <433852A8.10900@gish.demon.nl> <43394783.3020608@pobox.sk> <43395410.3010606@ywave.com> <200509271532.34672.list-freebsd-2004@morbius.sent.com> In-Reply-To: <200509271532.34672.list-freebsd-2004@morbius.sent.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: file name case issue on fat32 (Was: Re: Sharing data files on a dual-boot machine ...) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Sep 2005 14:56:12 -0000 RW wrote: > On Tuesday 27 September 2005 15:15, Micah wrote: > > >>>ps: and, btw, how freebsd knows there's a capital A in "A.txt~" ? >>>because it's stored on the filesystem in that way, i guess. being >>>case-insensitive doesn't (necessarily) mean a FS doesn't keep a case, >>>imho. >> >>The reason is as follows: a.txt is an 8.3 filename and is stored on >>fat32 in the old dos format. a.txt~ is NOT an 8.3 filename and is >>stored on fat32 in the extended long filename format. Case information >>is not stored in 8.3's file names. They're always the same case, but I >>can't remember now if they're stored as upper or lower case. Extended >>long filenames do store case information, even though windows ignores >>the case (as was pointed out earlier). FreeBSD is displaying 8.3 names >>as lowercase probably to mimic the tendency of unix filenames to be >>lowercase. Windows displays 8.3 names as upper case probably to mimic dos. > > > > The 8.3 names and the long names are stored separately whatever the name > format. FreeBSD displays the long name even when the filename fits the 8.3 > format. The directory structure of fat32 is still the same as from dos. In order to create long filenames, Windows uses subsequent directory entries to store the extra filename characters. If a filename fits the 8.3 format, Windows (at least Win98) does not bother to create the extra entries for the long filename record. If there's no ong filename record, how can FreeBSD use the long filename? Later, Micah