Very Computer

     I've been applying a number of patches to Solaris 2.3, but ran
into trouble.  Specifically, these patches:

101343-01:Synopsis: SunOS 5.3: troff .HM .FM macros causes page numbering format error
101344-03:Synopsis: SunOS 5.3: Jumbo NFS patch
101345-01:Synopsis: SunOS 5.3: cpio with -c option can't be used with multi-volume tapes
101346-01:Synopsis: SunOS 5.3: Solaris crashes with urgent data RFC 1122
101347-01:Synopsis: SunOS 5.3: system hangs due to mblk memory leak
101359-01:Synopsis: SunOS 5.3: nslookup -all dumps core
101362-01:Synopsis: OpenWindows 3.3: Patch to fix several misc. Window Server bugs
101389-01:Synopsis: SunOS 5.3: nm/prof/gprof/dump/dis doesn't demangle C++ 4.0 symbols

cause pkgadd to dump core, and the patch installation fails (very
cleanly, I might add.  Kudos to the installpatch script writer).

     I currently have these patches on the system:

        100961-06       100962-05       100974-01       101267-01
        101306-01       101316-01       101317-03       101318-06
        101319-01       101325-03       101327-01       101329-03
        101331-01

in case that makes any difference.  Has anyone else run into this problem?
Any known workarounds?  I'm running on a SPARCstation 10/30, with 32 megs,
an internal 424 and an external 1 gig drive.  Root has 11 megs free, so
there is plenty of room in /var/sadm/patch to save old files.  The log
file that installpatch says to check for error messages exists, and has
zero length.  Installpatch reports that pkgadd terminates with error code 1,
and a core file from pkgadd is in the directory when all is said and done.

--

Harris Corporation                      AOL : CMusciano
PO Box 37, MS 16/1912                   AT&T: (407) 727-6131
Melbourne, FL 32902                     Fax : (407) 729-3363

A good newspaper is never good enough,
        but a lousy newspaper is a joy forever.         -- Garrison Keillor

...

Quote:

>cause pkgadd to dump core, and the patch installation fails (very
>cleanly, I might add.  Kudos to the installpatch script writer).

>     I currently have these patches on the system:

>    100961-06       100962-05       100974-01       101267-01
>    101306-01       101316-01       101317-03       101318-06
>    101319-01       101325-03       101327-01       101329-03
>    101331-01

        ^^^^^^^^
        bad patch!

Quote:

>in case that makes any difference.  Has anyone else run into this problem?

oh yes ... Casper Dik fingered 101331-01 is the culprit, which is supposed
to patch pkgadd/pkgmk and friends.

101331-01: Topic: SunOS 5.3: fixes for pkgmk, pkgtrans

Instead of trying to back out of all this gunk, and since I was playing
with 2.3 on only 1 standalone, I did the simplest thing: reinstalled the
standalone with auto-install, applied all patches *but* 101331-01 and
everything's happy. If you've saved all the patch information in
/var/sadm/patch, you're set.

good luck

Patch 10331-01 was bad. If you've installed, back it out. If you look on
the sun maintained patch server, I believe you'll see that it is marked as
a bad patch.

I've been told a new version will be seen real soon now on the patch machines.