> I had a hal failure yesterday after updating from 114 > to 117, it was caused by some > renamed packages (in my case, SUNWdbus-bindings > became SUNWdbis-glib and a > number of other per-language packages).
How did you find out which packages needed installing though? > > If running "/usr/lib/hal/hald --daemon=no > --verbose=yes" fails quickly (instantly or > a few seconds after start), this might be a similar > problem. Worryingly, if I run that command, I get a list of devices being recognised, followed by a segmentation fault :-/ > Try "ldd" on the binaries > to check that all libraries were found - and perhaps > those which were not. On the hal binaries? What should I be looking for in the output? If I run ldd hald it lists all the dependencies and doesn't appear to ouput any errors, but I don't really know what I'm looking for... > > If your old BE is available, you can also compare > package lists as subdirectories of > BEROOT/var/sadm/pkg. Just do this: > > lumount snv_117 > cd /.alt.snv_117/var/sadm/pkg > ls -1d * | sort > /tmp/pkgOLD > cd /var/sadm/pkg > ls -1d * | sort > /tmp/pkgNEW > > diffing these two files would show packages unique to > each installation. Ok, did that. Upgrade from 111 to 117, seems like pretty much everything changed! Upgrade from 117 to 118, just a handful of packages added, mainly python ones... but how can I use those diffs to help me? > > HTH, //Jim Cheers, Matt -- This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
