From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keith Owens Date: Mon, 08 Oct 2001 01:50:31 +0000 Subject: Re: Network protocol for linux-hotplug. 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 Mon, 08 Oct 2001 01:05:45 +0100, Stamatis Mitrofanis wrote: >... a server will return info about how the client can >find appropriate driver software (like a precompiled kernel module >packaged together with appropriate driver agent scripts... or the source >code for a kernel module... maybe a ready-to-install >RPM/Debian/Slackware package...). A precompiled kernel module will not work, trust me on this. Modules must be compiled with the same config options, with a compatible[*] version of gcc, for SMP or non-SMP and for multiple architectures. The only way that will scale is a source driver. But that assumes that everybody using the server has a current set of sources and config for their kernel. I am not knocking the idea, but until you can solve the problem of building and loading modules on the fly, worrying about file formats and download protocols is a waste of time. [*] Different versions of gcc generate different code for the kernel. Blindly loading a gcc 2 module into a kernel compiled with gcc 3 or vice versa is a good recipe for Oops. _______________________________________________ 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