Rob Carlson on 21 Dec 2003 11:19:02 -0500 |
OK, my last words on the subject-- (Then again, a distro holy war could be fun...) easy to administer, but how easy is it to keep up to date? doesn't the same lack of package management put more of a burden on the administrator to keep up to date with security related information?
There are several choices with slackware, there's the upgradepkg route if you obtain the necessary files, then type upgradepkg foobar1.tgz if foobar.tgz isn't installed it doesn't upgrade. There is also a setup called swaret which after minor configuration will seek out a server and find all of the packages on a Slackware system that need to be updated, then allow you to choose whether or not to upgrade the packages. Finally there's slapt/slapt-get which is basically a version of apt for slackware. Slackware does have packages and it has one directory where a list of packages and all that is installed with the package is listed so it's not as difficult as you imagine, it's just different. I'm another slackware user incidentally.
Generally I find that all server related packages that are part of the Slackware base install without a hitch, regardless of dependency checking. (Pat is meticulous in that regard.) The reason I pushed to run Slack as our Linux distro at work was because of the ease of server administration. One final note, if foobar1.tgz isn't installed, you can do upgradepkg --install-new and it will install. This is a handy parameter for batch upgrades (i.e. upgrade what I have, install as new what I don't.) (Real final note-- I have a grudge against Mandrake after it "fixed" my partition table for me once. If you want RPMs, I'd say go with SuSE.)
|
|