John, I did not compile the vm; it is the second most recent from the Pharo web site. Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of John M McIntosh Sent: Tuesday, November 03, 2009 5:14 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] FW: vm on ubuntu Mmm, well assuming you compiled/linked your own VM, then in the interp.c it would have something like /* Automatically generated from Squeak on 17 September 2009 10:11:02 am by VMMaker 3.11.3 */ at the top, what does the one you have say? Oddly both supplied attributes speak of the image used, when build and compiler but speak nothing about what version the VM is, er like is this one 32/64bit clean, or 32bit address clean... An non-informed answer should be it's ok since it was compiled in feb, but without the VMMaker version number it's an uknown. On 2009-11-03, at 1:23 PM, Schwab,Wilhelm K wrote:
-----Original Message----- From: Schwab,Wilhelm K Sent: Tuesday, November 03, 2009 4:12 PM To: johnmci@smalltalkconsulting.com Subject: RE: [Pharo-project] vm on ubuntu
John,
My ageing image that did the mouse wheel crash is as follows:
SmalltalkImage current getSystemAttribute: 1004 'Pharo0.1 of 16 May 2008 [latest update: #10074]'
The system dictionary/error handling failure was the RC1 web image.
Both quit using the following vm:
SmalltalkImage current getSystemAttribute: 1006 'Unix built on Feb 5 2009 19:38:30 Compiler: 4.1.2 (Gentoo 4.1.2 p1.3)'
I had bad experiences with newer images, but the old image has been very stable. One could argue that both have been flaky since I upgraded to 9.10. My laptop chipset seems to like the new kernel, especially in terms of reliable access to the full native resolution, and sound works where it did not on 9.04. My desktop did not do so well. The upgrade was quite slow. It soon presented me with a black screen. With no response, I finally killed the power, which apparently corrupted the swap partition. I finally got it back by removing and re-creating the swap partition, followed by a certain amount of forced checking that might or might not have fixed something. Suspecting power management, I disabled putting the display to sleep, and have not had a problem since. The package manager crashed once on my laptop, so I do not rule out problems with the Koala.
Bill
-- = = = ======================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ======================================================================== _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project