DU4.0D patch install hanging part 2

From: Don Park <parkd_at_reed.edu>
Date: Wed, 27 May 1998 12:37:19 -0700 (PDT)

Here is some more info that should have gone into the first mail:

After aborting the patch install the first time, I ran it again (dou!).
Same result but on a different patch file (Patch: libc Library TCP/IP
Correction) - tar said insert volume 2 and it waitied forever. It was
suggested that I didn't have the whole kit.

I don't have the original tar so I cant compare checksums. I can say this:
parkd_at_amon:~$ du -sk patch_kit/
18429 patch_kit

Then I waited a day, noticing how the patch utility has this great
'baseline' feature. I used that and it found the messed up libXm and libc.
I thought I'll just try it again and maybe it will just work. It was on
'Various kernel patches" when I gave it 2 hours before aborting the
script. So I don't think its the patches themselves but rather setld's use
of tar. At least that is my theory.

Does my dupatch file look correct?
parkd_at_amon:~/patch_kit$ ls -l dupatch
-rwxr-xr-x 1 parkd system 24429 Aug 18 1997 dupatch*
parkd_at_amon:~/patch_kit$ sum dupatch
21215 24 dupatch


Don

--
Don Park  (503)777-7546(w) 940-7797(p) don.park_at_reed.edu [dlab.reed.edu]
---------- Forwarded message ----------
Date: Wed, 27 May 1998 12:01:26 -0700 (PDT)
From: Don Park <parkd_at_reed.edu>
To: alpha-osf-managers_at_ornl.gov
Subject: DU4.0D patch install hanging
We've had a major problem with our new DU 4.0D install as far as patch
installation. 
We have an alphaserver 1000A that was running 3.2D-2. It got a clean
install of 4.0D - that went ok.
I got the latest patch kit from digital's web page and untarred it. I ran
'dupatch' and did the #2 verify & install step for all patches.
What happens is, it installs a few patches OK, then it gets to a large
patch - in my case a libXm patch. 
It looked like this:
Patch: Motif Toolkit Correction 
   Copying from /home/parkd/patch_kit/kit (disk)
        Working....Thu May 21 23:24:28 PDT 1998
        Working....Thu May 21 23:26:29 PDT 1998
        Working....Thu May 21 23:28:29 PDT 1998
        Working....Thu May 21 23:30:30 PDT 1998
        Working....Thu May 21 23:32:31 PDT 1998
        Working....Thu May 21 23:34:32 PDT 1998
        Working....Thu May 21 23:36:33 PDT 1998
        Working....Thu May 21 23:38:34 PDT 1998
        Working....Thu May 21 23:40:35 PDT 1998
and on and on. What is not recorded in the 'script' is the message from
tar:
tar: Ready for Volume 2
tar: Type 'go' to continue...
Yet the controlling terminal is detached from the tar process (And the
whole thing is on disk so the message is obviously an error of some sort)
so I have no choice but to control-C the install.
This of course messes up my libXm - after that xdm would not start (core
dump).
I had to do an updateinstall of 4.0D over 4.0D to get the libraries back
to a consistent state.
It doesn't appear from the list archives that others are experiencing this
problem. Any help appreciated.
Don
--
Don Park  (503)777-7546(w) 940-7797(p) don.park_at_reed.edu [dlab.reed.edu]

Received on Wed May 27 1998 - 21:38:20 NZST