urpmi works just as well as apt for package management. To configure it, go to http://plf.zarb.org/~nanardon/urpmiweb.php and follow the steps.
Mandrake's automated security system is called msec. If you don't like it you can turn it off. More info at http://www.mandrakesecure.net/en/docs/msec.php On Wed, 03 Sep 2003 17:31:54 +0300, Anarky <[EMAIL PROTECTED]> wrote: > I (of course?) am quite excited about Mandrake ... told somebody > about it .. and that person gave me this stuff ... I was wondering what > people think about it: > > (from here on it's not my stuff anymore) > ------------------------------------------------------------------------- > > I like Mandrake a lot. We're currently running 9.0 and 9.1 on a few of > our machines, but we're slowly moving over to Debian based distros. I'll > give you a quick run down of why. > > 1. We're sick of RPM. We've hard RPM break on a few machines already (I > think the RPM database becomes corrupted if I remember correctly). > Needless to say, it's hard to upgrade your machine when your package > manager goes kaput. APT/debs are SO much easier to deal with anyway. > > 2. Too much crap! Literally, Mandrake has TOO MUCH crap these days. I > know Debian is hardly innocent, but the dependency train for whatever > reason seems to be much more palatable when using Debian as opposed to > Mandrake. Maybe it's all the package/package-dev combo packs that the > Mandrake/RedHat people like, I'm not entirely sure. It's just too much > honestly. Let me install mySQL and be done with it. > > 3. The big reason (for me personally), the Mandrake security model is > totally whack. Once upon a time, Mandrake used to just run a nightly > script which would email an audit of your system to the Administrator > letting you know what was wrong. That's all it did, and that was nice. > Now there's a set of different (horribly documented) security models > that have all sorts of (horribly documented) behavior. I don't mind the > security model idea, what I do mind is my system doing things for me > (such as changing file permissions) without being explicitly told when > and why this is going to happen. This has caused major problems for us > on a few occasions and it's simply unacceptable. Maybe we haven't looked > in the right place for the documentation, but I've tried to find it in > the past with little success. I should have to go reading scripts to > find this out. > > What I've found is that with Debian I have a much better idea what's > going on inside our systems. There are no surprises, things so far just > straight up work the way we expect them to. We're competent programmers > and system administrators, so this is great for us. If I were a newbie, > I would definitely still recommend Mandrake. Whatever the security > scripts are doing, it IS making the system more secure, but sometimes > you don't want that. > > If I wanted Mandrake to do one thing (short of switching to > .debs) to get me back on the Mandrake train: Please explain in > absolutely explicit detail the difference between your security modes. > You *HAVE* to do this during the install process as well. If I'm > rebuilding my firewall, for instance, I don't have the option to go out > to the internet to find out what these things mean. This is a very > important critical decision that should not be taken lightly. The only > way we can properly make that decision is if the knowlege is made > available to us when we need it most. -- Sridhar Dhanapalan [Yama | http://www.pclinuxonline.com/] {PGP/GnuPG: http://dhanapalan.com/yama.asc 049D38B4 : A7A9 8A02 78CB AB1B FCE4 EEC6 2DD9 249B 049D 38B4} "That's just incestuous. And we all know where incest leads. Hereditary insanity." -- Linus Torvalds
pgp00000.pgp
Description: PGP signature
