I vote for this topic! I'd LOVE to know more about this. I'm a magic
man regarding this topic, for sure.
Mike K.
In an ideal world, the need to build new kernels would be minimal. Most new kernels support initrd - the initial ramdisk. By building your own initrd you can choose which kernel modules are available at boot time. I used to think that initrd was unnecessary additional baggage, but I've come to embrace it as a nice way to avoid building tons of modules into a kernel. Of course we have to statically link the module(s) needed to access the storage device that contains the initrd image, but that's about all we need (other than some of the core modules that all kernels need...)
A possible meeting topic could be building kernels, modules, and/or initrd images. I suspect that this is considered "magic" by many users, yet it does lead to some interesting revelations regarding how our systems really work.
Chuck
larry wrote:
He is not talking about building the kernel, just the kernel module. Even I do that.
M. Knisely wrote:
Horrifying, shocking confession.... I don't build my own kernel. I only have once or twice, and that was just for the fun of it. I've just never had the reason.
Perhaps some day someone will show me the light. For now, I'm happy with my stock kernel (as bloated as it may be).
Mike K.
Chuck Stickelman wrote:
I too am having trouble with the bcm43xx driver.
I downloaded kernel sources for linux-2.6.17.3 and built it using make-kpkg. I think I have all of the dependencies met, yet I too get error messages.
This is on my Acer laptop (that forces me to run XP to write this message... yuk!)
I can provide more details in a future message... Chuck
To unsubscribe send to ncolug-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field.
To unsubscribe send to ncolug-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field.
