Re: [Xpert]Re: User-level Tasks in Hotplug Scripts?

[Jim Carter <jimc@math.ucla.edu>]

Hmm, I seem to see a little different side of this issue.  In PCMCIA
hotplug, the user sticks in the card, and it says "beep-beep" if it loads
the driver and runs the init script, or "beep-blecch" otherwise.  That's
the extent of the GUI.  I think we should be starting from that end, not
the specific beeps, but with the idea of a very simple interface with
minimal user involvement.

When the card doesn't load, the person does "su root" (if privileged) and
starts mucking around with the card database, and even recompiling drivers
to add the PCI ID of the "you get what you pay for" rebrand card he (I)
bought. I'm not saying that some GUI help for the sysop is bad, but it's
going to be able to cover only limited and routine operations. I think the
main focus for the current discussion started out as a user-level issue,
starting a special init script that downloaded and displayed some photos,
not assistance for the sysop.

So one of our students in the lab plugs in his Rio or iPod into USB to copy
some songs to it.  If we have the drivers set up, fine, it works, no GUI
needed.  If we don't, you can be sure that we aren't going to offer him a
GUI so he can download nekulturny lyrics (that he probably didn't pay for)
in *our* lab.

James F. Carter          Voice 310 825 2897    FAX 310 206 6673
UCLA-Mathnet;  6115 MSA; 405 Hilgard Ave.; Los Angeles, CA, USA  90095-1555
Email: jimc@math.ucla.edu    http://www.math.ucla.edu/~jimc (q.v. for PGP key)


_______________________________________________
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