Back to webnames for you.

I don’t prefer proxmox, but I will say that when you have even a machine with 8 or 16gb RAM, virtualizing a workload on it just makes sense. At that point the cost is 12% resources, and the benefits IMHO farrr outweight that.

expensive piece-of-shit (enterprise) systems, since they sometimes explode if your server changes interface names.

At no time in the past 25 years with Medium Iron have I seen something blow up on a reboot because an interface comes up late. We’d solved the issue of unreliable init order in 1998 - RH6? Zoot? Compaq, Supermicro, even embedded stuff on was-shit/still-shit gigabyte mobos. /etc/udev/rules.d handled this reliably, consistently and perfectly. Fight me.

so does RPM.

Careful. Jeff’s format gives us really great advantages from an atomic package that we don’t have elsewhere. THAT, at least, was a great thing.

Lennart’s Cancer, though, can die in a fire.

It’s amazing how many linux problems stem from ‘Redhat, however, found this solution too simple and instead devised their own scheme’. Just about every over complex, bloated bit of nonsense we have to fight with has the same genesis.

Ansible can be heard mumbling incoherently and so, so slowly, from the basement.

Remember who saw apt4rpm and said “too fast, too immune from python fuckage, so let’s do something slower and more frail”. twice.

A someone who worked in OS security, I beg you dont use flatpaks.

per serve

“No child left behind” meets the corporate world.

Intel went ahead and used it to build Management Engine, arguably one of the most widespread and invasive pieces of malware in the world, without even as much as telling him.

Is that arguable because it’s complete bunk? You may as well say the same about IPMI.

The best kanban is the one you already have. It’s like “the best camera is the one you have with you” – Annie Lennox, I think.

For me, that’s gitlab on-prem.

Help/Advices

Sure! ‘advice’ isn’t pluralized with an S. It’s like ‘traffic’; and you don’t say ‘traffics’ as a noun.

Happy to help!

*/1

Get out. You’re fired.

It seems we’ve lost sight of reality there.

As we don’t intend to attend much cinema any more, I hope they bring back essentially a Dolby Noise Switch for movies. I don’t want to sacrifice too much, but booming noise followed by what comes out as whispered dialogue really cheapens the experience.

I hope they can find a process that gives us back a sound track for the sub-17:7 sound system.

VI was so pathetic and old - blasphemy! - that I almost gave up on college and the career as I mistakenly thought in my grief, at having to suffer that dreck, that it was all gonna be like that.

Thankfully someone showed me anything different. About 5 options, actually . I picked one and I’m happy to use anything else (eg sed-i) unless vi is the only thing left; and then I decide whether it’s worth it.

What a sad old callback to the Vietnam war that is (not for the name; it’s that old).

I know the vi cabal will be upset to hear someone who tried it actually doesn’t worship it. They’re gonna downvote me. That’s okay. I got over that hate 30 years ago.

Just remember : there’s probably something else you can use and experience more joy, if they haven’t demanded everything else be removed.

We ship a single dependency-free binary that runs on all Linux distributions

It’s like 20 years of security awareness vanished in an instant.

incostomizable

Stay in school, kids.

imagine

imagine

imagine

imagine

imagine

imagine

imagine

imagine

imagine

And maybe learn other words.

Thank you for spelling “every time” properly, and I’m sorry we’re at the stage where that’s an accomplishment.

THE BELOW MESSAGE

No, it’s “the message below” or “the following message”. Pick a lane.

those from Red Hat

Not the enterprise stuff; just the beta mayflies.

Like, what are we even suppose

supposed

to tell “normal people” about security? “Yeah, don’t download files from people you don’t trust and never run executables from the web. How do I install this programming utility? Blindly run code from over 300 people and hope none of them wanted to sneak something malicious in there.”

You’re starting to come to an interesting realization about the state of ‘modern’ programming and the risks we saw coming 20 years ago.

I don’t want to go back to the days […]

You don’t need to trade convenience for safety, but having worked in OS Security I would recommend it.

Pulling in random stuff you haven’t validated should feel really uncomfortable as a professional.

Former Unix security chief.

Do not use snaps. Risky as hell.