kjetil

In both client config and forgejo config? And docker config?

It's working for me, but I had to add a config to my ~/.ssh/config file

For Bazzite , I search for "how to do X in Silverblue", or "how to do X in KDE"

Bazzite is built on the same technologies as Fedora Silverblue (immutable base, ostree, btrfs etc).

You probably already know this, but just to be clear; Timeshift (by default) only backs up your system, but not your data, documents photos etc . Basically everything outside your Home directory.

You can probably tell Timeshift to also backup your home directory, or install a separate backup app for that.

Difference is timescale. Coal "sequestered carbon" over millions of years, and released over a few decades.

Biomass gathers and realeases on the same timescale

From the article:

In a statement, the police in Finland said the authorities had boarded the Eagle S tanker in Finnish waters.

So no international waters in this case. In fact there are no international waters in the Baltic Sea ( https://en.m.wikipedia.org/wiki/International_waters )

Thanks, I'm running Bazzite on a (gaming) laptop now, but I'll install Aurora next time I set up a laptop

I was about to say Bazzite. But Aurora seems to do the same thing? Fedora UniversalBlue based atomic image, with KDE and a sprinkling of of handy out-of-the-box stuff like proprietary codecs, Nvidia drivers etc

Any idea where these hundreds of unused Docker volumes came from?

Yes, this happens automatically for me when I launch games. I don't remember doing anything special to set it up (Kubuntu with nVidia drivers on X11). I do mostly game in true full screen though, not "full screened window"

Amazing project, well done HeavyBell!

I've had a WD Blue SSD completely die in the past, but that could be coincidental. Then again I now have a WD Black nvme where the SMART error counter trickles upwards, so thanks for reminding me I need to change it xD

I've also had a Kingston SSD fail on writes, and a Samsung SSD where the error counter trickles upwards, so it might just be coincidental. I've also encountered a batch of very expensive Intel SSDs dying early due to a firmware bug, so... TLDR: WD Blue is probably fine :P

Regarding TimeShift, I'm assuming you've specified what it should back up, and where. By default it only backs up system files, basically everything outside your /home folder. And stores it on the root partition. That setup is great for recovering from bad system updates, but useless to protect against drive failure.

Assuming you have specified TimeShift to backup your home folder, to a separate physical drive, then twice per day sounds fine. Daily would probably also be fine. Just ask yourself how catastrophic would it really be to loose 1 day of changes?

Oops, sorry, I meant 'dmesg --follow' (or 'dmesg -w' )

Normally the dmesg kernel log will be quiet after boot, and only give new messages when there's hardware related changes, like pluging in or out a USB device, or the charger cable.

In my case the log was spamming several messages every second non-stop so it was very obvious