On Wed, 3 Jul 2002, Robert Kearey wrote:
>> That has not been the general experience
>> of long time contributers to this list.
>
>It may then be time to re-evaluate that perception.
Here are my thoughts on the matter:
Package management is invaluable from a system administration
standpoint; there's no question about that. However, vendor provided
packages are something I deem inappropriate for an application as
configuration intensive as amanda. I don't want to install a package
and then have to tweak anything post-package install. If I am going to
have to do that I might as well just NFS mount the source and run 'make
install'. The better solution to managing your amanda install is to
create your own packages. It's not terribly difficult to take the
existing amanda RPM and convert it to suit your needs. It's also not
terribly difficult to create custom apt packages for your Debian systems
or create custom inst packages for your SGIs. This is the approach I
prefer to take to managing my systems. For instance, we use OpenSSH on
our SGIs but the SGI Freeware package for OpenSSH is almost always out
of date and rarely do the included configuration files suit our needs.
So, I maintain custom inst packages for internal use on our machines.
--
Brandon D. Valentine <[EMAIL PROTECTED]>
Computer Geek, Center for Structural Biology
"This isn't rocket science -- but it _is_ computer science."
- Terry Lambert on [EMAIL PROTECTED]
