From owner-freebsd-hackers Wed May 8 11:23:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA28970 for hackers-outgoing; Wed, 8 May 1996 11:23:22 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA28963 for ; Wed, 8 May 1996 11:23:18 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA26343; Wed, 8 May 1996 11:13:25 -0700 From: Terry Lambert Message-Id: <199605081813.LAA26343@phaeton.artisoft.com> Subject: Re: dosfsck anyone? To: kaleb@x.org (Kaleb S. KEITHLEY) Date: Wed, 8 May 1996 11:13:25 -0700 (MST) Cc: terry@lambert.org, hackers@freefall.FreeBSD.org In-Reply-To: <199605072243.SAA21637@exalt.x.org> from "Kaleb S. KEITHLEY" at May 7, 96 06:43:06 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Same goes for DOS 7.0 shells running INT 21 emulation for programs > > running in DOS "Command" on Win95. > > > > If you "cd .." you *don't* get a ".." at the IFSMgr_SetReqHook() > > call level. You get an absolute path with the ".." parsed back. > > Fine, but what does that have to do with how the bits are laid on on > the disk in FAT/VFAT/VFAT32? > > My guess is that FreeBSD programs don't care too very much about INT21 > emulation or IFSMgr_SetReqHook. :-) > > On the disk there are "." and ".." directory entries. If the Windows > IFS chooses to parse out the ".." in a filespec, that doesn't sound > like something that affects how dosfsck will work. It depends. It means that it isn't required to maintain the FS in what BSD would consider a "consistent state" to keep it usable by DOS/Windows. FWIW. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.