Red Hat Stops Shipping Kernel Changes as Patches
mvar writes to point out a report from h-online about the Red Hat
kernel source controversy. From the article: "Red Hat has changed
the way it ships the source code for the Linux kernel. Previously, it
was released as a standard kernel with a collection of patches which
could be applied to create the source code of the kernel Red Hat
used. Now though, the company ships
a tarball of the source code with the patches already
applied. This change, noted by Maxillian Attems and
LWN.net, appears to be aimed at Oracle, who like others, repackage
Red Hat's source as the basis for its Unbreakable Linux. Although
targeted at Oracle, the changes will make work harder for
distributions such as CentOS."
Did they stop shipping diff too?
Since CentOS is basically removing trademarks and recompiling how exactly does this make their work more difficult? Does CentOS not ship the same kernel as Red Hat by using Red Hat source? Wont CentOS simply compile the pre-patched source from the tarball and be good to go?
It also makes life much harder for us downstream engineers who actually have to troubleshoot problems in the Redhat kernel. More often than not, it's a vendor-applied patch responsible for creating the problem in the first place. Now I guess it's up to Redhat Support to come up with a solution, which often reads "in 3 major versions time, if ever"
Red Hat is doing more heavy lifting than anyone else, but organizations like Oracle and CentOS are leeching off of Red Hat's hard work.
Boohoo? If you don't want people to leech your work then why would you release it under a license that specifically allows that?
They are absolutely meeting the requirements of the GPL.
And so are the people you claim are "leeching" off of Red Hat.
If these other organizations like Oracle and CentOS were saying "we're going to fork what Red Hat has done and come up with something different because we think we can do it better," like Mandrake did, that would be one thing. But Oracle and CentOS both pretty much have the same message: "we're going to take all the hard work that Red Hat has paid for, claim that ours is just like theirs, but make sure that Red Hat doesn't get paid for it."
But if they aren't violating the GPL, so what? You've basically constructed a double standard where it's okay for one party to use GPLed code however they want within the bounds of the license but yet you come back and whine about others who are doing the exact same thing. Once again, if you don't want people to use your code this way, why would you release it under a license that was specifically worded in order to allow this?
RedHat exercises the GNU freedom by selling for money a distribution consisting mostly of free programs made by others.
For the record, RedHat is selling support for a distribution they have engineered. They aren't selling the distribution, except possibly a "media charge", year 1 to obtain the support and year 2 to maintain the support are the same price.
CentOS does not offer any support beyond the standard Open Source model of chat boards, bugzilla, etc. As a general rule, when I introduce Linux to a company with a small unsupported project, I bring in CentOS, not Fedora, because I know if it takes off we'll be bringing in RHEL 9 times out of 10 when the company decides they want/need support. That way, there is pretty much zero retraining of the staff that needs to happen.
You are in a maze of twisted little posts, all alike.
Red Hat's job isn't to make things easier for CentOS, or Oracle for that matter - how is that even relevant? Red Hat isn't doing anything that's disallowed by the GPL. They're not even doing anything that could be reasonably interpreted as "contrary to the spirit of the GPL".
They're still releasing the source. They're still paying their coders to do substantial work on the kernel. How big of a twit do you have to be to complain about how they release their kernel updates?
#DeleteChrome