systemctl is trying to do the right thing

I love how this comment suggests every fucking alternative doesn’t or wouldn’t. That’s just bloody arrogance.

Systemd’s entire existence is against best coding practice. Famously, when called out just on the ability to work with others, the systemd team represented trends ably.

Never have I raged at a machine and demanded it tell me what the flying flaming fuck it was actually doing now than when systemd was trying to do what I’m charitably deciding is the right thing.

Why would be doing the right thing now? It honestly only does a thing through luck and race conditions anyway.

will shutdown now

‘shut down’ is two words, here.

When you run git-bash from an install of the git suite, that’s a valid pathname.

Oh. Just on my system?

Remember: GNU/Linux

I stopped there. Enough kowtowing to the toejamophage.

My old employer used to have people on staff just for technical writing. Some of that writing became the man pages you know, and some of it was ‘just’ documentation for commercial products - ID management and the like.

Then we sued IBM for breach of contract, and if you ask anyone about it they’ll parrot the IBM PR themes exactly, as their PR work was brutal. People in Usenet and Forums were very mean, and the company decided to stop offering much of the stuff that it was for free. It was very ‘f this’.

If man pages needed a volunteer to maintain, I know why ours tapered off.

If I need systemd for a specific use, like testing systemd services

So you’re hoping to test systemd in this theoretical test environment, but your prod isn’t built like this? Tell us why you’re ignoring the first rule of testing and deploying internal software?

Instead I now run “terribly slow” OpenRC on my systems.

I suspect you’re entirely free of init problems where you raise your fists to the heavens and ask WHAT ARE YOU DOING as if it’ll tell you why systemd is on holiday now.

My understanding is that it boots faster.

I tested this with EL6 and EL7. There was no discernible difference. It was all theories and brochureware.

I can’t understand anyone wanting that hot mess that is systemd anywhere. I’m only glad lennart went to microsoft so the pruning can begin.

Oh my god.

sh -c "$(curl -fsSL https://raw.githubusercontent.com/knadh/listmonk/master/

We absolutely need to stop this. Sure, I saw the disclaimer, but we need to end the normalization of running ANY black-box crap off the net. “curl|sh” needs to be laughed into exile for all our safety.

The easiest thing needs to be the right thing – common security saying

Then it’s

vim

As if that’s actually user-friendly or a positive experience instead of the worst thing to ever survive from the last century, crawling along on its rotting flesh and drooling on the pavement like some toxic residue from the vietnam war that it is.

In what asylum do you have the people willing to suffer vi and who also need a curl|sh ? Are they lazy or just misled as noobs into thinking vi is the only editor out the–

You guys, I just realized how vi masochists actually reproduce. It’s like zombies, guys, eating brains until the victim raises up another zombie.

And that curl|sh – does it invite supply-chain exploits? Ohhh, you bet it does! Best black-box script ever! Use this as a test for your security people – if they gauge this as a threat from within another threat, they pass. But, honestly, had it not been for the horrible spelling, I wouldn’t have thought to check further. \shrug. Mineshafts and canaries I guess.

As a sarcastic joke comment. Whoosh?

I’m glad to see were rediscovering what we lost in 2002 when we laid off all our mentors and experts after y2k.

Reproducible builds require complete and consistent validation. The deb format lacks this ability.

bunch of old C devs

I knew this ageist bullshit would pop up. I know we lost our mentors and are kinda feeling in the dark, but the moment people pop out the ageist slurs I know they’ve got nothing to say.

I heard that C developers are trained to use memory smartly

Kernel coders are an entirely different breed, and when I worked with a few of them they were just stunning. The smartest man I know on the planet so far coded on the Unix kernel – the one that IBM forced back to Novell who’d already fired their staff after selling it, and thus shelved it and killed Unix. He is and was amazing.

So yes, I can confirm that Kernel devs know how to manage their memory – they use very little, they allocate and free it, and they build very small, tight, optimized kernels by knowing how the optimizer will do things and how to hint it to do what they know needs to happen.

Yeah, it’s a skill. Yeah, it takes skilled people. I’d like to one day find out that really big training wheels will let anyone build code that well, but I’ve seen the goal and I don’t expect we’re there yet.

Let the kernel be built by kernel devs.

“primacy”?

Fuck that accusation of turf.

Doesn’t run on my OS.

“I am no visionary but if Linux doesn’t internalize this, I’m afraid some other kernel will do to it what it did to Unix.”

Linux has no owner, really, aside from Linus. How can IBM wrangle a reversal in the sale of it back to Novell who has no more devs to maintain it - because they sold it - and they put it on the shelf for 20 years until it’s dead?

I don’t get how this is like how Unix was killed; at all.

supposed to be VIM vs Emac?

30 years ago it was vi vs everything. I don’t see it changed today.

thru

There are other exceptions.