Gnome makes absolutely no promises of version compatibility for extensions.

You’re stuck waiting for an extension dev to update to support the new gnome version.

Ah. I figured it was plausible enough to ask for a source rather than out right rejected as bullshit.

I see now that was a “got a source to back up that outlandish claim?”

Agreed. That it’s even plausible is a sad state of affairs.

It’s no less bat shit crazy than what we do have sources for.

That server’s root access is now vulnerable to a compromise of the systems that have the private key.

On the context of a node package,

It’s probably a package with one five line function, and a poor implementation at that.

An alternative, if you have console access, to doing that root password dance, is:

1. Drop to rescue/emergency/single-user mode.
2. Do your changes to the user account
3. Drop back to multiuser mode.

“Except for me, in my case it doesn’t count”

They my go to to quickly triage a problem being caused by SEL or not.

Not quite. But sorta, yeah.

Learning to “not fuck with it” or ways to do so and rollback are valid lessons themselves.

Being able to segregate “production” and “development” environments is very valuable.

100%

The alternative being variations on:

Hi my name is [redacted], I have [X] years experience.

Please run sfc /scannow.

You can find more help at [Irrelevant KB URL].

Please rank me 5 stars.

Ticket closed

Theoretically one could also prohibit rebooting.

IIRC kexec is pivot_root but for the kernel.

Anything you need to buy is more expensive than anything you already have.

Especially if youre worried about power costs.

Reuse wha you have, replace when you need to.

Mine are all named for the colour of the case, or case accent when ambiguous, though network infrastructure items are named for their models, being the typical default.

I sometimes use A records or mDNS-SD for the actual services provided and use a *.home.arpa. domain.

Another theme at another site is native fauna and flora names.

No cringe, no pop culture.

embedded RTOS

That sounds like a domain where memory safety is secondary to size and speed… though compile time memory safety guarantees could help.

Good thing we have so many options!

Like riding a motorcycle in a tee shirt and shorts.

Fuck C and it’s lazy shit pointer arithmetic array indexing shortcut. I.e. you just add the index × size(t) to the array pointer.

Bounds checking? We’ve heard of it.

Going from three classes (low, middle, upper) down to two (low, upper) sounds like progress.

Uhn-jun-uhks in NZ TYVM.

That’s the thing, it’s a useful assistant for an expert who will be able to verify any answers.

It’s a disaster for anyone who’s ignorant of the domain.