Michael Tosch wrote:

> In article <bjkpcc$1tlo$1@agate.berkeley.edu>, Alan Coopersmith
> <alanc@alum.calberkeley.org> writes:
>> Dmitry Sazonov <dmitry@quite.net> writes in comp.sys.sun.admin:
>> |Then the users came and asked to install this and that. So, naturally I
>> |install those packages from the installation tree (2/02 unpatched
>> |packages).
>> |One package SUNWbtool required SUNWcsl.
>>
>> Not surprising, SUNWcsl is the core system libraries that Solaris
>> requires to run just about any program.
>>
>> |That was the last package I was able to install.
>>
>> It should have already been installed, so if you re-pkgadded it you
>> downgraded it and made it mismatch the rest of your system.
>>
>> You might be able to boot from CD and recover, but reinstalling is
>> probably the safest and simplest way out of the hole you have dug.
>>
>
> Yes SUNWcsl is always present. SUNWbtool should have installed
> right away.
>
> Instead of re-installing everything, you can try a restore from
> tape backup on these files:
>
> nawk '/^[^=]*SUNWcsl$/{print $1}' /var/sadm/install/contents


I restored only two libraries for now /usr/lib/libadm.so.1 and
/usr/lib/libbsm.so.1

>
> and live with the too old patch level information in the package
> database.

pkgchk complains. I think I would need to forcefully reapply some (which?)
patches.


>
> The question remains: pkgadd should say:
> "warning: remove these patches first: ... ... ...".

Maybe it did.
Unfortunatelly I'm used to not read it's output and hit y in advance...


>