On 09/16/2011 04:58 PM, Daniel Clark wrote:
On Fri, Sep 16, 2011 at 5:32 PM, Dan Locks<[email protected]> 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
Are you familiar with SFE? You'll have to have to use /opt as your
install prefix. Is there a reason why you're not using a whole-root
zone?
I'm not familiar with SFE. What's that? (I'll look it up too...)
When you say install prefix, do you mean the flag passed to
./configure? Or perhaps you're thinking of the solaris package variable
BASEDIR?
We've had a number of users request an install appropriate for a
sparse-root zone. In the past we've also had complaints that amanda
dumped files in unexpected places on Solaris. We're making an attempt
to satisfy the first group and might have a pleasant side-effect of
satisfying the second group.
Dan
