Summary: | compile order of modutils and module-init-tools causes errors on reboot | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andre Hinrichs <andre.hinrichs> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | robert.w.thomas |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andre Hinrichs
2004-04-04 12:56:05 UTC
you cant use both packages at the same time if you plan on using 2.6, then only use module-init-tools ... it installs <program>.old so that you can do module related stuff in 2.4.x and earlier Then they should really block each other, shouldn't they? Means, if somebody installs module-init-tools he should be forced to remove modutils. No, as stated before, module-init-tools has an intelligent backup function. The problem is that modutils don't. So there'd have to be something like re-emerging module-init-tools after every merge of modutils only if module-init-tools are installed. At least give the poor users a warning what they should do if they're running 2.6 kernels, I spent some time figuring this one out with a kernel without loaded modules ;) But module-init-tools builds modutils. If you have module-init-tools installed, then you don't need modutils. Isn't that enough reason for a block? P.S. - I just ran into this problem. Luckily it didn't take me too long to figure out that I just needed to re-emerge module-init-tools. I don't know why I had modutils installed anyway, since I only run 2.6.x |