Actually, I did read, but what I understood is only that I should look for another URL do download PharoS :). In any case, thanks a lot. I tried with the Pharo VM and it works as expected, too. I set it to 1GB and got the warning only when the image went passed that limit. Cheers, Doru On Mon, Jul 15, 2013 at 5:36 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 15 July 2013 16:59, Tudor Girba <tudor@tudorgirba.com> wrote:
Aha :).
Ok. I tested PharoS with 1GB and I got a 800MB image running well.
Is there really no chance of getting Cog with this feature? :)
please ,read more carefully.. :) it was error in config, which copied PharoS files over Pharo ones. And answering your question: you should have the same feature in both VMs since they sharing same C codebase.
Doru
On Mon, Jul 15, 2013 at 4:23 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 15 July 2013 15:34, Damien Cassou <damien.cassou@gmail.com> wrote:
On Mon, Jul 15, 2013 at 3:27 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Ok, I admit. I should read emails thoroughly :). Please ignore the second issue. Still, why is it called PharoS?
may it be because this is a StackVM and not Cog?
yeah, it looks like Esteban by making configs for PharoS VM made a mistake and these VMs uploaded into same location as Cog ones.. (we fixed it already, building new VM, which will copy stuff properly)
alternatively , you can download VM from build server:
https://ci.inria.fr/pharo/view/VM/job/PharoVM/182/Architecture=32,Slave=vm-b...
(to make sure we're talking about same VM)
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com "Every thing has its own flow"