Treat Your Moderate-to-Severe Technophobia With Linux Lite!

I’ve written before on both my own fear of technology, and about Linux Lite. Today I’ll combine both subjects. It all started with a flare-up of my moderate-to-severe technophobia that started last week, triggered by a discussion on Diaspora about systemd, the evil “one ring to rule them all” program manager used by most Linux distros these days. Just click on the systemd tag for a little more about it (but not much – I’m no expert).

But it’s big and intrusive and “does too much.” Some people complain that it’s an attempt to wrest control of Linux from it’s end-users to the developers, maybe more. The interest of so many “big evil corporations” in adopting it has the same familiar red-flag properties that have people running scared of Google and Facebook, using TOR and proxies online and that kinda stuff. Well I guess it just got to me, having gone on for so long.

I mean, it just depends on how you look at it, right? Or maybe…

I had already dumped Google, killed my gmail account, and quit facebook over fear of becoming a commodity for these companies to sell to advertisers and government agencies or whatever. Now, oh my Lord, systemd is threatening even the sacred refuge I fled to for privacy and safety and dignity! I’ve never experienced any issues – that I know of – with systemd as far as functionality. My Linux OS does what I want it to, does it well, and stays out of my way (unlike Microsoft’s OS). But still…

So…. I went and did something really stupid. Please don’t laugh (at least not where I’ll see you or hear you).

Instead of just switching back to Salix, PCLinuxOS, or any number of other systemd-free Linux distros that I have run before (because there’s no Gnome in any of the Slackware derivatives and PCLOS is too resource-hungry), I tried to rid Xubuntu of it’s horrific, demonic, intrusive systemd. I read on how to do it “safely” before I gathered my courage and ventured into the dark, fearful, mysterious netherworld of the command line interface (CLI). I didn’t do so recklessly or without a plan. I checked and double checked, referred to several official and unofficial sources, and proceeded with all deliberate caution.

I don’t care what the experts say. The only Ubuntu-based stuff that is free of systemd and that can function without it, is based on version 12.04 and older. None of those are supported anymore. I not only crippled my operating system, but apparently something I did in my efforts to exorcise the evil systemd demon from my machine seems to have physically damaged it somehow. Every technophobe’s worst case scenario! Push the wrong button and

Poor old Dell Dimension desktop. It served me so well for so many many years! Linux kept that old relic out of the landfill for decades! And then killed it, mercifully fast. No, I killed it, in a fit of technophobic panic over something that I really know too little about to be so worried about. Rest in peace, you trusty old friend. <sniffle>

But I didn’t spend a dime for my new one. An HP all-in-one with a huuuuge 500 GB hard disk drive! It was unresponsive after an upgrade from Windows 8 to Windows 10. My partner used it to play one of those Windows-based MMPORPGs (Massively Multi-Player Online Role Playing Game) on Windows, and bought a new one to keep playing, and for Skype and other stuff she absolutely has to have for her job… All of which, by the way, will run in WINE on Linux. Now’s my chance to show her just how effective Linux can be as a drop-in replacement for that bloated, expensive OD from Redmond!


I’ve loaded up Linux Lite again, because it has cool tools, Xfce desktop’s simplicity and beauty, and readiness for the tasks I want to demonstrate for my Windows-addicted partner. This new computer is many times more powerful than the noble old relic that preceded it, and I hope it will help me win over one of the most challenging Windows addicts I know.

Stay tuned!

Sticking With Salix!

Well this is certainly unexpected! The first time I tried Salix, it refused to boot after an update, and I was like, “I’m done. I thought ‘borked by an update’ was uniquely a Debian/Ubuntu phenomenon until now. Screw this.”

What an ignorant and impatient fool I was. When an update includes a kernel update, you also have to update your bootloader to load the new kernel. That’s what I did wrong, and it wasn’t anyone’s fault but my own, for not reading the instructions and assuming far too much. Typical, perhaps, of a technophobic user playing with a Slackware derivative for the first time after using almost exclusively Ubuntu-based distros previously. I was used to being spoon-fed and giving the operating system too much automation. Simplicity does not mean “everything happens automagically and you don’t have to do anything but click Okay.” The user is responsible for knowing what the heck he or she is doing!

Salix tells me what my choices might mean during installation and updates, and when it refused to boot after I made a stupid decision, I should have known. Silly spoon-fed Ubuntu user and Slackware rookie.

But y’know what? I think I’m just gonna leave Salix on my old ancient relic desktop computer for good. I’m probably all done messing around with other distros, at least on this particular computer. Here are my reasons:

It’s Slackware-based and fully compatible with it’s parent distro, unlike most of the other Slackware-based “lightweight” distros. This means it has Slackware’s legendary stability and reliability, and ultra-mega-super-duper-uber-long-term support.

It’s super simple! In keeping with the whole Slackware philosophy – and Linux philosophy, for that matter. One application per task. Do one thing and do it well. Stay the heck out of the user’s way.

It’s systemd-free.
I know, before you jump all over me about it, I’ve read all the debates and I think I’ve probably never personally had any issues with systemd, except that even my beloved Xubuntu began to slow down over time (almost like “Windows rot”) and had to be rebooted regularly just to refresh it and dump cache and stuff. It didn’t do that before Ubuntu (and thus Kubuntu, Xubuntu, Lubuntu, Mint, and all their derivatives and spin-offs and remixes) adopted systemd, so I wonder if that might be part of the reason. The “one ring to rule them all” feature of systemd is counter to the “do one thing and do it well” principle that has made Linux so awesome to begin with (until recently). I don’t reboot Salix. I don’t need to. Could systemd be the reason? I don’t know, but it sure is nice not to have the gradual loss of speed over time that I experienced with Xubu and other old favorites.

Yeah, he’s talking to systemd.

Salix doesn’t include kernel updates by default. Why should they? The installed kernel works fine, it’s secure, and my computer doesn’t need support for all kindsa features it doesn’t even have. It ain’t broke, no need to fix anything. The only thing I change is the wallpaper occasionally, or fonts and stuff. It’s perfectly boring, as it should be.

My distro-hopper-stopper is Salix.

I haven’t tried it on the laptop yet, but that’s another post for another day.