Jim, 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. There's a fairly long thread in the archives about this that starts here: http://www2.marist.edu/htbin/wlvtype?LINUX-VM.18546
Mark Post -----Original Message----- From: James Melin [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 2:50 PM To: [EMAIL PROTECTED] Subject: Re: Red Hat 7.2 S/390 Mark, any conjecture as to why Red Hat would do what I feel is a customer Disservice by not including the OCO modules where SuSE does include them? |---------+----------------------------> | | "Post, Mark K" | | | <[EMAIL PROTECTED]| | | m> | | | Sent by: Linux on| | | 390 Port | | | <[EMAIL PROTECTED]| | | IST.EDU> | | | | | | | | | 03/04/2003 01:12 | | | PM | | | Please respond to| | | Linux on 390 Port| | | | |---------+----------------------------> >--------------------------------------------------------------------------- ---------------------------------------------------| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: Red Hat 7.2 S/390 | >--------------------------------------------------------------------------- ---------------------------------------------------| Richard, A better description of Red Hat's install package is that it does not include any of IBM's OCO modules. As a result, people who want to do an install that requires one of the OCO modules to get a network connection have to go through some additional work to make that happen. The latest installation kernel on the Red Hat site is 2.4.9-37. There should be current OCO modules for that available on IBM's DeveloperWorks site: http://www10.software.ibm.com/developerworks/opensource/linux390/special_oco _rh_2.4.shtml The RELEASE-NOTES file from Red Hat's FTP server has instructions on how to get the OCO modules integrated into the installation files. Mark Post -----------Snip-----------------
