Date: Mon, 25 Oct 2004 14:23:03 -0400 (EDT) From: Andre Guibert de Bruet <andy@siliconlandmark.com> To: Garance A Drosihn <drosih@rpi.edu> Cc: current@freebsd.org Subject: Re: Breaking up kernel config files (GENERIC) Message-ID: <20041025141556.I42571@alpha.siliconlandmark.com> In-Reply-To: <p0611043abda24d6ecffe@[128.113.24.47]> References: <417960C2.8040007@freebsd.org> <20041022194008.GA23778@odin.ac.hmc.edu> <p06110423bd9f1b6312ed@[128.113.24.47]> <41796D6D.7000108@freebsd.org> <41799315.70201@elischer.org> <41799396.9090307@freebsd.org> <20041023082926.GE45235@ip.net.ua> <p06110433bda0a9094720@[128.113.24.47]> <p0611043abda24d6ecffe@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 25 Oct 2004, Garance A Drosihn wrote: > At 2:24 AM -0400 10/25/04, Andre Guibert de Bruet wrote: > > 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. What I would really like to see is a mechanism for recognizing hardware (arch, cpu family, scsi, ide, sound, firewire and net) that is currently in the system and generating a barebones configuration file with just the results. What happens when this "auto-probing" doesn't recognize the hardware that you have? Well, what are you forced to do now? :-) Regards, Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041025141556.I42571>