View Single Post
Old 08-13-2010, 03:25 PM   #399
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
I'd probably go with something simpler, like the thing attached (with the proper handling of starting/stopping the watchdog in a script launched at the proper runlevels, like the fonts/ss).

But that's still only triggered on usbPlugOut, so that's not very useful IMHO. We can always watch for another event, but I don't think we'd find something really more practical than typing the private command in the search box. Plus we'd have to always use a script to launch/stop the watchdog at the proper runlevels, which we don't really need without this.

(Regarding the event in itself, if the Kindle kernel supports inotify, we could use incron/whip up a simple C inotify watchdog, but that's a bit overkill ).

If you really, really can't stomach using the private command, I'd suggest using the hotkey hack posted a few weeks ago .
Attached Files
File Type: txt usbnet-wd.patch.txt (2.5 KB, 492 views)

Last edited by NiLuJe; 08-13-2010 at 10:00 PM.
NiLuJe is offline   Reply With Quote