On Wed, Apr 26, 2006 at 06:36:26PM +0000, Rui Paulo wrote: > > Module Name: src > Committed By: rpaulo > Date: Wed Apr 26 18:36:25 UTC 2006 > > Added Files: > src/sys/conf: lint.cardbus lint.compat lint.fs lint.isa lint.mca > lint.misc lint.net lint.pci lint.pcmcia lint.usb lint.wscons > > Log Message: > Add work in progress lint files that will be used by port specific > LINT kernel config files (will be added later). > The list is far from complete and there are some missing files, busses and > devices. I like the idea of having a LINT kernel (or some way to obtain it), but those files strike me as the wrong way to do it. I'd rather see config(1) generates a LINT file with all possible options stuffed in. It is foolish to expect people to maintain this bunch of files sprinkled all around the tree. LINT will not be meant to be booted, so config(1) may very well generate it, issueing starred instances definitions for all devices it finds, even though it makes little sense (and just plain doesn't work) for ISA devices and the like. The point is to compile every possible driver for a given arch, so config(1) ought to parse everything and spits out the resulting configuration. I'm willing to help with the details, but I really object to those lint.* files which will rot faster than it takes to write them. -- Quentin Garnier - cube%cubidou.net@localhost - cube%NetBSD.org@localhost "When I find the controls, I'll go where I like, I'll know where I want to be, but maybe for now I'll stay right here on a silent sea." KT Tunstall, Silent Sea, Eye to the Telescope, 2004.
Attachment:
pgpOGEnAAHQAh.pgp
Description: PGP signature