> > It seems your configure script indeed used /usr/local as a root prefix > which gets appended with the relevant dirs like var etc. > Right and I found the --prefix=PATH configure option that I could change that if I had the engery to start over again. :( > 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. > So the /etc/init.d is the new way, ala Slackware. That's good to know too. Thanks. > 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. > I don't grok "wrapped up a .spec" but I'm sure I will soon. The curinfo|index directories had to be created manually and then the directories below got created at some point - for the first client (the backup host itself) - from there I've had to do everything manually. How does one take a tar.gz and use rpm to install it? Or would I have to seek out the appropriate .rpm to install that way? Thanks for your responses! Randy Cordell __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
