To: opendos AT mail DOT tacoma DOT net Subject: Re: [opendos] BAD Filesystems Message-ID: <19970216.122945.8487.0.chambersb@juno.com> References: From: chambersb AT juno DOT com (Benjamin D Chambers) Date: Sun, 16 Feb 1997 15:27:25 EST Sender: owner-opendos AT mail DOT tacoma DOT net Precedence: bulk On Sat, 15 Feb 1997 11:54:35 -0600 (CST) "Colin W. Glenn" writes: >On Sat, 15 Feb 1997 mharris AT blackwidow DOT saultc DOT on DOT ca wrote: >> On Sat, 15 Feb 1997, Colin W. Glenn wrote: >> > > > >\Extended_Filesystem_Number_2.Dynamically_Loaded_Driver_Module >> > > > This _jams_!!, by utilizing the algorithm I proposed of using >the first >> > > What if I allready have a file called EXTEFN~2.DLD in that >> It would be something like EXTEN#KR.001 or something close. If a >> What ever method that gets implemented, it should be totally >> transparent to the user (not ask questions) and it should be > >Ok, that's close enough, but I don't like the extension handling, I'd >prefer somemeans to identify the type of file it is. Also, we could >modify my idea so that a really strange character is use, ie one you >would >never use in a regular filename but would serve as an indicator to the >user that namebashing had occured and the entry would of matched an >existing filename otherwise. Maybe an upper ASCII character? A trick to use spaces in filenames, use ASCII-char 255. This is a blank char (which is why it is used instead of a space). However, this char could also work as a flag to indicate name hashing. ...Chambers > > >A Christian Web Site! The Light >.
>A neat place to visit. HotSpot >.
>Caldera, Inc. / Makers of OpenDOS >.
>Caldera's OpenDOS page >.
> >