From owner-freebsd-questions Wed Jun 3 00:03:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10343 for freebsd-questions-outgoing; Wed, 3 Jun 1998 00:03:11 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10337 for ; Wed, 3 Jun 1998 00:03:08 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.8/8.8.8) with SMTP id AAA22727; Wed, 3 Jun 1998 00:03:05 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Wed, 3 Jun 1998 00:03:04 -0700 (PDT) From: Doug White Reply-To: Doug White To: "Benjamin A. Oldham" cc: freebsd-questions@FreeBSD.ORG Subject: Re: kernel.config In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Jun 1998, Benjamin A. Oldham wrote: > I've probably just not looked in the right places yet, but I've not been > able to figure out the format (and function) of /kernel.config I have to > manually configure a PnP device every time I install a new kernel, and > would like to automate that configuration. Any help would be appreciated. kernel.config is automatically generated, I don't know if it's even human-digestable. I assume you're stuck with an AWE32 :-) It may be time to add a kernel config line item for it. Luckily you get to a point where you have everything you need built into your kernel and you don't have to go through this every time. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message