There are a few things you have to remember when trying to keep your pilot synchronised with your Linux workstation. Most of these caveats are due to general Gnome 2.2 shittiness. My opinion that many open source programmers should rather go back to school has just been enforced by this opinion. :)
Testing kernel setup with pilot-xfer
Make sure your kernel has full support for usb and that you’ve built usbserial and visor modules as well. Make sure the visor module is installed. Connect your visor with the supplied mini-usb cable, switch it on and tap the sync thingy (that little star in the corner). Now type the following:
pilot-xfer -p usb:/dev/ttyUSB1 --list
You should see a list of all the databases on your palm. If you’ve gotten this far, you’ve done well! Make sure you have the latest pilot-link package.
Backing up with pilot-xfer
If you now try a backup with:
pilot-xfer -p usb:/dev/ttyUSB1 -s /home/yourname/your/backupdir/
You’ll see your USB stack crash reproducibly when synching ImgFile-Foto or Jpeg-Foto. It will do this with uhci and usb-uhci. This is frustrating.
To get around this, create a file called something like “excludeList” and add the following lines:
Now try your backup with:
pilot-xfer -p usb:/dev/ttyUSB1 -e /path/to/excludeList -s /home/yourname/your/backupdir/
Evolution and gnome-pilot
Now that we have a backup going, step 2 is synching with evolution via gnome-pilot. What a stinking piece of software. Note that, if you don’t have /proc/bus/usb mounted, gpilotd will crash inexplicably (and without any kind of meanigful hint as to why) every time you try to configure it to use /dev/ttyUSB1 as a usb port. Go GNOME! Idiots. Moral of the story: make sure your /proc/bus/usb/ is mounted.
Configure your gpilotd (via the capplet) to use /dev/ttyUSB1 (or whatever the devfs equivalent is) and make sure that the type is set to “USB”. Synching should now work in evolution, unless you’ve been so stupid as to expect the backup conduit to work! Those databases that we’ve excluded above are screwing us over again…
Now it seems that gpilotd can be configured to exclude certain databases as well, but this option is nowhere to be found in the GUI. Probably part of Gnome’s policy of making the best GUI for stupid idiots, i.e. so simple as to be useless. If you go scratching in $HOME/.gnome2/gnome-pilot.d/backup-conduit, you’ll notice an “exclude_files” option. Mostly due to the glaring lack of documentation, I was unable to modify this option and get gpilotd to heed my changes. “ImgFile-Foto,Jpeg-Foto” for instance does not work.
So, bye-bye backup conduit. I never liked you anyway.
Currently I sync my Calendar, Tasks and Contacts with evolution. For backups, I use my own leet Palm rotating backup Python script. Feel free to abuse it!