From owner-freebsd-hackers Tue Jan 21 17:07:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA28683 for hackers-outgoing; Tue, 21 Jan 1997 17:07:13 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA28671 for ; Tue, 21 Jan 1997 17:07:11 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA20491; Tue, 21 Jan 1997 17:51:39 -0700 From: Terry Lambert Message-Id: <199701220051.RAA20491@phaeton.artisoft.com> Subject: Re: Kernel driver source installer? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Tue, 21 Jan 1997 17:51:39 -0700 (MST) Cc: terry@lambert.org, hackers@freebsd.org In-Reply-To: <199701220045.LAA09939@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jan 22, 97 11:15:25 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Sure, but you still have to edit _something_ in that directory. The idea > > > behind putting it in files.i386 is that you can then generate as many > > > different configs as you like; the driver effectively becomes part of > > > the tree proper, until you rip it out again. > > > > Ideally, only the directory contents would need to be edited. . > > Nowere near good enough, Terry. Try "you should be able to build the > driver standalone, throw it into the kernel's linkage path and > reboot". Uh, why should you have to reboot? The act of placing the driver object in the directory should place it in your kernel... > But while I'm thinking and trying to work in that direction, it's > nowhere near reality, and that's what I have to deal with at the moment, > hence a script that reflects reality rather than some unrealised ideal. If you keep making these things easy without a real soloution, where is the "squeaky wheel" incentive for a real soloution? 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.