Linked by Thom Holwerda on Sun 30th Sep 2012 19:13 UTC, submitted by Beket_
Slackware, Slax "Slackware 14.0 brings many updates and enhancements, among which you'll find two of the most advanced desktop environments available today: Xfce 4.10.0, a fast and lightweight but visually appealing and easy to use desktop environment, and KDE 4.8.5, a recent stable release of the 4.8.x series of the award-winning KDE desktop environment. [...] Slackware uses the 3.2.29 kernel bringing you advanced performance features such as journaling filesystems, SCSI and ATA RAID volume support, SATA support, Software RAID, LVM (the Logical Volume Manager), and encrypted filesystems. Kernel support for X DRI (the Direct Rendering Interface) brings high-speed hardware accelerated 3D graphics to Linux."
Thread beginning with comment 537100
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by Sodki
by earksiinni on Sun 30th Sep 2012 22:36 UTC in reply to "Comment by Sodki"
earksiinni
Member since:
2009-03-27

Well that's an easy one to answer.

Its appeal lies in its simplicity and predictability, especially in its init scripts and conf files. I can always assume that Slack won't run over my settings.

Also, I know people think the packaging system is a throwback, but I personally prefer Slackware's over any other. Its genius lies not in its packaging format but in the de facto way that packaging works.

First, almost all dev libraries you need are installed by default. If you can't find a certain library or program, you can use slackpkg to autodownload and resolve dependencies. If slackpkg doesn't have it (which is more often than not the case), you can almost always find it in Slackbuilds. Is Slackbuilds too annoying to use? Then use sbopkg, which automates Slackbuilds. Don't want to tarnish the simplicity of your system? Don't use sbopkg. Still can't find things? Compile and install from source without fear of conflicting with your package manager in the future even if you overwrite a file, because Slack's package management is dumb.

Of course, another way to read all these "advantages" is to say that in a world where the Linux desktop still stinks, Slackware gets out of your way the most so that you can mop up the mess more easily once it happens (and it eventually will)...

Reply Parent Score: 3

RE[2]: Comment by Sodki
by Morgan on Mon 1st Oct 2012 00:45 in reply to "RE: Comment by Sodki"
Morgan Member since:
2005-06-29

Its appeal lies in its simplicity and predictability, especially in its init scripts and conf files. I can always assume that Slack won't run over my settings.


That's the main reason (among many) that I'm switching away from Arch Linux. Arch has always been bleeding edge, but these days they are making changes for the sake of it with no real benefit, and most recently doing a piss-poor job of documenting it where in the past they were one of the most well-documented distros around.

I'm currently installing the new Slack in a virtual machine, and if it does what I need it to I'm going to switch back to it full time for GNU/Linux work. I'll gladly give up Arch's pacman and go back to compiling my own slackbuilds if it means some daily sanity is restored.

Reply Parent Score: 4