On Wed, Jun 16, 2010 at 10:10 AM, Maciej (Matchek) Blizinski <[email protected]> wrote: > No dia 16 de Junho de 2010 17:12, Philip Brown <[email protected]> escreveu: > >> Could you give specifics of the problem, please? >> I thought I designed our csw implementation of alternatives, to >> specifically be nfs friendly. > > The alternatives file gets installed under /opt, its class is > 'cswalternatives'. It's the same case as with the SMF integration, > the CAS script is called, but doesn't get to handle the alternatives > file in the sparse non-global zones. The effect is that the symlinks > aren't created in the non-global zones.
errr.. but that shouldnt be a problem, because ideally, we should only be creating symlinks with it under /opt/csw in the first place. and so they should already be set up in sparse non-global zones. This was part of my implicit design assumptions. If someone is using alternatives, to set up symlinks ELSEWHERE... then I'd like to know why. becuase that would make no sense to me (and in that case we'd need to set up some explicit docs for "dont use 'alternatives' outside of /opt/csw" :-} ) _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
