If you want solid reliability, Debian is where you might want to start. Particularly on an older PC where the hardware should be well supported. Make a live install image USB boot drive and see if you like it before you decide.
Debian is all about stability, at the cost of having less recent software. For newer versions of the desktop environments you could try live boots of KDE Neon and Pop!_OS as well.
Interesting!
it wasn't for dumb people who didn't know any better
I mean, it kind of was though, wasn't it?
Just because more knowledgeable people found it interesting and got it for the novelty or to see how it worked doesn't mean it wasn't a product intended for people who, Kodak hoped, wouldn't know any better. That doesn't mean I'm saying your father didn't know better.
Hopefully he's still around and you can ask him about the relative image quality between those formats. If he was interested in quality, he wasn't going to grab the disc camera. It wasn't like Betamax where it was superior but lost a battle in the marketplace. Disc film was objectively much worse than even 110 while being much more expensive to buy and process.
It's not bad to get running, and the alerting is really flexible. You can add Nagios and syslog alerts easily too.
We watch many of yours, and also Trading Places.
Eating salmon through a filthy Santa beard. Delicious!
I moved two servers from Ubuntu to Debian after Bookworm released, and the graphs on my management server were interesting. Suddenly running 30% fewer background daemons and much less memory usage with the same workload.
If snapd was pulling from an open-source backend it wouldn't be as concerning for me on a desktop. I still might prefer flatpak, but as you say, there are conveniences. My laptops and desktops are on openSUSE and Fedora to have more up to date software in the repos than Debian.
But for a server I see no need for snaps at all. And yes, it's not difficult to remove snapd, but why bother when I can just run Debian. If I wanted a support contract from Canonical then it might be worth messing with it. But I'm just selfhosting at home.
Being force-fed snaps? 🤣
No Data = Stealth Corn
Using it here. Love the flexibility and features.
If you want to keep using networkd, you might want to consider if multiple interfaces are causing the wait. NM doesn't care, but networkd gives more granular options for dependencies. If you have wired and wireless and only one in use the systemd-networkd-wait-online.service waits for a timeout period. You can find lots of info on it related to boot delays with that service.
Try the --any switch on the systemd-networkd-wait-online.service launch configuration. This will tell the wait-online service that any single routable interface is enough, you don't need them all.
Run:
sudo systemctl edit systemd-networkd-wait-online.serviceThat adds the override.conf for the service. Add these lines:
The other possibility is if you have virtual .netdev devices configured (VPN, bridging, etc) and some of them are not essential for the machine to be online, you can set RequiredForOnline=no on the ones that aren't essential.