Language Selection

English French German Italian Portuguese Spanish

Slackware 10.1

Filed under
Reviews

On February 7 Slackware released its 10.1 version of its famous linux distribution. With the death of one of my harddrives the other night and the resulting loss of 10.0, I finally found the time to give it a try.

I found this version of Slackware to be pretty much what I expected in the fundamental areas. It was as usual stable, reliable, and fully functional. The installer was a familiar face and worked flawlessly and even sets up some of the tedious little configurations for the user such as network, root password, and timezone.

Upon boot we find a 2.4.29 vanilla kernel and kde 3.3.2. Slackware has never been accused of being cutting edge instead opting for stability and usability. It did employ udev but I found no hardware issues other than it detecting my bios-disabled on-board sound before my sbl!. Little edit of this file and that was resolved.

Which leads to one of the reasons I've always loved Slack, the ease of configuration. Hotplug raises the stakes just a tad, but for the most part one sets up their hardware in one file, the /etc/rc.d/rc.modules file. Hotplug now detects most everything and one can put things not wanted, like the snd-via82xx, in the blacklist. So, a quick reboot to check the hardware was no disappointment. All functionality was found.

KDE felt like a step back but because as per my habit I've been installing new releases as soon as available. Employing the same version as Mandrake's new beta release, it was complete with all the usual applications and fully functional. It seemed quite snappy as well.

One of the drawbacks with Slackware is having to download the extra applications and dependencies and compiling them yourself. First with Mandrake's urpmi and now Gentoo's portage, I've become quite lazy in that area and haven't had the time to install my favorite apps yet.

I haven't read reviews on Slackware 10.1, but I expect them to have been all positive. I could find nothing wrong in my layperson's experience with install, configuring, or using Slackware 10.1. It's always such a joy. Gotta love the Slack.

Since others have posted extensive collections of snapshots when it was released, I've just put a few up here.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

re: Slackware Packages

Wonderful, thank you. Yeah, I've known of swaret for quite some time. I think it's an awesome and must have application. Thanks again for the links and for stopping by my site.

----
You talk the talk, but do you waddle the waddle?

re: Nice review, but watch your "it's" and your "its"

Oh, ok, thanks. I'll try to remember that. Tongue

----
You talk the talk, but do you waddle the waddle?

re: Slack and Gentoo

I didn't know of slapt-get. I'll have to check that out! Thanks! <runs to google...>

----
You talk the talk, but do you waddle the waddle?

More in Tux Machines

Open-Source Radeon 2D Performance Is Better With Ubuntu 14.10

While we're most often looking at the OpenGL 3D performance of the Linux graphics drivers, in the tests currently being done of Ubuntu 14.04 LTS vs. Ubuntu 14.10 are also a number of 2D graphics benchmarks. In the article today are our 2D benchmarks between Ubuntu 14.04.1 and Ubuntu 14.10 for various AMD Radeon graphics cards and it shows off significant performance improvements. Read more

Today in Techrights

Today's articles: Links outline:

KDE With Theoretical Client-Side Decorations, Windows 10 Influence

KDE contributor and graphics designer Ken Vermette has penned an interesting series of KDE "What if..." articles where he talks about (and has some visual mock-ups) about what KDE might look like with client-side decorations along and separately if KDE were to use Windows 10 design components. Read more Also: What if… Plasma Used Launchers from Other Systems & Enviornments? (Part 1) What if… KDE Used Windows 10 Design Components?

Pondering FOSS foundations

In the case of the Document Foundation, the LibreOffice project needed an independent, solid and meritocratic entity dedicated to support it. In other terms, the OpenOffice.org community wanted to be its own boss and stop relying on corporate – or even third party – good will. If you attend the Community Track on the 31st you will be able to learn more about the Document Foundation and the other entities, but my message here is that while there is no silver bullet in these matters, forcing a community be hosted or to bend to a software vendor never works. It bends if it wants to; it goes whereever it wishes to go. In the case of the Document Foundation, independence and community rule prevailed over convenience; today the results do not need to be proven anymore. But it does not mean we hold the truth more than anybody else: we just ensured the community was in charge. Read more