Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#11487 - Mistake in the modprobe(8) and modprobe.conf(5) manpages

Attached to Project: Arch Linux
Opened by Carlo Bersani (carlocci) - Sunday, 14 September 2008, 23:17 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 18 October 2008, 15:04 GMT
Task Type Bug Report
Category Documentation
Status Closed
Assigned To Aaron Griffin (phrakture)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Both the manpages says that modprobe.d is considered only if modprobe.conf doesn't exist, which is false. This blows my mind away: I don't know if I will ever trust a man again.

man 5 modprobe.conf:
/etc/modprobe.conf (or, if that does not exist, all files under the /etc/modprobe.d directory) specifies those options, as required.

man 8 modprobe:
-C --config
This option overrides the default configuration file (/etc/modprobe.conf or /etc/modprobe.d/ if that isn't found).


Additional info:
both manpages are in module-init-tools-3.4-1


Steps to reproduce:

man 5 modprobe.conf
man 8 modprobe
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Saturday, 18 October 2008, 15:04 GMT
Reason for closing:  Upstream
Additional comments about closing:  closing it; if the author doesn't respond ever, I think the best way would be to raise this issue on LKML.
Comment by Roman Kyrylych (Romashka) - Sunday, 28 September 2008, 16:06 GMT
I don't know if we should patch manpages.
Please report this to module-init-tools developers.
@Aaron: should we keep this bug open just to keep track on its status?
Comment by Carlo Bersani (carlocci) - Monday, 29 September 2008, 15:19 GMT
I was unsure where to report the bug because I noticed that in the PKGBUILD the manpages come from an entirely different server and module-init-tools bugzilla seemed abandoned.
I will try the email route.
Comment by Aaron Griffin (phrakture) - Monday, 29 September 2008, 15:31 GMT
module-init-tools upstream is located here: http://kerneltools.org/KernelTools.org
If the bugzilla does not work, I'd suggest emailing Jon Masters directly (see main page above).

Roman, I think we should close this
Comment by Carlo Bersani (carlocci) - Saturday, 04 October 2008, 23:12 GMT
I reported the bug to Jon Masters (' email at least), no reply but I'm filled with (not so much) hope.
The more I witness different bug reporting systems, the more I come to appreciate emails and flyspray.
Comment by Roman Kyrylych (Romashka) - Sunday, 05 October 2008, 13:15 GMT
@ Cario about manpages from different server:
interestingly, while reading this patch: http://www.linuxfromscratch.org/patches/lfs/development/module-init-tools-3.4-manpages-1.patch
(which is incorrect too) it looks like manpages are generated from docbook files so distros are providing pre-generated manpages to avoid docbook2man :)
Comment by Carlo Bersani (carlocci) - Monday, 06 October 2008, 15:23 GMT
Damn you, SGML!
Thanks for clearing that out, that was interesting

Loading...