* Mark Knecht <markkne...@gmail.com> [120406 12:16]: > On Fri, Apr 6, 2012 at 9:03 AM, Todd Goodman <t...@bonedaddy.net> wrote: > > * Mark Knecht <markkne...@gmail.com> [120406 11:40]: > > [..] > >> To me it looks safe to emerge -C kmod and then emerge > >> module-init-tools if you want to go that way. I'd do an equery files > >> kmod and carefully study what you're getting with that package, or > >> else push a bug request up to that package maintainer for providing a > >> modprobe that's not 100% compatible. > >> > >> Good luck, > >> Mark > > > > udev-182-r2 and dracut depend on kmod. > > > > So if the OP hasn't masked them then he needs kmod. > > > > Todd > > > > I have the newer udev masked, but I do have dracut installed and don't > need kmod here. > > My system is _mostly_ stable, not ~amd64, so possibly that's part of the > issue. > > - Mark
Hmm, I'd expect dracut to depend on virtual/modutils-0 then but dracut-017-r3 sure doesn't seem to: equery d kmod sys-kernel/dracut-017-r3 (>sys-apps/kmod-5[tools]) Wait, I looked at the ebuild and it depends on either module-init-tools or kmod so that's why. So it looks like just udev-182-r2 depends upon it. Sorry for the misinformation. Todd
