Hi all,
There appears to be a bug in the alternatives mechanism when creating a new
sparse-root zone on Solaris 10 systems. My installed version of CSWalternatives
is 1.0,REV=2010.05.21
I have a global zone with CSW alternatives, CSWneon, CSWsudo, and
CSWsudo-common installed. The alternatives mechanism has registered the
symlinks in the right locations and alternatives --display neon and
alternatives --display sudo work as expected.
If I then create a new non-global zone with the default inherited paths (your
typical sparse-root zone), alternatives --display whatever shows the correct
paths listed, but the symlinks are not there.
After zone creation, I have to manually force the alternatives mechanism to
install the needed symlinks by running a shell loop:
for d in `ls /opt/csw/share/alternatives`; do
alt=`basename $d`;
alternatives --auto $alt;
done
Note that if I uninstall CSWsudo inside the zone and then re-install it, the
alternatives mechanism works as expected. It's only upon initial zone creation
that the alternatives symlinks do not get created.
Geoff Davis
Scripps Institution of Oceanography
[email protected], (858) 822-5756
_______________________________________________
users mailing list
[email protected]
https://lists.opencsw.org/mailman/listinfo/users
