Summary: | get rid of modules.conf in 2.6 kernels | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Simone Gotti (RETIRED) <motaboy> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 66504 |
Description
Simone Gotti (RETIRED)
2004-04-22 15:12:40 UTC
A debian developer (Marco d'Itri) saied to me that Debian already uses modprobe.d and a script to generate modprobe.conf (like now is done with modules.conf), so why gentoo doesn't uses it? Bye! gentoo has been generating modprobe.conf for a while now, that has nothing to do with this bug Actully modprobe allready scans /etc/modprobe.d so there is no need to generate modprobe.conf sure there is ... what if a package provides a modules.d config file but not a modprobe.d config file baselayout-1.12.0_pre19 and better should handle this graciously |