Date: Tue, 21 Jan 1997 17:51:39 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: msmith@atrad.adelaide.edu.au (Michael Smith) Cc: terry@lambert.org, hackers@freebsd.org Subject: Re: Kernel driver source installer? Message-ID: <199701220051.RAA20491@phaeton.artisoft.com> In-Reply-To: <199701220045.LAA09939@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jan 22, 97 11:15:25 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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. <sigh>. > > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701220051.RAA20491>