1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
|
<html>
<head>
<title>Multisync Opie/Zaurus Plugin Testing</title>
</head>
<body>
<div align="center">
<h3>Multisync Opie/Zaurus Plugin Testing</h3>
</div>
<h4>0. READ ME FIRST!</h4>
<p>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 <b>make backups of your PIM data</b>
on both sides of the sync pair (e.g. Evolution and the Opie device).</p>
<p>We appreciate your feedback in testing this release. To report bugs,
please email the <a href="http://lists.sourceforge.net/lists/listinfo/multisync-users">multisync
users email list</a> or email <a href="mailto:tom@foottit.com">the developer
directly</a>. 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!</p>
<p>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.</p>
<h4>1. Download</h4>
<p>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
<a href="http://multisync.sourceforge.net/compiling.shtml">this page</a> for details.
<h4>2. Compiling</h4>
<p>Before opie_sync can be compiled, you must have an <i>up to date</i> multisync compiled
and installed.</p>
<p>The opie_sync plugin requires serveral libraries on
top of those required by multisync:
<ul>
<li>curl</li>
<li>expat</li>
<li>openssl</li>
</ul>
If you are using RedHat, both the main package and the devel package
for each of these libraries must be installed.</p>
<p>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.</p>
<p>To compile, extract the tarball, cd into the directory and run configure:
<pre>./configure --prefix=<dir> --enable-debug</pre>
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:
<pre>make</pre>
If that completes successfully, run make install:
<pre>make install</pre>
This may have to be run as root, depending on the write permissions of the
directory you are installing to.</p>
<h4>3. Configuring</h4>
<p>Start multisync and create a new sync pair. In the pick list for the
remote side, select "Opie/Zaurus Multisync Plugin". Click on "Options...":
<br><br><img src="images/opie_sync_config.png" alt="opie_sync config screen"><br>
<br><b>Device IP:</b> Enter the IP address of your Opie/Zaurus device.
<br><b>Device Type:</b> Select Opie/OpenZaurus for an opie device, Zaurus if you
are running the Sharp Zaurus ROM.
<br><b>Username:</b> Leave this as 'root' (AFAIK Opie always runs as root).
<br><b>Password:</b> Leave this as 'rootme' (changing the root password does
not affect FTP).
<br><b>Protocol:</b> Select 'FTP' or 'SFTP'.
<br><b>Port:</b> Leave this as 4242 if you are running FTP, otherwise use 22 for SFTP.
</p>
<p>Press "OK" when you are done, "OK" to create the sync pair
and the first sync will be performed.</p>
<h4>4. Collecting Debug Information</h4>
<p>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.</p>
<h4>5. Bugs and Known Issues</h4>
<p><b>Known Issues:</b><br>
<ul>
<li>SFTP sync only works when you use host keys.</li>
<li>Newlines in contact info not preserved across a sync - this is actually a bug
with the Opie PIM apps.</li>
<li>The Gnome2 build could use some cleaning up.</li>
</ul>
</p>
<br><br><br>
<div align="center">
<i>$Id: testing.html,v 1.2 2003/07/19 20:26:15 irix Exp $</i>
</div>
</body>
</html>
|
