On Sep 20, 2011, at 18:30 , Dan Locks wrote: > On 09/17/2011 02:46 PM, Klas Heggemann wrote: >> I would split this, to make it possible to share the package between machines >> sharing /opt perhaps read only (NFS shared or in zones). >> >> # Shared binaries and libraries and documentation: >> >> /opt/amanada/bin >> /opt/amanada/sbin >> /opt/amanda/lib >> /opt/amanda/share >> >> # per host directories >> /etc/amada # local config files >> /var/amanda # local machine specific files ? >> >> >> My 5 cents. >> >> Klas Heggemann >> >> > You'd essentially only move the contents of /usr to /opt/amanda/. It's a > reasonable suggestion, and is similar to Sun's original intended usage > pattern. Klas, have you used sparse-root zones in production? I just want > to make sure your suggestion comes from a bit more than glancing over Sun's > documentation. That's as much as I did, and I feel a tad uninformed.
I've built packages (not SVR packages or IPS, just 'configure, make, make install') this way for a while. We have a lot of sparse-root zones. Some of these use packages built this way, like database server and web servers. > > The opinions don't seem particularly strong here. Since I debated Klas' > suggestion myself before sending my original message, I think I'll go with > that for the package, unless of course there's some pressing reasons *not* to > do it. The build scripts will be in SVN and included in the distribution > tarball and I'll try to make it easy to change file locations by just > tweaking some variables. Anyone who needs other locations should be able to > build a package fairly painlessly. It would be really nice if amanda turned up as an IPS package, useable by Solaris 11 or OpenIndiana. We usually build this ourself, to get the Kerberos stuff included in the build. Also a spec file would appreciated, since ot would be possible to add extra build options easily, I guess. Klas > > Dan > >> On Sep 16, 2011, at 23:32 , Dan Locks wrote: >> >> >>> Hi all, >>> >>> I'm in the process of creating a Solaris package designed to install in a >>> sparse-root zone. Solaris sparse-root zones mount /usr/* read only, so the >>> package can't put files in /usr at all. My first instinct is to use a >>> file-layout which puts *everything* amanda installs in /opt/amanda/. That >>> mean we would have something like: >>> >>> /opt/amanda/bin >>> /opt/amanda/sbin >>> /opt/amanda/lib/amanda >>> /opt/amanda/var/lib/ >>> /opt/amanda/etc/ >>> /opt/amanda/share >>> >>> I'm really not a Solaris admin, so I don't the have experience to know The >>> Right Way to do a sparse-root install. >>> >>> I'd like some input from any Solaris admins or users that either know, or >>> have (non-local-config-dependent) ideas. >>> >>> The source will end up in amanda's SourceForge repository, and the binary >>> package will be on download.zmanda.com. >>> >>> Thanks for any help! >>> >>> Dan Locks >>> >> >
