Re: [ANNOUNCE] Framework for automatic Configuration of a Kernel

[Emmanuel Fleury]

Hi,

Actually this autoconfig thing raise quite a lot of questions to me.

1) What should be detected, what should not ?

It seems obvious that all the choices beyond hardware are choices that
the user should do (what network protocols, what kind of filesystems,
etc). But, as Boddo Eggert pointed out (if I understood well), all the
hardware which is lying outside of the box (printer, scanner, usb key,
...) could be detected if plugged when the autoconfig is ran.

Should we trust these informations (as theses devices can be removed at
any time) ? Shouldn't we let the user make these choices by himself ?
What is the limit of the devices we can assume to be part of the machine
when building this autoconfig ?

2) What is the surest and the most stable way to detect the hardware ?

lspci, lsusb, dmidecode (or /proc and /sys) have been mentioned. This
brings two sub-questions:
- What kind of software environment / kernel release can we assume ?
- How to minimize the dependencies of the detection from other tools ?
 (changing all the Kconfigs just because the syntax of the output of one
of these command has changed would be quite painful).


3) Can this hardware detection be included in other interfaces ?

It would be nice to have this detection to be ran when no pre existing
.config is detected in all other interfaces (menuconfig, config, ...).


Regards
-- 
Emmanuel Fleury

Discontent is the first step in the progress of a man or a nation.
  -- Oscar Wilde
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/