Package: module-init-tools Version: 3.2-pre8-1 Severity: normal Hello,
while rewritting the init script of sl-modem-daemon I noticed that modprobe -r does not have reliable && consistant && useful error codes. That means, it differs from rmmod and does the following: - if a module is not loaded, it returns 0 - if the module is not loaded and is also not available, it returns 1 - if the module was in use, it also returns 1. It would be nice to see the reason for the failure encoded in the return code The first two should be consistent, I prefer having both return a false value, 1. Regards, Eduard. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages module-init-tools depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii lsb-base 3.0-1 Linux Standard Base 2.0 init scrip module-init-tools recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
