Date: Thu, 8 May 1997 17:29:46 -0400 (EDT)
From: "Mike A. Harris" <mharris AT blackwidow DOT saultc DOT on DOT ca>
Reply-To: "Mike A. Harris" <mharris AT blackwidow DOT saultc DOT on DOT ca>
To: pierre AT tycho DOT com
cc: OpenDOS Mailing List <opendos AT delorie DOT com>
Subject: Re: DOS utilities (was Re: A few FS notions)
In-Reply-To: <Pine.LNX.3.95.970506180241.7805H-100000@55-174.hy.cgocable.ca>
Message-ID: <Pine.LNX.3.95.970508172541.451T-100000@capslock.com>
Organization: Total disorganization.
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk

On Tue, 6 May 1997, Pierre Phaneuf wrote:

> > Yes, sounds good, but it has to be EASIER than RPM's, and the
> > "RPM" file must come ready to run as either a self extracting EXE
> > or a ZIP file IMHO, *NOT* as an RPM file.
> 
> Basically, the RPM files are renamed 'cpio' files (a backup system for
> Unix). I don't intend to use cpio files, but maybe renamed tar and gzipped
> files. I hope to preserve long file names and their case and access
> rights. There are many free programs to handle tar and gzip files. What do
> you think?

I'm open to a new system, but think it needs to be through a
large discussion first, and all avenues explored.
 
> > Lets decide exactly what should be in the different packages.
> > Sound good?  Here is my suggestion of what to start off with:
> 
> Maybe a bit premature to think about, no? ;-) Lets built it first!

Perhaps, but we need to start somewhere.
 
> > (Binary dists)
> > BASE package (16-bit OpenDOS version)
> > 	IBMDOS.COM
> > 	IBMBIO.COM
> > 	COMMAND.COM
> > 	FDISK
> > 	SYS
> > 	INSTALL.EXE
> > 	EMM386.EXE
> > 	OPENDOS\DRIVERS\NWCDEX.EXE
> > 	OPENDOS\DRIVERS\ODMOUSE.EXE
> > 	OPENDOS\DRIVERS\NWCACHE.EXE
> > 	OPENDOS\FILESYS\FAT.SYS
> > 	OPENDOS\FILESYS\EXT2.SYS
> > 	OPENDOS\FILESYS\NTFS.SYS
> > 	OPENDOS\FILESYS\HPFS.SYS
> 
> I think that NWCDEX.EXE and ODMOUSE.EXE, as well as the file systems
> drivers, shouldn't be included in the base syste but in separate systems.
> Probably that NWCDEX.EXE will be left behind and reimplemented as a
> ISO-9660 file system driver, just as for ext2, NTFS or HPFS...

Sure, sounds good, but the other functions in there need to be
allocated elsewhere then.  Right now we've got NWCDEX, so where
does it go?  Remember, CDROMs are becoming more and more
important, and you need the driver to access the disk.  I think
of these drivers as an extension of the kernel (which really they
are) and thus should be part of the BASE set.  Just my opinion
though, we need more input from other people too.
 
> > The BASE package SHOULD set up a MINIMUM OD installation IMHO,
> > without requiring any additional packages to get it working.
> > Packages should be able to be installed, removed, upgraded,
> > etc...  all with the smart installer program.
> 
> It should be very minimal. Note that Red Hat doesn't include things like
> fdisk, cp or the KERNEL in the base package! It simply sets up the
> directory structure and some rights. To have a bootable system, you also
> need the kernel, SysVinit and some other things... Anyway, we'll hack the
> packaging system before putting anything in them! And also hack what we're
> going to put in them!

Yeah, we need to discuss it at much greater length.



Mike A. Harris        |             http://blackwidow.saultc.on.ca/~mharris
Computer Consultant   |                  Coming soon: dynamic-IP-freedom...
My dynamic address: http://blackwidow.saultc.on.ca/~mharris/ip-address.html
Email: mharris at blackwidow.saultc.on.ca  <-- Spam proof address

4DOS is a very powerful COMMAND.COM replacement with over 80 commands!