[bug-notifications] [alternatives 0004538]: Symbolic links not created in new sparse-root zone

Mantis Bug Tracker noreply at opencsw.org
Mon Oct 4 19:29:38 CEST 2010


A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4538 
====================================================================== 
Reported By:                gadavis
Assigned To:                phil
====================================================================== 
Project:                    alternatives
Issue ID:                   4538
Category:                   regular use
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
====================================================================== 
Date Submitted:             2010-08-31 22:19 CEST
Last Modified:              2010-10-04 19:29 CEST
====================================================================== 
Summary:                    Symbolic links not created in new sparse-root zone
Description: 
There appears to be a bug in the alternatives mechanism when creating a new
sparse-root zone on Solaris 10 systems.

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.
====================================================================== 

---------------------------------------------------------------------- 
 (0008349) philadmin (administrator) - 2010-10-04 19:29
 https://www.opencsw.org/mantis/view.php?id=4538#c8349 
---------------------------------------------------------------------- 
Please tell me of a trigger to use, and I'll be happy to try to use it.
Unfortunately, I'm not aware of any.

I might instead attempt to make things a little easier for you, by adding
a
"--relink-all" option to alternatives. That would trigger the "go through
the directory" behaviour.

The only other solution, would involve having to actually register the
symlinks created, with a package. Then the symlink should be duplicated
upon zone creation. but I didnt see you comment about that. 
There's also the question of, WHICH package to register it with?
Potentially the one containing the binary being linked to, but I'm not
sure.



More information about the bug-notifications mailing list