Bug#548841: module-init-tools: Modprobe -q should always return 0.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



----- Forwarded message from Philipp Weis <pweis@xxxxxxxxx> -----

Subject: Bug#548841: module-init-tools: Modprobe -q should always return 0.
Reply-To: Philipp Weis <pweis@xxxxxxxxx>, 548841@xxxxxxxxxxxxxxx
From: Philipp Weis <pweis@xxxxxxxxx>
To: Debian Bug Tracking System <submit@xxxxxxxxxxxxxxx>

Package: module-init-tools
Version: 3.10-3
Severity: normal

When calling modprobe -q with a non-existing module, it returns with
exit code 1. According to the manpage, modprobe "normally" will report
an error, and with -q shouldn't, so I believe the exist code should
always be 0, at least that seems to be the assumption in some init
scripts (e.g. binfmt-support).

Philipp


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (600, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages module-init-tools depends on:
ii  libc6                         2.9-26     GNU C Library: Shared libraries
ii  lsb-base                      3.2-23     Linux Standard Base 3.2 init scrip

module-init-tools recommends no packages.

module-init-tools suggests no packages.

-- no debconf information

-- 
Philipp Weis



----- End forwarded message -----

-- 
ciao,
Marco

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux