3 ms·

Realistically redhat only serves two customers: 0. Government or affiliated that require scap/stig or other compliance frameworks like fips140 or hipaa and act

Realistically redhat only serves two customers: 0. Government or affiliated that require scap/stig or other compliance frameworks like fips140 or hipaa and actually use stuff like fapolicyd or aide. 1. Large companies that build "support" into the risk matrix for leadership who are obligated by law to protect shareholders. Other companies that just "use Linux" probably use alma or rocky, but certainly aren't joined at the hip. Personally I hope this comes back to bite big blue. For this to have any effect on Oracle you'd need to have started doing it like a decade ago before they too started eating customers from #0

lathiat 3y ago
They did something similar with the Kernel in 2011. It's not an entirely new strategy. They stopped publishing the git tree or separate patches for the RHEL kernel and only published the tarball with no version control. At the time, Oracle started a project to reverse engineer it back into a set of unique patchsets called "RedPatch". Was kindof wild. Not sure how long it lasted. It doesn't seem live now, though. https://www.theregister.com/2011/03/04/red_hat_twarts_oracle_and_novell_with_change_to_source_code_packaging/ https://www.theregister.com/2011/03/04/red_hat_twarts_oracle... https://www.theregister.com/2012/11/12/oracle_launches_redpatch_repository/ https://www.theregister.com/2012/11/12/oracle_launches_redpa...
- worthless-trash 3y ago
  Centos streams made the kernel source available in git.
  - rincebrain 3y ago
    The source was always available; the difference was that RH stopped breaking out their enormous delta from the vanilla tree into itemized patches. And as far as I can tell, that's still [1] just one giant patch wad for every update. [1] - https://gitlab.com/redhat/centos-stream/rpms/kernel/-/commits/c9s/ https://gitlab.com/redhat/centos-stream/rpms/kernel/-/commit...
bogantech 3y ago
Third option: your business relies on some expensive software that is unfortunately only supported on RHEL

lathiat 3y ago

They did something similar with the Kernel in 2011. It's not an entirely new strategy. They stopped publishing the git tree or separate patches for the RHEL kernel and only published the tarball with no version control. At the time, Oracle started a project to reverse engineer it back into a set of unique patchsets called "RedPatch". Was kindof wild. Not sure how long it lasted. It doesn't seem live now, though. https://www.theregister.com/2011/03/04/red_hat_twarts_oracle_and_novell_with_change_to_source_code_packaging/ https://www.theregister.com/2011/03/04/red_hat_twarts_oracle... https://www.theregister.com/2012/11/12/oracle_launches_redpatch_repository/ https://www.theregister.com/2012/11/12/oracle_launches_redpa...

worthless-trash 3y ago
Centos streams made the kernel source available in git.
- rincebrain 3y ago
  The source was always available; the difference was that RH stopped breaking out their enormous delta from the vanilla tree into itemized patches. And as far as I can tell, that's still [1] just one giant patch wad for every update. [1] - https://gitlab.com/redhat/centos-stream/rpms/kernel/-/commits/c9s/ https://gitlab.com/redhat/centos-stream/rpms/kernel/-/commit...

bogantech 3y ago

Third option: your business relies on some expensive software that is unfortunately only supported on RHEL