[ale] Sync a Palm Tungsten T5 with Linux

[Nathan J. Underwood]

Jason,

   Thank you for your response!!  I created the rule, and gave it a try, 
but didn't get the expected response when I typed the pilot-xfer command 
(I tried it as me, and then tried it as root, with the same results [see 
below]).

[nathan at l64-wks ~]$ pilot-xfer -p /dev/pilot -l
  Unable to bind to port: /dev/pilot
  Please use --help for more information
[nathan at l64-wks ~]$

I'm running FC4 i386_64 on an AMD64 3000+, kernel version 2.6.11-1.  
I've been kindof anal about only installing RPM's available via yum on 
the box (i.e. no installed from source anything, no dorked up libraries, 
etc.).  In short, it's a pretty boring, vanilla install.  The only other 
USB device is a USB Intellimouse Explorer 3.0a.

Nathan J. Underwood
President
Cyber Tech Cafe', LLC <><
269 Market Place Blvd
#258
Cartersville, GA  30121
678.792.7785(o)
877.534.8188(toll free)
770.386.9256(f)
http://www.cybertechcafe.net
Your Complete Technology Resource
nathan.underwood at cybertechcafe.net
Proverbs 16:11



Jason Day wrote:

>On Sat, Sep 17, 2005 at 02:12:45PM -0400, Nathan J. Underwood wrote:
>[snip]
>  
>
>>Has anyone had any luck with one of these neat but expensive (and 
>>seemingly useless, if you use Linux) PDA's?
>>    
>>
>
>I don't have a T5, but I've been syncing USB palm devices with linux for
>years.  I use J-Pilot, but all the PIMs (evolution, kontact, etc) are
>going to use pilot-link for the low-level communications with the palm
>device.
>
>What distro are you using?  Modern distros use udev to manage the
>devices in /dev.  The USB device files are created when you start the
>hotsync, and disappear again when the hotsync completes.  This is just
>the way USB works; you just need to configure the permissions on the
>device files.  Assuming you are using udev, you can configure your
>device files by creating a file named 10-visor.rules in
>/etc/udev/rules.d and put the following in it:
>
>BUS="usb", SYSFS{product}="Palm Handheld*", KERNEL="ttyUSB[13579]",
>NAME="tts/USB%n", SYMLINK="pilot", GROUP="usb", MODE="0666"
>
>That should all be on one line; it tells udev to create the ttyUSB?
>device files with permissions 0666, and creates a symlink from
>/dev/pilot to the correct ttyUSB file (the device file could change if
>you plug in or remove another USB device, like a scanner, digital
>camera, etc).
>
>After you create this file, execute /sbin/udevstart as root.  Make sure
>you don't have any sync daemons like kpilotd, gpilotd, or others running
>(ps aux | grep pilot).  Then tail /var/log/messages, connect your palm,
>and start the hotsync.  Wait for the device files to appear in the log,
>then execute "pilot-xfer -p /dev/pilot -l" in a terminal.  That command
>will just list the programs and databases installed on your palm, but it
>will let you know whether you can communicate with the palm or not.
>Once that is working, you can move on to evolution or your pim of
>choice.
>  
>