Date: Wed, 8 May 1996 11:13:25 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: kaleb@x.org (Kaleb S. KEITHLEY) Cc: terry@lambert.org, hackers@freefall.FreeBSD.org Subject: Re: dosfsck anyone? Message-ID: <199605081813.LAA26343@phaeton.artisoft.com> In-Reply-To: <199605072243.SAA21637@exalt.x.org> from "Kaleb S. KEITHLEY" at May 7, 96 06:43:06 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605081813.LAA26343>