| |||||||||||
package mismanagement, eh? ;-)package mismanagement, eh? ;-)Posted Apr 9, 2007 3:18 UTC (Mon) by pr1268 (subscriber, #24648)In reply to: package mismanagement, eh? ;-) by gvy Parent article: Debian GNU/Linux 4.0 released
>> I think that Slackware is great for both. But, I'm horribly biased! ;-) Yes, you're correct; I only manage two Slackware computers: my laptop and my desktop. A couple of years ago I managed two servers running Slackware 10.0. Package management on Slackware is really easy - you only have to be fluent in ssh, wget, and upgradepkg. Yeah, yeah, I know, the big-name distros do even that for you, but I kind of like having the control over upgrading packages and patches. Back on-topic to Debian 4, I also want to extend a "thank you" to those online who are participating in the bittorrent swarm. Just since this afternoon I've completed the 1st DVD-ROM ISO; hopefully I'll have the other two by tomorrow (assuming that my ISP doesn't shut off the valve before then...) :-)
(Log in to post comments)
package mismanagement, eh? ;-) Posted Apr 9, 2007 4:56 UTC (Mon) by dlang (subscriber, #313) [Link] I've run slackware on 50ish systems, (and switched to debian becouse another department tried to push us to redhat in the name of 'standardization' and 'supportability' now running on a couple hundred servers)
frankly, when you are running a lot of servers, you don't want to use yum, dpkg, aptitude, or any other package management tool from each box directly, you want to deploy some sort of centralized configuration controls, and use those to upgrade your boxes. once you have done this, it really doesn't matter what the 'native' package manager is for those boxes (although it does make a difference on how much work you have to put into the one central image)
|
|||||||||||