SUMMARY: Problems Upgrading Solaris 2.4 -> 2.5.1

From: Mike Mitchell (
Date: Fri May 09 1997 - 12:20:01 CDT


     Sorry to take so long in summarizing, but a trip to the Grand
Canyon got in the way. Thanks to the following for answering:

From: Jay Scott
From: "Young, Jim x3125"
From: Michael Pesaresi

The problem turned out to be an attempt, by one of the programmers
who has the root password and without my knowledge, to install SunLink
DNI 8.0 (Compatible with SPARC and Solaris 2.1) onto the Solaris 2.4
Axil machine prior to my attempt to upgrade to Solaris 2.5.1. I was
able to use pkgrm to uninstall part of the DNI package, but one of the
pkginfo files appeared to contain the stdout output of a ufsdump instead
of pkginfo information. ($5 to anybody who can figure out how the
programmer managed that one. . .) I'm still not sure whether I have
correctly removed all of the DNI files because of the damaged pkginfo
file. I removed the damaged pkginfo file, and at least I'm back to
where I can run "pkginfo" and get a complete list of installed packages
that does not include SunLink DNI.

     Thanks, again to all.


Original posting:

> Folks-
> I'm in the midst of performing my very first Solaris
>upgrade from Solaris 2.4 to Solaris 2.5.1. As usual,
>we have lots of added devices and drivers and I want to do
>an upgrade instead of a new install. I'm running into
>many problems. Among them are:
> 1. After the upgrade, running "pkginfo" errors out part
> way through its listing giving the following:
> |
> |
> |
> system SUNWdniCU SunLink DNI Core Utilities
> pkginfo: ERROR: pkginfo file is corrupt or missing
> so I can't even get a complete listing of what is
> installed. The file /var/sadm/install/contents exists
> and the directory /var/spool/pkg exists, but is empty.
> Is there a way to rebuild the database for the pkginfo
> command so that I can get a full listing of what is installed?
> I really don't want to have to install Solaris from
> scratch to get the pkginfo database correct.
> 2. After the upgrade, almost any package that I check with
> pkgchk gives lots and lots of errors. A very small
> example is:
> doom# pkgchk SUNWcsr
> ERROR: /etc/default/init
> file size <459> expected <462> actual
> file cksum <38298> expected <38700> actual
> ERROR: /etc/default/su
> group name <sys> expected <other> actual
> file size <703> expected <0> actual
> file cksum <58387> expected <0> actual
> |
> |
> |
> When I check out the above files I see:
> # ls -al /etc/default/init
> -r-xr-xr-x 1 root sys 462 May 17 1995 /etc/default/init*
> # ls -al /etc/default/su
> -r--r--r-- 1 root other 0 Apr 19 13:13 /etc/default/su
> If anyone has any advice on what to try to correct the database
>for the pkginfo command or how to interpret massive quantities of
>pkgchk ERRORs, I'd really appreciate the help.
> Thanks in advance.
> Mike

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:54 CDT