"ifup" should deal with non-zero exit codes from modprobe

[Cyberax]

Binary package hint: ifupdown

Ifup should deal with non-zero exit codes from modprobe. My ipv6 setup stopped working since ipv6 module is compiled into the kernel in Jaunty so "modprobe -Q" fails to load it.

Replacing modprobe with this script restored ipv6 functionality:
===============
#!/bin/bash

/sbin/modprobe.orig "$@"
ret=$?

if [[ "$1" == "-Q" ]] ; then
        exit 0
fi

exit $ret
===============

[Scott James Remnant (Canonical) (canonical-scott)]

Note that modprobe 3.7 doesn't _have_ a -Q option, so this patch would be invalid

[Cyberax (alex-besogonov)]

Jaunty still uses module-init-tools-3.3 which advertises support for "-Q" option:
===========
cyberax@devsrv:~$ modprobe
Usage: /sbin/modprobe.orig [-v] [-V] [-C config-file] [-n] [-i] [-q] [-Q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
/sbin/modprobe.orig -r [-n] [-i] [-v] <modulename> ...
/sbin/modprobe.orig -l -t <dirname> [ -a <modulename> ...]
===========

Either module-init-tools should be fixed or ifupdown. I think that module-init-tools should be fixed for Jaunty, since it's a minimal amount of work.

[Scott James Remnant (Canonical) (canonical-scott)]

On Wed, 2009-03-04 at 13:38 +0000, Cyberax wrote:

> Jaunty still uses module-init-tools-3.3 which advertises support for
> "-Q" option:
>
The 3.7 upload is pending ;) it very soon won't.

Trust me, I'm the maintainer/developer.

Scott
--
Scott James Remnant
<email address hidden>