tim at io41.com
Tue Aug 19 07:52:13 UTC 2008
Good job in spotting the bug. In order to keep track of all the bugs
and their info it is necessary to use a bug tracker. For ubuntu this
can be found here: https://bugs.launchpad.net/ubuntu/
There you can click the "Report a Bug" button ( or
https://bugs.launchpad.net/ubuntu/+filebug ), and follow the steps.
The pachage the command "modinfo" is part of is called
"module-init-tools". This is very useful information to the
If you could report the bug there it would be very helpful.
If you ever want to know what package a command belongs to there are
two simple steps involved.
1) Find the commands full path using the command "which".
i.e. which modinfo
This will show you modinfo's full path, in this case "/sbin/modinfo"
2) use "dpkg -S /path/to/file" to find out what package it belongs to.
i.e. dpkg -S /sbin/modinfo
On Thu, Aug 14, 2008 at 12:37 AM, Nicolas MICHEL
<nicolas.michel at lemail.be> wrote:
> I didn't know where to report this bug. In the man page of the command
> "modinfo" (8), the name of the field "param" with the "-F" option is wrong.
> The name of this field is "parm".
> Nicolas Michel
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss at lists.ubuntu.com
> Modify settings or unsubscribe at:
More information about the Ubuntu-devel-discuss