Linked by Michael Hall on Thu 15th Jul 2004 07:35 UTC
Slackware, Slax My first experience with Slackware Linux came with version 9.1, after 4 years of using various versions of Red Hat and SUSE Linux. I disliked the general direction these distributions were moving in and didn't see their increasing focus on the "big end of town" as auguring well for either myself or clients of my small one-person IT consultancy business. I quickly became a Slackware convert and have since used it exclusively for all my server deployments. Check in for more and 15 screenshots from Slackware 10.
Permalink for comment
To read all comments associated with this story, please click here.
@ enloop
by dpi on Sun 18th Jul 2004 11:49 UTC

"I'm talking about every distribution I've used with an automatic dependency resolver -- RedHat, Fedora, Gentoo, Debian -- sooner or later breaking my system, i.e., itself, by screwing something up."

Also rubbish. Any solid package management utility with solid packages should work well with precompiled binaries. I know this is very true for Debian GNU/Linux Stable and Testing. The point is that instead of doing the stuff yourself, you outsource it to people who know what they're doing. In the case they do / did not know / knew what they're doing, you can download the source package and compile that yourself. Much more convenient than doing it yourself by default which costs time. Loads of time. Heck, even the BSD's agree with me on that given they want to improve their Ports collection and provide binaries for it by default.

Because of this, the only reason i see why one would prefer to compile his/her own binaries is because of optimalisations (not very better performance if not less) or paranoia (which boils down to the fact you'l need to use binaries to compile from source) or when its broken (see above)

PS: there's another Slackware article on