after booting soas-1 on a XO or QEMU, stuff breaks in other platforms

[tomeu]

Because on boot we write /etc/X11/xorg.conf and /home/liveuser/.Xresources based on the architecture.

[tvoverbeek]

Wanted to report the same defect, but Tomeu beat me to it.

Some more information. The writing of xorg.conf is done in /etc/rc.d/init.d/livesys
and /etc/rc.d/init.d/livesys-late (Soas-200903051021).
The creation of /.livesys-configured and /.livesys-late-configured prevents
the re-execution when the same SoaS stick is booted on a different computer.

For QEMU no specific xorg.conf is needed. At least for me the auto detection
by the X-server works fine when running under QEMU for Windows. It recognizes
the cirrus card and starts Sugar. So maybe the QEMU specific xorg.conf can be removed.

Anyway, the livesys and livesys-late scripts should be reviewed carefully for
the use case of using the same stick booting on various computers with different
hardware. Currently the scripts inplicitly assumes they are always booting on the same computer.

[wadeb]

Interesting...What is the point of creating those *-configured files? I would assume that a LiveCD would never want to make assumptions about what it's booted on.

Perhaps the *-configured files were assumed to not be in persistent storage.

-Wade

[wadeb]

Not Sugar milestone related. Feel free to add a SoaS milestone if appropriate.

[sascha_silbe]

Bulk change distribution=SoaS -> component=SoaS

[bernie]

Is this bug still relevant?

[sdz]

Depends on whether somebody actually cares about supporting it on the XO. :)

Last time I tried a couple of days ago, the SoaS 3 snapshots wouldn't even boot on the XO-1 with a kernel panic.

[sdz]

Sugar on a Stick Mirabelle is currently marked as unsupported on the XO and won't work. We'd appreciate any help. However, there's not much we can do right now with our limited resources. I'm closing this for now.