On Mon, 27 Nov 2000, Randolph Cordell wrote:
<snip>
> I got real hung up on my first try at installing amanda because I was
> expecting things to go in presently existing directories and amanda is
> duplicating all those same directories (or expecting them) under /usr/local/
> rather than off of the root (/etc/, /var/, /lib/, etc.) and so, I ended up
> with a mixture of locations. Now that's much clearer for me. I do see the
> reasoning for this from an ease of trouble shooting, upgrading and removal
> perspective - but I honestly don't understand the mechanics of program
> installs/removals enough yet to know if this is a real issue or not, throwing
> everything into the same locations. But one thing that has been a tad
> frustrating is the lack of standards, or more specifically the 'partial
> adherance' to standards as seen so far in my miniscule introduction to the
> *nix world. I plan on this being my career direction so I am interested in
> any changes for the better. I noted that you are making action items and you
> got my attention... grin.
It seems your configure script indeed used /usr/local as a root prefix
which gets appended with the relevant dirs like var etc.
I still think the Linux fs standard is pretty clear and the only grudges
are between /etc/rc.d/init.d (neat, dying) vs /etc/init.d (messy,
popular) and things like that. Stuff like /var/adm has been long gone.
I would say that if you want to do an amanda without using a package
manager in Linux, you should install the files in correct locations (/var,
/etc etc) and just the binaries in /usr/local/*bin. If you want it all in
a (re)movable chunk, use prefix /opt/amanda.
I personally wrapped up a .spec and put amanda in standard system paths
with rpm and upgrade it etc easily. The only "problems" or rather extra
turns taken are creating the amanda user before rebuilding amanda and
creating the [curinfo|index]/host/_disk dirs (Does it do that
automatically?) and ofcourse, .amandahosts. Other than that, it's a
breeze.
