Thomas Maier-Komor writes:
> I am wondering if it is normal that pkginfo bails out with a dynamic linker
> error stating that libssl.so.0.9.7 is missing on a nevada build 67 (SPARC).
No. That sounds like a broken system.
/usr/bin/pkginfo (in SUNWpkgcmdsu) should dynamically link to
/usr/sfw/lib/libssl.so.0.9.8 (in SUNWopenssl-libraries). Both are in
SUNWCmreq and above, so every system should have both that executable
and the library.
Can you run these commands? It should show whether the executables
you've got are any good.
% ldd -s /usr/bin/pkginfo | grep sfw | head -1
search path=/usr/snadm/lib:/usr/sfw/lib (RUNPATH/RPATH from file
/usr/bin/pkginfo)
% ldd /usr/bin/pkginfo | grep libssl
libssl.so.0.9.8 => /usr/sfw/lib/libssl.so.0.9.8
> Additionally, can anybody tell me why a regular user always gets a current
> work directory of / instead of $HOME?
If the user's home directory is inaccessible, that's the usual result.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
opensolaris-discuss mailing list
[email protected]
