From: Brad Hards <bhards@bigpond.net.au>
To: Gregory Giguashvili <Gregoryg@ParadigmGeo.com>,
"Linux Kernel (E-mail)" <linux-kernel@vger.kernel.org>
Subject: Re: Multiple profiles
Date: Thu, 4 Jul 2002 23:28:24 +1000 [thread overview]
Message-ID: <200207042328.24263.bhards@bigpond.net.au> (raw)
In-Reply-To: <EE83E551E08D1D43AD52D50B9F511092E11411@ntserver2>
On Thu, 27 Jun 2002 23:19, Gregory Giguashvili wrote:
> One might think of external devices (tapes, scaners, disks, etc.) constanly
> being moved from machine to machine. I understand I can twist /etc/init.d/*
> to support all the configurations. However, I don't see a reason why it
> cannot be the responsibility of Linux kernel to "see" different hardware
> configurations on boot.
We can do this, for some device types. Not just for boot, but for hotplug type
devices as well. The kernel option is CONFIG_HOTPLUG, and it signals
userspace to describe what went on.
It is not appropriate for the kernel to decide what goes on (eg, if you attach
a USB scanner, whether you'd like to load the necessary kernel modules, start
up KDE and kooka, start a scan and save to /tmp/pr0n; or just ignore it for
now because the scanner is noisy, and you'll start it running overnight from
a cron job). So we make such policy decisions in userspace. This is normally
some shell script run as /sbin/hotplug (although you can change the script
name using a /proc interface). Sample scripts can be downloaded from
http://linux-hotplug.sf.net, which has lots more documentation on this.
Does this address your concern?
Brad
--
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.
next prev parent reply other threads:[~2002-07-04 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 13:19 Gregory Giguashvili
2002-07-04 13:28 ` Brad Hards [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-27 14:30 Gregory Giguashvili
2002-06-27 13:10 Jesse Pollard
2002-06-27 9:30 Gregory Giguashvili
2002-06-27 9:39 ` David Schwartz
2002-06-27 12:22 ` Oliver.Neukum
2002-06-27 18:53 ` David Schwartz
2002-06-27 19:19 ` Richard B. Johnson
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=200207042328.24263.bhards@bigpond.net.au \
--to=bhards@bigpond.net.au \
--cc=Gregoryg@ParadigmGeo.com \
--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
all inboxes | Powered by JetHome®