Since you can’t open the case and salvage much, engraving the case is a solid measure to confirm ownership.

Snipe-it failed iso27002 when I last checked.

1. Avoid anything with bad supply chains that fail iso27002
2. Yum via cron
3. Huh. That’s all of it.

Never trust a tech worker, they decided long ago to sell out the species and the planet.

As a tech worker, I resent that comment.

As someone who volunteered time over 20 years to maintain a well-used open-source project, I think your comment is a cheap generalization that shows remarkably low forethought.

As someone who knows what a comma splice is, though, I guess it’s all good.

Never tell the emacs haters why ctrl- and alt-stuff is just so familiar to the rest of us.

Butbutbut the name has ‘open’ in it. How can this be?

(I worked on OpenUnix and OpenLinux, so I get it)

It’s like you neither read the article, nor do you understand how software works.

That’s a bit of a reach.

[TVs] rated for long continuous use

Or, what we used to just label “TVs”. The ones not rated for long continuous use should get a new name; perhaps “weak TVs”.

English as far as I know doesn’t even have a word in common usage for it.

Staling. One L.

In reality, it’s “gone soggy from humidity”. The plastic layer ‘preserves crispness’.

Your first question is a challenge to understand and could do with clarification. The second question is orthogonal to the disputes and membership situation, and may be unaffected if the people involved don’t conflate the two.

I thought Australia implemented some sort of ID verification?

To answer the question as written, you did think so. I’m mostly certain of this. Glad I could help.

quarterhour

quarter-hour

27001

docker

Heh.

Nah. The vendors will kill their ecosystems earlier and all the established internet-of-trash will be e-waste quicker. We’re still using a portal-TV unit and loving it, for example, but so many other products brought out during the sudden rush will be killed while still on umbilical .

Ha! They used to run Unix.

Or …so I hear.

Day job: oneScrote and fucking ansible

Night job: some wiki for the architecture, but just config management for the config detail : we run the docs and it’s done. Thankfully not fucking ansible; because in any environment where there are options, it’s not fucking ansible.

I wouldn’t call systemd just an init system to begin with, though that was the initial project goal.

Scope creep. You’re describing scope creep.

“Systemd is built badly by weaponized dunning-kruger” – pros

exploit [happens]

World: surprised pikachu

Ugh. Come for the systemd, stay for the slop.

33 years with Linux (kernel 1.2.13, slackware). Worked at a distro. Worked in OS security – Unix and enterprise Linux. I helped build United Linux out of the dismembered corpse suse kicked over the fence as ‘collaboration’.

Because of the validation issue in the .deb package format and others, I’m on a mixture of Rocky and Nobara.

I’m subscribed to cloudLinux’s tuxcare enterprise updates for some older stuff, and I can’t recommend it enough. It’s excellent; and if almalinux releases their sLTS distro release and actually covers it for 25 years, that will be such a coup.

I’m worried at the direction Linux has been taken by IBM and I hope it can be unfucked one day. I miss the reliable, fast boots and uncomplicated tooling before this systemd shitshow.