New F11 for XO-1.5 build 32

[John Watlington]

On Oct 16, 2009, at 5:01 PM, Jerry Vonau wrote:

> On Tue, 2009-10-13 at 19:09 -0400, Chris Ball wrote:
>> http://wiki.laptop.org/go/F11_for_1.5
>> http://dev.laptop.org/~cjb/f11-1.5/os32
>>
>> Compressed image size: 396.18mb (+7.32mb since build 31)
>>
>> Description of changes in this build:
>> * now boots automatically, instead of dropping to ok prompt
>> * wifi stays up and associated across a suspend/resume cycle
>> * there's now a ".zd" file, which you can flash to internal SD  
>> from OFW with:
>>     ok fs-update ext:\os32.zd
>>
>
> Being an OFW novice I opted to build a multi-boot olpc.fth to be  
> able to
> boot the internal/external mmc slots or usb. I didn't want to mess
> around with the internal olpc.fth, just yet, for fear of messing  
> that up
> while testing. I just created a USB "boot-disk" with below olpc.fth
> file:
>
> http://members.shaw.ca/jvonau/pub/olpc.fth
cool.

> Not sure if option 4 is valid anymore...
>
> Perhaps this could be made available by default in the install?
> Just a choice between internal/external would be enough, to enable
> testing of a second image.

This is the subject of Trac ticket 9457:
http://dev.laptop.org/ticket/9457

The expected usage model for an XO is that if there is a bootable
image on the external SD card or USB, it will be booted.   If you
want to boot from the internal SD card, either remove the external SD
card or the bootable image installed on it.

I don't think we want to change this model.

This is currently broken, due to the way that the kernel names
devices.   I believe that the proposed solution was to use udev
in the initramfs image to provide stable names.

> Should be able to use filesystem labels here also. LABEL=OLPCRoot for
> the internal, maybe OLPCRoot2 for the external. That would leave just
> labeling the filesystem to the tester.

Can't use filesystem labels, as we are frequently testing standard
builds (an older one on the internal card, and a newer one on the
external one.)   Since we distribute disk images, both will have the
same label by default.

Cheers,
wad