Looking for status on #copyfail with an #openSUSE flavor? Short answer, make sure to zypper dup for #Tumbleweed and #Slowroll. Get more info about it at https://www.suse.com/c/suse-responds-to-the-copy-fail-vulnerability/

Is Slowroll on systemd-boot yet?

https://piefed.social/c/opensuse/p/1992675/is-slowroll-on-systemd-boot-yet

From the shoemaker's children go barefoot file...

On Sunday I didn't have any plans and was going to nerd out working on a personal dev project.

I'd suffered with a partially broken efi and initramfs on my primary Linux desktop because I didn't want to risk reinstalling and dealing with locally built kmods, packages, and customization. It's been this way for a few months, accumulating over years, and I kept putting off a base OS reinstall. I have other, slower, machines but it's convenient to work directly on the daily driver...

I localize stuff on a ZFS pool with stow and guix. I take nightly backups of that and my homedir anyway. All my dev environments and tools live there, mostly... some stuff ended up in /opt which wasn't backed up.

So of course I managed to accidentally crash the system and couldn't recover. My Sunday was now planned for me: a fresh #opensuse #slowroll install.

Pros: Fully up to date. System performance feels quite snappy. New KDE plasma seems nice. Jack/Pipewire works properly again. Successful test of my backups.

Cons: Didn't have years of shell history (#atuin) or some configs (a broken switch to XDG_* paths from who knows how long...) on ZFS. Discovering an error at a time what I didn't localize and need to reinstall.

Actualizando #openSUSE #SlowRoll, un placer ver todo al día para este fin de semana.