[bauruine]

Much of it is behind a paywall though. I manage more than a hundred licenced RHEL machines, was an RHCSA and RHCE with a company mail but I'd have to ask someone in my org to give me access. I just blocked access.redhat.com on kagi. F you.

[worthless-trash]

Most of the 'docs' are not behind the paywall, you're mixing up the KCS / FAQ's.

The docs are on https://docs.redhat.com/

[bauruine]

I didn't mix it up but most of the time I stumble upon redhat.com it's KCS (access.redhat.com) articles. Yes it's not "documentation" but if it's worth to create an article because that many people have the same issue I'd say you could add it to your documentation as known issues.

[worthless-trash]

I dont think that google is indexing that without a login/subscription though. TIL.

[SSLy]

> paywall

at worst a regwall.

[bauruine]

"You need an active subscription" is paywall for me.

[freedomben]

You manage over a hundred licensed RHEL machines but don't have an active subscription to access.redhat.com? Somebody is doing something terribly wrong in your org. How do you open support cases without that, or even manage the subs?

For the record I think Red Hat shouldn't put those behind a login, but that's a different argument

[bauruine]

I could ask for access I assume it's just a mail but I don't want to bother them because I can find a solution one or two results down from the redhat site anyway. I've worked with Linux and without a support contract for long enough that I know how debug and fix things. I wouldn't get direct access to support cases anyway. Our Linux guys provide a bash script to auto enroll.

It's not a login. It's a login with an active subscription. Are those article that valuable that they can't provide it for everyone with a @company.com address that has >n licences?

[freedomben]

Fair, I forgot they changed it to require an active sub rather than just an account. That was a bad move IMHO. And yes I fully agree they should at a minimun automatically allow access to everyone with @company.com with >n licenses.

Pure speculation, but I'm guessing they view the knowledge base as part of "support" (or like level 1 or something), which is why they're so restrictive. I think they greatly underestimate the number of people like us though that already use RHEL but don't want to bother with accounts because we can get by without it, but would benefit from having the access. They don't seem to understand the friction their policies create, and I think that's deeply unfortunate.

[jwildeboer]

(I’m a red hatter) anyone can get the Red Hat Developer subscription for free and get full access to the knowledge base.

[SSLy]

you can grab a free dev sub and it unlocks the KB and quick fixes too. Unless that changed relatively recently.