> > Shell scripts execution shouldn't be the only action
> > that can be taken, though it's likely time to start
> > agreeing on how and when to invoke scripts.
> >
> > I'm thinking we need design answers like:
> >
> > - Do we invoke /etc/usb/*.policy scripts? (Sure.)
> >
> > - ...
>
> Each device needs different information. I think only the device name
> and plug/unplug should be passed and let the script/program determine
> the rest of what it needs.
As a data point, PCMCIA passes quite a bit more info
than that ... and I think it's right to make it so
that most scripts won't need to reparse descriptors.
> > That seems like it'd be enough to start with.
>
> Hmm, it's good to see people finally looking into the
> problems I brought up a couple of weeks ago.
Hey, I saved that mail! It's in my now-dead Netscape
mailbox; sigh.
> Take a look at my userspace driver binding email and
> you'll see that it
> provides solutions for some of these questions.
There was a bit too much info there ... multiple kernel
patches, libraries and daemons, and so on.
Perhaps you could summarize in brief? (With change in
subject line, please!) It's really the work of just an
hour or so to come up with a daemon that can fork off
such scripts. No kernel patches beyond pre7-3 ... ;-)
- Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
