### Multisync Opie/Zaurus Plugin Testing

#### 0. READ ME FIRST!

This is a beta release of the the Multisync Opie/Zaurus plugin (opie_sync). It may not work correctly, and it could mess up your data. Before testing opie_sync make backups of your PIM data on both sides of the sync pair (e.g. Evolution and the Opie device).

We appreciate your feedback in testing this release. To report bugs, please email the multisync users email list or email the developer directly. Please let us know what platform you are running opie_sync on (i.e. Linux distro and version, Opie/Zaurus version, Evolution version, etc.) and provide a precise set of instructions to reproduce the problem you are seeing. We also appreciate reports of things working well :-) Thanks!

opie_sync is known to work with Opie/OpenZaurus and the Sharp Zaurus 2.X ROM. The new Sharp 3.X ROM does not work with opie_sync because Sharp has totlly shanged the sync mechanisim. We are looking to see what it will take to sync with the 3.X ROM, but don't expect support for it any time soon.

#### 1. Download

opie_sync can now be found in the main multisync CVS tree. We are enouraging people to grab a CVS snapshot tarball and start testing before the 0.8 multisync release - see this page for details.

#### 2. Compiling

Before opie_sync can be compiled, you must have an up to date multisync compiled and installed.

The opie_sync plugin requires serveral libraries on top of those required by multisync:

- curl
- expat
- openssl

If you are using RedHat, both the main package and the devel package for each of these libraries must be installed.

The opie_sync plugin has been succesfully compiled on RedHat 7.3, RedHat 9, Mandrake 9 and Gentoo. If you compile on another distro or have problems with another distro let us know. The only known problem is that the version of libcurl shipped with RedHat 7.2 will not work with opie_sync.

To compile, extract the tarball, cd into the directory and run configure:

    ./configure --prefix=<dir> --enable-debug

The <dir> value for --prefix must be the same directory that you installed multisync in when you compiled it. The --enable-debug will turn on some debug options that will help us diagnose if you have problems. Next run make:

    make

If that completes successfully, run make install:

    make install

This may have to be run as root, depending on the write permissions of the directory you are installing to.

#### 3. Configuring

Start multisync and create a new sync pair. In the pick list for the remote side, select "Opie/Zaurus Multisync Plugin". Click on "Options...":
Device IP: Enter the IP address of your Opie/Zaurus device.
Device Type: Select Opie/OpenZaurus for an opie device, Zaurus if you are running the Sharp Zaurus ROM.
Username: Leave this as 'root' (AFAIK Opie always runs as root).
Password: Leave this as 'rootme' (changing the root password does not affect FTP).
Protocol: Select 'FTP' or 'SFTP'.
Port: Leave this as 4242 if you are running FTP, otherwise use 22 for SFTP.

Press "OK" when you are done, "OK" to create the sync pair and the first sync will be performed.

#### 4. Collecting Debug Information

Multisync and the opie_sync plugin will log to stdout when they are running. opie_sync also places a debug log file in ~/.multisync/<pair number>/opie_sync.log. If you have a problem, please include the relevant portions of both of these in the bug report.

#### 5. Bugs and Known Issues

Known Issues:

- SFTP sync only works when you use host keys.
- Newlines in contact info not preserved across a sync - this is actually a bug with the Opie PIM apps.
- The Gnome2 build could use some cleaning up.

$Id: testing.html,v 1.2 2003/07/19 20:26:15 irix Exp $