[Sugar-devel] Soas snapshot

[Marco Pesenti Gritti]

On Mon, Feb 2, 2009 at 3:22 AM, Gary C Martin <gary at garycmartin.com> wrote:
> Yep, that would be great. Perhaps a sensitive question, but should 'we' now
> start to forget joyride and focus on images coming out of the SoaS effort?

I think Chris was thinking along these lines in irc but... I'll let
him answer this :)

>>> * boot felt slow, but usable as is (~2min on subsequent boots).
>>
>> I wonder how it does compare to joyride builds.
>
> Let me flash the nand back back to joyride (2639) and time it... OK, avg
> over 3 boots was joyride = 90sec (with full G1G1 activity/library data) vs.
> SoaS1 = 130sec.

OK, thanks. It looks like there are several services we can turn off
if nothing else. HAL seems very slow to start for some reason also.

>>> * some nasty stripy/bitty/strobing screens during boot cycle, but didn't
>>> last too long.
>>
>> When starting up X?
>
> Yes, as it hits X, it seemed worse on first boot (before name and colour UI
> requests), on subsequent boots it's 1-2sec of vibrating pixel gibberish
> before the screen blacks out prior to sugar cursor showing up.

It would be good to report this to Fedora bugzilla.

>>> * all UI fonts are horrendously small, some dpi magic desperately needed
>>> :-)
>>
>> Can you open a ticket under the SoaS component, I'm not sure exactly
>> what is going on here, should be easy to fix anyway.
>
> Done:
>
>        http://dev.sugarlabs.org/ticket/282

I figured out what is wrong here, hopefully a new image will be out
tonight or tomorrow.

>>> * fair selection of starter/essential Activities installed (I've not
>>> re-tested all actually work yet), significant ones missing (for testing
>>> and
>>> education) are read, record, the tamtam suite, speak, colors! (for
>>> testing/showing collaborative painting), image viewer (which may be the
>>> new
>>> default for showing images).
>>
>> We need to figure out which .xo just works if installed manually.
>> Those can be then trivially added to the image. And for those that
>> doesn't work we need logs, so that we can decide if it's an activity
>> problem or a system one and report it appropriately.
>
> I'd love to help here, my understanding is SoaS is for many diverse HW
> types, so I can (currently) only test for 'activity works on SoaS for XO.'
> I'll install extra activities and report back.

Most activities are not HW dependent so that would be awesome :)

Thanks a lot for the help!

Marco