si0_tb90020@debet.nhh.no (05/04/91)
I had a PC a few years back. I also had MINIX. The computer was thrown
out, and MINIX started collecting dust. Now, I hav got myselfe a new
computer, and I am thinking of installing minix on it. So I would also
like to upgrade my old version. By the old version, I really mean old.
1.1 I think it is... very old anyway.
So, the questions. Is it worthwhile starting the upgrade process, or
should I shell out a $169 for the last version.
If upgrading is managable... How much HD space should
I set aside for minix (for upgrading).
Thanx for any kind of responce...
By the way. I do not have the original diskettes, it was when limited
copying for educational puposes were allowed. And three of us bought
MINIX together, doing a OS cource.wilker@gauss.math.purdue.edu (Clarence Wilkerson) (05/05/91)
I don't know what your time is worth or how much you will enjoy the patching process. I would guess it took me a couple of weekends to move from 1.1 to 1.5.10. That was doing the patches on a Sun workstation. Certainly in the process you learn the directory structure of MINIX. I would say it's pretty hopeless if you don't have a hard disk. If you have a hard disk but it's not set up for MINIX yet, you might try using the bios-wini version of the kernel as used on the PC demo disk. Then you can tune it later and enable the protected mode if you have a 286/386. Clarence Wilkerson
enders@plains.NoDak.edu ( WD0BCI ) (05/06/91)
In article <1991May4.114742.485@debet.nhh.no> si0_tb90020@debet.nhh.no writes: >So, the questions. Is it worthwhile starting the upgrade process, or > should I shell out a $169 for the last version. > If upgrading is managable... How much HD space should > I set aside for minix (for upgrading). > The question here is really "which is more important, your time or your money?". The upgrade process is relatively manageble, even on a pc. For reference, it took me about 3 weeks, off and on, to go from 1.2 to 1.5.10. Aside from some small glitches (which are readily fixed, even if you are not a Minix source guru :-), it only took the time to patch and recompile everything. I have 10 MB on my HD for Minix, and with all the source, binaries, etc., I have about 2 meg left. 15 meg would probably be better. All temporary files should be directed to the HD (which does slow things down a bit), to save you from the frustration of running out of room on the RAM disk. Of course, if you have lots of RAM available, you just have to increace the size of /dev/ram (700KB would be nice, more if you could spare it). If you don't have the time to play with upgrading, break down and spend the $169. Also, if you are coming up from 1.1, be sure that you have the copy for 640K pc's, as the version for 256K pc's doesn't have the compiler binaries on it. =============================================================================== Todd Enders - WD0BCI ARPA: enders@plains.nodak.edu Computer Center UUCP: ...!uunet!plains!enders Minot State University or: ...!hplabs!hp-lsd!plains!enders Minot, ND 58701 Bitnet: enders@plains "The present would be full of all possible futures, if the past had not already projected a pattern upon it" - Andre' Gide ===============================================================================
klamer@mi.eltn.utwente.nl (Klamer Schutte) (05/06/91)
In <11878@mentor.cc.purdue.edu> wilker@gauss.math.purdue.edu (Clarence Wilkerson) writes: >I don't know what your time is worth or how much you will >enjoy the patching process. I would guess it took me a couple >of weekends to move from 1.1 to 1.5.10. That was doing the >patches on a Sun workstation. Certainly in the process you >learn the directory structure of MINIX. I don't know about the differences in upgrading from ST minix 1.1 to 1.5.10 #3 and upgrading on a PC, but upgrading can be done much faster. At home, on my ST with HD (is essential, or you should have losts of time) it typically takes me about 4 hours. (typically because i have the habit to remove unwanted files ;-( ). This is the time for unpacking (you need approx 10Mb), patching && recompilation of the kernel. So not counting recompilation of libc.a and all the commands (which for some i >>still<< don't have compiled) Klamer -- Klamer Schutte Faculty of electrical engineering -- University of Twente, The Netherlands klamer@mi.eltn.utwente.nl {backbone}!mcsun!mi.eltn.utwente.nl!klamer
news@mentor.cc.purdue.edu (USENET News) (05/07/91)
package for you! I had to go 1.1 -> 1.2 1.2 -> 1.3 1.3 -> 1.5.10 From: wilker@gauss.math.purdue.edu (Clarence Wilkerson) Path: gauss.math.purdue.edu!wilker Most of these had slightly incompatible directory structures, and existed in the form of many change files. Clarence :)