| 1 |
On Tue, 10 Dec 2002 13:50:19 -0500 |
| 2 |
Bob Thomas <gtg663h@×××××××××××.edu> wrote: |
| 3 |
|
| 4 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 5 |
> Hash: SHA1 |
| 6 |
> |
| 7 |
> Alan wrote: |
| 8 |
> | On Tue, Dec 10, 2002 at 10:45:24AM -0800, Alan wrote: |
| 9 |
> | |
| 10 |
> |>An addition to this would be how to set up a non-usb pilot for the nifty |
| 11 |
> |>automated devfsd EXECUTE tricks. I realize that this would be very |
| 12 |
> |>similiar of course :) Also, a note on the right way to restart devfsd |
| 13 |
> |>would be nice. I tried to kill -HUP it, but no go, and there is no |
| 14 |
> |>init.d script. My devfsd.conf had the following added to try to execute |
| 15 |
> |>the jpilot sync for a palm V (already working with jpilot) on /dev/ttyS0 |
| 16 |
> |> |
| 17 |
> |>REGISTER ^tts PERMISSIONS 0.0 0777 |
| 18 |
> |>REGISTER ^tts/0 EXECUTE /bin/su alan -c |
| 19 |
> "/usr/bin/jpilot -sync" |
| 20 |
> |> |
| 21 |
> |>I'm not sure what I'm missing here, but having some simple things like |
| 22 |
> |>that in the docs would help the non-usb palm'ers like me :) |
| 23 |
> | |
| 24 |
> | |
| 25 |
> | Ok, my mistake, sent off the email a bit too soon :) But I do now have |
| 26 |
> | some more sensical comments :) It should be /usr/bin/jpilot-sync, not |
| 27 |
> | /usr/bin/jpilot -sync |
| 28 |
> | |
| 29 |
> | I'm also wondering if it is possible to have this sort of trickery for |
| 30 |
> | serial devices, as as soon as I run devfsd /dev (after killing it) it |
| 31 |
> | immediately starts the jpilot-sync program. I'm wondering if it is a |
| 32 |
> | USB feature that allows this to be controlled? |
| 33 |
> | |
| 34 |
> | Alan the sheepish |
| 35 |
> | |
| 36 |
> |
| 37 |
> Isn't a serial port always registered, though? The USB trick only works |
| 38 |
> because /dev/usb/tts/1 only appears when you hit the hotsync button on |
| 39 |
> your palm. |
| 40 |
> |
| 41 |
> [Alan: I forgot to CC to group] |
| 42 |
> |
| 43 |
> - -- |
| 44 |
> Robert Thomas |
| 45 |
> Georgia Institute of Technology |
| 46 |
> Email: gtg663h@×××××××××××.edu |
| 47 |
> -----BEGIN PGP SIGNATURE----- |
| 48 |
> Version: GnuPG v1.0.7 (GNU/Linux) |
| 49 |
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 50 |
> |
| 51 |
> iD8DBQE99jdrkRe6eFyQaRcRAqcPAJsHq7WZiLm2s3e3YesovSphQGl5CgCeN9VR |
| 52 |
> oL9I6Ow9sBft2+Yw9iBnvHA= |
| 53 |
> =ytWc |
| 54 |
> -----END PGP SIGNATURE----- |
| 55 |
> |
| 56 |
> |
| 57 |
> -- |
| 58 |
> gentoo-dev@g.o mailing list |
| 59 |
> |
| 60 |
I belive this is correct. There would have to be some sort of monitoring script that would monitor the serial device. Any dibs on writing it? |
| 61 |
|
| 62 |
//ZhEN |
| 63 |
|
| 64 |
-- |
| 65 |
John P. Davis |
| 66 |
Gentoo Linux Documentation Developer |
| 67 |
http://www.gentoo.org |
| 68 |
#gentoo-doc on irc.freenode.net |
Archives