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