That’s a terrible sword to live by. How do you expect to get blood, then? If you’re unconscious you can’t take it by force.

ZFS. It’s come so far, and it has so far to go. but it’s a good concept for sure.

Firefly.

sike

Bone apple tea!

Oh, that’s a great suggestion.

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.

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.

English may not be their first language.

Right. If and when I post in French or Spanish or Gaelic on a sub that is more than a language practice, though - in consideration of the reader - I’ll have my stuff checked. It’ll be by an AI, so there’s the hallucination risk, but at least I’ll have it checked. Even grammarly is a train wreck for non-american English, but it’s good for catching the really bad mistakes in English and maybe others.

I don’t see where someone’s criticizing for writing in a second language. I see where someone is expressing worry about content posted without getting it checked. Do we not want our questions to be read? Do we not want to make it as easy to get an answer as possible?

Remember when we used to see this?

1. Search first, ask later. On most forums, there are certain questions that come up again and again. …
2. Choose wisely. There are many, many forums out there. …
3. Breathe. …
4. Write like you made it through grade school. …
5. Be complete, but concise. … 6.Proofread, then proofread again. …
6. Ask politely

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.