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.
Decent review. My favorite, and yet the most problematic, aspect of the review is this:
Quote:
Criticizing Slackware for lack of modernity would be like criticizing a well-maintained 1957 Chevy for not having power windows or satellite radio.
It's a decent perspective and conveys something that I like about Slack - it is the simple, powerful, Detroit heavy metal of Linux - but it makes Slackware sound consciously retro and more like a curiosity piece. I run fvwm, which many people also often look at like a museum piece but, if you want, you can use the latest KDE, the 'premiere' (to some) Linux desktop, along with polkit, even, and udev and the latest (perhaps too late) kernel and so on. The last part of "[a]side from newer versions of everything, Slackware has changed very little" is true in an important sense, but makes the first part (italics mine) sound pretty trivial, when it's not.
Anyway - he definitely gets it better than most reviewers but it sounds like a distant, abstract appreciation rather than really inhabiting the Slack.
I do think it is a shame whenever any reviewer does not mention important third-party "add-ons" like SlackBuilds.org. With the reference to apt, this particular review gives the impression that slackpkg will install third-party software from other repos which of course we all know it does not do. Thus, mentioning things like SlackBuilds.org is important to give non-users some guidance on "where to go next" after installing the OS.
This section characterises Slackware well and is one of Slackware's most important features:
"The nice thing about Slackware is that you get to see upstream software pretty much as it was shipped by the projects. Most of the major distributions spend time modifying, customizing, and polishing the upstream software to tailor it to the audience they're trying to serve. This means adding and removing features, ensuring that packages are well-integrated, and branding the software. So the KDE you use with one distro isn't going to be quite the same from distro to distro.
Slackware, on the other hand, takes a very light touch with upstream software. There's very little, if any, branding to be found. Software is mostly presented just as the upstream projects shipped it".
You've probably surmised that Slackware isn't for everyone as a full-time OS. It's not. Slackware is for users who like a basic, solid Linux distribution that makes very few assumptions about how the system is going to be used. That approach means that Slackware is perfect for a small percentage of Linux users.
Still, I think Slackware has a certain style that should be appreciated. Criticizing Slackware for lack of modernity would be like criticizing a well-maintained 1957 Chevy for not having power windows or satellite radio. You don't run Slackware to escape from the complexity or configurability of Linux; you run Slackware to embrace those things.
The first part of the above quote is not really a good indicator of usage nor user. I think the narrow minded point of a small percentage for users of Slackware is not justified. Just my .02.
The last is a fair point about the reasoning behind usage but the point is indicative of a typical Slacker.
Overall my sense is that the reviewer really doesn't know Slackware but did try to provide a fair review with information at hand.
I am certainly not among the 2 percent special users. The opposite: I use Slackware, because, once set up, it allows me to forget about the system, as it just works and helps me get done what I want or need to do with it. No other distro imposes so few restrictions on the user. So, if there is a generaly purpose Linux distribution, at all, it has to Slackware.
I really don't think it's fair to a potential new user to have prejudice because of a misinformed reviewer. The bias is that Slackware is hard. Not so if your willing to read, investigate and know the internal workings of the system instead of hand holding.
Out of the box, most times the tweaking is minimal for any install that I perform but at times it can be trying. This does depend on how the user wants or the needs for a system along with the hardware to be used. Not the fault of the distribution.
Even if you install the kitchen sink, a few things are held back in the extra directory on the CD. This includes stuff like official Java, an MPlayer browser plugin, and a script to create a Slackware package out of the current Flash plugin for installation.
Was I missing something? I couldn't find in extra/ any reference to such a script to build a Flash plugin package. For me, the most appropriate method is to use the SlackBuild script from SlackBuilds.org.
Was I missing something? I couldn't find in extra/ any reference to such a script to build a Flash plugin package. For me, the most appropriate method is to use the SlackBuild script from SlackBuilds.org.
Here you go. Only in 64-bit Slackware from the looks of it.
Was I missing something? I couldn't find in extra/ any reference to such a script to build a Flash plugin package. For me, the most appropriate method is to use the SlackBuild script from SlackBuilds.org.
it makes Slackware sound consciously retro and more like a curiosity piece.
I've often thought of Slackware like a modern Morgan Roadster. For those not familiar, Morgan is a small British car company that still makes a design similar to 40s and 50s roadsters like the MG TC or TD. However, they have modern materials, manufacturing methods, and amenities. They are indeed "consciously retro" but they are intended for those that appreciate older ways of doing things. It's a philosophy of "improve without changing" that I think is analogous to how Slackware is developed.
For another less "consciously retro" car analogy, consider the Porsche 911. It is essentially the same car it has been since 1964, simply freshened and modernized every few years. Anyone can instantly recognize the car no matter what year, but it keeps getting better with every iteration.
If every driver in the world was given a free 911, I can guarantee you that a large majority of them would want their Camry back. A 911 makes sacrifices in comfort and convenience for performance and driver control. Most 911 owners wouldn't have it any other way, but the experience isn't for everyone.
Oddly, any car reviewer will understand a 911 for what it is, and it is brilliant at that. In a 911 review, you wouldn't complain about how much more cargo space an SUV has, or how it doesn't ride as smoothly as a Lexus. For some reason, Slackware reviewers simply can't see the differences between it and the now more mainstream distros. They want to compare it on terms that aren't really relevant to why someone chooses to run Slackware in the first place.
The bias is that Slackware is hard. Not so if your willing to read, investigate and know the internal workings of the system instead of hand holding.
Unfortunately, many people have been conditioned to believe that reading, investigating, and obtaining knowledge are some of the most difficult tasks a human can undertake.
It's a decent perspective and conveys something that I like about Slack - it is the simple, powerful, Detroit heavy metal of Linux - but it makes Slackware sound consciously retro and more like a curiosity piece.
Agreed. This is one of the better reviews I've read, but, it does tend to foster the notion that Slackware is old and outdated. I was chatting with my IT director who does use Linux and I mentioned that I prefer Slackware. His comment was: "Doesn't it run really old software?" I let him know that 13.1 has a shiny new 2.6.33.4 kernel, KDE 4.4.3, XFce 4.6.1, and FF 3.6.3. He was surprised that Slackware has new software.
I don't think Slackware is a retro distro, but, the opinion piece does present that common, albeit incorrect point of view.
If you're willing to read and learn how a real operating system works then Slackware is the right distro for you.
Oddly, any car reviewer will understand a 911 for what it is, and it is brilliant at that. In a 911 review, you wouldn't complain about how much more cargo space an SUV has, or how it doesn't ride as smoothly as a Lexus. For some reason, Slackware reviewers simply can't see the differences between it and the now more mainstream distros. They want to compare it on terms that aren't really relevant to why someone chooses to run Slackware in the first place.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.