linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dr Andrew C Aitchison <A.C.Aitchison@dpmms.cam.ac.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Xpert]Re: User-level Tasks in Hotplug Scripts?
Date: Tue, 05 Feb 2002 08:47:11 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-101289943619520@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101272582331992@msgid-missing>

On Mon, 4 Feb 2002, David Brownell wrote:

> The "single user desktop" model is well known to be the one
> which is relatively straightforward to address -- and arguably hits
> the "95% of end users" case here.  So long as one can kick in a
> "no gui" mode for servers, and do something intelligent in the case
> of multi-gui systems, that's a good place to start.

Not quite sure what you mean by "multi-gui systems".

Supplying a solution for "single user desktop" and "no gui servers"
will satisfy *almost* everyone.
However installing "single user desktop" on a classroom full of 
workstations runs the risk of being insufficently secure.
Although it may be a minority market, screwing it up could be very
bad for everyones reputation.

Even having a "classroom workstation" option, could be dangerous
if it doesn't have the features of "single user desktop", since some 
people will install the full-featured version however much you warn them 
of the pitfalls.
Besides it is much harder to bolt on security ofterwards.

-- 
Dr. Andrew C. Aitchison		Computer Officer, DPMMS, Cambridge
A.C.Aitchison@dpmms.cam.ac.uk	http://www.dpmms.cam.ac.uk/~werdna


_______________________________________________
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-05  8:47 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
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 [this message]
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-101289943619520@msgid-missing \
    --to=a.c.aitchison@dpmms.cam.ac.uk \
    --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).