From: Linda Walsh <lkml@tlinx.org>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Security downgrade? CONFIG_HOTPLUG required in 2.6.16?
Date: Thu, 23 Mar 2006 21:03:03 -0800 [thread overview]
Message-ID: <44237D87.70300@tlinx.org> (raw)
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
next reply other threads:[~2006-03-24 5:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 5:03 Linda Walsh [this message]
2006-03-25 18:54 ` Security downgrade? CONFIG_HOTPLUG required in 2.6.16? Jan Engelhardt
2006-03-26 10:11 ` Linda Walsh
2006-03-25 19:26 ` Adrian Bunk
2006-03-26 9:42 ` Linda Walsh
2006-03-26 19:29 ` Jim Crilly
2006-03-30 21:45 ` Linda Walsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44237D87.70300@tlinx.org \
--to=lkml@tlinx.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.