Here's another kernel tip I use that I forgot to mention in my first post:
3) As soon as the kernel looks OK, *SAVE* the ".config"
file to something, e.g. "working.config".
I say this because a "make mrproper" will wipe out your .config.
Also, if you start playing around with different kernel configurations,
you can find yourself with a broken kernel wishing you knew what
was in .config three tries ago!
On my system I have a kernel-configs dir right next to /usr/src/linux
where I save all the kernel configs for working kernels for all 5-6
different machines I have. (I build the kernels on one machine, my
workstation, and tar over the bits to the destination machine). Keeping
this history of .config's per machine has saved me a few times
when I notice a piece of hardware is no longer working, but I knew it
was 6 months ago with a different kernel.
Karl Runge
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
