3 ms·
Containers aside, I've long considered RHEL the go-to for production servers with a commercial budget. Partly because they've always had one of the best assembl
by neilv 6y ago
Containers aside, I've long considered RHEL the go-to for production servers with a commercial budget. Partly because they've always had one of the best assemblies of kernel people and other heavy-hitters, and are just generally credible for production.
With CentOS (before this latest news) possibly making a lot of sense for when you don't have the budget for RHEL, or don't yet have it, like for startups. Which then gives an easier upgrade path to nobody-ever-got-fired-for-buying-IBM/RHEL.
I don't have as much confidence in Ubuntu, and the last few months of monitoring security update regressions hasn't reinforced confidence. And the Grub problem this year, which could've bricked some remote devices for me, and where some other distros seemed more earnest and upfront about the problem. I've also grown skeptical of Snap (especially on workstations and servers, though I haven't yet ruled it out for appliances, as an easier path than Yocto).
For personal systems, I've been using Debian Stable for about 20 years (which I initially moved to because the APT network package management experience was vastly better than scouring various RPM sites or building from source, and later decided I also like the principles). And recent Ubuntu experience is making Debian compare favorably for some kinds of production use, though I'm aware of some of the substantial weaknesses of that.
Of course, then there's containers, which sometimes encourages a stripped-down distro within the container, and different requirements for what's hosting or orchestrating those.
- morrbo 6y agoMind explaining a bit more about the weaknesses of Debian in prod? I'm a Debian fanboy and from what I can gather people are still hung up over the SSH keys security fiasco (which was [and handled] extremely bad ofc) a long time ago, but am obviously wrong here so would love some enlightenment from someone in the know
- neilv 6y agoThe keys incident was a good example of one general weakness that I'd want to vet: how easy is it for an arbitrary one of the numerous Debian package maintainer to introduce a change (accidentally or intentionally) that compromises the system? Before that incident, I'd already had mixed feelings about Debian-specific changes to upstream, and one of those turned out to be a whopper. One thing that's reassuring: both of us thought immediately of the same incident, from years ago, so there's not like there's a stream of known defects discovered frequently, like in some other other areas of this general kind of system. Another thing that's reassuring about Debian is that some of their principles or policies align with security. For example, in the past I reported an instance in which upstream code of a package was effectively phoning-home to upstream unnecessarily, and Debian took it seriously, and fixed it. I like that the intent is there, so hopefully they'll catch many problems before I have to, and not introduce new problems on top of upstream.