From owner-freebsd-arch Wed Sep 27 9:27:11 2000 Delivered-To: freebsd-arch@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id B137537B424 for ; Wed, 27 Sep 2000 09:27:07 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8RGR0H19790; Wed, 27 Sep 2000 09:27:00 -0700 (PDT) Date: Wed, 27 Sep 2000 09:27:00 -0700 From: Alfred Perlstein To: Sue Wainer Cc: freebsd-arch@FreeBSD.ORG Subject: Re: Kernel configuration with new device drivers Message-ID: <20000927092700.X9141@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from wainer@sandgate.com on Wed, Sep 27, 2000 at 11:29:19AM -0400 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Sue Wainer [000927 08:29] wrote: > What is the proper way to specify new driver source modules for a kernel > configuration? > E.g., the config manual page mentions /sys/i386/conf/files.ERNIE. How does > this file > get picked up when runing "config ERNIE"? Should files.i386 be modified to > include it? If it's archetecture neutral you want to use: /usr/src/sys/conf/files If it's i386 specific you want to use: /usr/src/sys/conf/files.i386 The reason for the /sys/i386/conf/files.ERNIE file is so you can have a local modification without it being wiped out by cvsup. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message