I see no problem with updating CogVM in general on the new servers. But as 
the current case shows, a bit of testing before upgrading is generally better.


Levente

On Sun, 29 Jun 2014, Chris Muller wrote:

> Didn't Levente ask us to use stable VM's for production services?
> 
> 
> On Fri, Jun 27, 2014 at 4:01 PM, Eliot Miranda <eliot.miranda at gmail.com> wrote:
>       Hi Chris,
> 
>
>       On Fri, Jun 27, 2014 at 1:14 PM, Chris Cunnington <brasspen at gmail.com> wrote:
>             I intend to upgrade the VM on box4 VM.r2776 (Aug. 2013) to VM.r2987 (June 2014). The intention here is to refine the install/removal process. I just did this on my Debian Wheezy box,
>             so it seems pretty straightforward.
> 
> 
> 3018 is the latest and greatest.  Please use it.
> 
>
>       Installing:
>
>       - get a Cog binary from mirandabanda.org
>       - use Ken's cogdeb.zip to make a deb
>       - install with dpkg  (i.e. dpkg -i cogvm_2776-1_i386.deb)
>       - execute "man squeak" to see if it's loaded
>
>       Removing:
>
>       - check the package name with dpkg-query -l
>       - see it's actually called "coglinux" as opposed to cogvm or squeak
>       - dpkg -r coglinux
> 
>
>       So, as I said, I just did this on my server and is seemed to work OK. I plan to upgrade the VM from last year's model (2776) to this year's (2987). If there's anything people with more LInux
>       experience could add to this process, I'd be happy to hear it.
>
>       Chris
> 
> 
> 
> 
> --
> best,Eliot
> 
> 
> 
> 
> 
>