Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 Oct 2004 02:49:49 -0400
From:      Garance A Drosihn <drosih@rpi.edu>
To:        Andre Guibert de Bruet <andy@siliconlandmark.com>
Cc:        current@freebsd.org
Subject:   Re: Breaking up kernel config files (GENERIC)
Message-ID:  <p0611043abda24d6ecffe@[128.113.24.47]>
In-Reply-To: <20041025020407.V42571@alpha.siliconlandmark.com>
References:  <417960C2.8040007@freebsd.org> <20041022194008.GA23778@odin.ac.hmc.edu> <41796396.5070804@freebsd.org> <p06110423bd9f1b6312ed@[128.113.24.47]> <41796D6D.7000108@freebsd.org> <41799315.70201@elischer.org> <41799396.9090307@freebsd.org> <20041023082926.GE45235@ip.net.ua> <417A17E0.7000800@freebsd.org> <p06110433bda0a9094720@[128.113.24.47]> <20041025020407.V42571@alpha.siliconlandmark.com>

next in thread | previous in thread | raw e-mail | index | archive | help
At 2:24 AM -0400 10/25/04, Andre Guibert de Bruet wrote:
>On Sat, 23 Oct 2004, Garance A Drosihn wrote:
>
>>   1) Turn off *all* scsi, because they know they have no
>>      scsi card at all.
>
>This will break USB CF readers, pendrives and Firewire SBP2 storage
>devices, unless by "*all* scsi" you're just refering to "all scsi
>controllers".

I meant "all scsi controllers", not "all scsi support".  I think
it would be good-enough to provide a way to select some list of
scsi controllers, and thus turn off all other scsi controllers.
Same with ethernet cards.  I have never built a PC with more than
three ethernet "chipsets" in it.  I would rather have to specify
the three ethernet-devices that I know I have, and not have to also
know the device-names for all the ethernet-devices that I do not
have, just to comment them out.

So, I would expect "categories" to only handle simple cases like that,
and we would leave the lines for things like 'da' and 'scbus' just the
way they currently are.

Right now I'm just tossing out some ideas of what we'd really like to
see.  I think that if all we do is split up all the per-architecture
GENERIC kernels into smaller files, then we will end up creating *more*
work for most people who want to create a smaller kernel config. I
suspect we can come up with something better than that.

-- 
Garance Alistair Drosehn            =   gad@gilead.netel.rpi.edu
Senior Systems Programmer           or  gad@freebsd.org
Rensselaer Polytechnic Institute    or  drosih@rpi.edu



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0611043abda24d6ecffe>