the easiest way to do this is leave everything modularised, as in the installation kernels, so you don't need to recompile at all. Agreed that some sort of hardware detection is valuable - presumably this is what hwdetect is about. The test a couple of weeks back seemed to me to be about comparing what hwdetect could tell about a system versus what the users knew to be true. At least on my stsrem hwdetect was 100% accurate. On Fri, 3 Mar 2000, Jon Pennington wrote:
I was sitting here at home, compiling a new kernel for my machine (2.3.48), and I thought to myself, "Jon, there's got to be a better way to do this than `make menuconfig' or `make xconfig'. The kernel source tree is a great thing, also a very *large* thing, and difficult to manage.
I was just wondering if it would be possible to use something like the hwdetect utility to recommend a `safe' and an `aggressive' kernel configuration. `safe' would be no non-experimental code, and `aggressive' would have experimental options turned on, like support for the ALi and VIA Super-7 chipsets and USB/IEEE1394 options.
The stock SuSE kernels are great, but a hobbiest like myself still wants to play with things, but may still not have the foggiest idea what VIA82CXXX support is for. That's where hwdetect (or the like) would come in handy; find the VIA82CXXX chipset on the motherboard, correlate it with a .config option, and offer it to the user. It's just a thought, but I figured that somebody might think the same thing ;).
What do *you* think? Is it worth slapping together?
-=|JP|=- Jon Pennington | Atipa Linux Solutions -o) jpennington@atipa.com | http://www.atipa.com /\\ Kansas City, MO, USA | 816-241-2641 x121 _\_V
-- This sig brought to you by SuSE 6.3 and sendmail. Linux - you know it makes sense. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/