Gene Heskett wrote: >>It's just too simplistic to blow off a packaged amanda, especially >>when there are possible support issues involved. It's possible >>that someone following Gene's advice may find that their Red Hat >>Network setup is compromised, for example. And not everybody >>*has* the luxury of being able to compile from source.
> Humm, interesting, citing security concerns from one of my > recommendations? Can you supply a situation where that could > apply? Or are you more concerned with the fact that its > configuation is published at all? OK, poor choice of words. I meant "compromised", not so much in the sense of "W3 0wnz y00", but more in the sense that you've changed the state of your system in a way that Red Hat Network (via rpm) won't recognize, and perhaps modify in some undesired way. I can probably best some up by saying that when using a system that relies on package management, it's best to stick using packages. If there's a problem with those packages, then let us know and we can fix them! -- Rob Kearey Website: http://apac.redhat.com Red Hat Asia-Pacific Legal: http://apac.redhat.com/disclaimer +61 7 3872 4803 Stuff: http://people.redhat.com/rkearey
