From: "Wayne" <wjackson AT powerup DOT com DOT au>
To: "J P Morris" <b52g AT usa DOT net>
Cc: "OpenDOS" <opendos AT delorie DOT com>
Subject: Re: disk devices (was ls, killing disk 0)
Date: Tue, 21 Oct 1997 21:27:06 +1100
Message-ID: <01bcde0b$e11cd160$f28125cb@client.whack.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Precedence: bulk

It would be good to have a "must load at all times" section or something
along that line.

BTW have a \dev\dsk0$ is necessary but does not have to be able to be
accessed.  If the device disk 0 was not available, to what would the OS be
written to?

Food for thought!!!

-----Original Message-----
From: J P Morris <b52g AT usa DOT net>
To: opendos AT delorie DOT com <opendos AT delorie DOT com>
Date: Tuesday, October 21, 1997 7:42 PM
Subject: Re: disk devices (was ls, killing disk 0)


>-= ArkanoiD =- wrote:
>>
>> nuqneH,
>>
>> > Date: Tue, 21 Oct 1997 09:32:40 +1300
>> > From: physmsa AT cantua DOT canterbury DOT ac DOT nz (Mr M S Aitchison)
>> > Subject: Re: disk devices (was ls, killing disk 0)
>> > To: opendos AT delorie DOT com
>>
>> [dd]
>>
>> > > > This character file, is only usable in OS/2.
>
>Oh.  It didn't work in OS/2 either....
>
>>
>> You _can_ destroy your CMOS contents by writing to /dev/clock$
>> (i have that done once: i was curious what happens if you write to
>> /dev/clock$ and that was _my_ problem when that happened,not an OS
>> "misfeature") ,so /dev/clock$ is evil?
>
>What OS did you do this with??
>
>>
>> > and most of the
>> > benfits are available via IO controil reads/writes that is already a
>> > feature of DOS.  A read-only subset of the OS/2 notion might be
>> > something though.
>>
>> r/w. I want to be able to write images,not only to read them.
>> I copied hdd's once: dd if=/dev/hda0 of=/dev/hdb0 ;)
>
>Evil!  Eeevil!
>
>
>(Wonders how to put this tactfully)
>
>Umm,  I doubt that you will see this feature, unless Matthias puts it
>in his kernel.
>
>Most people will not want to do this, ever, and it will take up space
>in the Kernel.  However, the new config.sys operator I mentioned is a
>considered possibility.
>
>Does anyone have a suggestion about that before it is implemented
>or shelved?  (Ie, do you want it, what character should it be?)
>
>> ---
>>                                        _     _  _  _  _      _  _
>>    Must be a visit from the dead..     _| o |_ | | _|| |   / _||_|   |_
|_ |_
>>    CU in Hell ..........  Arkan#iD    |_  o  _||_| _||_| /   _|  | o
|_||_||_|
>
>--
>* JP Morris        aka DOUG the Eagle (Dragon)  -=UDIC=-     *
>* b52g AT usa DOT net         Author of the U6 develorer's kit      *
>**************************************************************
>* http://members.tripod.com/~JPMorris - Ultima, Doom, AViOS  *