Given your situation, I would ask Red Hat to provide a compiled kernel module for that kernel. They have the source code now, so it's no longer an IBM OCO module situation. I would think the module would compile with no problems (but then I don't know for sure). If they're forcing you to live with the equivalent of a Red Hat OCO kernel, then they can do the rest of the job as well.
Mark Post -----Original Message----- From: Vic Cross [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 08, 2003 9:34 PM To: [EMAIL PROTECTED] Subject: Re: Updated OCOs for Red Hat 7.2? On Wed, 8 Oct 2003, Post, Mark K wrote: > Normally, it is IBM that has to produce new OCO modules for Red Hat and > SuSE. Now that the qeth source is available, you might just want to grab it > and compile it on the target system. Refer to my reply to db's note, re support. Let's not open the can-of-worms about whether Red Hat will support us at all with an OCO module installed, but in theory if I use packaged stuff I should be able to get support from one of them. It seems like I'm stuck here. I agree, I would expect that IBM should build modules corresponding to RH's kernel, but they *did* that, only for RH to pull that kernel. Can I compile the open-source qeth code against a 2.4.9 kernel? I'd have to think not... Regardless, I'd still have the same support issue. What I'd like would be for IBM to rebuild an OCO module package for the RH 2.4.9-38 kernel, including the patches they applied to the 2.4.9-43 version. But how would I request this? Cheers, Vic
