Hello, I would like to submit a script I wrote to the portage tree. The script automatically finds and formats the /etc/modules.autoload.d/kernel-2.[4,6] file with all available (compiled) modules. I have found it very convenient when building my systems and would like to share it with others. I believe that app-admin/kmods-autoconfig would be a good location for this package, though I am new to developing for Gentoo, so feel free to place it wherever is most suitable. Thanks, Jayson
Created attachment 80145 [details] kmods-autoconfig-1.0.0.ebuild Note: I have only tested this fully on ppc and x86. Since this script relies on bash and the find utility (and requires no compiling), I am assuming it will function properly on other architectures as well, but have labeled them as unstable as I have not tested it on those architectures. Please let me know what architectures you recommend to list for this if different from what I have listed. Thanks, Jayson
I just cleaned out my temp directories and tried the ebuild I just submitted and I am receiving an error. Since the file is not compressed, it is not copied to the working directory and thus errors on the move. Any idea how I can fix this?
(In reply to comment #0) > The script automatically finds and formats the /etc/modules.autoload.d/kernel-2.[4,6] file with all available (compiled) modules. this Errr... why would you want to unconditionally load all available modules at boot time?
Usually I only build the modules I need, so I often load all of them or most of them. Usign the script I can go back and comment out the one or two I don't need, but it's a lot easier than adding all of the ones I do need. Also, I would be willing to maintain the package, I'm just new at this, so I'm not sure how to.
(In reply to comment #4) > Usually I only build the modules I need, so I often load all of them or most of > them. Usign the script I can go back and comment out the one or two I don't > need, but it's a lot easier than adding all of the ones I do need. What I meant was, why compile them as modules if you load them unconditionally at boot time? Why not just compile them into the kernel? Or compile them as modules and use either coldplug/hotplug/udev for loading the modules when needed?
When I'm first building a system, I like to build most of the device drivers as modules since I'm not always positive they will work. That way it's easier to debug. As I've been getting better and better at pickign the right ones, I tend to keep most if not all of them and then later, when I'm confident everything is working well on the system, I build them in to the kernel.
I'm in agreement with Henrik. Generally speaking if you need a module to be loaded automatically every-time then you should be building these in-kernel. On the offchance that there is a bad kernel module which causes OOPs and the likes floating around, I would not like to think it was being automatically loaded because of an automated process. However, I do thank-you for the efforts, and of course if you find it useful I'm sure others would as well. But as far as policy goes, I can't see this being possible to accept.
Ok, closing as WONTFIX then. Thanks.
