James Carlson schrieb:
> 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.
> 

I've done an upgrade with live upgrade from Solaris 10 update 3. I
observed both behaviours now since a couple of community builds. I think
you should at least take a short look at this issue. I don't think that
my installation is broken in any way, as it runs without any problem,
and I never encountered these kind of problems with live upgrades before.

I'm now on travels for one week, but I'm reachable via e-mail, but
cannot check anything, because the system is inaccessible for me in this
time.

> /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
> 


[EMAIL PROTECTED]:~$ uname -a
SunOS azalin 5.11 snv_67 sun4u sparc SUNW,Sun-Blade-2500
[EMAIL PROTECTED]:~$ ldd -s /usr/bin/pkginfo | grep sfw | head -1
    search path=/usr/sfw/lib  (RUNPATH/RPATH from file /usr/bin/pkginfo)
[EMAIL PROTECTED]:~$ ldd /usr/bin/pkginfo | grep libssl
        libssl.so.0.9.7 =>       (file not found)
        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.
> 

The user's home directory is accessible. A simple 'cd' jumps to the
regular home directory. The terminal is started the same way as on
Solaris 10 update 3 (i.e. with '/opt/csw/bin/xterm -ls')... I had this
issue on any SXCE I can remember. Really weird...

- Thomas

_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to