[comp.os.minix] Help - Upgrade ST 1.1 - 1.55 FS

james_jim_woomer@cup.portal.com (03/25/90)

Where have I gone wrong?

Here is what I've done:

I transferred all of the ST orginals (right off the 1.1 distrubution disks)
to my AT hardisk in directory - minixorg.

Collected all of the PC upgrades and put them into the following directories:
minix150, minix153, and minix155.

Collected all of the ST upgrades and put them into corresponding directories:
stminx150, stminix153, and stminix155.

Collected all of the posted fixes and correspondance (at least the ones of
which I'm aware) and put them into directories st150fix, st150doc, etc..

Then I created a directory called newminix and created directories with a
1-1 correspondance with the new directory structure on the ST.

How can this miss.  I plan to do all of the cdiffs and and related work on
my AT running UNIX at 20mhz and 80megs.  Transfer the new libs,fs,mm,kernel,
etc, .. sources to the ST compile - create a new kernel. Get Kermit up
and running and transfer the rest of the stuff like GOD intended.

Guess what? It's not working. Example - FS
Here's what I did:
  cp minixorg/fs/* newminix/fs
  cp stminix150/fs/* newminix/fs
  "applied the patches"  - worked great!
  cp minix153/fs/* newminix/fs
  "applied the patches" - didn't work so great!
	
    The following files wouldn't patch cache.c, inode.c, inode.h, link.c,
	const.h. These do not appear to be trivial.
Where did I go wrong?  Did I do something dumb again? 
Did I miss something on the net. 
Is there somthing wrong with my plan?
Do I not understand the relationship between the ST153 and PC153?
What is the relationship with respect to fs and mm?
Question: What rev did fs and mm become the same for ST and PC.
Suggestion:  Could we come up with some sort of numbering system to indicate
whether we have missed a fix or some important correspondance?
Thanks
Jim Woomer