Bill Studenmund wrote:
> The thing though is that we define around 265 kernel configurations as
> best I can tell ("ls -d */conf/[A-Z]* | grep -v CVS | grep -v Make | wc")
> and compiling all of them would be silly. Many of these files are
> duplicates/include parts. But we still have a mess of kernel configs. How
> many is enough?

I had some thoughts about kernel configs recently (I was adding PCMCIA drivers
to sparc and alpha kernels).  With all the subsystems we have, wouldn't it be
nice to only have to update a single file when adding a new driver?  We could
have:

  .../common/PCIDEVS
  .../common/PCMCIADEVS
  .../common/MIIDEVS

etc. and kernel configs would just:

  include	".../common/PCIDEVS"

The downside is when you want a kernel that only includes a subset of all the
devices.  Maybe something like the way (e.g.) atari configs are generated
could be used for this.

J

-- 
                    My other computer also runs NetBSD
                          http://www.netbsd.org/