Date: Sun, 9 Feb 1997 01:36:25 -0600 (CST)
From: "Colin W. Glenn" <cwg01 AT gnofn DOT org>
To: "'OpenDOS newsgroup'" <opendos AT mail DOT tacoma DOT net>
Subject: Re: [opendos] OpenDOS + Win95 w/FAT32?
In-Reply-To: <Pine.LNX.3.95.970207164126.4560W-100000@capslock.com>
Message-ID: <Pine.GSO.3.95.970209012527.5332B-100000@sparkie.gnofn.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-opendos AT mail DOT tacoma DOT net
Precedence: bulk

On Fri, 7 Feb 1997 mharris AT blackwidow DOT saultc DOT on DOT ca wrote:
> On Tue, 4 Feb 1997, Brian Dukes wrote:
> 
> It cant.  The filesystem upon which CONFIG.SYS resides *MUST* be
> built into the kernel.  This requires either a kernel
> recompilation (with sources), OR an obj distribution so you can
<prune>
> to %OPENDOSCFG%\FSTAB for later mounting by MOUNT in
> AUTOEXEC.BAT.

Rather than go through that sort of trouble, why don't you have the
kernel, the file system drivers, and config.sys sit inside of their own
private partition for booting purposes, then after booting, it calls the
NEXT partition C: .  This would also baffle virus's, until they catch up. 
This would allow you to create different filesystems for different
purposes, and seeing as config.sys is isolated from whatever filesystem
you decide to use, you can specify which one(s) you need for which
drives/partitions.  You might actually be able to boot OpenDOS, with a
drive/partition for Lunix, and maybe call upon a Lunix program under the
taskmanager?  The TM would swap anything which would interfere with the
Lunix program out of the way, load the Lunix system out of the Lunix
section, and the Lunix program would run and never see the difference.

It's _w_a_y_ past my bedtime here.

<! PrePared HTML!  Just export as a HTML file and Click!>
The Light<a href="http://www.thelight.org/">.</a>
A Christian Web Site!