On Fri, Aug 25, 2000 at 06:40:29PM -0500, Barrett Cervenka wrote:
> I'm trying to be a real Linux user and upgrade my kernel to 2.2.16. I
> followed the HOWTO with no problems but I'm confused about modules. Is there
> some way that I can capture the information about what modules I currently
> use and incorporate that into the new kernel? It's sort of redundant that
> everytime I want to put a new kernel on my system I have to remember what
> kind of sound card/net card I use. I could use a few tips here..
Well, at least for kernels that Redhat packages quite a bit is modularized. The
only way to know for sure is to find the .config file used to create the
top-level Makefile and I don't know that of hand. If your Linux box dual boots
into Windows as well, you can use Device Manager to make an inventory of you
hardware and then use that to chose which devices you need to enable in the
kernel.
However, here is what I do in this case: Modularize as little as possible. Try
to compile everything that you *know* you will need into the kernel. The only
things I have as modules are parallel port, fat, vfat, ppp, and sound. (I would
have compiled sound support into the kernel but Creative's instructions are to use a
module so who am I to argue?). This rule-of-thumb makes you think about those
drivers you _need_ vs. those you _want_. It also generally produces a smaller
kernel.
Modules are a really cool idea but the implementation (vis-a-vis
configuring configuring them), leaves something to be desired. I really tried
to understand it better about 2 months ago with some success but not enough to
give anyone sound advice. Therefore, I try to avoid them. :-/
Steve
--
illegitimi non carborundum
"Don't let the bastards grind you down"
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
