| Summary: | different kernel support for /etc/init.d/modules | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | nth <y.lesaint> |
| Component: | [OLD] Core system | Assignee: | Martin Schlemmer (RETIRED) <azarah> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | drobbins |
| Priority: | Low | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | /etc/modules.autoload support for kernel versions customization | ||
Created attachment 9143 [details, diff] /etc/modules.autoload support for kernel versions customization I'm no shell script expert, this patch is making your well-written /etc/init.d/modules rather ugly, but for kernel 2.4.20, it would load (in this order) : - /etc/modules.autoload - /etc/modules.autoload-kernel-2 - /etc/modules.autoload-kernel-2.4 - /etc/modules.autoload-kernel-2.4.20 Hope it helps. For information, my email is y.lesaint@free.fr PS: sorry if i have not attach this patch with my first report, but i could not find any attachment button. I do not like it. What about an additional /etc/modules.auto/, and in there you have files '2', '2.4', '2.5', etc ? Some possibilities for /etc/modules.autoload/kernel-2.4 and /etc/modules.autoload/kernel-2.5 would be great, yeah :) And i don't like my patch either, just pointing out the fact that i need some mechanism to detect kernel version at boot time and then modprobe the associated modules i have defined. :p Only issue I see with calling it /etc/modules.autoload/, is that you have a file called that .. thus baselayout will have to move things around ... No doubt /etc/modules.auto/ is great to :p Check baselayout-1.8.6.3
baselayout-1.8.6.3 support for modules autoloading / kernel versions is
great, thanks azarah :)
I'm just filling two more patches (good these ones ;) ) for
/etc/init.d/{modules,net.eth0}
|
I'm using kernel 2.5 every day and have some 2.4.20 as backup. My concern is that /etc/init.d/modules can only handle a single /etc/modules.autoload, which is very bad since kernel 2.4 and 2.5 has several distinctions for module names and usage. So i thought maybe it would be cool if for example, with kernel 2.4.20 : - /etc/init.d/modules would load /etc/modules.autoload - then /etc/modules.autoload-kernel-2.4 - then /etc/modules.autoload-kernel-2.4.20