From owner-freebsd-current Thu Jan 7 15:50:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26471 for freebsd-current-outgoing; Thu, 7 Jan 1999 15:50:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26466 for ; Thu, 7 Jan 1999 15:50:13 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA26129; Fri, 8 Jan 1999 10:19:28 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 08 Jan 1999 10:19:39 +1030 (CST) From: "Daniel O'Connor" To: Kenneth Wayne Culver Subject: Re: Kernel configurator Cc: FreeBSD-Current Cc: FreeBSD-Current , "Thomas T. Veldhouse" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Jan-99 Kenneth Wayne Culver wrote: > Well, I don't think that would be a problem, I guess all the devices could > be read from LINT, that way we wouldn't have to hardcode the devices into > the configurator program. That idea came from someone else on this mailing > list, I neglected to look at that person's name, but I can't take credit. It would also have to know what devices can use what busses etc.. Which requires parsing some more files :) Also there would have to be a file which contains explanations for the various devices and options. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message