deleted by creator

a […] infrastructure

The uncountable becomes countable.

Ever? That’s a lot.

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.

Breathe, son.

Oh, that’s a great suggestion.

This one’s only counting active mass shooters. When it’s still a lesser shooting with under 4 victims, the odds of a vigilante rando with a gun - that is, a citizen packin’ heat and not a cop off the clock - stopping the violence is about 1 in 7000.

So, once a year in America.

We all know it sucks. I have no idea why people use it instead of anything else. My workday is jammed with fucking ansible which, while also being so ghetto that we were easily doing more with less in 2002, uses So.much.fucking.yaml . Just when you think ansible couldn’t get more clunky and useless and slow, it also is configured in yaml.

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

Oh. Just on my system?

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.

assume that productivity is a feature of an individual and not a feature of a team. That’s a wrong assumption. The fairest way to pay is same salary for the whole team.

So much of what we do produces nothing, but prevents a lot. There is definitely a reason to pay for experience and seniority: it’s not so much about creating widgets faster but more about not making short-sighted decisions. And in dev work, we have a high chance of making bad decisions as we’re second-generation lost-boys.

Having said that, those individuals are out there for whom compensation starts competitive and ends just short of their value. It’s eye-opening to meet and talk with these people and, once you do, it will change your life having them in it.

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.