summaryrefslogtreecommitdiffabout
Unidiff
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/MultiSyncHowTo.txt294
-rw-r--r--bin/kdepim/Zaurus-KDE_syncHowTo.txt8
2 files changed, 297 insertions, 5 deletions
diff --git a/bin/kdepim/MultiSyncHowTo.txt b/bin/kdepim/MultiSyncHowTo.txt
new file mode 100644
index 0000000..25e5be8
--- a/dev/null
+++ b/bin/kdepim/MultiSyncHowTo.txt
@@ -0,0 +1,294 @@
1
2HAS TO BE WRITTEN
3
4Sync HowTo Zaurus <-> KDE
5
6
7This is a
8Sync HowTo Zaurus <-> K-Desktop Environment(KDE)
9using the KDE-Pim/Pi applications
10KAddressbook/Pi (KA/Pi) and KOrganizer/Pi (KO/Pi)
11on the Zaurus (Z).
12
13You can now easily sync your Z with the
14PIM data of the KDE.
15(addressbook and calendar data).
16You need to install the desktop versions
17of KA/Pi+KO/Pi on the desktop.
18You need KDE version 3.3.0 or higher on your desktop.
19You need KA/Pi+KO/Pi version 1.9.11 or higher on the desktop
20and on the Z.
21
22NOTE: Almost the same procedure will make it possible to
23sync KA/Pi+KO/Pi running on Windows with KDE via network.
24
25The setup+sync procedure is:
26
270) How the syncing works
281) Installing KA/Pi+KO/Pi on the Z
292) Installing desktop version of KA/Pi+KO/Pi on the desktop
303) Connection your Z to the desktop via network
31 (network connection can be set up via USB cable or (W)Lan
324) Configuring KA/Pi+KO/Pi on Z for Sync
335) Enable remote sync in KA/Pi+KO/Pi on the desktop
346) Sync
35
36*****************************************************
370) How the syncing works
38*****************************************************
39
40After setting up everything, the following actions will
41be performed when syncing:
42User enables "remote pi-sync" on desktop.
43User chooses "sync with configured desktop profile" on the Z.
44Z sends sync request via network to configured IP/port/password.
45KO/Pi on desktop detects sync request and syncs with KDE (configurable!).
46A window pops up, that KO/Pi on desktop is in "remote syncing mode".
47If a conflict occurs when syncing KO/PI<->KDE on the desktop,
48automatically the newest entry is choosen.
49(To avoid the need of user interaction)
50KO/Pi on desktop sends synced file to Zaurus.
51KO/Pi on desktop is in "waiting mode" to get synced file back.
52Zaurus is syncing it's own calendar with the received file.
53Here can be some user interaction needed, i.e.
54if the sync profile is configured as
55"ask for every entry on conflict" and a conflict occurs.
56Zaurus sends back synced file to desktop.
57Syncing on Zaurus is complete now.
58KO/Pi on desktop gets back synced file.
59KO/Pi on desktop removes all entries in its own calendar and
60reloads the synced file.
61KO/Pi on desktop syncs with KDE.
62After syncing with KDE is finished, KO/Pi closes
63the "remote syncing mode" window and displays
64a "syncing complete" message in the headline.
65
66The actual syncing KO/Pi on desktop <-> KDE is
67performed by a small command line tool "kdecaldump",
68which writes/reads the complete KDE calendar resources to
69a file/from a file.
70KO/Pi tags changed entries such that an unchanged entry
71is not changed in KDE by kdecaldump. That is important for
72calendar entries in KDE, stored in a "disconnected IMAP" calendar resource.
73
74
75Same way is KA/Pi working.
76
77
78*****************************************************
791) Installing KA/Pi+KO/Pi on the Z
80*****************************************************
81
82Download latest version of KA/Pi+KO/Pi from
83http://sourceforge.net/projects/kdepimpi/
84Project KDE/Pim.
85Direct link is:
86http://sourceforge.net/project/showfiles.php?group_id=104103&package_id=112604
87Click on the version number to read the release notes/change log.
88Choose there the right precompiled package for your Z:
89For Sharp ROM
90-File: kdepim_1.x.xx_for_SharpROM.ipk.zip
91For Open Zaurus ROM:
92-File: kdepim_1.x.xx_for_OZ-gcc3xx.ipk.zip
93If unsure, choose:
94-File: kdepim_1.x.xx_for_SharpROM.ipk.zip
95
96Unzip the file and install the packages as usual on your Z.
97In order to intstall KA/Pi+KO/Pi on your Z,
98you need to install the following files:
99kmicrokdelibs_1.x.xx_arm.ipk
100kaddressbook_1.x.xx_arm.ipk
101korganizer_1.x.xx_arm.ipk
102
103*****************************************************
1042) Installing desktop version of KA/Pi+KO/Pi on the desktop
105*****************************************************
106
107Precompiled packages are available for SuSE 9.1.
108Choose on the above download location:
109File: KDE-Pim-Pi-1.9.11-SuSE9.1.i586.rpm
110Download file and install it on console with
111su
112rpm -ihv KDE-Pim-Pi-1.9.11-SuSE9.1.i586.rpm
113(NOTE:update with rpm -Uhv KDE-Pim-Pi-1.9.11-SuSE9.1.i586.rpm)
114NOTE for users of SuSE 9.1:
115You need KDE version 3.3.0 or higher on your desktop.
116Plese make an online update in SuSE (YAST), then update
117your KDE to version 3.3.0 or higher.
118You can find links to updated precompiled versions of KDE
119for SuSE 9.1 on the SusE web site,
120a direct link is for example:
121ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.1
122HOWTO UPDATE KDE:
123Download there the packages in "base".
124And the needed package for your language in "internationalization".
125Put all downloaded files in one "installation" directory.
126Open console and go to the downloaded "installation" directory.
127Do there a
128su
129and then perform a test for the update:
130rpm -Uhv --test *.rpm
131
132If no dependencies are shown, you can do the actual update with
133rpm -Uhv *.rpm
134
135If there are missing dependencies, you can resolve them by
136- download the needed updated KDE package from the
137 "applications" or from the "development" folder on the server.
138- adding a needed rpm package from the SuSE install DVD
139- remove the package that has dependencies from your "installation" directory.
140
141Do the
142rpm -Uhv --test *.rpm
143until you get no dependencies and no errors, then do a
144rpm -Uhv *.rpm
145Run
146SuSEconfig
147after installing with rpm is finished.
148Restart KDE.
149
150*****************************************************
1513) Connection your Z to the desktop via network
152 (network connection can be set up via USB cable or (W)Lan
153*****************************************************
154
155a) Connection via network cable/(W)Lan cards
156 Connect your desktop to the network.
157 Set up networking on the Z.
158 Make sure, you can ping the desktop from Z.
159b) Connection via USB cable:(is working for Z 7x0 and Z5500)
160 (i) Open console on desktop and type
161 su
162 tail -f /var/log/messages
163 (ii) Connect your Z with the USB cable to your desktop
164 You should get as output in the above console
165 something like this:
166 ("BUG" is the name of the desktop computer!)
167 Oct 26 12:49:37 BUG kernel: usb 2-2: new full speed USB device using address 2
168 Oct 26 12:49:37 BUG kernel: usb 2-2: Product: SL-C860
169 Oct 26 12:49:37 BUG kernel: usb 2-2: Manufacturer: Sharp
170 Oct 26 12:49:37 BUG /etc/hotplug/usb.agent[22659]: need a device for this command
171 Oct 26 12:49:43 BUG kernel: usb0: register usbnet at usb-0000:00:1d.0-2, Sharp Zaurus, PXA-2xx based
172 Oct 26 12:49:43 BUG kernel: usbcore: registered new driver usbnet
173 You see in the 5. line ("BUG kernel: usb0: register"), that usb device usb0 is used.
174 (iii) Create a network startup entry in /etc/sysconfig/network
175 Depending of the number X of the used usb device, create a file
176 /etc/sysconfig/network/ifcfg-usbX
177 (in our case /etc/sysconfig/network/ifcfg-usb0 )
178 with the following content:
179 # usbX config for Zaurus
180 IPADDR='192.168.129.200'
181 NETMASK='255.255.255.0'
182 NETWORK='192.168.129.0'
183 BROADCAST='192.168.129.255'
184 STARTMODE='hotplug'
185 (iv) Disconnect the Z and connect the Z again to the desktop.
186 Now you should be able to ping the Z from the desktop, try in console on desktop:
187 ping 192.168.129.201
188 Now you should be able to ping the desktop from the Z, try in console on Z:
189 ping 192.168.129.200
190
191 Now you will get a network connection automatically,
192 if you connect your Z to the desktop via the USB cable.
193
194
195In the following, we assume, that
196the desktop has the IP address: 192.168.129.200
197and that
198the Z has the IP address: 192.168.129.201
199
200*****************************************************
2014) Configuring KA/Pi+KO/Pi on Z for Sync
202*****************************************************
203
204Start KO/Pi on the Z.
205Choose Menu: Synchronize - Configure
206Fill in name for "Local device name:", e.g. "Z760"
207Click on "New profile"
208Set name of "Profile:", e.g. "BUG".
209(that is the above name of the desktop computer)
210Choose "Profile kind": Pi-Sync.
211Set "Password for remote access", e.g. "xyz" for
212Calendar and Addressbook.
213Set Remote IP address to 192.168.129.200 for
214Calendar and Addressbook.
215(Note: That is the IP address of the desktop!).
216The "Remote port number" is 9197/9198 for
217Calendar and Addressbook.
218You do not have to change the
219"Remote port number" or any other settings.
220Click "OK" button to save your settings.
221
222Now you have configured KA/Pi+KO/Pi sync on the Z,
223no need to configure anything in KA/Pi.
224
225
226*****************************************************
2275) Enable remote sync in KA/Pi+KO/Pi on the desktop
228*****************************************************
229
230Start KO/Pi on the desktop.
231Do a "test" sync with KDE, choose menu:
232Synchronize - KDE_Desktop
233After syncing, you should have the same data in KDE
234and in KO/Pi.
235NOTE:
236The KO/Pi version 1.9.10 had the bug, that on the first
237sync with KDE, all data in KDE was deleted.
238DO NOT USE VERSION 1.9.10!
239
240The bevaviour on the first sync is
241(in versions >= 1.9.11)
242that no data is deleted, the data in KO/Pi and in
243KDE is merged into one calendar.
244
245When the first sync was ok, please choose menu:
246Synchronize - Enable Pi-sync
247Fill in the values for port ("9197" in our examle)
248and for the password ( "xyz" in our example)
249that you did configure on the Z for that computer.
250Enable "Automatically start at application start"
251and "Automatically sync with KDE-Desktop when receiving sync request"
252by checking the two boxes.
253Close KO/Pi.
254
255Configure / test KA/Pi on the desktop in the same way.
256Fill in the right value for the port (9198 in our examle)
257in KA/Pi!
258
259*****************************************************
2606) Sync
261*****************************************************
262
263After configuring everything as above, you have to do
264the following, if you want to sync your Zaurus with KDE:
265(It syncs will all resources in KDE, that are not "readonly").
266
267Start KO/Pi on the desktop.
268If Kontact or KOrganizer is running, save the calendar!
269Connect the Z with the USB cable to your desktop.
270(Or to the local network).
271Choose on the Z the menu:
272Syncronize - <your name for the desktop sync profile>
273( that was "BUG" in our example ).
274That's all.
275
276Do the same with KA/Pi.
277
278NOTE:
279If an appointment/addressee is created on the Z, it is added to the
280standard resource in KDE.
281
282If you have todos with subtodos in your calendar, you will get on
283every sync (after you restartet KOrganizer or Kontact in KDE)
284the message "xx items changed on local", where
285xx is greater or equal to the number of todos.
286That behaviour is caused by a bug in KDE.
287(In KDE, everytime a subtodo is loaded,
288it's "last modified" settings are set to the current time - ouch!)
289I hope I can fix this bug in KDE soon.
290
291
292
293
294
diff --git a/bin/kdepim/Zaurus-KDE_syncHowTo.txt b/bin/kdepim/Zaurus-KDE_syncHowTo.txt
index 5aad5da..6ceabdb 100644
--- a/bin/kdepim/Zaurus-KDE_syncHowTo.txt
+++ b/bin/kdepim/Zaurus-KDE_syncHowTo.txt
@@ -1,21 +1,19 @@
1 1
2Sync HowTo Zaurus <-> KDE 2Sync HowTo Zaurus <-> KDE
3 3
4NOTE:
5CURRENTLY ONLY SYNCING OF CALENDAR DATA IS SUPPORTED!
6 4
7This is a 5This is a
8Sync HowTo Zaurus <-> K-Desktop Environment(KDE) 6Sync HowTo Zaurus <-> K-Desktop Environment(KDE)
9using the KDE-Pim/Pi applications 7using the KDE-Pim/Pi applications
10KAddressbook/Pi (KA/Pi) and KOrganizer/Pi (KO/Pi) 8KAddressbook/Pi (KA/Pi) and KOrganizer/Pi (KO/Pi)
11on the Zaurus (Z). 9on the Zaurus (Z).
12 10
13You can now easily sync your Z with the 11You can now easily sync your Z with the
14PIM data of the KDE. 12PIM data of the KDE.
15(addressbook and calendar data). 13(addressbook and calendar data).
16You need to install the desktop versions 14You need to install the desktop versions
17of KA/Pi+KO/Pi on the desktop. 15of KA/Pi+KO/Pi on the desktop.
18You need KDE version 3.3.0 or higher on your desktop. 16You need KDE version 3.3.0 or higher on your desktop.
19You need KA/Pi+KO/Pi version 1.9.11 or higher on the desktop 17You need KA/Pi+KO/Pi version 1.9.11 or higher on the desktop
20and on the Z. 18and on the Z.
21 19
@@ -93,37 +91,37 @@ For Open Zaurus ROM:
93If unsure, choose: 91If unsure, choose:
94-File: kdepim_1.x.xx_for_SharpROM.ipk.zip 92-File: kdepim_1.x.xx_for_SharpROM.ipk.zip
95 93
96Unzip the file and install the packages as usual on your Z. 94Unzip the file and install the packages as usual on your Z.
97In order to intstall KA/Pi+KO/Pi on your Z, 95In order to intstall KA/Pi+KO/Pi on your Z,
98you need to install the following files: 96you need to install the following files:
99kmicrokdelibs_1.x.xx_arm.ipk 97kmicrokdelibs_1.x.xx_arm.ipk
100kaddressbook_1.x.xx_arm.ipk 98kaddressbook_1.x.xx_arm.ipk
101korganizer_1.x.xx_arm.ipk 99korganizer_1.x.xx_arm.ipk
102 100
103***************************************************** 101*****************************************************
1042) Installing desktop version of KA/Pi+KO/Pi on the desktop 1022) Installing desktop version of KA/Pi+KO/Pi on the desktop
105***************************************************** 103*****************************************************
106 104
107Precompiled packages are available for SuSE 9.1. 105Precompiled packages are available for SuSE 9.1.
108Choose on the above download location: 106Choose on the above download location:
109File: KDE-Pim-Pi-1.9.10-SuSE9.1.i586.rpm 107File: KDE-Pim-Pi-1.9.11-SuSE9.1.i586.rpm
110Download file and install it on console with 108Download file and install it on console with
111su 109su
112rpm -ihv KDE-Pim-Pi-1.9.10-SuSE9.1.i586.rpm 110rpm -ihv KDE-Pim-Pi-1.9.11-SuSE9.1.i586.rpm
113 111(NOTE:update with rpm -Uhv KDE-Pim-Pi-1.9.11-SuSE9.1.i586.rpm)
114NOTE for users of SuSE 9.1: 112NOTE for users of SuSE 9.1:
115You need KDE version 3.3.0 or higher on your desktop. 113You need KDE version 3.3.0 or higher on your desktop.
116Plese make an online update in SuSE (YAST), then update 114Plese make an online update in SuSE (YAST), then update
117your KDE to version 3.3.0 or higher. 115your KDE to version 3.3.0 or higher.
118You can find links to updated precompiled versions of KDE 116You can find links to updated precompiled versions of KDE
119for SuSE 9.1 on the SusE web site, 117for SuSE 9.1 on the SusE web site,
120a direct link is for example: 118a direct link is for example:
121ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.1 119ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.1
122HOWTO UPDATE KDE: 120HOWTO UPDATE KDE:
123Download there the packages in "base". 121Download there the packages in "base".
124And the needed package for your language in "internationalization". 122And the needed package for your language in "internationalization".
125Put all downloaded files in one "installation" directory. 123Put all downloaded files in one "installation" directory.
126Open console and go to the downloaded "installation" directory. 124Open console and go to the downloaded "installation" directory.
127Do there a 125Do there a
128su 126su
129and then perform a test for the update: 127and then perform a test for the update: