tight-packed schedules

Extra hardware.

Not something sitting there hot and ready to go, but there to take the place of the flight. Maintain a one-unit queue of planes ready to board and launch so that each and every plane sits for 2 hours and is actually prepped.

Or, when that inevitable daily breakage happens and a plane needs to be taken off the line for the day, it allows time to bring in another spare to keep that queue full (of 1) when the rotation loses that active plane.

there was nothing they could do

I’m willing to bet ‘showing basic humanity’ was an available option the flight crew was just unable to consider.

Pierre will tell us we’re still over-funded and his rich friends should pay even less taxes than the pittance they’re paying now.

With no extra airplanes, they probably don’t have time.

Again, the problem comes down to no extra equipment; even when it would give them the lag time to properly clean between departures at no added hw maintenance or aircrew costs.

Agreed. We’ve had just so many experiences of negligence and apathy from Air Canada that we’ve given up on them and also consider them an airline of last resort. We’ll move dates and locations to open up other options before considering them, as well, and even reconsider just not going.

Great news for Air Canada is that Westjet got bought and declined sharply since then, so they’re only much better than Air Canada instead of being in a different category completely as before.

Now do ‘home and native land.’

Not being psychic, I’d be far more reluctant to over-leverage assumptions like that.

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

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.

. 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.

Thank you for this excellent summary. It answers all the questions I had, and it’s wonderful news.

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.

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.

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.

dairy subsidies

Do you mean Canada’s dairy supply management system?

Remember, though, that in the previous arrangements the company recouped almost all the labour costs as offsets to the housing cost. It’s like a tax but unavoidable, and can fund proper facilities management… or profits.

“You dig 16 tons and what do you get? Another day older and deeper in debt…”

There’s a lot of worry about Mr Biden as the nominee; given Ms Harris’ low visibility and back-fill position and his failing health, and how the anti-science challenger in Mr Kennedy is appealing to similar anti-science voters, I’m not sure he’s going to win against Mr Trump who is appealing to anti-science as well as anti-society.

I wish him well but I will definitely be interested in whether our biggest trading partner has a valid government.

Are we still calling LNG a ‘green’ fuel? Is fracking still a big deal, given the impending water crisis?

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.