Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!uflorida!gatech!utkcs2!nall
From: nall@cs.utk.edu (John Nall)
Newsgroups: comp.os.minix
Subject: Re: mx386 upgrade problems -- help!
Message-ID: <1991Apr7.124257.25423@cs.utk.edu>
Date: 7 Apr 91 12:42:57 GMT
References: <1991Apr6.144159.22831@cunixf.cc.columbia.edu>
Sender: usenet@cs.utk.edu (USENET News Poster)
Organization: University of Tennessee, Knoxville - CS Department
Lines: 25

In article <1991Apr6.144159.22831@cunixf.cc.columbia.edu> rt2@cunixb.cc.columbia.edu (Rens Troost) writes:
>
>Actually, though, I'd rather avoid shoelace, as I do a fair bit of
>kernel-building. Has anyone gotten the normal build process working with
>this setup? Or does shoelace actually cut down turnaround time? (It took me
>less than 4 minutes to compile FS, 'make image', and reboot on my 386 befor
>I started this endeavor!)

The reason that I advised using Shoelace at the time I wrote the tutorial
had to do with problems that have since been corrected (or at least have
had corrections posted to the net).  If I were writing it today, I would
not put in the part about Shoelace.  (Although I personally like it, and
use it, it makes the process a little more complicated the first time
around).

Also, while I have the soapbox :-)........ I've had several people send me
e-mail who quite obviously have bought P-H Minix 1.5, immediately grabbed
the 386 stuff, and tried to upgrade.  For a seasoned systems guy, this is
probably ok. But for those who are using Minix as a learning tool (which
it was designed to be, as I understand it), I highly recommend becoming
completely familiar with "standard" Minix before upgrading.  A lot of my
tutorial language is pretty casual - it is definitely NOT a Heathkit
manual!

John Nall