Should you run ‘testing’?

Bill, a photographer friend from Florida who is also a programmer recently decided to try Debian, and, some days later, decided to upgrade it from ‘stable’ to ‘testing’. I commented on his blog that I had done so as well for a while, but in the end I decided that ‘stable’ was more than good enough for me, so I stayed with that until now (and probably always will).

In case you don’t know, Debian comes in mainly three different ‘flavours’, namely ‘stable’ and ‘testing’ as noted above, and also ‘Sid’, with the latter being the ‘unstable’ branch (with ‘Sid’ being the ‘bad boy’ from the neighbourhood who breaks toys from time to time, so ‘unstable’ Debian will always be called ‘Sid’). If packages don’t get any error reports after being uploaded by developers to ‘unstable’, they usually get into ‘testing’ after about two weeks, for use in a wider audience, and thus with the chance of getting more bug reports.

So ‘testing’ isn’t as ‘stable’ as ‘stable’, but also not as ‘unstable’ as ‘unstable’, but are that all differences besides having newer packages?

No. While there are many good reasons to use Debian, running ‘testing’ still has some risks; its page for instance names the biggest one as: ‘Please note that security updates for “testing” distribution are not yet managed by the security team.’ It’s also work in progress, and as such lacks a lot of documentation, and to even get it, you’ll have to move to the Debian-Installer page which is *not* the one for the official ‘stable’ installer. You’ll have to follow the Debian Release Management team and their pages to get some updates on it from time to time other than their famous and proud quote “quando paratus est” (=”when it’s ready”). And the team’s release-critical bugs page lists the number of problems which are still to solve until the freeze for the next version of Debian, which at the time of this writing will be called ‘Bookworm’ (like always, after a character from the “Toy Story” movies).

Release critical bugs for Debian ‘testing’ as of today. Release dates are when RC bugs (the green line) are zero, that’s where the “when it’s ready” comes from, and Debian can be rightfully proud of that…

Don’t get me wrong – Debian ‘testing’ isn’t ‘unstable’, or worse than any other Linux distribution, even those with some kind of “Enterprise” in their names. But it’s also not ready, and as such not meant for all of us. If you’re a developer, you’ll run both ‘stable’ and ‘unstable’, simply because you’ll have to send in and upload new packages against the latter (I did so for a while as well, but never became an official Debian Developer due to lack of time). If you’re an average Joe (or Jack or Wolfgang) like me, you’d probably be better off with ‘stable’.

So to run ‘testing’ has some risks you’ll have to cope with, and as such in my opinion isn’t recommendable for the greater audience, most people who want newer packages than ‘stable’ has would be better off with adding the ‘backports’ repositories to ‘stable’, and so get some stuff earlier than with having to wait for the next big release date.

But as I said, Bill is a programmer himself, and like every developer he has read the documentation and so he knows what he’s doing. If that’s you as well, then go ahead and run ‘testing’, or anything you like. For me these days (approaching retirement), it’s too much effort to constantly care about my operating system, so I’m happy to have ‘stable’.

My 2 (Euro-) Cents of course, and as always, thanks for reading.

7e6_7064491-pssst
… (pssst – no words and no title), Mörfelden-Walldorf 2022

Whispering: thanks for viewing… 🙂

Wilma is here :)

In fact, at the moment, both neighbours’ cats are here – Cookie is sleeping on the couch, and Wilma on my bed. Here she is resting against my leg:

7e6_7064484-wilma-resting
Wilma resting against my leg, Mörfelden-Walldorf 2022

We’re happy to see that little whirlwind again – but I wonder what happened to her offspring, haven’t seen any (yet)…

As always, thanks for viewing.

The race to reclaim the dark, on BBC Future Planet

Here’s a nice article which explains the importance and the benefits of having a dark sky. Britain seems to be ahead and leading, so bravo 🙂

https://www.flickr.com/photos/wjlonien/26260428525/
Riding piggyback on the observatory’s largest telescope to see the stars…

In the photo above you see lots of stars – but on the left you also see the heavy light pollution of the city where I took this (Darmstadt, Germany).

As always, thanks for reading.

Below the sphere

What a nice chillout song from Andri and from Wade – couldn’t resist to add my ‘grandma’ to it:

This track is embedded with the friendly permission by the creatives on wikiloops.com.

As always, thanks to my friends and to Wikiloops for all the fun, and thanks to you for listening 🙂

Trying Fedora and Suse, on Arch

I’m no “distro hopper”, and pretty much set with what I have on my machine – and if you are reading this since a bit, you’ll probably know that I’m normally using Debian Linux, and for some newer things, Arch.

So when my friend Bill from Florida (a really good photographer who also has cats and dogs and is a computer nerd) wrote about Fedora and some problems he’s having with it, and when shortly after that seeing that I just got new Gnome “Boxes” on Arch, I decided to try and see…

For those of you who might not know Linux: on that OS you normally have both qemu and also kvm, which means that virtualisation is built into the kernel and your operating system already – and with a smart tool like the mentioned “Gnome Boxes”, the installation of other systems is only a few mouse clicks away, and really child’s play, even if you’d want Windows.

So I went and downloaded Fedora Workstation, and because I was curious I also downloaded openSUSE Tumbleweed, and installed them both in Boxes. First, Fedora:

Welcome Screen of Fedora Linux 36

and a few minutes later, Suse:

Configuration of openSUSE Tumbleweed

Because my machine has “only” 16GB of main memory, and my host operating system has a system drive of ~240GB, I was a bit conservative and chose the default settings of 2GB of RAM and 20GB of storage for both. Fedora comes with Gnome42 by default which is fine, and openSUSE asks you, and from (old) experience I assumed that the first option (namely, KDE Plasma) was/is still their default one, so I chose that.

And voilá, both running in parallel on my Arch system as their host:

Linux³

I haven’t tested much yet since I just interrupted my “work” on a beautiful Wikiloops song for this, but what I can say so far is that at least in my virtual machine and from my desktop, printing wasn’t a problem with Fedora – I had to give the Gnome desktop the local IPv4 address of our printer (an OfficeJet Pro 7740), but then I could print a test page no problem.

I’ll have a look at both and report more if there is something to say about these.

For now, and like always, thanks for reading.

P.S.: just discovered another first of usually many little “niggles” I have when testing Fedora – look at the clocks, after falling asleep for a while:

Fedora likes to sleep a bit longer as it seems…

So often I have tried to love it… :/