[csw-maintainers] Adjusting $(DIRPATHS) for sparse zones support with shared /opt

Philip Brown phil at bolthole.com
Thu Jun 18 18:46:51 CEST 2009

On Thu, Jun 18, 2009 at 10:32:23AM -0400, Ben Walton wrote:
> I'm combining threads here, since they are of overlapping subject matter.
Unfortunately, you quoted too much, and overly long emails tend to get zero
replies. I'm going to try to shorten it a lot in the interests of
more focused discussion:-)

> 1. For people sharing out a single install (possibly per $arch) with
>    NFS, /etc/opt/csw may make things more difficult, although I'd
>    argue that symlinks could work around this quite easily.  [For
>    people in this situation, would creating symlinks for you?]

For people with a shared /opt (whether that be NFS or zones), the same
issues still come into play. the issue of, "should configuration for 
software X, be unique to each box, or globally shared?"

You dont see to address that type of issue at all.

> Personally, I really dislike having multiple etc directories...it
> feels wrong to me, but that is likely due to my Linux roots 

Or bsd. yes, i understand your background :-)

Personally, I think /etc/opt/VENDOR makes a lot of sense.
I also think that, in the rare cases global configs are desired
(and it really is quite rare) /opt/csw/etc makes sense for those also.

>   I also
> dislike having /opt/csw/apache2/etc and would prefer
> /etc/opt/csw/apache2, for example.

I think most everyone dislikes that. it is legacy configuration, and should
really be changed to use /etc/opt/csw/apache2, in my opinion.

> Should this discussion be taken to users@ to 'poll the audience'?

I think we should have the discussion on the maintainers list first, to
pre-air out any controversial issues.
A fully public, large sized mailing list, is never a good place to have
initial "exploratory" type technical discussions. Better to distill the
core issues first.

More information about the maintainers mailing list