<br><br><div class="gmail_quote">On Thu, Oct 8, 2009 at 4:11 PM, Sebastian Dziallas <span dir="ltr"><<a href="mailto:sebastian@when.com">sebastian@when.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Sean DALY wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Could this be solved by branding, linking a boot helper to a SoaS<br>
version? Strawberry helper, Blueberry helper?<br>
</blockquote>
<br></div>
Yes, I'd agree here! Since that's how they were intended. We originally didn't release boot helpers with each snapshot, since those are snapshots for a reason. On the other hand, updates for Sugar on a Stick (v1) had, when being mentioned, a huge warning sign.<br>
<br>
That's not because we wouldn't want people to try it out, but because it's just a support hell. There's even been a blueprint in Launchpad, but I'm not sure whether this will happen for v2:<br>
<br>
<a href="https://blueprints.edge.launchpad.net/soas/+spec/distribution-updates" target="_blank">https://blueprints.edge.launchpad.net/soas/+spec/distribution-updates</a><br>
<br>
So to be clear: Updating via yum is not the recommended way of moving to another release (which is also the way since we had originally some forked packages from Fedora).<br>
<br>
If I recall correctly, you could type yum update on your XO, but this wouldn't necessarily move you to the next OLPC software release.<br>
<br>
Anyway, finding good ways of updating SoaS / the base system / the activities is a good thing to discuss. Anybody up for another lengthy discussion here? ;)<br></blockquote><div><br></div><div><br></div><div>I think we are going to try to update by backing up the XS, collecting the sticks, reburning, reassociating the user with their XS account. Haven't tested it yet but that plan seems to have the most promise and least effort.</div>
<div><br></div><div>We will need to change all the CDs at the same time. We will need to send home new CDs and communicate they need to throw the old one out. </div><div><br></div><div>Effort, but should not be impossible. </div>
<div><br></div><div>Any thoughts on how to make it easier?</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><font color="#888888">
<br>
--Sebastian</font><div><div></div><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Mike Lee did amazing CD labels.<br>
<br>
It's quite a bit cheaper to press runs of CDs than USB sticks, even<br>
with 4-color disc labels.<br>
<br>
Sean<br>
<br>
<br>
On Thu, Oct 8, 2009 at 12:42 AM, Caroline Meeks<br>
<<a href="mailto:caroline@solutiongrove.com" target="_blank">caroline@solutiongrove.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We ran into a bug at GPA where we made a new spin and it ended up with a<br>
newer version of the Kernel then the boothelper had. The result was<br>
everything worked fine, except networking. It took us a long time to figure<br>
out what was wrong.<br>
Use Scenario<br>
1. We send kids home with computers and CDs and then a few months or a year<br>
later the school upgrades SoaS. We can send home new CDs but its quite<br>
likely that there will be confusion and some people will use the wrong CD.<br>
2. A day care center serves several elementary schools. At some point the<br>
schools are running different versions. (Now this would be a nice problem to<br>
have!).<br>
So its not a critical issue but its worth thinking about.<br>
There is a solution, Bill found a different kind of boot helper that boots<br>
one kernel then boots the USB. The issue is it takes about a minute longer<br>
then the current boot-helper. I'm not sure if its worth the tradeoff or<br>
not. It maybe in some cases.<br>
<br>
--<br>
Caroline Meeks<br>
Solution Grove<br>
Caroline@SolutionGrove.com<br>
<br>
617-500-3488 - Office<br>
505-213-3268 - Fax<br>
</blockquote></blockquote>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Caroline Meeks<br>Solution Grove<br>Caroline@SolutionGrove.com<br><br>617-500-3488 - Office<br>505-213-3268 - Fax<br>