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.
some server apps not easy to install
by tech_user on Thu 15th Jul 2004 09:42 UTC

with some of the more popular distros, some complex-to-install packages are alsready packaged and scripted... however.. this is not always the case for slackware.

for example, if you wanted to install the collaboration server, you would find it not on the CDs, not in the swaret (current) online repository. so you look to the website and you are lucky that it links to someone who has apparently done some work to get it working on slackweare. but its for 9.1 and you lose a little confidence. but since slackware has no frilly extras to break it should work all fine? (indeed, it was for me one of the ealrliers distros that worked with an early upgrade to kernel 2.6 - it shows that the slackware philosophy pays iff - all the popular distros broke).

but, alas, the .tgz package syou download are lacking automated scripts... you have to unpack... install and dependency you have to have postgresql ... not in swaret ... and so you install the supplied (untrusted?) postgresql and try to configure it ... which takes time as you're used to mysql. then you compile the apache module (thankfully apache is in swaret) but find that sys/types.h is missing. luckily you've seen this before and search swaret for -dev packages.. nothing tehre... so you try "glibc" and a few entries pop up.. which one? ah, its the main glibc package tat is not installed (why?). but that's fixable.. and we then proceed to get apache up and postgres up ... finally we can get the service up... (which also had dependencies on gnustep and objective-c which required ugly softlinking directories, adding things to /etc/, and addign strange things to the $PATH just to make the scripts retuirn with no erros- but that would scare many readers off) ...

in the end - did it work? no... a complete serach of the the filesystem (find / -name ...) to find the binaries which the rc.opengroupware scripts actually start are no-where to be found!

... or you can apt-get opengroupware, or uprmi opengroupware?

the choice is yours.

(ps - i still love slackware and use it for its no-frills strengths - i'm just highlighting one aspect which other popular distros have an advantage with)