I paid for the premium version of Citymapper primarily because I need to use their “speak directions” option while on public transport. Something that used to be free, and then they put it behind a paywall.
Now they only went and made it FREAKING FREE again, after I’d gone premium and paid for the year >_<
The final issue with the post-upgrade is now fixed (dependency issue) and it self-resolved by a new package update that came through this morning
I did fine one new issue — a new kernel dropped and installed successfully, but did the same thing as the upgrade and did not generate an initrd line, but did generate the initrd line once I regenerated the grub configs.
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.
This article popped up on my Google News feed and the first thing that caught my eye was the fact the headline mentions they were sacked, but the subheading says “affected due to layoffs”
Laying someone off is not the same as sacking them. As someone at work explained: sacking someone is when you keep the role but do away with the person; layoff is when you do away with the role, but (sometimes) keep the person. These workers were laid off since they also got severance pay. Something you’d never get if you were fired.
In fact, this article may get the writer and the publication in trouble. Being fired has a far more negative impact on your career than being laid off so anyone of those 140 workers trying to get jobs elsewhere may find it harder to get a new job if their prospective employers do a basic internet search and find this article that implies (incorrectly) that they got sacked.
You must be logged in to post a comment.