Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!sun!yipeia!saj
From: saj%yipeia@Sun.COM (Scott A. Jordahl)
Newsgroups: comp.os.minix
Subject: 1.1 -> 1.2 Patch Problems
Message-ID: <129310@sun.Eng.Sun.COM>
Date: 15 Dec 89 22:02:50 GMT
Sender: news@sun.Eng.Sun.COM
Reply-To: saj@sun.UUCP (Scott A. Jordahl)
Organization: Sun Microsystems, Mountain View
Lines: 43

Well, I have dusted off my 1.1 floppies, booted Minix up on my new
20Mhz 286 clone, and started the upgrade process to 1.3 (getting ready
for 1.5.0!!!).  I got all the upgrade kits off of the N. Dakota State
archive server (Thanks Glen!!!) and started plugging away.  The thing
that most suprised me is that I had no problem getting Minix installed
on the second partition of my "D:" RLL drive (hd7) (ST251-1 with the DTC
7287 1:1 RLL Controller).  I actually was "amazed" that Minix right from
the 1.1 box came right up on the disk (I used a special version of "fdisk",
but everything else was stock).  I figured with such a strange configuration
of hardware that getting my hard disk going would be my big problem.  Not
so.

Now to the REAL problem:

I installed all the new compiler stuff including the 1.3libc.a and the
"/usr/include" files from 1.3.  I got everything else in place from the
11-12kit including creating new directories and shuffling files.  All I
had left was to run the patch program (from the archive server) on the
"diff.patch" file.  Well, as soon as patch got to cc.c (Third patch in)
it got to hunk #6 saying it was a strange context diff, applied the
patch anyway, and then came to the next hunk and asked which file it
was for.  I told cc.c again and it continued on its way, but it
starting acting funny on subsequent files to the point I decided to
quite and give up.  I thought that maybe the version of "patch" I had
was buggy, so I down loaded the source to patch 2.0 Level 12 and
compiled that.  Same results.  When I removed the offending hunk from
the diff file (#6), patch worked fine for the rest of the cc.c diffs.
It did stop again, however, in a later patch.

I looked at the part of the diff that caused the problem and can't find
anything obvious wrong with it.  Has anyone else experienced this
problem?  Any clues or suggestions?

Thanks all!

-- Scott

/########################################################\
| Scott A. Jordahl                                       |
| UUCP:   saj@sun.COM                                    |
| PHONE:  WK: [415] 336-5463                             |
|         HM: [408] 270-5619                             |
\########################################################/