Posts by Palo M.

1) Questions and Answers : Unix/Linux : no climate prediciton on debian etch ? (Message 33208) Posted 5 Apr 2008 by Palo M. Post: Thank you for your explanations. I understand that compilation of CPDN applications is more complex than usual compilation of other application... BTW, it is possible to link statically some libraries while having some others linked dynamically (i.e. standard libs can be linked statically to avoid incompatibility, and \"own\" libraries can be linked dynamically, as they are distributed by the project anyway). ... The 32-bit vs. 64-bit issue comes up time and again. An attempt to port to 64-bit was attempted a couple years ago. It died in Alpha because there was not staff resource available to support it. If memory serves, there was no performance gain to justify the effort. In my case it was not about performance - I agree that performance cannot be improved that much - and little shorter (let\'s say 10%) computation time isn\'t worth the effort; more important is that models are computed till the end. In my case it is about ability (or better said inability) to run CPDN at all. And, 32-bit Debian etch uses the same glibc 2.3.6, so probably the same problem would happen there anyway (so maybe it\'s not problem of 64-bit at all, just glibc incompatibility problem). ... People keep saying this, but the truth lies elsewhere: people keep running operating systems or hardware that don\'t have the software needed by this project. I run 64-bit system for the reason - 32-bit system cannot use all 4G memory that I have (well, custom 32-bit Linux kernel could do it in principle, but it would be too slow, so it wouldn\'t make sense). It is the server, therefore 4G and therefore stable distribution (and, I\'m not going to overclock it). It seems Josi is in exactly same situation as me - maybe we are only two, or maybe there are more of us, I don\'t know. But Debian is one of the most popular distributions. BTW, it\'s pretty sure that the world is moving towards 64 bits - as soon as someone uses 4G or more, 64-bit OS is the only reasonable way. And x86-64 architecture has big advantage of backward compatibility with i386 - so this transition needn\'t be very painful. I see that project did something in this direction: i386 version of HadSM is provided also for x86-64 architecture - it\'s just pity it doesn\'t run on some systems due to libraries incompatibility... such a small step is missing. I know it\'s not easy because of complicated verification; I hope CPDN beta could help here.
2) Questions and Answers : Unix/Linux : no climate prediciton on debian etch ? (Message 33204) Posted 4 Apr 2008 by Palo M. Post: Ok Conclusion is : To run this project I need Glibc 2.4 , which I don\'t have . See you once Debian Lenny goes stable :). I\'m in the same situation: Having 64-bit Debian stable (Etch) on Q6600 (with 4 GB RAM, so it does not make sense to run 32-bit system there). Machine runs 24/7 (it is server, that\'s why it is running stable distribution and not unstable), so it is very suitable for CPDN which takes long time... I was optimistic with this new machine, but all I\'ve got is failed WUs. And as I read on several places of the forum, it is not going to be solved soon - so it seems project does not care about such machines (which sounds strange to me, since memory consumption by CPDN applications is big and 32-bit machine has memory limit). If CPDN doesn\'t want my Q6600, let it be so. There are several projects which send 64-bit applications directly and some other projects are open-source, so we can compile applications ourselves. BTW, I do not understand, why dynamically linked applications are distributed and not static - dynamic linking has just big chance it will not work on some systems. It is the same with BOINC-core-client - official Linux 64-bit binary is dynamically linked (with no static alternative) and it needs GLIBC_2.4, so it didn\'t work for me; I had to compile it myself (which went smoothly without any problems on the other hand). There is CPDN-beta - according to this post it uses glibc 2.3 and my first WU didn\'t crash yet - but it\'s still dynamically linked 32-bit application, so it is not ideal for 64-bit systems as well. I will let this WU run, but I will probably not start another until there\'s 64-bit...