Richard Skelton wrote: >> Richard Skelton wrote: >> [many problems ellided] >>> It also seems that pkginfo -l on the current BE >> seems to be broken:- >>> root: pkginfo SUNWcsr >>> system SUNWcsr Core Solaris, (Root) >>> root: pkginfo -l SUNWcsr >>> pkginfo: ERROR: bad entry read in contents file >>> pathname: Unknown >>> problem: incomplete entry >>> >>> Is is safe to luactivate this BE >>> >> No, it's not safe to activate the new BE, and you >> really need to fix the >> current one before creating a new alternate BE. >> /var/sadm/install/contents on the current boot >> environment appears to be >> corrupt, based on the above output. >> >> Dave >> _______________________________________________ >> install-discuss mailing list >> install-discuss at opensolaris.org >> http://opensolaris.org/mailman/listinfo/install-discus >> s >> > > Hi Dave, > I have also come to the conclusion that my package database is corrupt. > How can I fix it?
Depends what's wrong. You may want to run pkgchk to see what it says, though that's likely to produce massive amounts of output in such a case. If you have a backup that should be in sync with what's installed, I'd restore it from there. Otherwise it's hand-editing, which is not recommended unless you really know what you're doing. Your easiest way out may be to do a fresh install to the slice where you were going to place the alternate boot environment for Live Upgrade, then copy over any customizations from the existing boot environment, then delete the existing boot environment when you're sure the new one is all set. > Is the file /var/sadm/install/contents the source for the pkginfo command? It's one of the things it uses. Dave
