linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Xpert]Re: User-level Tasks in Hotplug Scripts?
Date: Sun, 03 Feb 2002 21:13:05 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-101277088528956@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101272582331992@msgid-missing>

"> "        =  "Christer Palm" <palm@nogui.se>
"> > "     ="Jim Gettys" <jg@pa.dec.com>

> > We need a secure, interoperable way for configuration scripts running
> > as root to pop up configuration GUI's on user's servers, and we need it soon
> > (yesterday), as hot-plug is now a reality on Linux systems....
> 
> Is this really what "we" need?

Yes, with flexibility.  Essentially every Linux box out there that's
serving as a single-user workstation would benefit from this.
It's a fairly basic usability issue for non-expert end-users.  We
aren't dealing with hardware of ten years ago, where dynamic
reconfiguration was only for extremely high end systems.

And if you look at this as an issue for larger systems, it's clear
that "hot" reconfiguration is critical for preserving uptime; just
think of hotplug events as configuration management alerts.
Though in that case a lot more intelligence needs to go into
choosing whether (and where) to present any GUI, as noted
in your questions.


> Having stuff "pop up" when certain event occur is probably very nice in 
> many situations, but there are good reasons to why this kind of stuff 
> only happens in the windoze world.

And Macintosh ... basically, that single-user workstation model,
which defines the "mass market".  There are a lot of folk who
are working to make sure the Linux community doesn't repeat
the mistakes of the UNIX (hardware) vendor community, so that
Linux {desk,lap,palm,...}top solutions remain economically viable.

- 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

  parent reply	other threads:[~2002-02-03 21:13 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 [this message]
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
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-101277088528956@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).