On 15 July 2013 16:59, Tudor Girba <tu...@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 <siguc...@gmail.com> wrote:
>>
>> On 15 July 2013 15:34, Damien Cassou <damien.cas...@gmail.com> wrote:
>> > On Mon, Jul 15, 2013 at 3:27 PM, Tudor Girba <tu...@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-builder-win/
>>
>> (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.

Reply via email to