Questions about kernel-package 6.x and kernel-source*.deb's

[Richard Kaszeta <kaszeta@me.umn.edu>]

Recently I upgraded most of my machines from the version of
kernel-package that came with hamm to 6.05.

Now when I build kernel source packages, instead of the kernel-source
package unrolling to /usr/src/kernel-source-x.x.x it just creates
/usr/src/kernel-source-x.x.x.tar.gz.  

The make-kpkg man page states:

kernel_source
              This  target  produces  a debianised package of the
              Linux kernel sources. The package produced also has
              scripts  called  at  install  and delete times that
              manage the symbolic link /usr/src/linux and  ensure
              that   the   link   is   pointed   at   the  latest
              source/header package on the system.

suggesting that the /usr/src/linux link gets updated by the
kernel-source and kernel-headers packages.  But on my system, after
installing custom kernel packages, I get:

%ls -la /usr/src
total 12944
drwxrwsr-x   4 root     src          1024 Mar  5 08:46 .
drwxr-xr-x  17 root     root         1024 Feb  4 10:18 ..
drwxr-xr-x   8 root     root         1024 Oct 26 09:48 boot-floppies
drwxr-xr-x   3 root     root         1024 Mar  5 08:45 kernel-headers-2.2.1
-rw-r--r--   1 root     root     13196998 Feb  5 09:58 kernel-source-2.2.1.tar.gz

so this obviously isn't happening.

The problem I have is that I have a number of third party kernel
modules (mostly gpib), which are expecting to find a configured src
tree in /usr/src, including module information .  Even if I unroll
kernel-source-2.2.1.tar.gz and point /usr/src/linux to it, these won't
building since neither of these packages include the version
information contained in /usr/src/linux/modversions.h and
/usr/src/linux/modules/*.ver.  So something isn't working here.

My workaround has been ugly... when I make a custom kernel, I sandbag
the .config.  When I need to build third-party modules, I unroll my
upstream kerenl source in /usr/src/linux, copy in the .config, do a
full kernel build but no install, then build the modules, install the
modules, and clean up my mess.
 
There's definitely at least one bug here, but I thought I'd ask for a
clarification before submitting a bug report.

Can anyone clear up this mess?

Thanks.


-- 
Richard W Kaszeta 			Graduate Student/Sysadmin
bofh@me.umn.edu				University of MN, ME Dept
http://www.menet.umn.edu/~kaszeta