On Friday 29 April 2005 09:50, Colin Carter wrote:
On Friday 29 April 2005 01:28, R Kimber wrote:
On Thu, 28 Apr 2005 08:20:31 -0400
Valur Olafsson
wrote: Spoke too soon, the computer froze not 10 minutes after I emailed the list. Still have the same problem. Any other suggestions to debug the problem?
I have experienced something similar, always while using a browser. This suggests it might be related to the network connection, but it might well be something else. All I can say is that I've been experimenting with a fully 64-bit distribution (as opposed to the mixed 64 and 32-bit that I assume most people have) and I have not experienced the problem at all. On the other hand, the stability might be due to some other difference between the 64-bit distribution (Ubuntu) and Suse. I realise this isn't really very helpful, but it may give you something to think about.
- Richard
Richard, What do you mean by mixed" Vs "Fully 64" ? I noted that you said most people have the mixed system.
Not all applications are 64 bit. Some are 32 bit only. You therefore have a 32 bit version and a 64 bit version of most libs. One is in lib, such as /usr/lib, the other in /usr/lib64. This is the correct way to do it, according to the defined standards
I installed the SuSE 64 bit system and just assumed that it is fully 64 bit.
No, it is not fully 32 bit. Some apps are 32 bit. Just one example, java 1.4.x is 32 bit. This is not SuSEs fault or a bug. It is perfectly OK to run 32 bit apps on a 64 bit system, this is one of the features of this specific 64 bit architecture. Proprietary apps, without sourcecode and therefore only available as 32 bit version, can be used on a 64 bit AMD64 Linux system without problems.
Am I being naive? Perhaps it is the cause of half of my SuSE problems!
May be, and may be not. Bugs can be everywhere.
Regards, Colin
HTH, Matt