author | zautrix <zautrix> | 2004-10-08 22:22:02 (UTC) |
---|---|---|
committer | zautrix <zautrix> | 2004-10-08 22:22:02 (UTC) |
commit | 44169895703beb3e8b1551a313d2d341bf742905 (patch) (unidiff) | |
tree | 4e337f9b55d544a939185dbcdbad558b1ed2504d /bin/kdepim | |
parent | 10a0e05cc4962d9412a7a5faf3d69a3caf6d1c34 (diff) | |
download | kdepimpi-44169895703beb3e8b1551a313d2d341bf742905.zip kdepimpi-44169895703beb3e8b1551a313d2d341bf742905.tar.gz kdepimpi-44169895703beb3e8b1551a313d2d341bf742905.tar.bz2 |
gammu changes
-rw-r--r-- | bin/kdepim/korganizer/howtoSYNC.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bin/kdepim/korganizer/howtoSYNC.txt b/bin/kdepim/korganizer/howtoSYNC.txt index c4e80f5..3cab446 100644 --- a/bin/kdepim/korganizer/howtoSYNC.txt +++ b/bin/kdepim/korganizer/howtoSYNC.txt | |||
@@ -299,25 +299,25 @@ b) Pi-Sync (direct Kx/Pi to Kx/Pi sync) | |||
299 | 299 | ||
300 | c) Remote file | 300 | c) Remote file |
301 | Syncing with the profile kind "Remote file" is performed in three steps: | 301 | Syncing with the profile kind "Remote file" is performed in three steps: |
302 | i) download the remote file to your local machine to a temp file | 302 | i) download the remote file to your local machine to a temp file |
303 | ii) sync with this temp file | 303 | ii) sync with this temp file |
304 | iii) upload the synced file to the remote device | 304 | iii) upload the synced file to the remote device |
305 | 305 | ||
306 | The down-/uploading if i) and iii) is done via a command line command. | 306 | The down-/uploading if i) and iii) is done via a command line command. |
307 | Please specify the download/upload command ( like scp, ftp, ...) and the | 307 | Please specify the download/upload command ( like scp, ftp, ...) and the |
308 | file name of the temp file in the corresponding fields. | 308 | file name of the temp file in the corresponding fields. |
309 | 309 | ||
310 | d) Mobile device (cell phone) | 310 | d) Mobile device (cell phone) |
311 | Note: On the Zaurus you have to install the kammu_xxx_arm.ipk package | 311 | Note: On the Zaurus you have to install the phoneaccess_xxx_arm.ipk package |
312 | to be able to access mobile phones. | 312 | to be able to access mobile phones. |
313 | We mention here only KO/Pi, but the same is valid for KA/Pi. | 313 | We mention here only KO/Pi, but the same is valid for KA/Pi. |
314 | Note: | 314 | Note: |
315 | It is only possible to sync a mobile phone with one particular device | 315 | It is only possible to sync a mobile phone with one particular device |
316 | running KO/Pi. If you want to be able to write data of more than one device | 316 | running KO/Pi. If you want to be able to write data of more than one device |
317 | to the mobile phone (e.g. from your Zaurus and from your Windows Laptop) | 317 | to the mobile phone (e.g. from your Zaurus and from your Windows Laptop) |
318 | do not sync with the mobile phone at all, but use the | 318 | do not sync with the mobile phone at all, but use the |
319 | "Export to phone" functionality from the different devices. | 319 | "Export to phone" functionality from the different devices. |
320 | Using "Export to phone" makes it not possible to get back data from the | 320 | Using "Export to phone" makes it not possible to get back data from the |
321 | phone, if it was changed there, of course. | 321 | phone, if it was changed there, of course. |
322 | If you sync with the phone, do not use "Export to phone" from any device. | 322 | If you sync with the phone, do not use "Export to phone" from any device. |
323 | (And do not sync, as mentioned above, from any other device with that phone). | 323 | (And do not sync, as mentioned above, from any other device with that phone). |