Fair call. In any case I think you'll find things moving towards bootc and away from having to know rpm-ostree at all. The bootc documentation for fedora is pretty good and the Universal Blue project has built some awesome distros that use bootc.
That all of Debian will have a baby? Or that all of ArchLinux gets impregnated at once? Big projects are usually not led by a single person....oh whait...linux is, and now Linus cannot have sex anymore, thank you OP.
Debian handles all of these transitions by itself during upgrade process, and shows you a nice readme before starting all of them.
For example, Debian has finished two big transitions recently. Merging /usr and 64 bit time support. Both are done on testing, and even on testing nothing has broken.
Another big change (which also made HN front page via LWN) was /tmp behavior change. It's handled differently. If your system is already installed, it doesn't change the behavior, but new systems will behave differently.
All of these changes are again communicated via "NEWS" mechanism. If Debian changes a config file, it's replaced. If you modified this file, apt will ask what you prefer, and you can diff the file in place.
In the past, many similar changes are made, and all were transparent. If you're not using any external repositories which change tons of system packages with their own versions, nothing changes during upgrades for you.
While there's an extensive release note provided with every release like [0], the upgrades are pretty straightforward.
As a result, having a few or many Debian systems which are older than a decade is a norm, not an exception.
... And we all know that rolling upgrades frequently introduce breaking changes that don't make sense for enterprise environments. To your (great) point: Customers pay companies like red hat for software stability, both in how it works and how their software interfaces to it.
Is the problem ultimately to do with your configurations on your centos 7 boxes? Converting to rhel should be easy if you aren't doing anything that red hat wouldn't support in rhel.
Yeah, I thought so too (since they're only moving from COS signed to RH signed), but it's hard to describe. I've had everything from proxy issues; to python; to PHP-fpm breaking after the upgrade. It's just a constant flood of 1 step forward 3 back. Some from random gremlins. For example, last week I wanted to try a test conversion of a box to Alma linux and it worked fine, but broke PHP, so I had to revert the snapshot.
This week, the analysis blows up completely, despite nothing changing on the box. And that's just dev systems, I have zero confidence to move any prod systems.
reply