From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Jansen Date: Thu, 18 Oct 2001 00:47:02 +0000 Subject: Re: Automatic download and installation of drivers. Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Thursday 18 October 2001 01:32, you wrote: > But how do you resolve all of the previous points I raised about > compilers, .config files, in kernel apis, and security with regards to > "automatic downloads"? - compilers By requiring the user to have a certain gcc (make, ld..) version installed, possibly called kgcc or installed independently of the regular compiler. Its path must be be specified in a configuration file. - .config files The source, or at least the headers, and the .config files of the installed kernel must be available. The location could be specified in the configuration file as well. The only real problem are .config files that lack options that are needed by a driver (in other words the installed kernel does not have all features needed by the driver). - kernel apis Like with today's patches, even though it would be nice if source compatibility in the stable kernel series could be guaranteed. - security The security is not much different than with Debian's apt, Redhat Network or Suse's YOU. Either you get the driver from a trusted source, or the user has to be asked before the system downloads from a new/untrusted source. To allow a download from new/untrusted sources you need to know the root password, of course (or maybe be in a special group) bye... _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel