Language Selection

English French German Italian Portuguese Spanish

My Slackware 13 review

Filed under

Well Slackware 13 was released a few weeks back and I had a chance to install it on my laptop. I ran Slackware as my main Linux distro for about 2 years. It’s reputation as being stable and solid are well earned. If you run Slackware for any significant amount of time you will learn the intricacies of how Linux works. The packages that come by default in the latest version of Slackware are pretty up to date and an official 64 bit distribution is now available. I opted for the 64 bit version and was off to the races. The Slackware installer is ncurses based and is pretty straightforward. The only part a noobie might have trouble with is using fdisk to manually partition their hard drive before installing the OS on it. Once you have partitions setup just go with the default package set for a desktop install and you should be golden. The install is pretty quick (as most Linux installers are these days). I’m not going to get too detailed so I’ll list what I liked and didn’t like.

I liked the following:

* This thing screams. KDE on 64 bit Slackware is sooo fast
* A very nice selection of default applications
* Everything seems very stable. This is Slack, what do you expect?

I didn’t like the following:

More in Tux Machines

Today in Techrights

A few thoughts on OpenBSD 5.8

I've been using OpenBSD since way back at release 2.3 in 1998, so I've gone through upgrades that took a fair amount of work due to incompatible changes, like the switch from ipf to pf for host firewalling or the change to ELF binaries. The upgrade from 5.7 to 5.8 was a pretty smooth and easy one, for the most part. The two most painful changes for me were the replacement of sudo with doas and the dropping of support in the rc.conf for the pf_rules variable. While sudo is still available as a package, I like the idea of reducing attack surface with a simpler program, so I made the switch. The two things I miss most about sudo are the ability to authenticate for a period of time and the ability to have a single config file across a whole set of servers. The former I'm just living with, the latter I've adjusted to by having a single config file that has lines commented out depending on which server it's on. I did have one moment of concern about the quality of doas when it incorrectly reported the line number on which I had a syntax error in the config file--fortunately, this was just a failure to increment the line count on continuation lines (ending with a "\") which is fixed in the -current release. Read more

10 recently open-sourced products from big tech companies

Releasing internal products to the open-source community is the hip new thing for technology giants to do Read more