From: Linda Walsh <lkml@tlinx.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Security downgrade? CONFIG_HOTPLUG required in 2.6.16?
Date: Sun, 26 Mar 2006 01:42:36 -0800 [thread overview]
Message-ID: <4426620C.2040707@tlinx.org> (raw)
In-Reply-To: <20060325192635.GQ4053@stusta.de>
Adrian Bunk wrote:
> - hotplugging devices != module loading
> - CONFIG_HOTPLUG does not load any code into the kernel.
> - hotplugging devices can work without any userspace support
>
> As an example, hotplugging an USB hard disk works fine with
> CONFIG_MODULES=n and without any userspace support (assuming
> a static /dev).
>
---
Ah, I see. But if I have no USB hard disk to plug in?
Should I still be compiling in HOTPLUG? Seems a waste.
Thanks for the example though...
-linda
next prev parent reply other threads:[~2006-03-26 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 5:03 Security downgrade? CONFIG_HOTPLUG required in 2.6.16? Linda Walsh
2006-03-25 18:54 ` Jan Engelhardt
2006-03-26 10:11 ` Linda Walsh
2006-03-25 19:26 ` Adrian Bunk
2006-03-26 9:42 ` Linda Walsh [this message]
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=4426620C.2040707@tlinx.org \
--to=lkml@tlinx.org \
--cc=bunk@stusta.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox