On Wed, 17 Dec 2008, John Summerfield wrote:
I've never used RHEL so I don't _know_ what the support arrangements are, but
it seems to me time to bang some heads together. I gather from what others
have said, you have an account rep from RH, and I expect you
also have one at IBM.
I like the idea of "asking" them to go away and sort it out jointly lest they
hear more, very cross, words.
One of the ideas of EL distros, I thought, was to ensure problems such as
this do not arise.
Right, the only way to get out of these problems is to make vendors
accountable for the complexities they create. Which often means to report
them, and press on these issues whenever you get a chance.
Much too often I have seen system engineering departements accept the
incompatibilities and complexities that software vendors impose. I have
seen situations where it was impossible to have needed hardware and
software in a supported configuration on a single system because of
multiple vendors having restricted support rules.
Also often the documentation that ships (or is found on websites) simply
does not get updated on subsequent kernel releases because the operational
'system' to keep in sync with what is used *after* the product ships, is
simply missing. And support desks strictly follow the documentation they
have and nobody cares about software updates (or internal strict QA rules
are impossible to comply with to even bother).
Pragmatism ofcourse requires you to find a solution at hand, and not
bother about stressing your own problems to vendors. But escalating is
the *only* way to create awareness and accountability.
--
-- dag wieers, [email protected], http://dag.wieers.com/ --
[Any errors in spelling, tact or fact are transmission errors]
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
