RHEL never did to install it. To get any updates though, you have to provide a contract number.

Edit: 10 might be different, but I don’t think it would be.

But did you kiss?!?

Why not?

You continue responding. You are as complicit in this thread as I am. 😊

Hard agree to setuid being a problem. And that it is a problem because any of these tools written in c can be a security hole, because c is hard to get right. And I find it funny that c devs are butthurt over how rust won’t let them write obviously bad code.

But it’s OK, words are difficult. 😊

Sure, but that was a strong response for a comment on the situation. Sounds like you care. I do not. 😊

And you’re complaining about rust?

It’s OK, you don’t have to use so many words to tell us you work with c.

If that were on the table, the stool would’ve already been cleaned out.

Hard agree. This is why rust is getting so much attention, and the c/c++ crowd are so mad. They’re happy just blaming it on a “skill issue” while losing their shit over [the rust crowd] saying “how about we don’t let you in the first place.”

(Imaginary numbers though can fuck off)

I understand the sentiment, but complex numbers literally fall out of computations once you start shaking them hard enough.

Yes, they’re difficult and hard and have a stupid name tagged onto them. Also, they exist and are useful.

Asking the right questions

Slackware was my first intel Linux. First linux ever was red hat for DEC alpha. Quite weird after OSF/1.

Still use slackware, though mostly now actual work is done on debian, arch, and alpine.

It helps keep the more caustic linuxers away from lemmy.

Let’s be honest: nearly all of them now are windowslike girly distros…

It’s much more… manual than others, I’ll admit. For me anymore it’s a labor of love.

Slackware: because I’m old and arch is too trendy.

hunter20

Sorry, the best I can do is busybox as init.

I mean, it still could be…