Date: Mon, 2 Jun 1997 13:36:38 +0800 (WST) From: Adrian Chadd <adrian@obiwan.psinet.net.au> To: Nadav Eiron <nadav@cs.technion.ac.il> Cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, hackers@FreeBSD.ORG Subject: Re: LINT and GENERIC - between a rock and a generic place. Message-ID: <Pine.BSF.3.95q.970602132439.1656A-100000@obiwan.psinet.net.au> In-Reply-To: <Pine.GSO.3.95-heb-2.07.970601095133.4782A-100000@csd>
next in thread | previous in thread | raw e-mail | index | archive | help
[snip] > is the first step (same goes for npx0, FFS, COMPAT_43, loop etc.). I think > what would be better is for config, or even the kernel's makefile, to do > some sanity checks and spit out warnings like: > > *** You didn't put in INET. There's a good chance your kernel won't > boot *** > *nod*, have a file somewhere with the mandatory options? Means we would only have to hack config up once, then we just add to this file when "madatory" options change. > This sure will save bandwidth on -questions, and many frustrated newbies > from climbing up on walls. > > Yet another $.02 (I think someone is getting rich here collecting these > cents :-) ). Don't joke about that. ;) Fine. Michael, want to share what you've done so far? Who else has done a bit of work on it ? I'd *really* like even just a dialog-based kernel build tool. (Although, I suppose, how about we use TurboVision ? :) I can setup a mailing list if people are interested. I just think "committee" way of doing things never gets anywhere :-) Adrian.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970602132439.1656A-100000>