[Testing] Bug report - SoaS-Beta iso conversion
Mikus Grinbergs
mikus at bga.com
Sun May 3 22:10:17 EDT 2009
> This page, http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_Ubuntu, refers to
> installing a package,
I've now looked at that page - still don't understand how it would
help me. I think what it describes is fashioning a system (on
stick) on which the underlying operating system is Ubuntu, with
Sugar as an installed Window Manager (with Activities) on top of that.
I don't want Ubuntu as the underlying operating system; I want
fedora-11 (rawhide) to be the underlying operating system when my
XO-1 is booted. So I don't think that webpage applies to what I
want to do. The principal advice that page gives is to use System
-> Administration -> Create a USB startup disk -- but if script
'livecd-iso-to-disk' works (see below), I see no need to do that.
[Before I ever started, I did make sure the packages mentioned on
page http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation/OLPC
were installed on the system I ran the conversion on.]
> apt-get --force-yes -y install sugar-* squashfs-tools
> that may provide the missing functionality.
Thank you. As Tabitha wrote, if there are packages that the
'livecd-iso-to-xo' script needs, they should be documented.
After I installed the package 'squashfs-tools' on my Jaunty system,
script 'livecd-iso-to-disk' ran to completion (though giving out all
those error messages, plus an error pop-up window by Ubuntu saying
"Unable to mount media"). Script 'livecd-iso-to-xo' still fails,
the same way as Tabitha described it.
I *really* don't want to install 'sugar-*' on my Ubuntu system - so
I shall not be trying that.
At least now I can boot the latest Soas2 20090503 from an USB stick.
On my XO-1, its text characters need a magnifying glass to be seen.
The first thing I had to do was to add '14' to the line "font = " in
file .sugar/default/terminalrc, then go to Home -> My Settings ->
Frame and fool with the Activation Delay -- that offered me a
(Sugar) restart, which I took. The result is that the text
characters in Terminal can now be seen (though they're still faint).
mikus
More information about the Testing
mailing list