On Feb 20, 2006, at 3:12 PM, Peter Seebach wrote:

> Okay, now I'm completely stumped.  What's a kernel config file FOR,  
> then?

Specifying what should be included.  I'd like to see the kernel  
config file get smaller and smaller, actually, as more things become  
dynamic / loaded on-demand.

> ... Isn't code duplication normally considered bad?

I never suggested duplicating the code.  I only suggested using the  
code in one way for which it was specifically designed.

> (BTW, is there documentation to explain how you know which  
> functions to use
> for what, e.g., what goes in device_register?  I tried a couple of  
> obvious
> man ideas, and got nothing.)

Not enough documentation, but there are plenty of examples of what  
can be done in that function.

-- thorpej