From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Xpert]Re: User-level Tasks in Hotplug Scripts?
Date: Tue, 05 Feb 2002 01:54:19 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-101287421930005@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101272582331992@msgid-missing>
> >>Jim, if the user is logged in so is the rest of the user interface. Why
> >>not have a monitoring program (like console) that watches the hotplug
> >>events and invokes corresponding configuration program ?
Actually one of the goals of the hotplug framework is to avoid
requirements to have Yet Another Monitoring Daemon hanging
around wasting resources ... likewise, to avoid needing to start the
apropriate magic program before plugging in devices.
> >>This would also
> >>allow for various user environments to customize configuration tools to
> >>match their look.
... of course, if the events could get fed into some existing daemon
(via authenticared RPC, SSH-secured channel, or whatever) that
kind of appearance-agnostic behavior becomes simpler! The issue
then becomes how hotplug identifes and accesses the channel, and
who will modify what existing daemons. :)
> > That solution is not in itself sufficient. You might not want everybody
> > to see all hotplug events.
>
> And what would the problem be with using an event distribution mechanism
> that would require the listener to have certain privileges?
Another of the goals classic end-user "usability". Remember that
the original problem was how to fire up an unprivileged tool ... not
all hotplug events imply any need for privilege. Users initiate hotplug
events with just physical access privileges. When the device software
has already been set up, additional privilege shouldn't be needed.
- Dave
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2002-02-05 1:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-03 8:43 [Xpert]Re: User-level Tasks in Hotplug Scripts? Dr Andrew C Aitchison
2002-02-03 17:43 ` Owen Taylor
2002-02-03 19:06 ` Jim Gettys
2002-02-03 19:59 ` Christer Palm
2002-02-03 20:46 ` David Brownell
2002-02-03 21:13 ` David Brownell
2002-02-03 23:49 ` Christer Palm
2002-02-04 5:57 ` Owen Taylor
2002-02-04 15:15 ` Vladimir Dergachev
2002-02-04 23:17 ` Oliver Neukum
2002-02-05 1:22 ` Christer Palm
2002-02-05 1:54 ` David Brownell [this message]
2002-02-05 2:14 ` Christer Palm
2002-02-05 2:41 ` David Brownell
2002-02-05 4:49 ` Vladimir Dergachev
2002-02-05 7:53 ` Oliver Neukum
2002-02-05 8:47 ` Dr Andrew C Aitchison
2002-02-05 8:56 ` Oliver Neukum
2002-02-05 11:21 ` Christer Palm
2002-02-05 11:35 ` Oliver.Neukum
2002-02-05 15:19 ` Jim Gettys
2002-02-05 18:37 ` Jim Carter
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=marc-linux-hotplug-101287421930005@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).