Maciej (Matchek) Blizinski wrote: > On Mon, Sep 14, 2009 at 8:37 PM, Maciej (Matchek) Blizinski > <[email protected]> wrote: >> 3. The actual migration process involving shared/read-only /opt. >> ("just move it" does not work) >> >> I'm mostly concerned with the discussion number 3, as it's blocking my >> work with three pieces of software (cups, unixodbc and tightvnc). >> Trygve, since you objected to putting my sample implementation into >> testing, can you comment on the suggested solutions or suggest one of >> your own? > > Trygve, ping?
My concern with simply placing symlinks in /etc is that it doesn't reduce the clutter that i feel we have today. Some files reside in /opt others in /etc. I know there is the definition about what has to go into /etc/opt/csw and what has to go into /opt/csw/etc, but i see how this confuses people (including me). My preference would be to have it all in /etc, i.e. move config files over. To not break with setup like yours, couldn't we introduce a csw.conf variable that would indicate such a setup? cswclassutils scripts running in such an environment would know that they need to behave different. This way we could focus on having a simple baseline that works with the traditional "one host" (or "full root zone") setup and treat special setups in a special way (i don't feel we can fully address all of them with one single approach). I haven't thought that through completely, but it might be an alternative approach. Might also turn out to be even more complex. Sebastian _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
