I am using the following script that resides in the $PATH to always
have the right VM ready.

  #!/bin/sh
  SQUEAK_PLUGINS="/usr/local/lib/squeak/4.0-2496-cog"
  export SQUEAK_PLUGINS
  exec "$SQUEAK_PLUGINS/squeak" "$@"

Works from anywhere.

Lukas


On 19 October 2011 19:37, John Toohey <[email protected]> wrote:
> Am now using the latest VM from Elliot. Looks good so far, but most of
> my users have left, so I'll continue to monitor it. Actually has to
> write a new script to get it to work, and run that directly from a bin
> directory containing the VM and the plugins. For some reason, even
> with the -plugins directive, the VM could not find the vm-display-null
> plugin.
>
> On Wed, Oct 19, 2011 at 11:44, Igor Stasenko <[email protected]> wrote:
>> On 19 October 2011 16:04, John Toohey <[email protected]> wrote:
>>> I just downloaded the latest COG Unix VM from Jenkins. Can I just copy
>>> the contents of the zip into the one-click image that I am running?
>>> (Into ../Contents/Linux)
>>>
>>
>> Just keep in mind that VMs built on Jenkins using different naming for
>> executable
>> i.e. CogVM instead of squeak.
>> So you may need to fix script(s) to invoke it properly.
>>
>>>
>>>
>>> On Wed, Oct 19, 2011 at 09:50, Lukas Renggli <[email protected]> wrote:
>>>> I am using VM.2496 from Eliot's builds for the build server and
>>>> TextLint. This version works quite well for me.
>>>>
>>>> Lukas
>>>>
>>>> On 19 October 2011 15:19, John Toohey <[email protected]> wrote:
>>>>> Do you know of a VM that is in production somewhere? I've switched to
>>>>> the COG VMs (much faster than the old ones) , but they all seem very
>>>>> unstable. Maybe I'm taking the wrong ones from the build server, but I
>>>>> desperately need one that is stable enough to deploy. I'm using this
>>>>> one, at the moment,  VM Version: Croquet Closure Cog VM [CoInterpreter
>>>>> VMMaker-oscog-IgorStasenko.123]
>>>>>
>>>>> On Wed, Oct 19, 2011 at 08:44, Lukas Renggli <[email protected]> wrote:
>>>>>> PharoDebug.log is created before the image opens a debugger.
>>>>>>
>>>>>> crash.dmp is created when the VM dies.
>>>>>>
>>>>>> Lukas
>>>>>>
>>>>>> On 19 October 2011 14:26, John Toohey <[email protected]> wrote:
>>>>>>> One of my production servers was down this morning, but instead of a
>>>>>>> PharoDebug.log file, all I found was a file called crash.dmp, with a
>>>>>>> minimum stack trace and no information about what caused the crash.
>>>>>>> Can someone tell me what this file is, and why the usual log file was
>>>>>>> not created?
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> ~JT
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Lukas Renggli
>>>>>> www.lukas-renggli.ch
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> ~JT
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Lukas Renggli
>>>> www.lukas-renggli.ch
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> ~JT
>>>
>>>
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>>
>>
>
>
>
> --
> ~JT
>
>



-- 
Lukas Renggli
www.lukas-renggli.ch

Reply via email to