On Sun, 24 May 2009, Mike Frysinger wrote:
Some people expect to be able to do `man modprobe.d` and see the relevant content. Not surprising considering modprobe.conf(5) already documents that.
Ah yes, definite agreement here. We already do that in our builds, so it somehow didn't even occur to me that it should be done upstream.
Signed-off-by: Mike Frysinger <vapier@xxxxxxxxxx> --- Makefile.am | 2 +- modprobe.d.5 | 1 + 2 files changed, 2 insertions(+), 1 deletions(-) create mode 100644 modprobe.d.5 diff --git a/Makefile.am b/Makefile.am index be697dc..b66517a 100644 --- a/Makefile.am +++ b/Makefile.am @@ -36,7 +36,7 @@ depmod_LDADD = $(LDADD) libmodtools.a modinfo_LDADD = $(LDADD) libmodtools.a modindex_LDADD = $(LDADD) libmodtools.a -MAN5 = modprobe.conf.5 modules.dep.5 depmod.conf.5 +MAN5 = modprobe.conf.5 modules.dep.5 depmod.conf.5 modprobe.d.5 MAN8 = depmod.8 insmod.8 lsmod.8 rmmod.8 modprobe.8 modinfo.8 SGML = $(addprefix doc/, $(MAN5:%.5=%.sgml) $(MAN8:%.8=%.sgml)) dist_man_MANS = $(MAN5) $(MAN8) diff --git a/modprobe.d.5 b/modprobe.d.5 new file mode 100644 index 0000000..d0ed026 --- /dev/null +++ b/modprobe.d.5 @@ -0,0 +1 @@ +.so modprobe.conf.5
I might even suggest reversing that -- in other words, the primary file itself being modprobe.d.5, and modprobe.conf.5 being a symlink
to modprobe.d.5 -RW -- To unsubscribe from this list: send the line "unsubscribe linux-modules" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
