Thread: [Zsrep-devel] Woot Progress!!!
Status: Alpha
Brought to you by:
cyphactor
Menu
▾
▴
zsrep-devel
|
From: Andrew De P. <cyp...@so...> - 2006-09-07 09:10:47
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello to all you Zaurus enthusiasts out there who have been hanging on this mailing list. The good news is over this past 4 day weekend I managed to get a huge amount of work done on lib_zdtm_sync. What specifically you may ask, well I started implementing a testing daemon which is designed specifically to test the functionality of lib_zdtm_sync. It also has the purpose of allowing me to design an API interface to conform to the opensync plugin API interface, so that some day soon they can meet in a nice and clean fashion. Right now this testing daemon implements quite a bit of the syncing protocol. It does not, I repeat does NOT provide backup or syncing at this point it is just a tool for us developers to test the protocol against other peoples Zauri, test the lib_zdtm_sync, and have a preliminary design for the opensync plugin API. HOWEVER IT DOES PLAY NICELY WITH THE ZAURUS. THAT MEANS ANY OF YOU OUT THAT THAT WANT TO TRY IT FEEL FREE, it generates some output based on parsing of the Zaurus sync protocol as well as a protocol dump log which would be of great use to use if you would kindly run the testing daemon and e-mail your log dumps to the mailing list. I WILL PROVIDE DETAILED INSTRUCTIONS BELOW. On a side note. jcmdev0 has been kicking but on a new website for us, and today I decided to add a bit of functionality myself. You can watch the new website be developed at http://zsrep.sourceforge.net/new-site/. Please give suggestions. Oh yeah, back to today, well I added support for "Developer Logs" to the new website so that those interested can look at the detailed logs of the developers if you so choose without using svn or any command line stuff. BUILD AND TEST INSTRUCTIONS (assumes Zaurus is connected, can ping it) - --------------------------- 1. svn co https://svn.sourceforge.net/svnroot/zsrep/lib_zdtm_sync 2. cd lib_zdtm_sync 3. ./bootstrap.sh 4. ./configure 5. make 6. cd testing 7. ./zdtm_test_daemon 8. e-mail us ~/.lib_zdtm_sync.log and the terminal output You should see a bunch of text in the terminal and hopefully your Zaurus should make the sync noise and you should notice the sync software startup and cleanly finish on the Zaurus (you won't see this if your Zaurus screen saver is on). If this is not the case, then it is even more of a reason for you to send us the log files and terminal output. K, thats it for now ladies and gents. I am going to continue developing this as much as possible as quickly as possible now that it really has regained some momentum. Let me know (via the mailing list) if you have any questions suggestions etc. - -- Andrew De Ponte Contact Info - ------------ AIM Nick: HUNNYnNUTTS Jabber 0: cyp...@ja... Jabber 1: cyp...@ja... Jabber 2: cyp...@ja... Current Open Source Projects - ---------------------------- Zaurus Synchronization REPository (a.k.a. Zaurus Synchronization Reverse Engineering Project) - - http://zsrep.sourceforge.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE/+PxVroBBszP8ekRAkX1AJ4pouk2QO3JtQdY5WBGn4tWM4vDNQCgjhI1 Ss5fbo1c37ztSuxw9hdhBlk= =5FwP -----END PGP SIGNATURE----- |
|
From: David B. <dav...@le...> - 2006-09-07 23:38:53
|
Fantastic work, Andrew! Unfortunately, I tried the test script and got this output: zdtm_open_log - (0). zdtm_listen_for_zaurus - (0). initialize - (0). zdtm_conn_to_zaurus - connect: Connection refused zdtm_conn_to_zaurus - (-3). connect - (1). and it didn't seem to create a log file. I verified before and after that I could ping the zaurus. It sounds like I'm missing something obvious, so let me know what to try and I'll give it another shot. David Andrew De Ponte wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello to all you Zaurus enthusiasts out there who have been hanging on > this mailing list. The good news is over this past 4 day weekend I > managed to get a huge amount of work done on lib_zdtm_sync. What > specifically you may ask, well I started implementing a testing daemon > which is designed specifically to test the functionality of > lib_zdtm_sync. It also has the purpose of allowing me to design an API > interface to conform to the opensync plugin API interface, so that some > day soon they can meet in a nice and clean fashion. > > Right now this testing daemon implements quite a bit of the syncing > protocol. It does not, I repeat does NOT provide backup or syncing at > this point it is just a tool for us developers to test the protocol > against other peoples Zauri, test the lib_zdtm_sync, and have a > preliminary design for the opensync plugin API. HOWEVER IT DOES PLAY > NICELY WITH THE ZAURUS. THAT MEANS ANY OF YOU OUT THAT THAT WANT TO TRY > IT FEEL FREE, it generates some output based on parsing of the Zaurus > sync protocol as well as a protocol dump log which would be of great use > to use if you would kindly run the testing daemon and e-mail your log > dumps to the mailing list. I WILL PROVIDE DETAILED INSTRUCTIONS BELOW. > > On a side note. jcmdev0 has been kicking but on a new website for us, > and today I decided to add a bit of functionality myself. You can watch > the new website be developed at http://zsrep.sourceforge.net/new-site/. > Please give suggestions. Oh yeah, back to today, well I added support > for "Developer Logs" to the new website so that those interested can > look at the detailed logs of the developers if you so choose without > using svn or any command line stuff. > > BUILD AND TEST INSTRUCTIONS (assumes Zaurus is connected, can ping it) > - --------------------------- > 1. svn co https://svn.sourceforge.net/svnroot/zsrep/lib_zdtm_sync > 2. cd lib_zdtm_sync > 3. ./bootstrap.sh > 4. ./configure > 5. make > 6. cd testing > 7. ./zdtm_test_daemon > 8. e-mail us ~/.lib_zdtm_sync.log and the terminal output > > You should see a bunch of text in the terminal and hopefully your Zaurus > should make the sync noise and you should notice the sync software > startup and cleanly finish on the Zaurus (you won't see this if your > Zaurus screen saver is on). If this is not the case, then it is even > more of a reason for you to send us the log files and terminal output. > > K, thats it for now ladies and gents. I am going to continue developing > this as much as possible as quickly as possible now that it really has > regained some momentum. Let me know (via the mailing list) if you have > any questions suggestions etc. > > - -- > Andrew De Ponte > > Contact Info > - ------------ > AIM Nick: HUNNYnNUTTS > Jabber 0: cyp...@ja... > Jabber 1: cyp...@ja... > Jabber 2: cyp...@ja... > > Current Open Source Projects > - ---------------------------- > Zaurus Synchronization REPository > (a.k.a. Zaurus Synchronization Reverse Engineering Project) > - - http://zsrep.sourceforge.net > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (GNU/Linux) > > iD8DBQFE/+PxVroBBszP8ekRAkX1AJ4pouk2QO3JtQdY5WBGn4tWM4vDNQCgjhI1 > Ss5fbo1c37ztSuxw9hdhBlk= > =5FwP > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Zsrep-devel mailing list > Zsr...@li... > https://lists.sourceforge.net/lists/listinfo/zsrep-devel > > |
|
From: Andrew De P. <cyp...@so...> - 2006-09-08 21:15:15
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Barnett wrote: > Fantastic work, Andrew! > > Unfortunately, I tried the test script and got this output: In general in the test script the the numbers in the parenthesis are the return values of the corresponding functions in the test program. Zero generally means success and positive numbers mean a specific success while negative numbers indicate failure. However, in the encapsulation functions a return value of 1 indicates a general error. Hence, the following reads: > zdtm_open_log - (0). Good, this means that it opened the log file ~/.lib_zdtm_sync.log successfully (that does not mean it has written anything, it just means it opened it successfully). > zdtm_listen_for_zaurus - (0). Good, this means that it setup the socket communications stuff necessary for the Zaurus to connect back to the test_daemon. > initialize - (0). Good, initialize is an encapsulation of the above two functions. It is specifically here to provide similar interface to that of the OpenSync plugin API. Since, the above two succeeded this encapsulation function is happy. > zdtm_conn_to_zaurus - connect: Connection refused > zdtm_conn_to_zaurus - (-3). Bad, zdtm_conn_to_zaurus failed with an error code of -3. Error code -3 in this case means that zdtm_conn_to_zaurus function did everything correct except for it's very last step, actually connecting to the Zaurus, BOOO HOO. This could be for a number of reasons. I will list them here in the order that you should probably check them. 1. The test_daemon currently has hard coded in it that the IP address of the Zaurus it is trying to connect to is 192.168.129.201. If your Zaurus is not using this IP address then that is definitely a factor. You can test it by changing the IP of your Zaurus. 2. This software is designed to synchronize with Sharp Based ROMs that use DTM for storage. I know for a fact that with the Zaurus SL-5500 this includes ROMs version 3.10 and UP. With Zaurus SL-5600 this includes ROM 1.0 and UP (which happen to be the intial ROM that it comes with). I have been told by people running Zaurus SL-6000s that the SL-6000 used DTM based as well. --- Hence, you should be using SL-5500s Sharp ROM 3.10 (because if I remember you are using a SL-5500), which if you don't have can easily be obtained from http://www.myzaurus.com/ROMupdate5.asp 3. After, making sure of the first two things it gets a little more involved. Let me know your information about about the first two options and let me know the results. Also, let me know if you have any questions > connect - (1). This is just saying that a member (specifically the zdtm_conn_to_zaurus function) of this encapsulation function has failed. > and it didn't seem to create a log file. It looks to have opened it but never closed the log file because it exited with a failure. Beyond that it would have never written anything since the .lib_zdtm_sync.log file is a log of all the communications between the program and the Zaurus of which it had none because it failed to connect to the Zaurus. > I verified before and after > that I could ping the zaurus. It sounds like I'm missing something > obvious, so let me know what to try and I'll give it another shot. Well, this is excellent that you can ping the Zaurus, this is literally half the battle. What IP address are you using when you ping your Zaurus? Copy and paste a ping call into an e-mail and send it back. Ex: adeponte@devtux:~$ ping 192.168.129.201 PING 192.168.129.201 (192.168.129.201) 56(84) bytes of data. 64 bytes from 192.168.129.201: icmp_seq=1 ttl=255 time=6.16 ms 64 bytes from 192.168.129.201: icmp_seq=2 ttl=255 time=0.769 ms 64 bytes from 192.168.129.201: icmp_seq=3 ttl=255 time=0.751 ms Also, if you run an nmap command it can tell us is the proper ports on the Zaurus are listening and such which correspond to telling you if you are using a proper ROM. You can also check the ROM version on your Zaurus by going to the Settings Tab->System Info->Version->Linux Kernel it should have a ROM Version listed there. On my Zaurus SL-5600 it is at ROM Version 1.32 which is the latest official ROM release for my model from Sharp. An example up the nmap command to run would be as follows (it assumes you have nmap installed already): adeponte@devtux:~$ nmap -sT -p 4244,4245 192.168.129.201 Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2006-09-08 14:21 PDT Interesting ports on 192.168.129.201: PORT STATE SERVICE 4244/tcp open unknown 4245/tcp closed unknown Nmap finished: 1 IP address (1 host up) scanned in 0.134 seconds I hope my comments have been helpful and can't wait to see back your results. - -- Andrew De Ponte Contact Info - ------------ AIM Nick: HUNNYnNUTTS Jabber 0: cyp...@ja... Jabber 1: cyp...@ja... Jabber 2: cyp...@ja... Current Open Source Projects - ---------------------------- Zaurus Synchronization REPository (a.k.a. Zaurus Synchronization Reverse Engineering Project) - - http://zsrep.sourceforge.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFAd8PVroBBszP8ekRAqSfAKCew3B8Rr95OIrCMYeQ+HliELL0cQCfcfI/ 7g+T+o9bHSG9T596I8BkrQw= =1sMK -----END PGP SIGNATURE----- |
|
From: David B. <dav...@le...> - 2006-09-09 04:48:48
|
Andrew De Ponte wrote: > 1. The test_daemon currently has hard coded in it that the IP address of > the Zaurus it is trying to connect to is 192.168.129.201. If your Zaurus > is not using this IP address then that is definitely a factor. You can > test it by changing the IP of your Zaurus. > The Zaurus has IP 192.168.129.201, which is the address I successfully pinged. > 2. This software is designed to synchronize with Sharp Based ROMs that > use DTM for storage. I know for a fact that with the Zaurus SL-5500 this > includes ROMs version 3.10 and UP. > This is most likely the problem because my ROM is version 2.38. > Also, if you run an nmap command it can tell us is the proper ports on > the Zaurus are listening and such which correspond to telling you if you > are using a proper ROM. Interesting ports on 192.168.129.201: PORT STATE SERVICE 4244/tcp closed unknown 4245/tcp closed unknown This also seems to indicate the ROM is the problem. Reflashing the ROM requires an SD/CF memory card, doesn't it? I don't have either yet. =( David |
|
From: Andrew De P. <cyp...@so...> - 2006-09-09 07:44:26
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Barnett wrote: > Andrew De Ponte wrote: >> 1. The test_daemon currently has hard coded in it that the IP address of >> the Zaurus it is trying to connect to is 192.168.129.201. If your Zaurus >> is not using this IP address then that is definitely a factor. You can >> test it by changing the IP of your Zaurus. >> > The Zaurus has IP 192.168.129.201, which is the address I successfully > pinged. >> 2. This software is designed to synchronize with Sharp Based ROMs that >> use DTM for storage. I know for a fact that with the Zaurus SL-5500 this >> includes ROMs version 3.10 and UP. >> > This is most likely the problem because my ROM is version 2.38. >> Also, if you run an nmap command it can tell us is the proper ports on >> the Zaurus are listening and such which correspond to telling you if you >> are using a proper ROM. > Interesting ports on 192.168.129.201: > > PORT STATE SERVICE > > 4244/tcp closed unknown > > 4245/tcp closed unknown > > This also seems to indicate the ROM is the problem. I would totally agree that the ROM is the problem. You need ROM 3.10. > Reflashing the ROM requires an SD/CF memory card, doesn't it? I don't > have either yet. =( Doing this ROM upgrade does NOT require a SD/CF memory card! If you have a Windows box that you can connect your Zaurus to and run the upgrade software it should work fine. http://www.myzaurus.com/ROMupdate5.asp provides you with the instructions for the upgrade and the files necessary (they are all the way at the bottom). Let me know if you have any questions or difficulties. - -- Andrew De Ponte Contact Info - ------------ AIM Nick: HUNNYnNUTTS Jabber 0: cyp...@ja... Jabber 1: cyp...@ja... Jabber 2: cyp...@ja... Current Open Source Projects - ---------------------------- Zaurus Synchronization REPository (a.k.a. Zaurus Synchronization Reverse Engineering Project) - - http://zsrep.sourceforge.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFAnLVVroBBszP8ekRAmNyAJ4/WhjCewubk64NbaH/X4kly58OTgCdE28D BP7OFIZ+UE0osRleybtajGY= =PJwh -----END PGP SIGNATURE----- |
|
From: David B. <dav...@le...> - 2006-09-10 20:11:01
Attachments:
zdtm_console.log
.lib_zdtm_sync.log
|
Andrew De Ponte wrote: > to use if you would kindly run the testing daemon and e-mail your log > dumps to the mailing list. I WILL PROVIDE DETAILED INSTRUCTIONS BELOW. It took me most of the weekend to get the 64M file downloaded over dialup (along with a bunch of school-related downloads), but I finally got my ROM reflashed and the zdtm test working! Attached are the console output and log file. Hope that helps! David |
|
From: Andrew De P. <cyp...@so...> - 2006-09-11 17:24:21
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Barnett wrote: > It took me most of the weekend to get the 64M file downloaded over > dialup (along with a bunch of school-related downloads), but I finally > got my ROM reflashed and the zdtm test working! Attached are the console > output and log file. Excellent, I am glad to find out that you have finally got the ROM downloaded and flashed. The log files you presented are of great use. They help me correlate assumptions about the protocol to make sure that other peoples Zauri work the same way mine does despite the different model numbers and such. You, can also see now that a sync solution is coming soon given that the zdtm_test_daemon can interact appropriately with the Zaurus. A bunch of restructuring and planning work has been going on in the Zaurus project to make sure that things are as smooth as possibly in the development of lib_zdtm_sync, zdtm_test_daemon, and the opensync plugin. This includes some project management so that tasks can be assigned to certain people etc. An html version of the project plan will posted on the new site as soon as it is ready. Other than that it is just a matter of time and how much development support we get will totally effect that. Things that need work that you or others may be interested in. 1. Further develop the new website (make it nicer looking and content complete). Let me know if you would like to do this. This would include maybe writing howto docs and things like that. 2. Development work on lib_zdtm_sync and zdtm_test_daemon, etc. 3. Restructuring and Review of the Protocol Assumptions and Observations document. - -- Andrew De Ponte Contact Info - ------------ AIM Nick: HUNNYnNUTTS Jabber 0: cyp...@ja... Jabber 1: cyp...@ja... Jabber 2: cyp...@ja... Current Open Source Projects - ---------------------------- Zaurus Synchronization REPository (a.k.a. Zaurus Synchronization Reverse Engineering Project) - - http://zsrep.sourceforge.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFBZ3aVroBBszP8ekRAp9sAJ4l2mPX7+NofuIR8+Y4/YaJMOnF4QCfazof 44CxZ9IfeIadyi2e5IOhcYo= =LiBc -----END PGP SIGNATURE----- |
|
From: John M. <jc...@gm...> - 2006-09-11 18:34:18
|
> > Things that need work that you or others may be interested in. > 1. Further develop the new website (make it nicer looking and content > complete). Let me know if you would like to do this. This would include > maybe writing howto docs and things like that. > Where is your cronjob for the dev logs? For the sake of flexibility we should dump the raw logs to their own file and include them elsewhere. I am thinking that we should have them in a general development section. -John |
|
From: Andrew De P. <cyp...@so...> - 2006-09-11 23:28:50
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John McCullough wrote: > Things that need work that you or others may be interested in. > 1. Further develop the new website (make it nicer looking and content > complete). Let me know if you would like to do this. This would include > maybe writing howto docs and things like that. > > > Where is your cronjob for the dev logs? For the sake of flexibility we > should dump the raw logs to their own file and include them elsewhere. The cronjab is in my personal cronjob on the server. There exist no group specific crontabs in sourceforge.net. Hence, one person has to manage them. I will modify the cronjob to dump the raw logs. Where would you like the raw svn logs dumped? > I am thinking that we should have them in a general development section. This probably makes the most sense and will reduce on the number of major links in the menu. - --Andrew - -- Andrew De Ponte Contact Info - ------------ AIM Nick: HUNNYnNUTTS Jabber 0: cyp...@ja... Jabber 1: cyp...@ja... Jabber 2: cyp...@ja... Current Open Source Projects - ---------------------------- Zaurus Synchronization REPository (a.k.a. Zaurus Synchronization Reverse Engineering Project) - - http://zsrep.sourceforge.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFBfNYVroBBszP8ekRAnmWAJ9DTqETbjTvegSM8/Pgj7cmrWG2NACgp1nA a4dopT0XvyON4A4CsmGiTGo= =fFHf -----END PGP SIGNATURE----- |
|
From: Andrew De P. <cyp...@so...> - 2006-09-12 02:33:24
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John McCullough wrote: > Things that need work that you or others may be interested in. > 1. Further develop the new website (make it nicer looking and content > complete). Let me know if you would like to do this. This would include > maybe writing howto docs and things like that. > > > Where is your cronjob for the dev logs? For the sake of flexibility we > should dump the raw logs to their own file and include them elsewhere. K. The raw logs are now being dumped to /home/groups/z/zs/zsrep/htdocs/svnlog.txt and the old php generated stuff is no longer updated. I will let you do your PHP magic with it! - -- Andrew De Ponte Contact Info - ------------ AIM Nick: HUNNYnNUTTS Jabber 0: cyp...@ja... Jabber 1: cyp...@ja... Jabber 2: cyp...@ja... Current Open Source Projects - ---------------------------- Zaurus Synchronization REPository (a.k.a. Zaurus Synchronization Reverse Engineering Project) - - http://zsrep.sourceforge.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFBh6dVroBBszP8ekRAiVNAJwJrkmHHCB+Eos3JmL3z8n1KZHzDwCdE51T dFM738RxcOVhXhXnDcY350Y= =Ufxv -----END PGP SIGNATURE----- |
|
From: John M. <jc...@gm...> - 2006-09-12 06:43:36
|
On 9/11/06, Andrew De Ponte <cyp...@so...> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > John McCullough wrote: > > Things that need work that you or others may be interested in. > > 1. Further develop the new website (make it nicer looking and > content > > complete). Let me know if you would like to do this. This would > include > > maybe writing howto docs and things like that. > > > > > > Where is your cronjob for the dev logs? For the sake of flexibility we > > should dump the raw logs to their own file and include them elsewhere. > > K. The raw logs are now being dumped to > /home/groups/z/zs/zsrep/htdocs/svnlog.txt and the old php generated > stuff is no longer updated. I will let you do your PHP magic with it. Cruddy php magic done. -John |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X