From owner-freebsd-current Thu Aug 7 20:49:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA18856 for current-outgoing; Thu, 7 Aug 1997 20:49:09 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [208.129.189.48]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA18842 for ; Thu, 7 Aug 1997 20:48:59 -0700 (PDT) Received: from bmccane.uit.net (localhost.mccane.com [127.0.0.1]) by bmccane.uit.net (8.8.6/8.8.5) with ESMTP id WAA08583; Thu, 7 Aug 1997 22:47:54 -0500 (CDT) Message-Id: <199708080347.WAA08583@bmccane.uit.net> X-Mailer: exmh version 2.0gamma 1/27/96 To: Philippe Regnauld cc: Alex , freebsd-current@FreeBSD.ORG Subject: Re: Kernel configuration script In-reply-to: Your message of "Mon, 04 Aug 1997 11:52:19 +0200." <19970804115219.19743@deepo.prosa.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Aug 1997 22:47:53 -0500 From: Wm Brian McCane Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Alex writes: > > Well, since I've seen nobody else make one, or publish one, etc, etc. I > > spent a few hours, and created a trio of kludgy bash (not sh) scripts to > > make configuring kernels a bit easier for the average newbie. If anyone > > would like to give them a try, I'll tar,gz em and email em out. Otherwise > > I'll post em in my web space when I feel they're fairly useable. > > I'll take a look. But let's say right away that such a tool would > need three things (Terry is gonna love this :-) : > > - UI independent code, meaning you could have this as a batch > processor, command-line or pseudo-UI interaction (i.e.: dialog). > > - dependency check to see what's available relative to the > system we're runnning -- we don't want to have to customize > the script every time, and it should still be able to offer > SMP on 3.0, but not on 2.2.x. Device-dependent have to be > treated as such (don't want AHC_SCB_PAGING to be selectable > when one uses ncr0, or PCI devices on ISA machine :-) You might want to take a look at my kernel configuration program. It is written in "C" and allows many forms of interaction between the various options. It automatically checks for IRQ/DMA/IO conflicts. And is fairly easy to configure. > - some mechanism for reading and parsing pre-written configuration > files -- accepting files like /sys/i386/conf/GENERIC is obvious, > but I'm talking at something capable of reading "skeleton" > pieces, and filling in the blanks -- for instance: > > include net-subsystem-defs > include disk-subsystem-defs > figure out cpu for yourself, etc... My program can read all of the standard configuration files, and can in fact use /sys/i386/conf/LINT as the main configuration file for itemizing options. I use a modified version of LINT to do all the work. I had considered adding an include option to the program, but it didn't seem "profitable" at this time. If you would like to see the program, it is at: fetch ftp://bmccane.uit.net/pub/kc/kc1.1.tgz brian