SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I moved to --current on one of my Slackware boxes a couple of years ago just because I wanted to see whether I could do it successfully. It was on 13.37 at the time. It ran almost flawlessly up through 14.1, then I put Mint on it and gave it to my son. (The only glitch I encountered was that, after a few months, gtkam stopped working. Since I could just pop the camera's memory card in the card reader, that was No Big Deal, so I didn't even bother to find out what broke. I'm guessing some library got updated out from under the installed version of gtkam.)
I otherwise found it rock-solid Slackware stable.
I have two Slackware boxes right now, and both are running --current.
Stable, always stable, because "bug-free" is an ideal which can never be reached in reality in any system of nontrivial complexity, and why deliberately put bugs into that system by using -current?
Every time -current approaches a release and Patrick announces release candidates, people have found bugs, which usually get fixed for the next release candidate. This implies that -current always contains some bugs that interfere with some users' use-cases.
14.0 contained at least two problems (one regarding a particular wireless device driver, and another regarding a bug in less(1) which only showed up when invoked from tcsh), so even though releases are better than -current, they're not entirely bug-free, either.
Slackware tends to be as close to bug-free as a Linux distribution gets, though, which is a big reason I remain fervently Slackful. I've had to use other distributions for my job, and they all range from slightly worse (Debian-Stable, CentOS) to much, much worse (Debian-Unstable, Ubuntu, Fedora Core, ScientificLinux). Slackware's robustness has spoiled me for any other distribution.
Stable. I can't go to a gig, only to find out my laptop won't boot. Rehearsal/tech time is precious enough without having to troubleshoot computer problems with the eyes of anywhere from 1-30 people on you and a conductor breathing down your neck.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.