On Sun, 15 Aug 2010 09:11:21 -0400 (EDT), Angus Hedger wrote: > Stephen Powell wrote: >> >> If you copy your module directly into the source tree, then you need >> to download a new kernel source tree and unpack it due to kernel >> maintenance, you lose your modifications. By keeping the out-of-kernel- >> source-tree modules in a separate directory, /usr/src/modules/..., >> you don't lose your modifications. You download and unpack the >> new kernel source, rebuild both packages, and install both packages. >> Simple. > > That makes a lot of sense, thanks for that!
Official Debian packages designed to be compiled as source and used as out-of-kernel-source-tree kernel modules are generally packaged in such a way that they can be installed and used either way, either by installing kernel headers and compiling using just the headers, or compiled using a kernel source package. For example, see the /usr/share/doc/nvidia-kernel-*source/README.Debian file in the various nvidia kernel source module packages. This file documents both compilation and installation methods and you can choose the one that suits your particular environment best. On the other hand, if you are downloading upstream source directly from the upstream site and following their installation procedure, they may give you a "one size fits all" installation procedure that requires kernel headers. That's one reason why it is best to use official Debian packages whenever possible. The Debian packages have been customized by the Debian package maintainer to do things "the Debian way". As I say in my kernel- building web page, there are three ways to do everything: the right way, the wrong way, and the Debian way! -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1371450646.109819.1281894198479.javamail.r...@md01.wow.synacor.com
