Todd A. Jacobs wrote:
I don't think anyone on this list, or any other list, is *obliged* to answer questions and I'm sorry if you think my e-mail suggested that.On Fri, 28 Feb 2003, Mike Reed wrote:that someone from Red Hat who knows the answer would read this list. As I said it makes you think that this is some guarded secret in RedIf it's module-related, then by definition it's kernel related. Why don't you ask on a kernel-related list, rather than assuming that people on a volunteer distribution-support list have an obligation to do research for you? Also, I'm sure that if you have a paid contract with Red Hat, they'd be glad to research it for you if they don't know the answer off-hand.
As for my Red Hat distribution, I bought it two years ago so the support has run out.
Surely *someone* knows the answer... unless they're all dead... the conspiracy theory grows!If nobody knows the answer, it's because it has zero impact on the
I didn't *expect* anything. Except the odd flame thrower or course.majority of people. So again, rather than expecting people to be responsive about something that has no relevance to them, be proactive and
I have been scratching my own itch. Posting to this list isn't the only thing I've done. I've been searching the internet, searching through kernel source code, trying to get info from Red Hat, experimenting with the file. It's because all of these things haven't born any fruit that I thought I would try and ask for help. I didn't expect to be told not to ask for help by somebody.scratch your own itch: contact kernel developers, search the source for references to modules-info, or experiment by moving the file and see what happens.
Don't worry if I ever find out what it does I will do my best to make sure the answer is available to everyone.When you find out, throw up a web page or a mini-howto, and share your insights with other people who might have the same question. That's how the open source *community* works.
