Your message dated Thu, 9 Nov 2006 00:34:55 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#397384: module-init-tools: Misleading error: "modprobe:
Can't locate module /lib/modules/2.4.27/misc/lirc_dev.o"
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.2-pre1-2
Severity: normal
I compiled a module, maybe in the wrong spot. This is
where it is:
tvbox:~# ls -l /lib/modules/2.4.27/misc/lirc_dev.o
-rw-r--r-- 1 root root 13180 2006-11-04 14:19
/lib/modules/2.4.27/misc/lirc_dev.o
Attempting to install it gives an error:
tvbox:~# modprobe -v /lib/modules/2.4.27/misc/lirc_dev.o
modprobe: Can't locate module /lib/modules/2.4.27/misc/lirc_dev.o
Maybe the error itself is necessary, but the error message is
puzzling, at least in the above context. The file exists, and is easy
to locate; maybe it's looking for it in a particular locate and it's
not there.
For whatever is wrong, it would be better if the error message
clearly explained the problem. Suggestions for clarity:
1) Have the error indicate where it's looking:
modprobe: Can't locate module
"/lib/modules/2.4.27/misc/lirc_dev.o" in "/lib/modules/foobar"
2) OR, if full pathnames are no good, say so:
modprobe: module name is not allowed to begin with a '/' char
-- no full pathnames allowed.
3) OR, if no pathnames are allowed, say so:
modprobe: module name contains a '/' char -- pathnames not
allowed.
Also unclear is which package this bug belongs in:
tvbox:~# which modprobe
/sbin/modprobe
tvbox:~# ls -l /sbin/modprobe
-rwxr-xr-x 1 root root 23564 2005-01-26 16:10 /sbin/modprobe
tvbox:~# dlocate /sbin/modprobe
modutils: /sbin/modprobe
module-init-tools: /sbin/modprobe
Hope this helps...
Note: right now I can't use 'reportbug' on the (Debian stable) system
I'm testing, so there's less detail, but it shouldn't matter, as the
bug seems entirely verbal.
2nd note, from a day later: I tried it on my 'unstable' system:
% cp /lib/modules/2.6.16-2-686/kernel/drivers/scsi/sata_sx4.ko /tmp/
% modprobe /tmp/sata_sx4.ko
FATAL: Module /tmp/sata_sx4.ko not found.
% which modprobe
/sbin/modprobe
% dlocate /sbin/modprobe
module-init-tools: /sbin/modprobe
modutils: /sbin/modprobe
% for f in module-init-tools modutils ; do echo -n $f: ; dlocate -s $f
| grep Ver ; done
module-init-tools:Version: 3.2.2-3
modutils:Version: 2.4.27.0-6
...pretty much the same thing, except the wording of the error message has
changed
from "can't locate module ...", to "module ... not found."
--- End Message ---
--- Begin Message ---
On Nov 08, "A. Costa" <[EMAIL PROTECTED]> wrote:
> Sending Debian bugs upstream is the maintainers job. Obviously we
Not if I disagree with them.
> 3. We will not hide problems
It's my call to decide if this is a problem or not, and I say no.
Stop reopening this bug.
--
ciao,
Marco
signature.asc
Description: Digital signature
--- End Message ---
