journalctl -xb-1 where 1 is last boot, 2 is boot before that, etc.

Fedora’s KDE is bulletproof on any of my installed systems (8 or 9 of them, completely different hardware including AMD). Now Kubuntu, on the other hand, has always been a shitshow, I’ve never had it work right for more than a couple days at a time.

I’ve been using the Collabora option for the mastercontainer since the start of the AIO, it’s worked well for my users.

Atomic distros update in a monolithic block and if it fails, it’s as if no part of it occurred.

Immutable distros have a readonly filesystem and you can’t change any part of the system without explicitly remounting the files to write, then doing your updates. It’s not necessarily atomic when that update occurs, either.

You don’t need to layer or containerize applications you install in an atomic system, you can install an application as normal with the system package manager, it just has to complete successfully to be installed, then it becomes part of the overall A/B update system.

Immutable distros need to containerize the installations, or use layering to apply applications to the underlying RO filesystem, which makes installing software rather a pain in the ass at times.

OP keeps using the word “atomic” but the questions and explanation are more about “immutable”. And my answer to them about why wouldn’t I use an immutable system is pretty much the last, installing/updating/troubleshooting non-system software is a pain in the ass. On a dev station, it’s a nightmare.

I wonder if OP and about 3/4 of the people in here understand the difference between atomic and immutable.

This is the way.

I remember building the kernel with the NE2000 drivers and having a network card for just installation and getting the 3com or RTL driver source over to the new install, then compiling those drivers, installing them, and downing the system to put the proper card in. There was a very small subset of sound cards and video cards that worked reliably. The notion that Linux was the OS where hardware just worked out of the box was ludicrous.

The DEs were pretty horrible and the software to use on them was scant. So desktop Linux was a pipe dream. I used Linux entirely as a security/server appliance. I built a couple hundred iptable/ipchains firewalls for businesses out of recycled pentium type desktops until hardware firewalls became a thing, it was fairly lucrative for a while there.

Ha, I still use rods for certain things.

Commute gone down?

I listen a lot because I’m either working where I need ear defenders and so I listen on BT headphones, or I’m in a combine/tractor. I’d be bored AF without podcasts.

Dammit, that’s one of my favorite podcasts.

Support had been dwindling and ad revenue is nearly non-existent for Linux podcasts, so I totally understand why. Still, too bad. I guess I’ll bump my donation to Late Night Linux since I can’t really find another self-hosted podcast that’s worth listening to.

Not as confusing as Debian though.

I can get notification to ntfy, but I’m not sure if the app is certain to blow my phone up until I notice it, which is my goal. Frankly, if I could trigger the Presidential Alert, I would do that.

The application isn’t 100% likely to stay active in the background it seems. I tried to program one myself but there’s a lot of bullshit going on in background apps in Android that I’m not familiar enough with to trust that I can do any better.

Any suggestions for services that do that? I like the idea, I’d actually get a few different phones to ring if some of the alarms were to get triggered.

This is my summer solar system. I like to winter in the Antares.

There is a guide in the Mail cow docs on integrating Roundcube, that’s the client I use for my stack.

I mean, it’s bcachefs. It’s far from production ready.

If LO doesn’t work for her, there are other options like OnlyOffice and WPS Office as well.

I’m not sold on GLinet’s implementation of OpenWRT. I have 3 of them in production, and all three need regular reboots to stay working. I like the VPN interface they have and the ability to get to the underlying Luci interface, but I’ve found just flashing my own device to have a more stable and deterministic result.

I can’t speak to VLANs in specific, because I haven’t trusted them enough after seeing the rest of it to use it anywhere critical enough that I use VLANs.

I’m trying to figure out how to add it to Mailcow Dockerized and hook the existing containers. If I sort it out, I’ll probably PR it to Mailcow. I think it would a nice addition to start to build out a network that isn’t susceptible to the same spam attacks as regular email (yet).