module-assistant support for zaptel

[Jose Carlos Garcia Sogo]

--=-+baZysq0gQXCqUafbYif
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

El mar, 29-03-2005 a las 07:35 +0200, Tzafrir Cohen escribi=C3=B3:
> On Sun, Mar 27, 2005 at 11:37:29PM +0200, Jose Carlos Garcia Sogo wrote:
>=20
> > > > I've played with it all day long and it seems very unsuitable for
> > > > non-root builds. If it requires that the code module is compressed =
to a
> > > > rather than kept in its own directory than it really does harm. If =
not,
> > > > I have no problem with it and it might actually turn out useful one=
 day.
> >=20
> >   If you want to use it as non-root you have to pass --user-dir dir/ to
> > m-a, being dir a directory you have permissions.
>=20
> The troubles begin when it tries to get into the kernel source
> directory. Other modules (shfs was my test) build fine because they
> don't need to use the kernel source tree itself. Zaptel does. And this
> is where the build (very silently, and log-less, even at the presence of
> -v) fails.

  Mmmm. I have tested that, and it only happens when you have compiled
your own kernel.

  I think that we have 3 scenarios:

 1. You use Debian provided kernels and you don't compile them. When
using m-a you will get kernel-headers-$version (where $version) matches
your running kernel from Debian archives, you build and install the
modules.

 2. You use Debian provided sources but you compile your own kernels.
 3. You use pristine kernel sources for building your kernels.

 In this two when using make-kpkg you should provide something to append
to (--append-to-version) or a version. For example, if you use
--append-to-version swsusp2 your kernel package would be
kernel-image-2.6.10swsusp2_2.6.10_i386.deb

 In this case, if you still have sources in /usr/src, m-a will detect
that and will link to them, so modules building will use them. If you
don't have them installed, m-a will try to install
kernel-headers-2.6.10swsusp2 package, which will fail unless you have
compiled them and you have them around in an apt repository.

 If you don't use --append-to-version option, but compile your own
kernels, your version won't match version installed in Debian, so
kernel-headers won't be find either by m-a. But in this case you can
solve this problem by passing -l option to m-a. So if you are running a
2.6.10 kernel, you should pass -l 2.6.10-1 (as those are the
kernel-headers provided by Debian). You cannot do this when using
--append-to-version because in this case modules won't be installed
in /lib/modules/$kernel_version$whateverappended but
in /lib/modules/$kernel_version, so modprobe won't find them.

 I hope this shows you how m-a works, and can help you on making clear
to you where the problems you're finding are.

 Cheers,


--=20
Jose Carlos Garcia Sogo
   jsogo@debian.org

--=-+baZysq0gQXCqUafbYif
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
	digitalmente

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCScVnS+BYJZB4jhERAipGAJ9Ql9c32hACOWMPjMpKhOwrZ3F0vgCfQUf+
VmUjJKUny5gqR6IAHz9NnQM=
=7xua
-----END PGP SIGNATURE-----

--=-+baZysq0gQXCqUafbYif--