> Sorry, might have worded this incorrectly... We can build a > kernel using > Red Hat's kernel-source or kernel-*.src.rpm packages > *exactly* as supplied > and changing only config options, and we will be supported. > If we patch > their kernel (or remove one of their patches), or build a > kernel.org tree, > we're on our own.
Hmm. I'd still question that. We have a number of large customers that remove some of RH's "improvements" on a regular basis and still are supported. We can discuss further off-list if you need names, or I can get these folks to report bugs for you in a way where RH doesn't have the option to ignore them. > In addition, if we have a problem with our system while it > has the IBM OCO > modules installed, we will get no support unless we can duplicate the > problem with the OCO unloaded. Makes it a tad difficult to > troubleshoot > problems with network servers... If you are working with OCO modules, that's a understandable response. If the point is to remove the requirement for an OCO module, you're providing source, and they're still resisting, I'd say they're not living up to their end of the bargain. -- db
