Madwifi-ng Recent Builds

[Ian MacDonald]

Hi Kel,

On Fri, 2006-03-31 at 06:15 +1000, Kel Modderman wrote:
> > Today it produced:
> >
> > kernel-xen0-2.6.12.6-xen_12.6_i386.deb
> > madwifi-ng-modules-2.6.12.6-xen_0.svnr1486.20060328-1+12.6_i386.deb
> >
> > Previously, until my update of madwifi-ng-source today, the
> > modules_image looked like:
> >
> > madwifi-ng-modules-2.6.12.6-xen_0.9.0+svn1401-2+12.6_i386.deb
> >   
> 
> 
> I changed the version number of the package, no big deal here . . .

Yeah, that was clear; I just wanted to show you exactly which revisions
I was using.
> >
> > root@/usr/src# dpkg -i
> > madwifi-ng-modules-2.6.12.6-xen_0.svnr1486.20060328-1+12.6_i386.deb 
> > (Reading database ... 62830 files and directories currently installed.)
> > Preparing to replace madwifi-ng-modules-2.6.12.6-xen
> > 0.svnr1486.20060328-1+12.6 (using
> > madwifi-ng-modules-2.6.12.6-xen_0.svnr1486.20060328-1+12.6_i386.deb) ...
> > Unpacking replacement madwifi-ng-modules-2.6.12.6-xen ...
> > dpkg: dependency problems prevent configuration of
> > madwifi-ng-modules-2.6.12.6-xen:
> >  madwifi-ng-modules-2.6.12.6-xen depends on linux-image-2.6.12.6-xen |
> > kernel-image-2.6.12.6-xen; however:
> >   Package linux-image-2.6.12.6-xen is not installed.
> >   Package kernel-image-2.6.12.6-xen is not installed.
> > dpkg: error processing madwifi-ng-modules-2.6.12.6-xen (--install):
> >  dependency problems - leaving unconfigured
> > Errors were encountered while processing:
> >  madwifi-ng-modules-2.6.12.6-xen
> > root@/usr/src# 
> >   
> 
> 
> Its because of the name of your kernel, 
> (kernel-xen0-2.6.12.6-xen_12.6_i386.deb), madwifi-ng expects to see 
> linux-image-_KVERS_ | kernel-image -_KVERS_ to install properly.  I do 
> not know anything about these xen kernels, pehaps i should take a closer 
> look at the names given to the various arch/flavours produced by the 
> debian kernel source, or consider dropping the strict dependency (in 
> control.modules.in) if there will be no consistency in naming.
> 
> Is that an official kernel? Or was it built using kernel-package? why 
> isn't it named "kernel-image-xen0-2.6.12.6-xen_12.6_i386.deb" or 
> "linux-image-*"?

The kernel is built from unofficial sources (Xen 3.0 is not yet in
unstable).

I think kernel-image-xen0 would be more appropriate too. There would
also then be a kernel-image-xenu also. 

With the Xen Archicture the patch creates  kernel-xen0-2.6.12  and
kernel-xenu-2.6.12 depending on which kernel config options are set.  I
would describe them as sub-arch of Xen.  In fact I always used to supply
--sub-arch=xen0 or sub-arch=xenu to the make-kpkg line, but when I tried
to debug this problem, I noticed that it made no difference.  ie. The
--subarch flag was not causing kernel-image to be replaced by
kernel-${subarch}.

Sounds like I can manually relax the restrition using the
control.modules.in. I will check with the maintainer for the Xen patches
and see what sort of feedback I get.

If you are curious (And Xen is REALLY COOL), the sources for the Xen
kernels are here:

deb http://packages.debianbase.de/stable/i386/xen3 ./

thanks,
iMac