Description of problem:
dracut-0.7-1 uses a modprobe option (-d) that exists only in
module-init-tools >= 3.7-9, but the 'Requires: module-init-tools'
of dracut is not version-specific.
If one uses dracut on a Fedora 10 system (yes, it does work), as of
version 0.7-1 all /lib/modules files are silently omitted from initrd.

Version-Release number of selected component (if applicable):
dracut-0.7-1.fc11

How reproducible:
100% (on a Fedora 10 system).

Steps to Reproduce:
1. Install dracut-0.7-1 on a Fedora 10 system.
2. Run: /sbin/dracut -H /tmp/initrd
3. Run: /sbin/lsinitrd /tmp/initrd | grep lib/modules
  
Actual results:
On a Fedora 10 system, there are no lib/modules files (and no complaints
from dracut).

Expected results:
Several files under lib/modules (as was the case with dracut-0.5-1).

Additional info:
FIX:
In the dracut spec file, change:
    Requires: module-init-tools
to:
    Requires: module-init-tools >= 3.7-9
That's the earliest Fedora 11 version of module-init-tools; it supports
modprobe -d .

With an earlier module-init-tools, there are no complaints when dracut
is run because stderr from modprobe is discarded, to get rid of several
WARNINGs.  Perhaps those should be filtered out explicity, and let
all other stderr appear (while letting stdout proceed out the pipe).
This is an advanced exercise in redirection; extra credit will be given.