"John R. Jackson" <[EMAIL PROTECTED]> writes:
> And are you also willing to handle the E-mail from each and every new
> Amanda user who gets it wrong? :-)
>
> >1. It means I have to keep a locally-compiled version on each of my
> >machines ...
>
> Do you mean a locally compiled version of Amanda? If so, that's the
> strongly recommended approach anyway. Amanda and pre-compiled are
> (in general) not a good combination.
But apt-get install amanda-client is just SOOOO easy!
Ah sigh, I gave in and compiled my own .debs with bzip2 hacks :-)
> >2. If I wish to use different compression programs for different
> >filesystems or configuration sets, I can't without using multiple
> >installations of amanda, which is a real PITA.
>
> Also not true (you can use wrappers around the compression program and
> let them decide, for instance), but I agree it's still a PITA.
How would such a wrapper work, since there's still no way to vary how
it's called per-filesystem? (Unless we overload "fast" and "best" to
do something weird, I guess?)
> You're correct that things are (might be -- I don't really know anything
> about bzip2) simpler if we're talking about gzip and bzip2. But what
> about some other mythical compression program that looks and acts totally
> different from them and needs a lot of extra support?
Somebody can write a wrapper to make it sane (read from stdin, write
to stdout.....)
> And just so we're clear, I'm not opposed to any of this. I'm just
> rambling when I really should be coding :-).
You too, eh? :-)
>
> >John Goerzen
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>
--
John Goerzen <[EMAIL PROTECTED]> www.complete.org
Sr. Software Developer, Progeny Linux Systems, Inc. www.progenylinux.com
#include <std_disclaimer.h> <[EMAIL PROTECTED]>
