Bitten by the Red Hat Perl bug (InfoWorld) [LWN.net]

Bitten by the Red Hat Perl bug (InfoWorld)

Posted Aug 28, 2008 18:39 UTC (Thu) by arjan (subscriber, #36785)
In reply to: Bitten by the Red Hat Perl bug (InfoWorld) by ncm
Parent article: Bitten by the Red Hat Perl bug (InfoWorld)

you were right if the OS used was an actual Red Hat OS.
It wasn't.

(Log in to post comments)

Bitten by the Red Hat Perl bug (InfoWorld)

Posted Aug 28, 2008 22:20 UTC (Thu) by rahulsundaram (subscriber, #21946) [Link]

I wouldn't call it exceeding unlikely and those issues are not necessarily the fault or rebuilders. Besides if you are a RHEL customer, you would have got a hotfix for this issue a while back

Bitten by the Red Hat Perl bug (InfoWorld)

Posted Aug 29, 2008 0:03 UTC (Fri) by rise (guest, #5045) [Link]

Err, no - read the articles & posts. It's a Red Hat issue that CentOS inherited and if you check with current RHEL customers they can tell you that the fixes have been slow to come and insufficient. Cutting Perl performance by a factor of 100 and then "fixing" it to only a 50x performance drop (or even 10x) isn't good support.

Bitten by the Red Hat Perl bug (InfoWorld)

Posted Aug 29, 2008 0:59 UTC (Fri) by qg6te2 (guest, #52587) [Link]

[an] issue that CentOS inherited

CentOS is not commercially supported. Period. If the recent re-discoverer of the perl bug (Vipul Ved Prakash) had been using RHEL (and hence had a support contract) he may have had a more direct recourse to getting it fixed, notwithstanding Red Hat's (current) low priority on the bug. Instead of moaning about it on his blog, he would have had the right to raise a stink with Red Hat directly.

Bitten by the Red Hat Perl bug (InfoWorld)

Posted Aug 29, 2008 9:29 UTC (Fri) by felixfix (subscriber, #242) [Link]

None of that changes the fact that if the CentOS perl is straight from RedHat, and that is where the bug originated, it is a RedHat bug. If the bug originated within Perl HQ, RedHat coped it, and CentOS copied RedHat, it would be a Perl bug. If CentOS modified what they got from RedHat and thereby introduced the bug, it would be a CentOS bug.