matt...@gmail.com wrote:
> It looks like I'll build 2.0.2 then.
> Do you know where I can get the fixes based from 2.0.2?
Only formal I know of is... 2.0.3.
Besides it, most public informations were pushed on this very Usenet
group, where you'll encounter the most information, as well as...
Hul Tytus indeed wrote in <news:ldu2va$ikn$
1...@reader1.panix.com> :
: For info on the 2.0.? minix systems, most of the files & info can be
: found at
http://minix1.woodhull.com.
... which is definitively worth reading!
: The 2.0.2 version is a 32 bit system,
Nope, 2.0.2 (as all 2.0.* releases) exists as both a 16-bit and a 32-bit
release. Source is common to both.
: though I believe it can be compiled for 16 bits.
I also believe that (particularly since beginning from 2.0.3, the i386
system is able to compile the boot monitor which is a 16-bit binary),
but to be honest I never tried the cross-compilation system. Make sure
you have /usr/lib/i86/lib*.a available to your i386 system.
> ...
>> The main (only?) difference between the XT versions and the others is
>> the disk driver, the XT versions are using the xtwini controller, the
>> 386 and 286 variants are using the atwini,
> ...
>
> After looking at it all again I think the stock kernel supports all hard
> disk types?
Seem so. There are details about it at the bottom of
http://www.minix-vmd.org/pub/minix/2.0.3/
> The differences between i86 flavours seem to be the floppy size and
the size of the RAM disk.
This is correct, and it reflects the most often encountered
combinations: XT with 512K and 2 floppy drives, XT with hard disk (and
hence only one 360K floppy drive), AT286 with about 2M memory and HD
floppies, etc. To start off, MINIX cannot use the hard disk so should
rely on the floppies; the system (including the shell etc.) needs more
than 360K, so when there is only one floppy drive of this capacity, you
need kludges (explained in details in xt/README.) One such hack which is
common enough, is to have enough of RAM, so it get embedded in the
system: the bootstrapped system creates a big-enough RAM disk, loads the
content of the first floppy (ROOT) into it, then mounts the second
floppy (USR) in the (only) floppy drive: done.
> Removing the unneeded drivers should gain me a bit of space?
Yes, but not enough: a driver is several K, and what is missing is more
in the 100-200 K...
> The binary for the 286 is the same as the 8088. Does the 286 use protected
> mode?
Yes, as soon as it detects a 80286; that is, until overridden with
processor=86; see monitor(8).
> Or does it just put the RAM disk into the extended memory (I think I read that somewhere)?
Yes, it does that as well! I do not exactly remember how (or even if) it
handles enhanced memory (EMS, as opposed to XMS), I just remember it is
NOT compatible with protected mode so can only be handled in real mode;
I do not remember if support for that, if it even made its way into
official MINIX, survived into 2.0.x.
Antoine