It's been quite a long time since I did any updates on this blog so a couple of updates are in order
House
I've now been living in the new place for just over a year. Generally everything is good, we've started putting in a lawn and currently letting it get its roots in before we try to cut it
Twitter
Oh, boy, what an absolute train wreck. I've tolerated Elon's presence at Twitter because most of the stuff he did wasn't far off what Jack was doing prior. But cutting off all third party clients, forcing everyone onto the new TweetDeck (which likely will be paywalled too) has literally driven users away. Twitter has been losing users and revenue constantly, and it is totally unsurprising.
I've disabled my two TweetDeck profiles (a professional one, and a casual one) from Ferdium. But I doubt I will be going back any time soon.
Red Hat
Another train wreck of a situation. Red Hat's decision to first kill CentOS's stability, then for RHEL sources to only be accessible behind a subscription has pissed of a lot of users, even if it's not strictly speaking against license.
The only one left in its sights will be Fedora so that leads me onto the next update
Manjaro & Archlinux
I've been tinkering with Manjaro more and more lately, with its rolling release schedule meaning I never need to upgrade from a major version to another major version.
It's downside I'm finding is that some packages, especially those in the AUR are essentially "compile from source" packages which does the build on your machine during the install. This can take a varying amount of time depending on the code. With my RSS reader of choice: QuiteRSS, this build takes a mind numbing 2.5 hours to do, even on a high spec machine.
That's where I found out about setting up your own Arch repo. I've been tinkering with that, setting it up on GCP and fronted by a CDN. This works pretty well, but I still need to find how I can do scheduled builds to keep that up to date, but it looks like I'll be switching to Manjaro at some point in the near future. Sound works fine, using lyncolnmd's work.
Another downside with Manjaro, however is that its btrfs filesystem, my home directory backup, and CloneZilla don't seem to want to work well together
Wordpress & Domains
One final update, I will likely be transferring out the blenderfox.com domain out of Wordpress, while I had this registered as part of the blog, I'm finding it much harder to maintain this domain using Wordpress's very limited DNS management tools. I will likely transfer it out to Google Domains, even though there's talk of them shuttering that service. Secondary service would be AWS.
So, quite a few things have been happening recently.
I tried to go the next step on Manjaro and copy my home directory across ready for me to run the Ansible playbook to do the setups (I've been testing it would work via VirtualBox on my Windows laptop)
After waiting ages for the file copy, when I went to do the backup, there was a btrfs checksum error so I'll have to try again some other time.
Separately, I got a message on an issue I raised at Fedora's bugzilla the Fedora 36 (the version of Fedora I raised the bug on), was coming up to EOL so I should look to move away from it or upgrade. So I decided to try doing the upgrade.
The upgrade completed without error, but first boot after the upgrade hung with a weird Kernel Panic error (I have posted this on the Fedora Forums)
So I rolled my laptop back to preupgrade state for now.
I suspect I may need to end up doing a clean install, so I've prepared a btrfs and a ext4 lvm installation and have imaged those in preparation.
Finally, Wordpress posted that they're stopping Autosharing to Twitter because of Twitter's Idiot-in-Chief screwing up the API usage.
Still, they have mentioned they will be adding autosharing to Instagram and Mastodon instead, and that helps me, since I'm slowly moving what little Twitter presence I had onto Mastodon anyway.
My Twitter has been disconnected from my Wordpress and I've revoked its access from Twitter's side anyway.
I've been continuing to tinker with ArchLinux and Manjaro and have since found out about "Oh-My-Zsh" and "Oh-My-Bash" -- basically addons you can add onto your shell via the shell's rc and profile files and it provides a really nice prompt that tells you additional information at a glance, like which branch you are in if you are in a git repo, or whether the previous command returned a non-zero error code.
They are quite polarising though, as I found out when I mentioned this to one of the systems architects here in the office. One of the architects told me someone he worked with even considered OMZ malware.
Vanilla ArchLinux uses bash out of the box, Manjaro uses zsh out of the box, which is how I found out about the OMZ/OMB addons.
OMZ has a ton more plugins than OMB - unsurprisingly since it's also the default shell for Macs (vomit).
I did start copying my files across to my Manjaro installation. It took nearly 6 hours to copy. However, when trying to do the backup afterwards, it failed with a btrfs checksum error. That worried me since I hadn't done anything since the previous backup other than copying files.
I do remember running into similar issues with btrfs last time I tinkered with it when reinstalling Fedora. It could end up with me switching to either ext4 (like I did with Fedora) or trying the xfs file system option in Manjaro.
Referring to my earlier blog post, I finally got Manjaro sound to work and have been spending my spare time working on getting the Arch/Manjaro side of my setup playbook to work. VirtualBox has helped with that.
I've been struggling with making CloneZilla backups on my new Toshiba SSD. The transfer speed onto it is horrendous, but the speed on my Samsung SSD is fine. And the return window is now closed so I can't return it. I guess, I'll need to look at purchasing yet another external SSD.
After spending many years using Ubuntu, Debian and Fedora, I've decided to look at going a bit deeper and start tinkering with ArchLinux
Initially I tried to use Manjaro, but I couldn't get its sound working with my Pixelbook, even using u/LyncolnMD's setup (reddit link here). That being said, a commenter on that thread did say they had sound working, so I'm not sure how he made that happen.
Bizarrely, under vanilla ArchLinux, on which Manjaro is based, it works. So I've decided to go into ArchLinux instead.
I spend several hours making backups of my current Fedora setup and making CloneZilla images.
It took several hours to copy back the files too (212GB of content in my home folder).
I have also decided to reutilise my pixelbook-fedora-setup repo to configure for archlinux too. That will take a while to reconfigure everything since ArchLinux uses pacman as its package manager (with some AUR helpers like yay or pamac). Ansible has a pacman module, but no yay module, so each time I have to use yay to install packages under ArchLinux, I have to use the shell module instead. A minor issue, and I can see a few people have already worked on some yay modules, but none are officially distributed yet.
So until I finish reconfiguring my pixelbook setup repo, I'm staying on Fedora. I'm using a VirtualBox machine to do the testing of the setup.
I've been getting horrendously slow speeds on Linux Steam (~500k/s) and 5-6Mb/s on Windows, and only now found out why. There's a ticket on GitHub for this:
In short, the client is very aggressive on its DNS requests, which normally causes it to be throttled by servers, leading to really slow downloads. However, using dnsmasq allows the requests to be cached locally and offload the requests.
Even though the instructions are for Arch, they worked for me:
Install dnsmasq
Modify /etc/dnsmasq.config and add the line listen-address=127.0.0.1
Restart the dnsmasq service (systemctl restart dnsmasq.service) or reboot your machine
