On Fri, 28 Dec 2001, John Summerfield wrote: > There is a good reason for the way RH names its kernels. ...
SuSE is following RedHat's lead and making it harder for the customer to run third party modules. I'm wondering if "version information on all symbols" might help. That's the CONFIG_MODVERSIONS flag. It causes heartburn for me when building the *kernel*, but I wonder if it might help when IBM builds their *modules*. The documentation is not clear: It implies that this flag applies to the kernel. Does it instead apply to the modules? At least most of these "one off" kernel labels are parsable. If it were simply for human consumption (for doc), it would be fine, helpful even. The problem is when something other than a person has to grok the string and it's not an exact match for anything known. This is not merely a documentation string! Also, who says that a module built for 2.4.9 won't work with 2.4.9-4GB? What patches are these that warrant changing the label?? -- Rick Troth, BMC Software, Inc. 2101 City West Blvd., Houston, Texas, USA, 77042 1-800-841-2031
