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.
It seems a limited review in that it mostly centers around apps, packages. And, sometimes the rating is done on the basis of which package(s) "should" be shipped with Slackware.
It must be a review that is targeted for those of us who already know the direction that Slackware takes?
A very good job that you did of the package/app reviews.
I've not yet time to install 12.0. But, I will soon, though.
I've not yet tried 12.0. But, on the basis of "Slackware being Slackware" or, IOW, (with release version 12.0) "how well are we keeping up with the Slackware tradition?"
On this, that latter, I rate Slackware 12.0 as an eleven points out of a possible ten points.
Is there a vision and/or mission/purpose statement somewhere that proclaims and/or declares Slackware's purpose or what it is that Slackware is all about?
I *might* call Slackware as being more than just a Linux distro. Slackware is a direction, a wise one I think, for those who either already know or are willing to learn the Linux way.
It's **so** easy for me to customize Slackware to my own liking. Slackware build scripts exist all over the place available for free. And they work so reliably well.
I await the day that I get more around to its so that I've sufficient enough time to learn how to make my own Slackware package, say, using makepkg
From this eaze of customizability aspect, there's no sense for the overhead of maintaining x number of apps to fall upon those who release Slackware 12.0. So, instead, let them do the important stuff (of which I'm absolutely certain that they have done).
Not that packages aren't important. They are. But (whatever the wizards did) ie upgrade/update the 12.0 tool chain, latest Xorg ver., add_the_rest_here.
I called them Wizards because to me they are. The keenest of developers. Nothing less. I can write a script kid bash or Perl script once in a while. But such development as what those who have released Slackware 12.0 have accomplished -- this sort of a development is a staggering thing to me. It's like "abra cadabra" how did they do that. I can only comment that it must've taken copious amounts of elbow grease not to mention the amount of computer science programming experience and knowlege also needed.
The eaze of customizability of Slackware could be seen/rated as a positive attribute. (unless one doesn't already know this and also is not interested in learning it).
As I understand it, Slack "is" because Slack does. IOW Slackware leaves you with more Slack time to spend however you want "because Slackware is so dauntless, runs forever". IOW I admin the Slack box not because I want to spend time working on it but because I have users of whom I want them to use it. And, use it they do. And, use it they do. And, admin it I not.
Slackware deserves the "Slack" in Slackware. Once set up, then very little admin. Run run run. Long time.
Well, my 11.0 Slackware box runs so well. Soon I'll try 12.0.
I wrote my own biased review, geared toward the things I like and it showed up on the review page yesterday, but not today! I put it in the LQ "Review" section. It isn't really a review for the masses, but hey, I'm not the masses! Two thumbs up for being biased! But the word "full" does imply that all others are considered.
If you are using one of the non-SMP kernels (huge.s or generic.s) and need
to compile third-party modules (such as the proprietary NVidia driver),
have a look in /extra/linux-184.108.40.206-nosmp-sdk/ for information on what
is needed to build them.
If you are installing Slackware 12 and doing your first boot and the bootup hangs, it's probably because the kernel they are using is the one-size-fits-all brand. Just so happens I had a 220.127.116.11 kernel ready to go and was able to setup a /test directory and make adjustments to the lilo.conf file to point to the customized vmlinux kernel.
In your case, I'm not sure what to recommend other than try to either compile a stripped down kernel to use or find a bare 18.104.22.168 kernel or something similiar.