Revision 4 as of 2007-05-07 08:49:31

Clear message

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

  • Launchpad entry: ltsp-palm-devices

  • Packages affected: ltsp-client, ltsp-server, ltsp-localapps


Currently, thin clients in a business environment cannot use palm syncing, as there's no way to plumb a connection over the network. We need to install some extra bits in the LTSP chroot to make this happen.


Palm devices are still in use in the business world, and this is a feature that the LTSP developers desire to get working.

Use cases

  • Clay, a lawyer, walks up to his thin client, and logs in, he launches gnome-pilot, and connects to his palm, and syncs to his calendar within Evolution.
  • Julia wants to back up her palm. She plugs in her palm to the thin client, and starts KOrganizer. Things work as expected.


  • ltsp-build-chroot should also include pilot-link

  • pilot-link needs promotion to main.

Design and Implementation

  • Install pilot-link

  • the ltsp-client-setup needs a section like:

if [ ${LTSP_PALMPILOT} == "true" ]; then
    pilot-nredir -n -p /dev/pilot
  • User will need to set up their palm application to point to their thin client.

Unresolved issues

  • It would be nice to automatically set the $PALMPORT environment variable on the client to point to what LTSP client they're on. For a first cut, the user can manually configure, and we'll sort out auto configure next cut.

Future Plans

  • Auto background sync with Evolution when the "palm sync" button is pressed, without the need for user interaction?