From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Jansen Date: Tue, 30 Oct 2001 08:26:48 +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 Monday 29 October 2001 22:53, you wrote: > But I don't keep my kernels in /usr/src/linux, and neither do most > people. And vendor kernels include a number of different .config files, > all of them placed in a different file within the .src.rpm. Work with > the LSB if you want to push for this kind of standardization. You don't have to use /usr/src/linux, the system would need its own kernel tree at different location (installed by the distribution or copied by a make target similar to modules_install when you compile the kernel yourself). You shouldn't even access it yourself. For each kernel release there must be a gcc version defined, and the compilation system must have this gcc available. This could mean that you have 10 gccs (if you have 10 different kernels installed). These gcc's should not be in the usual PATH directories (/usr/bin..) but in a private directory. > How would you describe the fact that between kernels x and y, the struct > usb_serial_device changed the field "lock" from being a "struct > spinlock_t" to being a "struct semaphore"? Changes that that _have_ to > have code changes to the driver made. That's the main problem that you > are going to run into here. IMHO it is neccessary that stable kernels keep source compatibility. > Remember /sbin/hotplug runs as root. You do _not_ want to be doing any > of these actions as root :) But it shouldn't be a problem to su to a special user for compiling. 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