showing clcok skew in pisync

1 files changed, 5 insertions, 2 deletions

diff --git a/bin/kdepim/Zaurus-KDE_syncHowTo.txt b/bin/kdepim/Zaurus-KDE_syncHowTo.txt
index 6ceabdb..8186dd7 100644
--- a/bin/kdepim/Zaurus-KDE_syncHowTo.txt
+++ b/bin/kdepim/Zaurus-KDE_syncHowTo.txt
@@ -46,130 +46,133 @@ If a conflict occurs when syncing KO/PI<->KDE on the desktop,
 automatically the newest entry is choosen.
 (To avoid the need of user interaction)
 KO/Pi on desktop sends synced file to Zaurus.
 KO/Pi on desktop is in "waiting mode" to get synced file back.
 Zaurus is syncing it's own calendar with the received file.
 Here can be some user interaction needed, i.e.
 if the sync profile is configured as
 "ask for every entry on conflict" and a conflict occurs. 
 Zaurus sends back synced file to desktop.
 Syncing on Zaurus is complete now.
 KO/Pi on desktop gets back synced file.
 KO/Pi on desktop removes all entries in its own calendar and
 reloads the synced file.
 KO/Pi on desktop syncs with KDE.
 After syncing  with KDE is finished, KO/Pi closes
 the "remote syncing mode" window and displays 
 a "syncing complete" message in the headline.
 
 The actual syncing KO/Pi on desktop <-> KDE is 
 performed by a small command line tool "kdecaldump", 
 which writes/reads the complete KDE calendar resources to 
 a file/from a file.
 KO/Pi tags changed entries such that an unchanged entry
 is not changed in KDE by kdecaldump. That is important for 
 calendar entries in KDE, stored in a "disconnected IMAP" calendar resource.
 
 
 Same way is KA/Pi working.
 
 
 *****************************************************
 1) Installing KA/Pi+KO/Pi on the Z
 *****************************************************
 
 Download latest version of KA/Pi+KO/Pi from
 http://sourceforge.net/projects/kdepimpi/
 Project KDE/Pim.
 Direct link is:
 http://sourceforge.net/project/showfiles.php?group_id=104103&package_id=112604
 Click on the version number to read the release notes/change log.
 Choose there the right precompiled package for your Z:
 For Sharp ROM
 -File: kdepim_1.x.xx_for_SharpROM.ipk.zip
 For Open Zaurus ROM:
 -File: kdepim_1.x.xx_for_OZ-gcc3xx.ipk.zip
 If unsure, choose:
 -File: kdepim_1.x.xx_for_SharpROM.ipk.zip
 
 Unzip the file and install the packages as usual on your Z.
 In order to intstall KA/Pi+KO/Pi on your Z,
 you need to install the following files:
 kmicrokdelibs_1.x.xx_arm.ipk  
 kaddressbook_1.x.xx_arm.ipk
 korganizer_1.x.xx_arm.ipk
 
 *****************************************************
 2) Installing desktop version of KA/Pi+KO/Pi on the desktop
 *****************************************************
 
 Precompiled packages are available for SuSE 9.1.
 Choose on the above download location:
 File: KDE-Pim-Pi-1.9.11-SuSE9.1.i586.rpm
 Download file and install it on console with
 su
-rpm -ihv KDE-Pim-Pi-1.9.11-SuSE9.1.i586.rpm
-(NOTE:update with rpm -Uhv KDE-Pim-Pi-1.9.11-SuSE9.1.i586.rpm)
+rpm -ihv KDE-Pim-Pi-1.9.11-SuSE_9.1.i586.rpm
+NOTE:update with 
+            rpm -Uhv KDE-Pim-Pi-1.9.11-SuSE_9.1.i586.rpm
+     erase (uninstall) with
+            rpm -e KDE-Pim-Pi-1.9.11-SuSE_9.1     
 NOTE for users of SuSE 9.1:
 You need KDE version 3.3.0 or higher on your desktop.
 Plese make an online update in SuSE (YAST), then update
 your KDE to version 3.3.0 or higher.
 You can find links to updated precompiled versions of KDE 
 for SuSE 9.1 on the SusE web site, 
 a direct link is for example:
 ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.1
 HOWTO UPDATE KDE:
 Download there the packages in "base".
 And the needed package for your language in "internationalization".
 Put all downloaded files in one "installation" directory.
 Open console and go to the downloaded "installation" directory.
 Do there a
 su
 and then perform a test for the update:
 rpm -Uhv --test *.rpm
 
 If no dependencies are shown, you can do the actual update with 
 rpm -Uhv *.rpm
 
 If there are missing dependencies, you can resolve them by
 - download the needed updated KDE package from the 
     "applications" or from the "development" folder on the server.
 - adding a needed rpm package from the SuSE install DVD
 - remove the package that has dependencies from your "installation" directory.
 
 Do the 
 rpm -Uhv --test *.rpm
 until you get no dependencies and no errors, then do a
 rpm -Uhv *.rpm
 Run
 SuSEconfig
 after installing with rpm is finished.
 Restart KDE.
 
 *****************************************************
 3) Connection your Z to the desktop via network
    (network connection can be set up via USB cable or (W)Lan
 *****************************************************
 
 a) Connection via network cable/(W)Lan cards
    Connect your desktop to the network.
    Set up networking on the Z.
    Make sure, you can ping the desktop from Z.
 b) Connection via USB cable:(is working for Z 7x0 and Z5500)
    (i) Open console on desktop and type
            su
            tail -f /var/log/messages
    (ii) Connect your Z with the USB cable to your desktop
         You should get as output in the above console 
         something like this:
         ("BUG" is the name of the desktop computer!)
             Oct 26 12:49:37 BUG kernel: usb 2-2: new full speed USB device using address 2
             Oct 26 12:49:37 BUG kernel: usb 2-2: Product: SL-C860
             Oct 26 12:49:37 BUG kernel: usb 2-2: Manufacturer: Sharp
             Oct 26 12:49:37 BUG /etc/hotplug/usb.agent[22659]: need a device for this command
             Oct 26 12:49:43 BUG kernel: usb0: register usbnet at usb-0000:00:1d.0-2, Sharp Zaurus, PXA-2xx based
             Oct 26 12:49:43 BUG kernel: usbcore: registered new driver usbnet
         You see in the 5. line ("BUG kernel: usb0: register"), that usb device usb0 is used.
    (iii) Create a network startup entry in /etc/sysconfig/network
          Depending of the number X of the used usb device, create a file 
          /etc/sysconfig/network/ifcfg-usbX
          (in our case /etc/sysconfig/network/ifcfg-usb0 )