<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jun 29, 2014 at 9:20 AM, Chris Muller <span dir="ltr"><<a href="mailto:asqueaker@gmail.com" target="_blank">asqueaker@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Didn't Levente ask us to use stable VM's for production services?<br></div></div></blockquote>
<div><br></div><div>Given that 3018 has nothing radically new but contains bug fixes IMO it is stable. Even the SPur VM is more stable than the one that preceeds it. What extra testing has 2776 had to make it more or less stable than 2987 or 3021? 2987 and subsequent all run the standard test suite with equivalent results. I don't make arbitrary changes to the Cog VMs (Spur is obviously evolving much faster, but again is getting more, not less stable). You need to specify a criterion by which a VM is judged stable, not merely go by age, which is, at least on average, inversely correlated with stability, older VMs containing more bugs, if you want to argue against using newer VMs. I don't put newer VMs out for amusement. I put them out because they're better (faster, fix bugs, etc).</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">
On Fri, Jun 27, 2014 at 4:01 PM, Eliot Miranda <span dir="ltr"><<a href="mailto:eliot.miranda@gmail.com" target="_blank">eliot.miranda@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Chris,<br><div class="gmail_extra"><br><br><div class="gmail_quote"><div>On Fri, Jun 27, 2014 at 1:14 PM, Chris Cunnington <span dir="ltr"><<a href="mailto:brasspen@gmail.com" target="_blank">brasspen@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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.<br>
</blockquote><div><br></div></div><div>3018 is the latest and greatest. Please use it.</div><div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Installing:<br>
<br>
- get a Cog binary from <a href="http://mirandabanda.org" target="_blank">mirandabanda.org</a><br>
- use Ken's cogdeb.zip to make a deb<br>
- install with dpkg (i.e. dpkg -i cogvm_2776-1_i386.deb)<br>
- execute "man squeak" to see if it's loaded<br>
<br>
Removing:<br>
<br>
- check the package name with dpkg-query -l<br>
- see it's actually called "coglinux" as opposed to cogvm or squeak<br>
- dpkg -r coglinux<br>
<br>
<br>
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.<br>
<span><font color="#888888"><br>
Chris<br>
</font></span></blockquote></div></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>
</font></span></div></div>
<br><br>
<br></blockquote></div><br></div>
</div></div><br><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>
</div></div>