From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 21 17:25:25 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10A5B16A4CE for ; Wed, 21 Jul 2004 17:25:25 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 520B543D2F for ; Wed, 21 Jul 2004 17:25:24 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.102] (ddsl-66-42-172-210.fuse.net [66.42.172.210]) (authenticated bits=0)i6LHFK2S009827 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Wed, 21 Jul 2004 13:15:21 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-hackers@freebsd.org Date: Wed, 21 Jul 2004 13:26:16 -0400 User-Agent: KMail/1.6.2 References: <20040721124345.GB99978@silverwraith.com> <20040721170019.GA88303@root.kableu.com> In-Reply-To: <20040721170019.GA88303@root.kableu.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200407211326.24064.mistry.7@osu.edu> X-Spam-Status: No, hits=-4.9 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE, QUOTED_EMAIL_TEXT,RCVD_IN_ORBS,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_KMAIL version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Re: "Next Generation" kernel configuration? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 17:25:25 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 21 July 2004 01:00 pm, Andrew Konstantinov wrote: > On Wed, Jul 21, 2004 at 05:43:45AM -0700, Avleen Vig wrote: > > On Tue, Jul 20, 2004 at 07:39:31PM -0500, Conrad J. Sabatier wrote: > > > Just musing on an idea here: > > > > > > I've been thinking for a while now about trying to write a tool to ma= ke > > > kernel configuration easier, sort of a "make config" (as in ports) for > > > the kernel, similar to what's available on some of the Linux distros. > > > > I've read over the other posts in this thread, but I cannot say I think > > this is a good idea. In fact, I think it's a very bad idea, but with > > very good intentions. Here's why.. > > > > I'm a strong proponent of user education. The FreeBSD handbook is one of > > the best education tools for someone who wants to use FreeBSD, right > > from beginner to more advanced levels. > > > > A "config tool", while useful for beginners, would quickly result is > > those beginners not learning about building a kernel themselves, copying > > GENERIC to `hostname -s | tr "[:lower:]" "[:upper:]"`, editing it, > > learning what is in LINT, remembering to look through there, etc. > > This process teaches users a lot about how a BSD kernel is configured, > > what options are availible, and where to look for more options. > > > > The end result would be more people building kernels themselves, but not > > knowing what is actually happening, or what more is possible. It would > > mean less educated users, and I don't think that is somewhere any > > organization needs to go (look at what happened to the average Microsoft > > user's IQ level, after people stopped using DOS and started having > > machines do the work for them). > > > > Like I said, I think your intentions are good, but I have concerns about > > the suggested solution. > > I think such a tool would actually influence user education in a positive > way. Here is a sample scenario: > > 1) User starts this "program" to configure the kernel > 2) User sees unknown to him option > 3) User decides to look it up on www.google.com > 4) "That's a nice feature, although I don't really need it" > 5) GOTO 1 > > The only suggestion I have is to make it a third party program and not > build it into the make procedure for the kernel. It would look like > pkg_tree that's located in ports, although with a better ncurses interfac= e. > > Andrew I think a tool with the functionality described in the original post would = be=20 very nice, but it shouldn't be menu driven etc. Something more like a kern= el=20 dependency checker that would take the kernel config file, and check that a= ll=20 the dependencies are correct. ie. for umass you need da, but if you forget= =20 you'll only get a cryptic failing of the kernel build. Also for things lik= e=20 bktr, which you need to have iic and friends. Something along the lines of a command line "make depend-check" before you = do=20 a make kernel would be nice. =2D --=20 Anish Mistry =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/qc/xqA5ziudZT0RAhLQAJ9HvvtFjmvOkP7hCX4nNR4LGbeMmACgr4vi gQGqNJyVysUTFlisDYohF+8=3D =3DgXI8 =2D----END PGP SIGNATURE-----