Just because Greg KH said that all users of the 4.4 kernel series must upgrade ;-) I’m happy to report that everything seems to be working as expected and have yet to notice any regressions.

In other “exciting” news: I’ve now been running this website on the RPi3 for 8 months without having a single “what just happened?” moment. Actually, the only reason why I’m still having a WordPress blog can be attributed to my amazement with the RPi3 actually being able to run this crap.

Dlackware is not your average “GNOME for Slackware” project but instead aims to take the slack out of Slackware. What you get in return is the latest in “enterprise” technology. Dlackware delivers a fully functional GNOME 3.22 desktop with PAM, Wayland and systemd.

These steps are partly dependent on my personal Gentoo installation and should not be viewed as a general recipe. Please refer to the official Gentoo wiki on the topic instead. I’m using genkernel to generate an initramfs and GRUB2 as my boot loader.

Most people have probably heard about the Internet of Things (IoT) by now and how these devices are constantly drafted for your friendly neighborhood botnet. My little place on the interweb is currently gaining popularity among my DVR based visitors. You know the type: running a public telnet service, using hard coded accounts and may occasionally be seen sporting an additional backdoor on port 31337.

These bots are posing as Googlebot, but they are effortless to identify due to their use of the old and largely abandoned HTTP 1.0 protocol.

With all the noise lately about Dirty COW (CVE-2016-5195) and the lack of patched kernels from Slackware’s “Benevolent Dictator for Life”, I decided it was time to roll up the sleeves and get it done. Since Slackware doesn’t have a “sophisticated” build system and all that grease, it’s a trivial matter to step up to the plate and take responsibility for your own system. I’ll be using “vanilla-kernelversion” as my tag for the kernel and initrd. Also notice that I build my kernels as a normal user.

I got a call last week from a client that was having some issues with retrieving email from a Dovecot IMAP server. The client was connecting over TLS and was using an Apple mail client. Upon checking the mailserver log, I was greeted with a flood of rather vicious looking errors. I’m not gonna post the entire backtrace since its rather long, but you’ll get the idea.

My RPi3 just missed the six month uptime mark due to a power failure that also caused some minor data corruption. Interestingly, the RPi powered up before the network equipment was online and thus failed to synchronize the time. I didn’t notice immediately but things go sour quickly when a Internet connected device believes the date to be Jan 1 1970.

I was playing around with an open source video editor named OpenShot when I suddenly felt a familiar shiver going down my spine. I felt the unmistakable presence of evil, and it was coming from inside my own computer. ‘You will know me as the Google Analytics measurement protocol’ the beast answered upon detection.

As of Wednesday, August 24, 2016, Slackware ARM is out of retirement and ready to power your modern ARM devices. The Slackware ARM maintainer has made the decision to pick up development again and go ahead with a hard float port. It was announced three months ago that a hard float port was in the works, and today it’s powering my Raspberry Pi 2. Unfortunately the hard float release has been mostly ignored by the mainstream teach sites, but it’s definitely on top of my list. Get up to date with the latest development at arm.slackware.com.

After four months of hosting this WordPress blog on a RPi3 I have yet to experience a single issue. No filesystem errors, no kernel oops’s and no hard freezes. Definitely an enjoyable change of pace from the preceding twelve months of hosting this site on a Raspberry Pi 2.

I’ve not been doing any overclocking whatsoever on this device and I believe that to be the decisive factor when it comes to improved stability. My old RPi2 is pretty much useless at this point and I’m guessing it simply got burned out before its time. As for storage, I’m still using a SanDisk MicroSDHC Ultra UHS-I 32GB card.