Is that suse-on-a-phone just a tease, or something awesome I have yet to discover?

The beast and rider vaguely make up the “A” shape of the Arch Linux logo.

How much red could a red-hat hat…

lol… if they had a job that was ONLY writing unit tests, I would take it!

Kind of the reverse… more lamenting the loss of QA and SRE roles in favor of mechanical (AI) code reviewers and non-technical persons rubber-stamping an increasingly deep pipeline that change requests must traverse.

With that typo, it sounds like a personal insult. :)

The trick is to have a second EFI partition. One for windows to destroy, and one for linux to enjoy.

Well how about that… all this time I thought they were the same character. IIRC, child-me thought it was Wile E’s day job so that he could afford all those ACME products.

https://looneytunes.fandom.com/wiki/Wile_E._Coyote

Getting flashbacks of me trying to explain to a mac user why using sudo “to make it work” is why he had a growing problem of needing to use sudo… (more and more files owned by root in his home folder).

Come to think of it… it’s also addressed in TNG when the guy from the past calls the captain on the intercomm, and says something like “if I was not supposed to use it it should have a lock/code”.

I can get the perspective behind the last one (unauth access). Coming from a closed society it may be unthinkable for someone without authority or authorization to perform an action “unauthorized by the authority”, but in an open society the mindset would be quite different. Much as we might without thought throw a light switch without expecting authorization, or maybe like the hoplophiles that don’t want an electronic lock on their weapons, perhaps what they optimize for (i.e. their security model) could be for even an extreme case such as if “the only survivor” is one unbadged civilian with no bridge/engineering knowledge needing to control the ship (and even weapons) with the usual security case simply being that the bridge/engineering is a secured by persons/staff… IIRC, even knowing who performed such an action is a distant secondary concern (in Voyager it is said that control panels try to log who uses them be the comm badge present), but I know of at least two cases where command-and-control was locked: one in TNG by data (which is presented as quite an exceptional workflow), and one shuttlecraft in DS9 by O’Brien (which might be more of a consideration for scouting operations… to help ensure one has a vehicle to come back to). Conversely, it seems far more frequent that the computer denies access to data in defense of another’s personal privacy.

You might be looking for the “ssh socks proxy” option (-D?).

It’s that awkward language between C and Zig that (even decades after it’s realized to be a false start) will take forever to die.

Ackshually… in season three episode seven “The Enemy” it is made clear that Romulan technology is generally assumed to be completely interoperable when Geordi could not connect his VISOR to his tricorder in more than a superficial way… Quote he: “they don’t speak the same language”. :-)

Maybe run a bandwidth speed test, and enable/set qos to 95% of that value… I found that’s an easy way to kill the buffer bloat (way better latency).

If you can wait a bit for the Rocky 10 release, you’d get a decade of boring rock-solid secure computing.

Someone needs to send this to uncle bob.

Tsk tsk… forgot to clean up your temp file!