The responsibility lies with Red Hat. We pay them for support. Support goes beyond answering phone calls and email. Support includes fixing known bugs (especially those that already have patches available).
We use Red Hat Enterprise Linux at $work because the PHBs get a warm fuzzy feeling deep down inside from knowing that Red Hat is just a phone call away should something go horribly wrong. We use the version of Perl that ships with Red Hat because, once again, the PHBs love that warm fuzzy feeling. If we build Perl ourselves then Red Hat won't support it and the PHBs lose that warm fuzzy feeling.
None of us knew about this problem because we simply have not noticed any performance degradation. Does that mean that are simply going to ignore it? Nope. We are not currently affected by the bug but that does not mean that we will never be affected by it. I will be calling our rep and demanding that they resolve this issue. We pay too much money to Red Hat to do any less.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
