linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: linux-hotplug@vger.kernel.org
Subject: I don't want much...
Date: Sat, 24 Jul 2004 21:34:35 +0000	[thread overview]
Message-ID: <4102D5EB.1000901@dgreaves.com> (raw)

Hi

This overview page:
  http://linux-hotplug.sourceforge.net/?selected=overview
Says that a "Starting an application" is a reasonable thing to want to do.

I just want to run a script.
A simple script.
That's it.
Why on earth is it so hard?

Hmm, maybe not the best tone to start with - but isn't hotplugging about 
making the user's life easier?
It's cool that it automatically loads my modules.
Now all I have to do is start a shell and type: mount -t vfat -o 
uidÚvid,gid=greaves,sync /dev/sda1 /mnt/lexar
Not exactly plug-and-play is it?

When I plug in my Lexar Jumpshot I want to mount the drive and rsync my 
piccies.
What happens?
I get a usb event
then a scsi-host event
then a scsi event
then a block event
and another block event
then a scsi-device event

Fine.
So I add a usermap tied to the usb vendor/product id (the 'right' place) 
and create a dummy module called lexar.script with a control script.
It runs - good.
At the wring time (ie before the scsi devices are registered) - bad.

Do I really have to hack into the generic scsi-device agent?


David



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id\x10040&op=click
_______________________________________________
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:[~2004-07-24 21:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-24 21:34 David Greaves [this message]
2004-07-24 21:59 ` I don't want much Olivier Mehani

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=4102D5EB.1000901@dgreaves.com \
    --to=david@dgreaves.com \
    --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).