Revisiting SalixOS

I’ve gotta say I have absolutely loved Xubuntu – up until anything after 12.04, and LXLE, the brilliantly mixed respin of Lubuntu – up until 14.04. Precise, 12.04, was rock-stable and fairly nimble on this ancient relic I’m still using. I could continue using it through April of next year, but it’s largely unsupported now except for security updates. So I upgraded to Trusty, 14.04. Xubuntu Trusty was too much for this aging dinosaur, halting and slow. So again, LXLE to the rescue. Gorgeous, full-featured, and much faster than Xubu. All was well. Until updates cumulatively made it increasingly buggy. I did a little research and found this interesting article on some changes to 14.04 that were um, unorthodox at least. Among other things, Trusty isn’t using an LTS kernel for an LTS release. They’ve opted for “greater hardware compatibility” by using a more recent kernel, which was updated two or three times on LXLE during my sojourn with it. They’ve got some apps that depend on systemd to work, but systemd isn’t the default init application / process manager. Maybe that’s one of the things that contributed to LXLE’s bugginess after some updates. It became slow, reluctant to boot, and themes got glitchy. Other users of Ubuntu Trusty and derivatives have reported frequent loss of networking (both wired and wireless) after updates. Borked after updating is a frequent complaint, and it always had me walking on eggshells with Ubuntu, and even more so with LXLE’s all-or-nothing way of updating (open Synaptic > Mark all upgrades > Apply).

I wondered if systemd, especially in an updated distro that didn’t ship with it but has a bunch of stuff that depends on it, was part of the problem. I never took a position on the whole systemd debate because as a self-confessed technophobe I never dabbled in that “advanced coder stuff.” Suffice it to say that the debate ignited a bloody war among Linux geeks which has kinda died down a little but still rages in spots, even though all the Big Players (Debian, Ubuntu, Fedora, SUSE, Gnome, etc) have adopted it. It’s more than just a “initiating” daemon, it’s a process manager also. So it sort of goes against the traditional “do one thing and do it well” rule of GNU/Linux. It’s not “mature” yet, to borrow another Linux cliche, yet it got widely adopted with such speed that bugs are still showing up, and developers are being forced to “fix someone else’ mistakes” by adapting their own projects for systemd. Uncool. So, I looked around for a “systemd-free” Linux distro that might be less buggy with all the changes being forced on users and developers and maintainers. One of them is PCLinuxOS, which I have played with before. I downloaded two of the community remixes, LXDE and Xfce. I made bootable USB keys of each, but both refused to boot. I spent a few hours retrying, but with the same result. Okay, chide me for giving up to easily, but I remind you – I’m a technophobe anyway, remember?

Enter my second choice from the systemd-free list of Linux distros: SalixOS. I’ve played with this one before too, and fled back to Xubuntu when SalixOS suddenly refused to boot one day. But a few things are different this time out. One of them is this cool LiloSetup utility that works in whether in Live mode or installed SalixOS. So I’m prepared now in case the bootloader ever balks again.

SalixOS 14.1 ships with Xfce4.10 (yeah I know, the new one is 4.12 but y’know what? I don’t care. New isn’t always better) and Linux Kernel 3.10.17 (yep, the LTS kernel, yay!) This superb and simple little distro is based on and fully compatible with Slackware, which is known for it’s rock-solid stability even though some of the software in Slackware-Current is “older.” I guess using Slackware Current is kinda like using Debian Stable. Older, perhaps, but stable. Certainly more stable than Ubuntu or cutting-edge Fedora, except not polluted with systemd. Gnome3 users take note: The Gnome people have decided to make Gnome3 with a bunch of systemd dependencies. Xfce is still good, if you’re trying to avoid systemd.

The repositories are chock full of awesome stuff, including Seamonkey! It’s nice not to have to add a PPA just to get one particular favorite application and keep it updated. There are all kinda of installation options, from bare-bones to full-on ready-to-play; and multiple desktops to choose from (Xfce is the default in the main edition). Software installation is nice and graphical for us technophobic users coming from the Ubuntu family, using GSlapt Package Manager. It looks and acts a lot like Synaptic! And if it ain’t in the repositories, there’s Sourcery, which works for a lot of users but was troublesome for me during my previous flirtation with SalixOS. Perhaps it’s better now. Sourcery compiles packages listed from source code – all from a sweet graphical interface that also looks and acts kinda sorta like Synaptic.

Rather than post screenshots just yet, I would encourage readers who are interested to look into this little-known gem for themselves. I think it’s a great choice for timid technophobic users like me as a “next step” beyond the Ubuntu family and it’s derivatives.


3 thoughts on “Revisiting SalixOS

  1. UPDATE: Seamonkey badly misbehaved on Salix after using the multimedia codecs installer. It froze and locked up, and the mouse got sticky and then locked. It was horrible! I had to use Midori for web and Seamonkey only for e-mail – until I figured out that the issue was “bad” and “ugly” multimedia codecs! On this old computer I can actually watch most videos and stuff without any proprietary drivers or non-free multimedia codecs. Once removed, Salix and Seamonkey seem to be getting along now. SalixOS has a nice multimedia codecs installer, but by default it installs codecs from the “bad” and “ugly” sets. These can be un-checked (de-selected) manually before installation, but I think the default setting should not include the bad and the ugly.


    1. BSD is still systemd-free, but not Linux. Among Linux distros COMMITED to avoiding systemd are Arch and PCLinuxOS. Slackware is systemd-free but not COMMITTED to staying that way (which is okay, someday when they fix the damned thing), so Slackware derivative that remain true and compatible with Slackware are also systemd-free for now. While there are a number of Slackware-based distros like Vector and others, there are few that remain completely backward-compatible with their parent distro – SalixOS among them, and committed, for as long as possible, to avoid systemd.

      Systemd is a cool idea I guess, but wreaks havoc with many things it touches. Other developers are having to adapt to it to avoid crashes and kernel panics and other headaches. It’s stupid that such a wide net is cast by systemd and everyone else is supposed to clean up the mess it makes of their longstanding software projects. It’s so intrusive and overreaching, but may in time be just unavoidable. Let’s hope that by that time systemd has matured and not all about forcing everyone else to adapt to it.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s