Knowing full well that people who give feedback DIRECTLY to the execs at
redhat, I will say this on the OCO subject:
The ONLY reason we went with SuSE over RedHat was the OCO module issue.
Once we solved the problem with our switch that made me go mad trying to
figure out why Linux was broken (wasn't was switch) SuSE installed just
fine. We did not feel that having to roll your own each time a proven
stable maintenance release of the Kernel was out was a good way to do
things. That was the deciding factor as to which vendor we currently are
going with.
|---------+---------------------------->
| | "Post, Mark K" |
| | <[EMAIL PROTECTED]|
| | m> |
| | Sent by: Linux on|
| | 390 Port |
| | <[EMAIL PROTECTED]|
| | IST.EDU> |
| | |
| | |
| | 03/04/2003 02:21 |
| | PM |
| | Please respond to|
| | Linux on 390 Port|
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: Red Hat 7.2 S/390
|
>------------------------------------------------------------------------------------------------------------------------------|
Vic,
One can only hope. It's made life miserable for a number of people, myself
included, over time.
Mark Post
-----Original Message-----
From: Vic Cross [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 04, 2003 3:14 PM
To: [EMAIL PROTECTED]
Subject: Re: Red Hat 7.2 S/390
On 05.03.2003 at 06:02:06, "Post, Mark K" <[EMAIL PROTECTED]> wrote:
> No conjecture needed. They have both business and philosophical issues
with
> distributing OCO code, and hence being responsible for supporting them
when
> source code is not available.
With IBM and Red Hat reaching an agreement on 'co-operative support' (the
exact
wording escapes me now), I wonder if we will see a change to this with
future
Red Hat releases...
Cheers,
Vic Cross
