Messages in this thread | | | Date | Thu, 23 Mar 2006 21:03:03 -0800 | From | Linda Walsh <> | Subject | Security downgrade? CONFIG_HOTPLUG required in 2.6.16? |
| |
I had this config'ed out in 2.6.15 for machine that didn't have any hotpluggable devices. It is also configured with all the modules it needs and has kernel-module loading disabled.
What has changed in 2.6.16 that my "static" machine now needs hotplugging? As I understand it, hotplugging requires application-level support code (in /etc/) and a special application level "demon" to run in order to support these requests.
I'd prefer my kernel not to be dependent on a run-time demon to load "arbitrary" (user defined) segments of code that could come from any source -- usually outside the vanilla kernel tree.
If I don't want a specific kernel or machine to be dynamically reconfigurable after boot, why do I need to build in a mechanism for runtime loading of modules?
Linda
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |