[Evolution] Re: Syncing Evolution

[Craig White]

oops - meant to send to list...

On Tue, 2005-02-08 at 17:25 -0500, Paul M. Bucalo wrote:

> My entry in /etc/udev/rules.d/50-udev.rules
> 
> KERNEL="ttyUSB[0-9]*",SYMLINK="pilot"
> BUS="usb", KERNEL="ttyUSB[0-9]*", NAME="usb/%k"
> 
> It may help for you to know that what you placed in your file wouldn't
work for me. How I came across the syntax above is by looking at the
entry for my Epson CX-5400, which was found, driven and worked from the
onset. 
> 
> This was the *only* syntax that worked for me.
> 
<snip>
> If you look both of my posts on this, together, you will come up with
all that I have done. From the time I started this project until I
finished it, I made no updates and didn't add any new programming.
> 
> Additionally, if I remove what I added to 'rules' file I will not sync
no matter what. I tried several combinations in syntax, including yours,
and nothing would work but the way I have it. 
> 
> Thanks for the bit on the 'rules' file. You will definitely save me a
lot of head banging that would have happened the first time that file
got overwritten. :0)
----
I wouldn't have expected what I had in 10-udev.rules to work for you.
That is the point of making extra entries into udev.rules - to add
devices that weren't known when the devicelist was made.

I found this info to be quite useful for udev and creating entries for
'unknown' hardware.

http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimerMisc.html

It enabled me to simply identify my Kyocera 7135 and point it
to /dev/pilot and it obviously works because J-Pilot and pilot-xfer
programs find it quite easily. gpilotd however - even when told to
connect to /dev/pilot remains deaf. That is my point. 

I was hoping that the evolution experts could understand what was going
on and tell me how to troubleshoot it but I am gathering that the gpilot
stuff in evolution is external - except for the conduits and the fact
that gpilot isn't connecting is beyond the evolution application itself.