linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Cuyle Fritzinger <scottf@med.unr.edu>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug ownership/permissions
Date: Mon, 03 Dec 2001 23:28:45 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-100742220805155@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100741069725050@msgid-missing>


On Mon, 3 Dec 2001, Ken Hahn wrote:

> 1. The reaction is not serialized as the notificaiton method changes this
> around.

so hotplug needs to selectively choose which script to run based on user
input.

> 2. In the case of a distro where lots of cd-player, or camera-software come
> for free, users could have multiple things launching on an event, instead of
> just one.

then what needs to happen is the user needs to select from a list of
applications which one to launch for a given device, which can be saved in
~/.hotplug or something similar.

how is the user prompted to choose which script? blech. doesn't seem like
hotplug should have knowledge of the desktop itself... perhaps a
/etc/hotplug/usb.delegators/ directory that contains scripts/programs that
will present the user with a list of possible scripts to run, and the user
can specify one or more.. the choices are stored in ~/.hotplug. the
desktops can place the script/programs in /etc/hotplug/usb.delegators/ so
that if there is more than 1 match in usb.maps/, it can run a delegator.
which delegator though? run them all? :P

this is getting nasty.

> Perhaps hogging the device is not a bad idea?

this is tending to lean towards to user preference rather than letting
hotplug delegate which scripts to run.

i can play around and see what works best here and then write back with
results... i'm just trying a bunch of different things to see what works
best for me for now... :P

-=Scott


_______________________________________________
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

  reply	other threads:[~2001-12-03 23:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 20:07 hotplug ownership/permissions Scott Cuyle Fritzinger
2001-12-03 23:28 ` Scott Cuyle Fritzinger [this message]
2001-12-04  0:05 ` David Brownell
2001-12-04  7:33 ` Tim Waugh
2001-12-04 17:51 ` Scott Cuyle Fritzinger
2001-12-04 22:46 ` David Brownell
2001-12-04 22:59 ` Scott Cuyle Fritzinger

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-100742220805155@msgid-missing \
    --to=scottf@med.unr.edu \
    --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).