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 could have sworn there were several other posts exactly like this. Or am I having dejavu ?
Nope, it's a commonly asked thing, and I'm pleased to see
that us Slackers aren't too slack to always answer it ;}
That said - now back to the OPs question: for me it's
the no-frills simplicity, and the fact that there's
no "black box" ticking away under the bonnet. Everything
is quite easy. Just looking at the slackware init-scripts.
I mean: Pat's approach just works, and all init scripts
together have less lines of code than a single one in e.g.
SuSE (OK, that's a mild exaggeration, but it's true that
it's a piece of cake to debug a slack script; maybe I'm
just too thick for the more user-friendly [and boy do I
loathe that word] distros out there).
I consider the absence of huge repositories and dependency
checking a blessing.
Tried RedHat, SuSe and some others, but they seemed too Windows like (package management etc.)
The reason I originally tried Linux at all, was because I felt I needed to learn more, and Windows wasn't 'doing it' anymore! Tried some other distros, and found that they seemed to be trying to copy the windows pattern. A friend at college recommended Slack, and when I tried it, it just seemed to be what I wanted.
My first Linux was RH 9.3. I was at friend home and saw linux I loved it on the first look. Then someone told me that Slack isn`t bad - it was Slack 10.0 and I installed it SEVEN TIME IN A ROW. Why? Becouse I just couldn`t be normal user - I HAD TO TOUCH everything and didn`t know how to fix it. Then I went to Suse - for about one day and went back to Slackware. And then I started to read man, readme files etc... And here I am - 4-5 years on linux - 3 on slackware I will never again go to something else
I came back to slack by way of Absolute linux. It is based on slack 12 and a very nice distro that uses icewm. I started my slack experience with version 3.5. I was able to install it and run it with the help of the book that came with it. I beleive it was a intel 386 machine. Later I had 10.0 installed and ran that for quite a while. Then tried an old version of red hat, suse, debian, and ubuntu. I used ubuntu starting with 4.10 and used it through the dapper drake. But with each new version of ubuntu things ran slower, hardware detection got worse, and several install problems. I moved to debian testing and ran that for a while. I tried several live cd's. other distros I tried were pclos, mandrive, fedora, zenwalk, dsl, youper, puppy, vector, and absolute.
I still run abs on two machines and I have a dual boot machine with XP and slack. Over the years using all of the other distros I have learned to really appreciate slack because of the way it stays out of the way. What I mean by this is slack used programs the way they are suppose to be. No tweaks to them, things are not left out because the developer of the distro does not like certain parts of the program. Slack lets you decide how you want to tweak things.
Slack is also rock solid, fast, easy on my old hardware, and has a great community for help.
So that is why I choose slackware. I plan to stay with it for a while.
Slack is simple, solid, fast, and reliable. What mor could you want or need from a distro.
I first installed slackware because on particular weekend, about 3 years ago it seemed to be the easiest of the major distributions to download the install iso for. I was also impressed with a comment that I read, that the best help in dealing with linux problems often came from slackware users.
Another factor which made me stick with it was that I was using a wacom graphire as my mouse. I found getting it to work properly a real pain but I managed it in slackware and couldn't in the other distributions I tried. Part of this was that generally if I tried to compile from source I was usually successful from slckware but often had problems using other distros.
When I first tried Kubuntu I was impressed by the ease with which I could install programs from the repository but then when I wanted to compile something it didn't work and in my attempts to upgrade th compiler some how broke it.
I like slackware because I have a fair idea of what is going on in the system. I feel that I am in control. I have an idea of what is going on when I install or uninstall a tgz package whereas I had no idea what was going on under the bonnet with other package managers.
Perhaps most important is the existence of this forum which I could not have managed without.
My first distro was Mandrake 8. After I had that for a while I wanted something more challenging, so it came down to Debian or Slackware and I randomly picked Slackware. I installed Slackware 8 back in 2001 or so and was stuck in the CLI for two weeks while I figured out how to edit my XF86Config file to work with my graphics card. After I got X to work, I just stuck with Slackware and now I can't think of using anything else (except OpenBSD maybe, which I liked a lot and would love to use on a server). I tried Debian once a year or so ago on a spare partition I had, to see what I missed when I made the original choice, and it just didn't do it for me so I went back to Slack.
There are so many reasons, but I'll just pick one: there's no Slackware wallpaper included with the Slackware installation of KDE. To me that signifies a certain confidence and pride in a product that stands on the basis of its substance, not its facade.
I didn't choose Slackware right away, I tried it out on a spare partition, and I really liked using it; it was what I wanted out of changing to Linux. PCLinuxOS got me started on the Linux experience, but Slackware evoked a certain Unix nostalgia that I wanted as soon as I found out about Linux. I decided to switch over completely after discovering how much easier it is to administrate.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.