Your message dated Wed, 8 Aug 2007 00:39:09 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#435129: module-init-tools: Would like a way to blacklist
only if running a particular kernel
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: module-init-tools
Version: 3.3-pre11-4
Severity: wishlist
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Marco,
I'm currently packaging the 'p54' kernel module, which replaces the
'prism54' module currently present in the upstream Linux kernel. I would
like to include a file in modprobe.d in the eventually-built
p54-modules-$kernelversion package that will prevent prism54 from being
loaded, but only if the user is currently running $kernelversion.
My first idea was to ship an etc/modprobe.d/p54-$kernelversion file
containing:
install prism54 if test "$(uname -r)" == "_KVERS_"; then :; else modprobe
--ignore-install prism54; fi
Where dh_installmodules replaces _KVERS_ with the correct kernel version
at package build time. But I think that this will not work, because if
the user also has a p54-modules-$otherkernelversion package installed at
the same time, the two definitions will conflict.
So I'm asking you if there is a sane way to do what I am trying to do,
or whether I should just not bother at all, and instead ship an
/etc/modprobe.d/p54 file in an arch:any p54-common package instead?
Regards,
- --
Sam Morris
http://robots.org.uk/
PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
- -- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-1-k7 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages module-init-tools depends on:
ii libc6 2.6-4 GNU C Library: Shared libraries
ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip
module-init-tools recommends no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGrIvpshl/216gEHgRAvfbAKDpGeg48Bg6vOT1VUE6ICPsHGBZqQCgkbWU
0YfFcg9hhTyIG0hONiYRk9E=
=QaWh
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Jul 29, Sam Morris <[EMAIL PROTECTED]> wrote:
> Where dh_installmodules replaces _KVERS_ with the correct kernel version
> at package build time. But I think that this will not work, because if
> the user also has a p54-modules-$otherkernelversion package installed at
> the same time, the two definitions will conflict.
Correct.
> So I'm asking you if there is a sane way to do what I am trying to do,
> or whether I should just not bother at all, and instead ship an
> /etc/modprobe.d/p54 file in an arch:any p54-common package instead?
Do not bother at all.
--
ciao,
Marco
signature.asc
Description: Digital signature
--- End Message ---
