module-init-tools-3.2.2

[Matthew Burgess]

Version increment (3.1). Plenty of things are mentioned in the ChangeLog, two though stand out IMO:

o modprobe: fall back to /etc/modprobe.d if fail on /etc/modprobe.conf. o modprobe: allow config files to be directories, and recurse.

Is this something we want to consider using in LFS? I don't use modules at all, so couldn't possibly comment on the usefulness or otherwise on this, but it would seem to fit better with the other configuration setups we have (udev being just one example).

Cheers,

Matt.

[Matthew Burgess]

Looks like this one needs docbook2man installed before it'll compile. The man-pages are distributed along with the tarball though, so we have a couple of options:

1) do a touch *.{5,8} before issuing the make command so that the docs aren't rebuilt 2) Hack the Makefile so the docs aren't rebuilt 3) Add docbook2man detection to the configure script and send it upstream.

Out of these, 1) works and is my preference over 2). 3) is the more preferable long-term solution IMO. Any takers? :)

Cheers,

Matt.

[jim@…]

I figured out a simple fix for this issue

Add the following to the make line DOCBOOKTOMAN=""

so the line should look like make DOCBOOKTOMAN=""

This will also allow us to use the premade man pages.

[jim@…]

Fixed and upgraded in unstable

[Matthew Burgess]

Version increment (3.2.1). 3.2 had a large number of changes and this just adds macio device support. This release now includes the testsuite, so separate download/untar instructions are required. IIRC, this release should fix the problem of the testsuite rebuilding the binaries.

[alexander@…]

These module-init-tools have a new "blacklist" keyword for modprobe.conf. E.g., if I add "blacklist snd-fm801" line, the following will happen:

# modprobe 'pci:v00001319d00000801sv00001319sd00001319bc04sc01i00' Result: loads nothing because the "snd-fm801" module that the alias resolves to is blacklisted. Without the "blacklist snd-fm801" line, this would load snd-fm801.

# modprobe snd-fm801 Result: works, because the module name is specified explicitly, not as a result of resolving an alias.

The question is: how should the book explain such functionality and its intended use?

[Matthew Burgess]

We generally try to avoid repeating documentation that is provide by upstream, lest ours becomes out of date (which regarding device and module handling is, unfortunately, entirely possible). From modprobe.conf(5):

blacklist modulename

Modules can contain their own aliases: usually these are aliases describing the devices they support, such as "pci:123...". These "internal" aliases can be overridden by normal "alias" keywords, but there are cases where two or more modules both support the same devices, or a module invalidly claims to sup- port a device: the blacklist keyword indicates that all of a particular module's internal aliases are to be ignored.

If that needs expanding, maybe upstream would accept a patch?

[alexander@…]

The documentation doesn't need to be extended. It's just an answer to the following future question:

"You removed hotplug and now udev loads that module that I used to put into /etc/hotplug/blacklist. How do I gain the similar functionality with hotplug-less setup?"

Are we going to say that the reader has to figure this out himself?

In BLFS, when the English keymap was split from the rest in Xfree86 4.3.0, we did add a note about the need to reconfigure the keymap. I see this module-init-tools case as similar (i.e.: drastically changed configuration) if we remove hotplug.

[Matthew Burgess]

Version increment (3.2.2)