bishopolis

joined 1 year ago
[–] bishopolis@lemmy.ca 1 points 1 year ago

consider PCLinuxOS for a mageia (mandriva, conectiva and mandrake, both branches from RedHat pre-Enterprise Linux) descendant.

[–] bishopolis@lemmy.ca 2 points 1 year ago

if they didn’t kick the cow and spoil that milk like they’ve kicked every cow before it

I miss Cringely's take on this.

[–] bishopolis@lemmy.ca 1 points 1 year ago

. I would not be surprised if this was just a Red Hat thing.

It's a tough one. We blame RedHat for a lot of its half-baked internal fridge art - systemd, network manager; and even, some days, yum in an apt-4-rpm world.

But this new one is QUITE the departure. It's not 'red hat' stupid but a little further on the spectrum.

[–] bishopolis@lemmy.ca 1 points 1 year ago

I was actually about to do that (move to Debian).

Maybe stay within the Enterprise Linux camp for a bit. Not to start a flame war, but when an OS company was deciding between EL and Debians, the RPM format was the deciding factor.

[–] bishopolis@lemmy.ca 1 points 1 year ago

But why would they want to kill their acquistion like that though?

I can only recommend you look at the last decade of IBM's history in that respect.

[–] bishopolis@lemmy.ca 6 points 1 year ago

While Jeff's support for ELs has been imperfect - I marveled at the supply-chain issues gleefully baked into the drupal vagrant stuff - I came here to really say:

IBM's not really the poster-child for preserving the sanctity of source code in the past (cough cough Monterey cough), and I'm surprised they're even suggesting everyone respect their own demands around that.

[–] bishopolis@lemmy.ca 2 points 1 year ago

Docker has an additional issue, but not one unique to docker. Like flatpak, pip, composer, npm or even back to cpan and probably further, as a third-party source of installed software, it breaks single-source of truth when we want to examine the installed-state of applications on a given host.

I've seen iso27002/12.2.1f, I've seen supply-chain management in action to massive benefit for uptime, changes, validation and rollback, and it's simplified the work immensely.

    .1.3.6.1.2.1.25.6.3

If anyone remembers dependency hell - which is always self-inflicted - then this should be Old Hat.

HAVING SAID THAT, I've seen docker images loaded as the entire, sole running image, apparently over a razor-thin bmc-sized layer, on very small gear, to wondrous effect. But - and this is how VMware did it - a composed bare micro-image with Just Enough OS to load a single container on top, may not violate 27002 in that circumstance.