[SoaS] The boot helper CDs will be a maintainability issue
caroline at solutiongrove.com
Mon Oct 19 10:03:48 EDT 2009
On Thu, Oct 8, 2009 at 4:11 PM, Sebastian Dziallas <sebastian at when.com>wrote:
> Sean DALY wrote:
>> Could this be solved by branding, linking a boot helper to a SoaS
>> version? Strawberry helper, Blueberry helper?
> 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.
> 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:
> 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).
> 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.
> 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? ;)
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.
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.
Effort, but should not be impossible.
Any thoughts on how to make it easier?
> Mike Lee did amazing CD labels.
>> It's quite a bit cheaper to press runs of CDs than USB sticks, even
>> with 4-color disc labels.
>> On Thu, Oct 8, 2009 at 12:42 AM, Caroline Meeks
>> <caroline at solutiongrove.com> wrote:
>>> We ran into a bug at GPA where we made a new spin and it ended up with a
>>> newer version of the Kernel then the boothelper had. The result was
>>> everything worked fine, except networking. It took us a long time to
>>> out what was wrong.
>>> Use Scenario
>>> 1. We send kids home with computers and CDs and then a few months or a
>>> later the school upgrades SoaS. We can send home new CDs but its quite
>>> likely that there will be confusion and some people will use the wrong
>>> 2. A day care center serves several elementary schools. At some point the
>>> schools are running different versions. (Now this would be a nice problem
>>> So its not a critical issue but its worth thinking about.
>>> There is a solution, Bill found a different kind of boot helper that
>>> one kernel then boots the USB. The issue is it takes about a minute
>>> then the current boot-helper. I'm not sure if its worth the tradeoff or
>>> not. It maybe in some cases.
>>> Caroline Meeks
>>> Solution Grove
>>> Caroline at SolutionGrove.com
>>> 617-500-3488 - Office
>>> 505-213-3268 - Fax
Caroline at SolutionGrove.com
617-500-3488 - Office
505-213-3268 - Fax
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SoaS