SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Just thought id post to say that i love slackware and what it does, i have tried alot of other distros such as Redhat, Debian, Mandrake, Mepis, and a heap of others and when it came to the crunch i stuck with slackware as it seems to run smoother ans stabler then the other distros , and another big thing i noticed with slack is that it is a hell of alot easier to compile apps then any other distro, i think this is because it seems to have all the dependencies that most apps need to be compiled. It also makes you learn linux faster to i think as you have to do a bit more to it to get it the way you like not just point and click type of thing , Anyway im loving slack and hope to have enough knowledge about it someday to be able to help develop it further.
I've been there, too, with all the other distros. Although I did like Gentoo for a while, here's what made me switch back to Slack:
1.) While it's cool and all that you can compile everything from source with Gentoo, the same can also be said of Slackware. For instance, I just install the a-ap-d-l-n series off the Salck CD (perhaps the equivalent of a Stage 3 in Gentoo), then compile X and all my apps entirely from CVS (where possible).
2.) By compiling the applications myself, I have more control and more awareness of each build; the dependencies and other build-time options and factors involved. In Gentoo, I found that "emerging" everything usually meant that you left it all up to the package maintainer to make the correct configurations for you, and let the "robot" do all the work. Now what did you learn from doing that? Not much.
Slackware has the dual ability to be what it is, and yet allow you to make it what you like, and how you like.
Originally posted by jymbo 2.)In Gentoo, I found that "emerging" everything usually meant that you left it all up to the package maintainer to make the correct configurations for you, and let the "robot" do all the work. Now what did you learn from doing that? Not much.
Actually, you can specify what switches you want to use when emergeing via the USE flag.
Originally posted by Crashed_Again Actually, you can specify what switches you want to use when emergeing via the USE flag.
Yes, I know that (obviously) from having used Gentoo for 4 months. I'm saying there's a big difference in the learning experience from "emerging" a package in Gentoo, and going out and searching for the package+depencies yourself, untarring, and actually reading the READMEs and INSTALLs and the output of ./configure --help.
Hmm, I've got Slackware for a few days and now I can say that's not exactly something what I have been expecting. Except it's rather difficult configuration (maybe not so difficult, but it's worse than for example RH and others) it's not so stable. Before installing Slackware, I had Mandrake 9.2 and it's easier but also faster on my computer , which includes AMD Duron 1 GHZ processor. It could be strange, but here KDE and Gnome works slower, too slow, but I've always prefered tiny desktop environment's and window makers such as IceWm or fluxbox. Slackware unexpectly kills some windows, for example Mozilla's windows and it can be very terryfing. It can also kill a whole terminal window with for example 10 labels, when a crash can become in only one label.