[SoaS] Physics fails in SoaS-34

[Frederick Grose]

See https://bugs.sugarlabs.org/ticket/4999
logs attached there.

>From Physics log:
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
562, in do_get_preferred_height
surface = self._buffer.get_surface()
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
370, in get_surface
handle = self._load_svg(icon_info.file_name)
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
197, in _load_svg
return self._loader.load(file_name, entities, self.cache)
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
140, in load
return Rsvg.Handle.new_from_data(icon.encode('utf-8'))
gi.repository.GLib.Error: rsvg-error-quark: XML parse error: error code=201
(3) in (null):22:40: Namespace prefix inkscape for connector-curvature on
path is not defined
 (0)
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
574, in do_get_preferred_width
surface = self._buffer.get_surface()
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
370, in get_surface
handle = self._load_svg(icon_info.file_name)
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
197, in _load_svg
return self._loader.load(file_name, entities, self.cache)
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
140, in load
return Rsvg.Handle.new_from_data(icon.encode('utf-8'))
gi.repository.GLib.Error: rsvg-error-quark: XML parse error: error code=201
(3) in (null):22:40: Namespace prefix inkscape for connector-curvature on
path is not defined
 (0)
Traceback (most recent call last):
  File "/usr/lib64/python3.9/site-packages/gi/_propertyhelper.py", line
401, in obj_set_property
prop.fset(self, value)
  File "/usr/lib/python3.9/site-packages/sugar3/activity/activity.py", line
612, in set_active
self.save()
  File "/usr/lib/python3.9/site-packages/sugar3/activity/activity.py", line
978, in save
self.write_file(file_path)
  File "/usr/share/sugar/activities/Physics.activity/activity.py", line
129, in write_file
self.game.write_file(file_path)
  File "/usr/share/sugar/activities/Physics.activity/physics.py", line 78,
in write_file
self.world.add.remove_mouseJoint()
AttributeError: 'PhysicsGame' object has no attribute 'world'
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
587, in do_draw
surface = self._buffer.get_surface(sensitive, self)
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
370, in get_surface
handle = self._load_svg(icon_info.file_name)
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
197, in _load_svg
return self._loader.load(file_name, entities, self.cache)
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
140, in load
return Rsvg.Handle.new_from_data(icon.encode('utf-8'))
gi.repository.GLib.Error: rsvg-error-quark: XML parse error: error code=201
(3) in (null):22:40: Namespace prefix inkscape for connector-curvature on
path is not defined
 (0)
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
587, in do_draw
surface = self._buffer.get_surface(sensitive, self)
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
370, in get_surface
handle = self._load_svg(icon_info.file_name)
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
197, in _load_svg
return self._loader.load(file_name, entities, self.cache)
  File "/usr/lib/python3.9/site-packages/sugar3/graphics/icon.py", line
140, in load
return Rsvg.Handle.new_from_data(icon.encode('utf-8'))
gi.repository.GLib.Error: rsvg-error-quark: XML parse error: error code=201
(3) in (null):22:40: Namespace prefix inkscape for connector-curvature on
path is not defined
 (0)
Terminated by signal 11, pid 1876 activity_id
fe77a8a253d76ced8ef2f6955bfa91a4cca2
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] SoaS 32 on iMac

[Frederick Grose]

On Thu, Apr 30, 2020 at 5:52 PM Alex Perez  wrote:

> Correct, this is a function of multiple audio outputs, and how they are
> enumerated. I have verified that SoaS boots and runs, with sound and no
> changes required, on an old iMac5,2, form 2007. As an aside, this is one of
> those weird Apple-manufactured 32-bit EFI machines (but 64-bit CPUs).
>

Alex,  When you say "that SoaS boots and runs," do you mean the SoaS livecd
or iso file, or do you mean a LiveUSB/SD disk loaded with the SoaS image
such as with livecd-iso-to-disk or with dd.  Please specify what was
verified.  Also, please tell us which special keys had to be pressed during
boot, if any.   Thanks!
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] SoaS 32 is silent?

[Frederick Grose]

So I found that SoaS and Fedora Workstation, at least, have the audio
output sink default on card/port index 1 instead of the convention of index
0.
Where and how this goes this way, I don't know.  But it happens on more
than one system.

I've updated the bug report, https://bugs.sugarlabs.org/ticket/4998.

A workaround is to use the PulseAudio command,
$ pacmd set-default-sink 0


On Tue, Apr 28, 2020 at 4:36 AM Peter Robinson  wrote:

> > With Fedora-SoaS-Live-x86_64-32-1.6.iso I'm hearing no sound.
> > And see no log messages.
> >
> > Is this a common problem?
>
> Ultimately in this cycle in particular an awful lot changed, we moved
> completely from python2 -> python3 among a lot of other changes.
>
> For me the Speak activity works for me on a VM and that's my usual
> go-to sound tester as I don't need to find any media to play.
>
> Things like sound are very complex, multiple output, defaults,
> different hardware. Some level of detail of the hardware and the setup
> is useful to even begin to know what the issue may be, is there any
> errors in dmesg etc.
>
> Peter
>
> > --
> > From: James Cameron 
> > Date: Mon, Apr 27, 2020 at 8:04 PM
> > To: Frederick Grose 
> > Cc: Development of live Sugar distributions ,
> Sugar-dev Devel 
> >
> >
> > I've no idea about your sound problem.  It doesn't happen for me on
> > Debian or Ubuntu.  I get sound from Speak and Music Keyboard.  I get
> > sound into Measure.
> >
> > For not seeing any log messages; Python 3 holds messages in process
> > memory and does not flush logs.  Another layer of buffering.
> >
> > Log files in .sugar/default/logs should be read after stopping the
> > program that writes to them.
> >
> > For activity logs, you have to stop the activity and confirm with
> > Frame F6 that it is stopped.
> >
> > For shell.log you have to log out and log in again.
> >
> > For datastore.log you have to log out for a couple of minutes and then
> > log in again.  Otherwise the same datastore process may be reused.
> >
> > James Cameron
> > http://quozl.netrek.org/
> >
> >
> > --
> > From: Alex Perez 
> > Date: Mon, Apr 27, 2020 at 8:11 PM
> > To: Frederick Grose 
> > Cc: Development of live Sugar distributions ,
> Sugar-dev Devel 
> >
> >
> > Frederick,
> >
> > Chances are, with the sound problem, that this is a system/Fedora
> specific problem, and has nothing to do with Sugar. You can test this
> hypothesis by downloading a different spin of RC1.6, for example the LXDE
> Live ISO, and test sound there.
> https://dl.fedoraproject.org/pub/alt/stage/32_RC-1.6/Spins/x86_64/iso/Fedora-LXDE-Live-x86_64-32-1.6.iso
> >
> > &&&&&&&&&&&&&&&&&&&&&&&&&
> >
> > Thanks for the hints.
> >
> > I tested a live USB installation of LXDE 32-1.6 and got sound for the
> music player sample.
> >
> > So probably not Fedora in general, nor Sugar, but something in the SoaS
> build.
> >
> > I've opened https://bugs.sugarlabs.org/ticket/4998 and attached the
> zipped logs from some test sessions.
> >
> >
> > ___
> > SoaS mailing list
> > SoaS@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/soas
> ___
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] SoaS 32 is silent?

[Frederick Grose]

On Mon, Apr 27, 2020 at 11:18 PM James Cameron  wrote:

> On Mon, Apr 27, 2020 at 10:25:28PM -0400, Frederick Grose wrote:
> > I've opened https://bugs.sugarlabs.org/ticket/4998 and attached the
> > zipped logs from some test sessions.
>
> Thanks.  I've reviewed the logs.  They show successful playback by
> GStreamer into a sound sink of some sort, but no indication as to why
> you did not hear anything.
>
> There's no feedback loop in the Sugar sound subsystem; there's no way
> to tell in software if a sound sink can be heard by a human.
>
> Was your test in a virtual machine or physical hardware?
>

Testing is on physical hardware.  Fedora-SoaS-Live-x86_64-32-1.6.iso was
installed
with livecd-iso-to-disk to a USB disk drive.

I also tested a pristine image by booting the .iso file directly.  Logs are
attached to the
referenced bug report.

> Was the Frame F6 used to check the speaker icon is present, not white,
> and set to an appropriate level?
>

Yes, yes, and yes.

> --
> James Cameron
> http://quozl.netrek.org/


Thanks for your interest, efforts, & applied experience!

   --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] SoaS 32 is silent?

[Frederick Grose]

Forwarded Conversation
From: Frederick Grose 
Date: Mon, Apr 27, 2020 at 2:50 PM
To: Development of live Sugar distributions 
Cc: Sugar-dev Devel 


With Fedora-SoaS-Live-x86_64-32-1.6.iso I'm hearing no sound.
And see no log messages.

Is this a common problem?


--
From: James Cameron 
Date: Mon, Apr 27, 2020 at 8:04 PM
To: Frederick Grose 
Cc: Development of live Sugar distributions ,
Sugar-dev Devel 


I've no idea about your sound problem.  It doesn't happen for me on
Debian or Ubuntu.  I get sound from Speak and Music Keyboard.  I get
sound into Measure.

For not seeing any log messages; Python 3 holds messages in process
memory and does not flush logs.  Another layer of buffering.

Log files in .sugar/default/logs should be read after stopping the
program that writes to them.

For activity logs, you have to stop the activity and confirm with
Frame F6 that it is stopped.

For shell.log you have to log out and log in again.

For datastore.log you have to log out for a couple of minutes and then
log in again.  Otherwise the same datastore process may be reused.

James Cameron
http://quozl.netrek.org/


--
From: Alex Perez 
Date: Mon, Apr 27, 2020 at 8:11 PM
To: Frederick Grose 
Cc: Development of live Sugar distributions ,
Sugar-dev Devel 


Frederick,

Chances are, with the sound problem, that this is a system/Fedora specific
problem, and has nothing to do with Sugar. You can test this hypothesis by
downloading a different spin of RC1.6, for example the LXDE Live ISO, and
test sound there.
https://dl.fedoraproject.org/pub/alt/stage/32_RC-1.6/Spins/x86_64/iso/Fedora-LXDE-Live-x86_64-32-1.6.iso

&&&&&&&&&&&&&&&&&&&&&&&&&

Thanks for the hints.

I tested a live USB installation of LXDE 32-1.6 and got sound for the music
player sample.

So probably not Fedora in general, nor Sugar, but something in the SoaS
build.

I've opened https://bugs.sugarlabs.org/ticket/4998 and attached the zipped
logs from some test sessions.
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Fedora 32 Final is GO, SoaS Release Candidate ISO available immediately

[Frederick Grose]

With Fedora-SoaS-Live-x86_64-32-1.6.iso I'm hearing no sound.
And see no log messages.

Is this a common problem?

On Thu, Apr 23, 2020 at 2:21 PM Alex Perez  wrote:

> The Fedora release team met today and approved the release of Fedora 32,
> which is scheduled for this coming Tuesday, April 28th.
>
> The 1.6 Release Candidate ISO for the Fedora 32 SoaS (Sugar on a Stick)
> LiveCD/ISO is downloadable from
> https://bit.ly/Fedora-32-RC-SoaS-LiveISO-x86_64
> It is one gigabyte in size.
>
> This is a purely Python 3 based Sugar environment, and Python 2 activities
> will not run here at all. This is the first version of Sugar on a Stick to
> drop Python 2 completely, and a few of the bundled activities which have
> yet to be ported to Python 3 were removed from this release, and will
> re-appear at which point the porting and testing of them is complete.
>
> Special thanks to Peter Robinson and Ibiam Chihurumnaya for making the
> Sugar-specific bits of this spin possible.
> ___
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] [Sugar-devel] Sugar on a Stick

[Frederick Grose]

corrected typo

On Tue, Jan 1, 2019 at 5:19 PM Frederick Grose  wrote:

> From https://wiki.sugarlabs.org/go/Sugar_on_a_Stick#Known_bugs
>
>- Reboot returns to initial start Name screen sequence, and no
>neighbors in Neighborhood view with jabber.sugarlabs.org,Wait for
>updates or next version; orTry applying this edit from a Terminal or
>console session,sudo sed -i 's/DSA/OPENSSH/'
>/usr/lib/python2.7/site-packages/sugar3/profile.pyWas caused by the
>OpenSSH project,See also #4991 <http://bugs.sugarlabs.org/ticket/4991>
>, #4992 <http://bugs.sugarlabs.org/ticket/4992>, and sugar#814
><https://github.com/sugarlabs/sugar/issues/814>
>
>
>
>
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] [Sugar-devel] Sugar on a Stick

[Frederick Grose]

>From https://wiki.sugarlabs.org/go/Sugar_on_a_Stick#Known_bugs

   - Reboot returns to initial start Name screen sequence, and no neighbors
   in Neighborhood view with jabber.sugarlabs.org,Wait for updates or next
   version; orTry applying this edit from a Terminal or console session,sudo
   sed -i 's/DSA/OPENSSL/'
/usr/lib/python2.7/site-packages/sugar3/profile.pyWas
   caused by the OpenSSH project,See also #4991
   , #4992
   , and sugar#814
   
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] [Sugar-devel] Help soas is not building in fedora30 rawhide

[Frederick Grose]

On Thu, Nov 15, 2018 at 5:03 PM Thomas Gilliard  wrote:
>
> Helpsoas is not building in fedora30 rawhide

The livemedia.log shows this error report:
...
2018-11-16 17:02:07,578 INFO pylorax: Non interactive installation failed:
2018-11-16 17:02:07,579 INFO pylorax: Problem: conflicting requests
2018-11-16 17:02:07,579 INFO pylorax: - nothing provides
ld-linux-armhf.so.3 needed by sugar-pippy-72-1.fc30.x86_64
2018-11-16 17:02:07,579 INFO pylorax: - nothing provides
ld-linux-armhf.so.3(GLIBC_2.4) needed by sugar-pippy-72-1.fc30.x86_64
2018-11-16 17:02:07,579 INFO pylorax: - nothing provides
libgcc_s.so.1(GCC_3.5) needed by sugar-pippy-72-1.fc30.x86_64
2018-11-16 17:02:07,579 INFO pylorax: - nothing provides
libstdc++.so.6(CXXABI_ARM_1.3.3) needed by
sugar-pippy-72-1.fc30.x86_64.
2018-11-16 17:02:07,579 INFO pylorax:
2018-11-16 17:02:07,579 INFO pylorax: The installer will now terminate.
...
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Some new bug tickets

[Frederick Grose]

On Fri, Oct 26, 2018 at 1:18 AM James Cameron  wrote:

> Interesting thing in your logs; once a network connection is available,
> some of the activities are updated automatically


Not automatically, I purposely ran the control panel updater to test the
newer versions.

Thanks for reviewing the logs.

because there are
> newer versions released; means you aren't testing the activity as
> supplied with SoaS.
>
> --
> James Cameron
> http://quozl.netrek.org/
> ___
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] Some new bug tickets

[Frederick Grose]

   - Ticket #4993 (bugs.sugarlabs.org: Error while sending notifications)
   This notice was observed on submitting a bug ticket: Warning: The …
   - Ticket #4992 (No neighbors in Neighborhood view with
   jabber.sugarlabs.org) Observed in Fedora-SoaS-Live-x86_64-29-1.2.iso
   installed to a LiveUSB.
   - Ticket #4991 (Reboot returns to initial start Name screen sequence)
   Observed in Fedora-SoaS-Live-x86_64-29-1.2.iso installed to a LiveUSB. …
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] Bug: Network control panel fails to open

[Frederick Grose]

There is a glitch observed in SoaS 29.
https://bugs.sugarlabs.org/ticket/4990
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Browse fails to launch in SoaS Fedora 27 beta

[Frederick Grose]

On Sun, Oct 29, 2017 at 4:01 AM, Peter Robinson <pbrobin...@gmail.com>
wrote:

> On Sat, Oct 28, 2017 at 4:26 PM, Frederick Grose <fgr...@gmail.com> wrote:
> > After updating SoaS Fedora 27 beta with downloaded
> > sugar-*-0.110.0-6.fc27.noarch.rpm, sugar launches but Browse fails to.
>
> You really start to need to test this all of this stuff on a more
> regular basis, and preferably before Beta.
>
> Can someone file a bug report so we can request freeze exception?
>

​https://bugzilla.redhat.com/show_bug.cgi?id=1507292
​

>
> > Here is the log:
> > /usr/lib/python2.7/site-packages/sugar3/activity/activity.py:96:
> > PyGIWarning: SugarExt was imported without specifying a version first.
> Use
> > gi.require_version('SugarExt', '1.0') before import to ensure that the
> right
> > version gets loaded. from gi.repository import SugarExt Traceback (most
> > recent call last): File "/usr/bin/sugar-activity", line 220, in 
> > main() File "/usr/bin/sugar-activity", line 164, in main module =
> > __import__(module_name) File
> > "/usr/share/sugar/activities/Browse.activity/webactivity.py", line 58,
> in
> >  from collabwrapper.collabwrapper import CollabWrapper
> ImportError:
> > No module named collabwrapper.collabwrapper Exited with status 1, pid
> 2117
> > data (', mode 'w' at 0x7f7e96f0f0c0>,
> > '688cd1c0f3e7f674ceff5e6516598ab17dac0048')
> >
> >
> > ___
> > SoaS mailing list
> > SoaS@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/soas
> >
> ___
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] SoaS Fedora 27 beta fails to launch Sugar session

[Frederick Grose]

On Mon, Oct 23, 2017 at 6:39 PM, James Cameron <qu...@laptop.org> wrote:

> On Mon, Oct 23, 2017 at 06:13:51PM -0400, Frederick Grose wrote:
> > On Mon, Oct 23, 2017 at 6:03 PM, James Cameron <[1]qu...@laptop.org>
> wrote:
> > Familiar.  Looks like RHBZ #1490668.
> > https://bugzilla.redhat.com/show_bug.cgi?id=1490668
> >
> > Sugar doesn't log to systemd journal, so best log file is still
> > ~/.sugar/default/logs/shell.log ... is that file present?
> >
> > On Mon, Oct 23, 2017 at 05:38:21PM -0400, Frederick Grose wrote:
> > > Tested with Fedora-SoaS-Live-x86_64-27-20171023.n.0.iso (similar
> failure
> > > on Fedora-SoaS-Live-x86_64-27_Beta-1.5.iso)
> > >
> > > The image boots to the liveuser login screen but fails to
> > > launch into the Sugar session.
> > >
> > > journalctl -ab -o short-monotonic > soas27bootjournal.txt
> > >
> > > https://gist.github.com/FGrose/97d834d362c7e1e3f690b97612c673dd
> > >
> > > The lightdm lines look suspicious to me...
> > >
> > > ​$ grep lightdm /home/fgrose/Documents/soas27bootjournal.txt
> > >
> > > [...]
> > >
> >
> > ​Yes,
> > Traceback (most recent call last):
> >   File "/usr/lib64/python2.7/runpy.py", line 174, in _run_module_as_main
> > "__main__", fname, loader, pkg_name)
> >   File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
> > exec code in run_globals
> >   File "/usr/lib/python2.7/site-packages/jarabe/main.py", line 73, in
> 
> > from jarabe.view import keyhandler
> >   File "/usr/lib/python2.7/site-packages/jarabe/view/keyhandler.py",
> line 32,
> > in 
> > from jarabe.journal import journalactivity
> >   File "/usr/lib/python2.7/site-packages/jarabe/journal/journalacti
> vity.py",
> > line 45, in 
> > from jarabe.journal.volumestoolbar import VolumesToolbar
> >   File "/usr/lib/python2.7/site-packages/jarabe/journal/volumestool
> bar.py",
> > line 42, in 
> > from jarabe.view.palettes import VolumePalette
> >   File "/usr/lib/python2.7/site-packages/jarabe/view/palettes.py", line
> 38, in
> > 
> > from jarabe.view.viewhelp import setup_view_help
> >   File "/usr/lib/python2.7/site-packages/jarabe/view/viewhelp.py", line
> 46, in
> > 
> > from jarabe.view.viewhelp_webkit2 import Browser
> > ImportError: No module named viewhelp_webkit2
>
> Thanks.
>
> The ImportError suggests file viewhelp_webkit2.py is missing; can you
> confirm that?  It should be right next to
> /usr/lib/python2.7/site-packages/jarabe/view/viewhelp.py
>

​ ls -la usr/lib/python2.7/site-packages/jarabe/view/
total 432
drwxr-xr-x.  2 root root  4096 Oct 23 08:17 .
drwxr-xr-x. 11 root root  4096 Oct 23 08:17 ..
-rw-r--r--.  1 root root  2028 Aug 12 08:30 alerts.py
-rw-r--r--.  2 root root  2647 Aug 12 08:30 alerts.pyc
-rw-r--r--.  2 root root  2647 Aug 12 08:30 alerts.pyo
-rw-r--r--.  1 root root  2754 Aug 12 08:30 buddyicon.py
-rw-r--r--.  2 root root  3008 Aug 12 08:30 buddyicon.pyc
-rw-r--r--.  2 root root  3008 Aug 12 08:30 buddyicon.pyo
-rw-r--r--.  1 root root  8687 Aug 12 08:30 buddymenu.py
-rw-r--r--.  2 root root  9396 Aug 12 08:30 buddymenu.pyc
-rw-r--r--.  2 root root  9396 Aug 12 08:30 buddymenu.pyo
-rw-r--r--.  1 root root  1728 Aug 12 08:30 cursortracker.py
-rw-r--r--.  2 root root  1330 Aug 12 08:30 cursortracker.pyc
-rw-r--r--.  2 root root  1330 Aug 12 08:30 cursortracker.pyo
-rw-r--r--.  1 root root  7418 Aug 12 08:30 customizebundle.py
-rw-r--r--.  2 root root  6241 Aug 12 08:30 customizebundle.pyc
-rw-r--r--.  2 root root  6241 Aug 12 08:30 customizebundle.pyo
-rw-r--r--.  1 root root  2473 Aug 12 08:30 gesturehandler.py
-rw-r--r--.  2 root root  2896 Aug 12 08:30 gesturehandler.pyc
-rw-r--r--.  2 root root  2896 Aug 12 08:30 gesturehandler.pyo
-rw-r--r--.  1 root root   677 Aug 12 08:30 __init__.py
-rw-r--r--.  2 root root   143 Aug 12 08:30 __init__.pyc
-rw-r--r--.  2 root root   143 Aug 12 08:30 __init__.pyo
-rw-r--r--.  1 root root  8290 Aug 12 08:30 keyhandler.py
-rw-r--r--.  2 root root  9438 Aug 12 08:30 keyhandler.pyc
-rw-r--r--.  2 root root  9438 Aug 12 08:30 keyhandler.pyo
-rw-r--r--.  1 root root  6044 Aug 12 08:30 launcher.py
-rw-r--r--.  2 root root  6752 Aug 12 08:30 launcher.pyc
-rw-r--r--.  2 root root  6752 Aug 12 08:30 launcher.pyo
-rw-r--r--.  1 root root 11282 Aug 12 08:30 palettes.py
-rw-r--r--.  2 root root 12132 Aug 12 08:30 palettes.pyc
-rw-r--r--.  2 root root 12132 Aug 12 08:30 palettes.pyo
-rw-r--r--.  1 root root  7262 Aug 12 08:30 

Re: [SoaS] SoaS Fedora 27 beta fails to launch Sugar session

[Frederick Grose]

On Mon, Oct 23, 2017 at 6:03 PM, James Cameron <qu...@laptop.org> wrote:

> Familiar.  Looks like RHBZ #1490668.
> https://bugzilla.redhat.com/show_bug.cgi?id=1490668
>
> Sugar doesn't log to systemd journal, so best log file is still
> ~/.sugar/default/logs/shell.log ... is that file present?
>
> On Mon, Oct 23, 2017 at 05:38:21PM -0400, Frederick Grose wrote:
> > Tested with Fedora-SoaS-Live-x86_64-27-20171023.n.0.iso (similar failure
> > on Fedora-SoaS-Live-x86_64-27_Beta-1.5.iso)
> >
> > The image boots to the liveuser login screen but fails to launch into
> the Sugar
> > session.
> >
> > journalctl -ab -o short-monotonic > soas27bootjournal.txt
> >
> > [1]https://gist.github.com/FGrose/97d834d362c7e1e3f690b97612c673dd
> >
> > The lightdm lines look suspicious to me...
> >
> > ​$ grep lightdm /home/fgrose/Documents/soas27bootjournal.txt
> >
> > [...]
> >
> > ___
> > SoaS mailing list
> > SoaS@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/soas
>
>
> --
> James Cameron
> http://quozl.netrek.org/
> ___
> SoaS mailing list
> SoaS@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>

​Yes,
Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File "/usr/lib/python2.7/site-packages/jarabe/main.py", line 73, in

from jarabe.view import keyhandler
  File "/usr/lib/python2.7/site-packages/jarabe/view/keyhandler.py", line
32, in 
from jarabe.journal import journalactivity
  File
"/usr/lib/python2.7/site-packages/jarabe/journal/journalactivity.py", line
45, in 
from jarabe.journal.volumestoolbar import VolumesToolbar
  File "/usr/lib/python2.7/site-packages/jarabe/journal/volumestoolbar.py",
line 42, in 
from jarabe.view.palettes import VolumePalette
  File "/usr/lib/python2.7/site-packages/jarabe/view/palettes.py", line 38,
in 
from jarabe.view.viewhelp import setup_view_help
  File "/usr/lib/python2.7/site-packages/jarabe/view/viewhelp.py", line 46,
in 
from jarabe.view.viewhelp_webkit2 import Browser
ImportError: No module named viewhelp_webkit2

​
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] SoaS Fedora 27 beta fails to launch Sugar session

[Frederick Grose]

Tested with Fedora-SoaS-Live-x86_64-27-20171023.n.0.iso (similar failure
on Fedora-SoaS-Live-x86_64-27_Beta-1.5.iso)

The image boots to the liveuser login screen but fails to launch into the
Sugar session.

journalctl -ab -o short-monotonic > soas27bootjournal.txt

https://gist.github.com/FGrose/97d834d362c7e1e3f690b97612c673dd


The lightdm lines look suspicious to me...

​$ grep lightdm /home/fgrose/Documents/soas27bootjournal.txt

[   37.710959] localhost-live audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?
addr=? terminal=? res=success'
[   39.271418] localhost-live lightdm[1324]: g_object_unref: assertion
'G_IS_OBJECT (object)' failed
[   39.328065] localhost-live audit[1378]: USER_AUTH pid=1378 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023
msg='op=PAM:authentication grantors=pam_permit acct="liveuser"
exe="/usr/sbin/lightdm" hostname=? addr=? terminal=:0 res=success'
[   39.332199] localhost-live audit[1378]: USER_ACCT pid=1378 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023
msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="liveuser"
exe="/usr/sbin/lightdm" hostname=? addr=? terminal=:0 res=success'
[   39.334772] localhost-live lightdm[1324]: g_object_unref: assertion
'G_IS_OBJECT (object)' failed
[   39.335508] localhost-live audit[1378]: CRED_ACQ pid=1378 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023
msg='op=PAM:setcred grantors=pam_permit acct="liveuser"
exe="/usr/sbin/lightdm" hostname=? addr=? terminal=:0 res=success'
[   39.360390] localhost-live audit[1378]: USER_ROLE_CHANGE pid=1378 uid=0
auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='pam:
default-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
selected-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
exe="/usr/sbin/lightdm" hostname=? addr=? terminal=:0 res=success'
[   39.921638] localhost-live audit[1378]: USER_START pid=1378 uid=0
auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023
msg='op=PAM:session_open
grantors=pam_selinux,pam_loginuid,pam_limits,pam_selinux,pam_keyinit,pam_namespace,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_lastlog
acct="liveuser" exe="/usr/sbin/lightdm" hostname=? addr=? terminal=:0
res=success'
[   39.921686] localhost-live audit[1378]: USER_LOGIN pid=1378 uid=0
auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=login
id=1000 exe="/usr/sbin/lightdm" hostname=localhost-live addr=?
terminal=/dev/tty1 res=success'
[   39.922024] localhost-live lightdm[1378]:
pam_unix(lightdm-autologin:session): session opened for user liveuser by
(uid=0)
[   43.517645] localhost-live audit[1378]: USER_LOGOUT pid=1378 uid=0
auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=logout
id=1000 exe="/usr/sbin/lightdm" hostname=localhost-live addr=?
terminal=/dev/tty1 res=success'
[   43.520204] localhost-live lightdm[1378]:
pam_unix(lightdm-autologin:session): session closed for user liveuser
[   43.520493] localhost-live audit[1378]: USER_END pid=1378 uid=0
auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023
msg='op=PAM:session_close
grantors=pam_selinux,pam_loginuid,pam_limits,pam_selinux,pam_keyinit,pam_namespace,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_lastlog
acct="liveuser" exe="/usr/sbin/lightdm" hostname=? addr=? terminal=:0
res=success'
[   43.520540] localhost-live audit[1378]: CRED_DISP pid=1378 uid=0
auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023
msg='op=PAM:setcred grantors=pam_permit acct="liveuser"
exe="/usr/sbin/lightdm" hostname=? addr=? terminal=:0 res=success'
[   44.222881] localhost-live lightdm[1324]: g_object_unref: assertion
'G_IS_OBJECT (object)' failed
[   44.234779] localhost-live audit[1612]: CRED_ACQ pid=1612 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023
msg='op=PAM:setcred grantors=pam_env,pam_permit acct="lightdm"
exe="/usr/sbin/lightdm" hostname=? addr=? terminal=:0 res=success'
[   44.234876] localhost-live lightdm[1612]:
pam_unix(lightdm-greeter:session): session opened for user lightdm by
(uid=0)
[   44.238478] localhost-live systemd[1]: Created slice User Slice of
lightdm.
[   44.241141] localhost-live systemd-logind[1144]: New session c1 of user
lightdm.
[   44.241653] localhost-live systemd[1]: Started Session c1 of user
lightdm.
[   44.248085] localhost-live audit[1615]: USER_ACCT pid=1615 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="lightdm"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   44.266694] localhost-live systemd[1615]:
pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
[   44.267034] localhost-live audit[1615]: USER_START pid=1615 uid=0
auid=995 ses=3 

[SoaS] Fwd: [IAEP] SoaS installation frustrations

[Frederick Grose]

See the posting below with inline suggestions.  The posting was to the IAEP
mailing list for the general Sugar audience.  I've copied the discussion
here to the SoaS list for technical followup.  Perhaps we could interest
some Google Code-In or GSOC applicants to innovate on the installation
issues.

-- Forwarded message --
From: Tony Anderson 
Date: Sat, Feb 18, 2017 at 12:18 AM
Subject: Re: [IAEP] IAEP Digest, Vol 107, Issue 15
To: i...@lists.sugarlabs.org


Consider an potential adopter who wants to try out Sugar. As Caryl knows
from Scale, an adopter wants to know:

1 - What are the capabilities of Sugar, what are its strengths, who is
using it, are there success stories, testimonials from users?
2 - How is it supported? If I were to deploy it and needed help, is it
available?
3 - How can I install it on my PC to try it out?

Going to the Sugarlabs website, the first screen features: Activities,
Wiki, Social Help. The next statement describes Sugar as a collection of
tools.
Being persistent, if you scroll down several screens, you get to a block:
Get Sugar featuring SOAS and Gnu/Linux.

For Sugar on a Stick, I am directed to another page. It starts out well -
how to make a stick with Windows (but 7). The instructions say to download
650MB and burn a CD. At this point the instructions become incoherent. They
say to mount a 2GB or more stick and then boot from the CD and start
running Sugar from it using the Terminal activity and su.

Then I am told that a change in Fedora 24 (the adopter is saying 'what's
that?') requires the use of the command:

sudo dnf install livecd-tools

No potential adopter would persist even to this point.

​>> We should go back to including the livecd-tools package in SoaS and we
should also copy the livecd-iso-to-disk script to the /LiveOS/ folder as
was previously standard in Fedora, because installing SoaS with persistent
storage is essential for the project goal of having a resumable Sugar
environment in your pocket.​

This is something Peter Robinson, our SoaS packager, can accomplish or
advise us on.

The other panel claims Sugar is available on most Gnu/Linux distributions.
The accompanying instructions from the links on this panel are even more
intimidating and provide evidence of lack of support for Sugar.

In fact, I believe that Ubuntu 16.04 enables yum install of Sugar 0.110.
This should be featured.

Like Pixel, I would like to see a current Sugar image available for
download which can be transferred to a usb stick by a single dd command.
This stick would operate as SOAS but also support installation in an
available block of hard drive on any amd_64 machine.

​>> This is currently available, but not featured in our instructions as
such an installation lacks persistence of user/learner Activities between
boots.  However, it is the easiest way to demonstrate a live SoaS system​.
Instructions should be updated.

A second image ideally would be installable as a Window application with a
supported Windows installer (like wubi did). Finally, there should be a
Debian image which can be copied to an SD card and booted by a Raspberry Pi
3 (and possibly 2).

Finally, our hypothetical adopter should find this 'get Sugar' information
on the main screen, not down six screens.

Tony

On 02/15/2017 11:20 PM, iaep-requ...@lists.sugarlabs.org wrote:

Message: 3
Date: Wed, 15 Feb 2017 21:15:05 +
From: Caryl Bigenho  
To: Bert Freudenberg  
Cc: IAEP SugarLabs  
Subject: Re: [IAEP] pixel
Message-ID:




Content-Type: text/plain; charset="utf-8"

+1 for Tony's comment!

Sent from my iPhone

On Feb 15, 2017, at 12:51 PM, Bert Freudenberg

> wrote:

On Wed, Feb 15, 2017 at 6:35 AM, Tony Anderson

> wrote:
This is what I hoped Sugarlabs would do:
https://opensource.com/article/17/1/try-raspberry-pis-pixel-os-your-pc

Tony

Isn't that exactly what SoaS does?
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation

- Bert -

__
IAEP -- It's An Education Project (not a laptop project!)
i...@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep​


For those interested alleviating these frustrations, the following links to
previous efforts provide some background:

https://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Resources​ 

https://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Goals
​
https://wiki.sugarlabs.org/go/Sugar_on_a_Stick/TODO

   --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org

Re: [SoaS] SoaS v10 TC5 tests with important activities INCLUDED in the standard distribution

[Frederick Grose]

On Thu, Dec 12, 2013 at 4:31 PM, Walter Bender walter.ben...@gmail.com wrote:
 On Thu, Dec 12, 2013 at 6:28 PM, Frederick Grose fgr...@gmail.com wrote:
 On Thu, Dec 12, 2013 at 3:30 PM, Walter Bender walter.ben...@gmail.com 
 wrote:
 On Thu, Dec 12, 2013 at 2:26 PM, Frederick Grose fgr...@gmail.com wrote:
 New failure in Physics-11Walter:

{...}


 Weird. That is a new bug. Try to grab a screen shot if you can.

Attached.


 thx

 Walter Bender
 Sugar Labs
 http://www.sugarlabs.org

Log also attached.
When the model was started the activity crashed and disappeared.

 --Fred
** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox)
1386890267.853905 WARNING root: KeepButton has been deprecated since Sugar 0.94 
and should not be used in newly written code.
1386890267.856247 WARNING root: No gtk.AccelGroup in the top level window.
1386890267.859673 WARNING root: No gtk.AccelGroup in the top level window.
1386890267.894453 WARNING root: No gtk.AccelGroup in the top level window.
1386890267.897649 WARNING root: No gtk.AccelGroup in the top level window.
1386890267.900948 WARNING root: No gtk.AccelGroup in the top level window.
1386890267.908378 WARNING root: No gtk.AccelGroup in the top level window.
1386890267.910710 WARNING root: No gtk.AccelGroup in the top level window.
/usr/lib/python2.7/site-packages/sugar/graphics/window.py:173: GtkWarning: 
IA__gtk_container_remove: assertion 'GTK_IS_TOOLBAR (container) || 
widget-parent == GTK_WIDGET (container)' failed
  self.__hbox.remove(self._canvas)
/usr/lib/python2.7/site-packages/sugar/datastore/datastore.py:103: 
UnicodeWarning: Unicode unequal comparison failed to convert both arguments to 
Unicode - interpreting them as being unequal
  if key not in self._properties or self._properties[key] != value:
1386891225.747478 ERROR root: pygame already stopped? video system not 
initialized
1386891225.750179 WARNING root: No gtk.AccelGroup in the top level window.
1386891225.750442 WARNING root: No gtk.AccelGroup in the top level window.
1386891225.750675 WARNING root: No gtk.AccelGroup in the top level window.
1386891225.753937 WARNING root: No gtk.AccelGroup in the top level window.
* Pygame selected as renderer
alpha difference: 46.7221965664
concave
alpha difference: 65.9787390523
concave
is line
concave
* Add Joint: (b2Body(
   allowSleep= True,
   angle = 0.0,
   angularDamping= 0.0,
   angularVelocity   = 0.0,
   fixedRotation = False,
   isBullet  = False,
   isSleeping= False,
   linearDamping = 0.0,
   linearVelocity= b2Vec2(0,0),
   massData  = b2MassData(
   I  = 0.237763956189,
   center = b2Vec2(3.6194e-09,-0.005),
   mass   = 0.417489856482),
   position  = b2Vec2(8.1,4.24),
   userData  = {'color': (32, 61, 97)},
   GetInertia()  = 0.237763956189,
   GetLocalCenter()  = b2Vec2(3.6194e-09,-0.005),
   GetMass() = 0.417489856482,
   GetWorldCenter()  = b2Vec2(8.1,4.235),
   GetXForm()= b2XForm(
   R= b2Mat22(
   col1   = b2Vec2(1,0),
   col2   = b2Vec2(-0,1),
   GetAngle() = 0.0),
   position = b2Vec2(8.1,4.24)),
   IsBullet()= False,
   IsDynamic()   = True,
   IsFrozen()= False,
   IsFixedRotation() = False,
   IsSleeping()  = False,
   IsStatic()= False), [811, 517])
* Add Joint: (b2Body(
   allowSleep= True,
   angle = 0.0,
   angularDamping= 0.0,
   angularVelocity   = 0.0,
   fixedRotation = False,
   isBullet  = False,
   isSleeping= False,
   linearDamping = 0.0,
   linearVelocity= b2Vec2(0,0),
   massData  = b2MassData(
   I  = 1.14382362366,
   center = b2Vec2(0.0244926,-0.152662),
   mass   = 0.756623983383),
   position  = b2Vec2(3.86,7.41),
   userData  = {'color': (103, 149, 206)},
   GetInertia()  = 1.14382362366,
   GetLocalCenter()  = b2Vec2(0.0244926,-0.152662),
   GetMass() = 0.756623983383,
   GetWorldCenter()  = b2Vec2(3.88449,7.25734),
   GetXForm()= b2XForm(
   R= b2Mat22(
   col1   = b2Vec2(1,0),
   col2   = b2Vec2(-0,1),
   GetAngle() = 0.0),
   position = b2Vec2(3.86,7.41)),
   IsBullet()= False,
   IsDynamic()   = True,
   IsFrozen()= False,
   IsFixedRotation() = False,
   IsSleeping()  = False,
   IsStatic()= False), [372, 225])
Exited with status 0, pid 2663 data (None, open file 'fdopen', mode 'w' at 
0x900db78, dbus.ByteArray('9b3bdd22601541b366fc67e618b547cbc140fd36', 
variant_level=1))
attachment: Screenshot of \___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] SoaS v10 TC5 tests with important activities INCLUDED in the standard distribution

[Frederick Grose]

On Thu, Dec 12, 2013 at 11:18 PM, Frederick Grose fgr...@gmail.com wrote:
 On Thu, Dec 12, 2013 at 4:31 PM, Walter Bender walter.ben...@gmail.com 
 wrote:
 On Thu, Dec 12, 2013 at 6:28 PM, Frederick Grose fgr...@gmail.com wrote:
 On Thu, Dec 12, 2013 at 3:30 PM, Walter Bender walter.ben...@gmail.com 
 wrote:
 On Thu, Dec 12, 2013 at 2:26 PM, Frederick Grose fgr...@gmail.com wrote:
 New failure in Physics-11Walter:

 {...}


 Weird. That is a new bug. Try to grab a screen shot if you can.

 Attached.


 thx

 Walter Bender
 Sugar Labs
 http://www.sugarlabs.org

 Log also attached.
 When the model was started the activity crashed and disappeared.

Repeatable (n=3)

1. Launch Physics-11Walter,
2. Drop several triangles into model,
3. Grab one and sling it around.
4. Erase all
5. Draw first line,
6. Stop model,
7. Draw 2nd  3rd lines,
8. Pin 3rd line,
9. Motor axle 2nd line,
10. Grab first line and reposition it.
11. Pin it.

Origin-to-pin/axle-point lines may appear at step 10 or 11.

12. Start model

Activity crashes and disappears.

On repeat 4,  the origin lines and crash did not occur until I dropped
a disc onto a jammed line1 and propeller(line2).

This attached log may belong to repeat 2 or 3.


  --Fred
** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox)
1386915805.519899 WARNING root: KeepButton has been deprecated since Sugar 0.94 
and should not be used in newly written code.
1386915805.522353 WARNING root: No gtk.AccelGroup in the top level window.
1386915805.526240 WARNING root: No gtk.AccelGroup in the top level window.
1386915805.562041 WARNING root: No gtk.AccelGroup in the top level window.
1386915805.565674 WARNING root: No gtk.AccelGroup in the top level window.
1386915805.568567 WARNING root: No gtk.AccelGroup in the top level window.
1386915805.575474 WARNING root: No gtk.AccelGroup in the top level window.
1386915805.578038 WARNING root: No gtk.AccelGroup in the top level window.
/usr/lib/python2.7/site-packages/sugar/graphics/window.py:173: GtkWarning: 
IA__gtk_container_remove: assertion 'GTK_IS_TOOLBAR (container) || 
widget-parent == GTK_WIDGET (container)' failed
  self.__hbox.remove(self._canvas)
* Pygame selected as renderer
Traceback (most recent call last):
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
212, in _mousemove_cb
self._post(evt)
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
246, in _post
raise e
pygame.error: video system not initialized
Traceback (most recent call last):
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
212, in _mousemove_cb
self._post(evt)
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
246, in _post
raise e
pygame.error: video system not initialized
Traceback (most recent call last):
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
212, in _mousemove_cb
self._post(evt)
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
246, in _post
raise e
pygame.error: video system not initialized
Traceback (most recent call last):
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
212, in _mousemove_cb
self._post(evt)
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
246, in _post
raise e
pygame.error: video system not initialized
Traceback (most recent call last):
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
212, in _mousemove_cb
self._post(evt)
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
246, in _post
raise e
pygame.error: video system not initialized
Traceback (most recent call last):
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
212, in _mousemove_cb
self._post(evt)
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
246, in _post
raise e
pygame.error: video system not initialized
Traceback (most recent call last):
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
212, in _mousemove_cb
self._post(evt)
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
246, in _post
raise e
pygame.error: video system not initialized
Traceback (most recent call last):
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
212, in _mousemove_cb
self._post(evt)
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
246, in _post
raise e
pygame.error: video system not initialized
Traceback (most recent call last):
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
212, in _mousemove_cb
self._post(evt)
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py, line 
246, in _post
raise e
pygame.error: video system not initialized
Traceback (most recent call last):
  File /home/liveuser/Activities/Physics.activity/sugargame/event.py

Re: [SoaS] SoaS v10 TC5 tests with important activities INCLUDED in the standard distribution

[Frederick Grose]

On Wed, Dec 11, 2013 at 4:32 PM, Frederick Grose fgr...@gmail.com wrote:

 On Wed, Dec 11, 2013 at 4:06 PM, Walter Bender walter.ben...@gmail.comwrote:

 Jean,

 Would you please test this new version of Physics [1]? Not quite ready
 for release, but I think (hope) it will run on F20 (SoaS).

 thx

 -walter

 [1] http://people.sugarlabs.org/walter/Physics-11.xo



 {...}


 Tested in Fedora 20 TC5 with
 sudo yum install @sugar-desktop sugar-runner xorg-x11-server-Xephyr

 Launched Physics-11.xo from the Documents folder,
 Dropped several triangles into the model,
 Switched to the grab tool,
 Tried to grab one of the triangles,
 Physics disappeared.

 Logs attached.

  --Fred


Reopened this ticket,
http://bugs.sugarlabs.org/ticket/3361#comment:27
 
http://bugs.sugarlabs.org/ticket/3361#comment:27http://bugs.sugarlabs.org/ticket/3361#comment:27

attached the log, and .xo.
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] SoaS v10 TC5 tests with important activities INCLUDED in the standard distribution

[Frederick Grose]

On Wed, Dec 11, 2013 at 6:01 PM, Walter Bender walter.ben...@gmail.comwrote:

 Could check one thing for me?

 Is elements installed in /usr/lib/python2.7/site-packages/elements ?


Yes, there are 30 items in that folder.

I've attached the elements.py file that was date 08/04/2013.


 If so, I suspect that there may be a conflict between that version and
 the one packaged with Physics.

 -walter



{...}


This file is part of the 'Elements' Project
Elements is a 2D Physics API for Python (supporting pybox2d)

Copyright (C) 2008, The Elements Team, eleme...@linuxuser.at

Home:  http://elements.linuxuser.at
IRC:   #elements on irc.freenode.org

Code:  http://www.assembla.com/wiki/show/elements
   svn co http://svn2.assembla.com/svn/elements 

License:  GPLv3 | See LICENSE for the full text
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see http://www.gnu.org/licenses/.  

__version__=  '0.11'
__contact__ = 'eleme...@linuxuser.at'

# Load Box2D
try:
import Box2D as box2d
except:
print 'Could not load the pybox2d library (Box2D).'
print 'Please run setup.py install to install the dependencies.'
print 
print 'Alternatively, recompile pybox2d for your system and python version.'
print See http://code.google.com/p/pybox2d;
exit()

# Standard Imports
from random import shuffle

# Load Elements Definitions
from locals import *

# Load Elements Modules
import tools
import drawing
import add_objects
import callbacks
import camera

# Main Class
class Elements:
The class which handles all interaction with the box2d engine

# Settings
run_physics   =True   # Can pause the simulation
element_count =0  # Element Count 
renderer  =None   # Drawing class (from drawing.py)
input =INPUT_PIXELS   # Default Input in Pixels! (can change to INPUT_METERS)
line_width=0  # Line Width in Pixels (0 for fill)
listener  =None

screen_offset = (0, 0)# Offset screen from world coordinate system (x, y) [meter5]
screen_offset_pixel = (0, 0)  # Offset screen from world coordinate system (x, y) [pixel]

# The internal coordination system is y+=up, x+=right
# But it's possible to change the input coords to something else,
# they will then be translated on input
inputAxis_x_left = False# positive to the right by default
inputAxis_y_down = True # positive to up by default

mouseJoint = None

def __init__(self, screen_size, gravity=(0.0,-9.0), ppm=100.0, renderer='pygame'):
 Init the world with boundaries and gravity, and init colors.

Parameters:
  screen_size .. (w, h) -- screen size in pixels [int]
  gravity .. (x, y) in m/s^2  [float] default: (0.0, -9.0)
  ppm .. pixels per meter [float] default: 100.0
  renderer . which drawing method to use (str) default: 'pygame'

Return: class Elements()

self.set_screenSize(screen_size)
self.set_drawingMethod(renderer)

# Create Subclasses
self.add = add_objects.Add(self)
self.callbacks = callbacks.CallbackHandler(self)
self.camera = camera.Camera(self)

# Set Boundaries
self.worldAABB=box2d.b2AABB()
self.worldAABB.lowerBound = (-100.0, -100.0)
self.worldAABB.upperBound = (100.0, 100.0)

# Gravity + Bodies will sleep on outside
self.gravity = gravity
self.doSleep = True

# Create the World
self.world = box2d.b2World(self.worldAABB, self.gravity, self.doSleep)

# Init Colors
self.init_colors()

# Set Pixels per Meter
self.ppm = ppm

def set_inputUnit(self, input):
 Change the input unit to either meter or pixels

Parameters:
  input ... INPUT_METERS or INPUT_PIXELS
  
Return: -

self.input = input

def set_inputAxisOrigin(self, left=True, top=False):
 Change the origin of the input coordinate system axis

Parameters:
  left ... True or False -- x = 0 is at the left?
  top  True or False -- y = 0 is at the top?
  
Return: -
  
self.inputAxis_x_left = not left

Re: [SoaS] SoaS v10 TC5 tests with important activities INCLUDED in the standard distribution

[Frederick Grose]

On Wed, Dec 11, 2013 at 7:29 PM, Walter Bender walter.ben...@gmail.com wrote:

 could you try renaming the directory from elements to elements-foo ?
 and then relaunch Sugar and try Physics again? just to ensure we are
 getting the local copy of elements ?


Did that; but it failed to start.

Here is the log:
** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox)
1386815703.690920 WARNING root: KeepButton has been deprecated since
Sugar 0.94 and should not be used in newly written code.
1386815703.693349 WARNING root: No gtk.AccelGroup in the top level window.
1386815703.695499 WARNING root: No gtk.AccelGroup in the top level window.
1386815703.699353 WARNING root: No gtk.AccelGroup in the top level window.
1386815703.700839 WARNING root: No gtk.AccelGroup in the top level window.
1386815703.702335 WARNING root: No gtk.AccelGroup in the top level window.
1386815703.703794 WARNING root: No gtk.AccelGroup in the top level window.
1386815703.705249 WARNING root: No gtk.AccelGroup in the top level window.
1386815703.706773 WARNING root: No gtk.AccelGroup in the top level window.
1386815703.709054 WARNING root: No gtk.AccelGroup in the top level window.
1386815703.710725 WARNING root: No gtk.AccelGroup in the top level window.
1386815703.712203 WARNING root: No gtk.AccelGroup in the top level window.
1386815703.713677 WARNING root: No gtk.AccelGroup in the top level window.
1386815703.715131 WARNING root: No gtk.AccelGroup in the top level window.
1386815703.716829 WARNING root: No gtk.AccelGroup in the top level window.
1386815703.718093 WARNING root: No gtk.AccelGroup in the top level window.
1386815703.719070 WARNING root: No gtk.AccelGroup in the top level window.
Traceback (most recent call last):
  File /usr/bin/sugar-activity, line 164, in module
main()
  File /usr/bin/sugar-activity, line 159, in main
instance = create_activity_instance(activity_constructor, activity_handle)
  File /usr/bin/sugar-activity, line 44, in create_activity_instance
activity = constructor(handle)
  File /usr/share/sugar/activities/Physics.activity/activity.py,
line 45, in __init__
super(PhysicsActivity, self).__init__(handle)
  File /usr/lib/python2.7/site-packages/olpcgames/activity.py, line
106, in __init__
canvas = self.build_canvas()
  File /usr/lib/python2.7/site-packages/olpcgames/activity.py, line
167, in build_canvas
self._pgc.connect_game(self.game_handler or self.game_name)
  File /usr/lib/python2.7/site-packages/olpcgames/canvas.py, line
96, in connect_game
mod = __import__(mod_name, globals(), locals(), [])
  File /usr/share/sugar/activities/Physics.activity/physics.py, line
39, in module
import elements
ImportError: No module named elements
Exited with status 1, pid 2665 data (None, open file 'fdopen', mode
'w' at 0x192fae0,
dbus.ByteArray('8280d3a822f0b2a179da19812c46c0d0afaf6037',
variant_level=1))



 thx

 On Wed, Dec 11, 2013 at 9:26 PM, Frederick Grose fgr...@gmail.com wrote:
  On Wed, Dec 11, 2013 at 6:01 PM, Walter Bender walter.ben...@gmail.com
  wrote:
 
  Could check one thing for me?
 
  Is elements installed in /usr/lib/python2.7/site-packages/elements ?
 
 
  Yes, there are 30 items in that folder.
 
  I've attached the elements.py file that was date 08/04/2013.
 
 
  If so, I suspect that there may be a conflict between that version and
  the one packaged with Physics.
 
  -walter
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] SoaS v10 TC5 tests with important activities INCLUDED in the standard distribution

[Frederick Grose]

On Wed, Dec 11, 2013 at 7:58 PM, Walter Bender walter.ben...@gmail.com wrote:
 On Wed, Dec 11, 2013 at 9:47 PM, Frederick Grose fgr...@gmail.com wrote:
 On Wed, Dec 11, 2013 at 7:29 PM, Walter Bender walter.ben...@gmail.com 
 wrote:

 could you try renaming the directory from elements to elements-foo ?
 and then relaunch Sugar and try Physics again? just to ensure we are
 getting the local copy of elements ?


OK, I had a bad extraction of the Physics-11.xo by launching it from
the ~/Documents folder (no elements and other folders)
By manually extracting and moving to /usr/share/sugar/activities/ AND
renaming the site-packages/elements to elements-foo, I was able to
grab the triangle successfully.  Here's the log:

** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox)
1386818798.820504 WARNING root: KeepButton has been deprecated since
Sugar 0.94 and should not be used in newly written code.
1386818798.821977 WARNING root: No gtk.AccelGroup in the top level window.
1386818798.824342 WARNING root: No gtk.AccelGroup in the top level window.
1386818798.844370 WARNING root: No gtk.AccelGroup in the top level window.
1386818798.846209 WARNING root: No gtk.AccelGroup in the top level window.
1386818798.847829 WARNING root: No gtk.AccelGroup in the top level window.
1386818798.851720 WARNING root: No gtk.AccelGroup in the top level window.
1386818798.852973 WARNING root: No gtk.AccelGroup in the top level window.
/usr/lib/python2.7/site-packages/sugar/graphics/window.py:173:
GtkWarning: IA__gtk_container_remove: assertion 'GTK_IS_TOOLBAR
(container) || widget-parent == GTK_WIDGET (container)' failed
  self.__hbox.remove(self._canvas)
/usr/lib/python2.7/site-packages/sugar/datastore/datastore.py:103:
UnicodeWarning: Unicode unequal comparison failed to convert both
arguments to Unicode - interpreting them as being unequal
  if key not in self._properties or self._properties[key] != value:
1386818881.677858 WARNING root: No gtk.AccelGroup in the top level window.
1386818897.396570 ERROR root: pygame already stopped? video system not
initialized
1386818897.397724 WARNING root: No gtk.AccelGroup in the top level window.
1386818897.397843 WARNING root: No gtk.AccelGroup in the top level window.
1386818897.397951 WARNING root: No gtk.AccelGroup in the top level window.
1386818897.398430 WARNING root: No gtk.AccelGroup in the top level window.
* Pygame selected as renderer
convexPoly: Polygon reduced from 3 to 3 vertices | tolerance: 10
convexPoly: Polygon reduced from 3 to 3 vertices | tolerance: 10
convexPoly: Polygon reduced from 3 to 3 vertices | tolerance: 10
convexPoly: Polygon reduced from 3 to 3 vertices | tolerance: 10
convexPoly: Polygon reduced from 3 to 3 vertices | tolerance: 10
Exited with status 0, pid 3827 data (None, open file 'fdopen', mode
'w' at 0x169e660,
dbus.ByteArray('f325cff9568047df48903af0a7bca7a34b26bd09',
variant_level=1))

Without renaming elements in site-packages, I lose the cursor when
trying to grab, but no crash.  Here's the log:

** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox)
1386819005.735682 WARNING root: KeepButton has been deprecated since
Sugar 0.94 and should not be used in newly written code.
1386819005.737815 WARNING root: No gtk.AccelGroup in the top level window.
1386819005.741079 WARNING root: No gtk.AccelGroup in the top level window.
1386819005.761918 WARNING root: No gtk.AccelGroup in the top level window.
1386819005.763760 WARNING root: No gtk.AccelGroup in the top level window.
1386819005.765361 WARNING root: No gtk.AccelGroup in the top level window.
1386819005.769241 WARNING root: No gtk.AccelGroup in the top level window.
1386819005.770508 WARNING root: No gtk.AccelGroup in the top level window.
/usr/lib/python2.7/site-packages/sugar/graphics/window.py:173:
GtkWarning: IA__gtk_container_remove: assertion 'GTK_IS_TOOLBAR
(container) || widget-parent == GTK_WIDGET (container)' failed
  self.__hbox.remove(self._canvas)
* Pygame selected as renderer
convexPoly: Polygon reduced from 3 to 3 vertices | tolerance: 10
convexPoly: Polygon reduced from 3 to 3 vertices | tolerance: 10
convexPoly: Polygon reduced from 3 to 3 vertices | tolerance: 10
convexPoly: Polygon reduced from 3 to 3 vertices | tolerance: 10
convexPoly: Polygon reduced from 3 to 3 vertices | tolerance: 10
convexPoly: Polygon reduced from 3 to 3 vertices | tolerance: 10
Traceback (most recent call last):
  File /usr/share/sugar/activities/Physics.activity/sugargame/canvas.py,
line 58, in _run_pygame_cb
main_fn()
  File /usr/share/sugar/activities/Physics.activity/physics.py, line
130, in run
self.currentTool.handleEvents(event)
  File /usr/share/sugar/activities/Physics.activity/tools.py, line
80, in handleEvents
return self.handleToolEvent(event)
  File /usr/share/sugar/activities/Physics.activity/tools.py, line
425, in handleToolEvent
tuple_to_int(event.pos))
  File /usr/lib/python2.7/site-packages/elements/add_objects.py,
line 515, in mouseJoint

Re: [SoaS] SoaS v10 TC5 tests with important activities INCLUDED in the standard distribution

[Frederick Grose]

On Wed, Dec 11, 2013 at 8:47 PM, Walter Bender walter.ben...@gmail.com wrote:
 Fred,

 Thanks for testing.

 Peter,

 Is there any reason we need elements in the build? I don't think it is
 used by anything but Physics in Sugar and Physics carries its own copy
 with it.

 -walter


Gary Martin has a Physics-11 in Fedora and the Activity Library,
http://activities.sugarlabs.org/en-US/sugar/addons/versions/4193#version-11

that is installed in SoaS.  This is what I must have been launching
when I clicked the Physics.xo item in my Documents folder in the
Journal.

Copying Walter's Physics-11.xo to the Journal and launching from there
(after erasing the original Physics-11.xo) AND hiding
/usr/lib/python2.7/site-packages/elements was effective in launching
and running Physics in Fedora 20 TC5.

  --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Physics activity [Sugar-devel] SoaS v10 testing and a few minor issues with 0.100

[Frederick Grose]

On Tue, Nov 19, 2013 at 4:15 PM, Jean THIERY jean.thi...@modlibre.infowrote:

 {...}


 There is also a recording error when we stops Physics !

  Can you take the log file and send to sugar-devel list.


 Yes later on, but I have to learn how to do it.


If you download the new, version 36 of Log,
http://activities.sugarlabs.org/en-US/sugar/addons/versions/4056#version-36

It is now working in SoaS for collecting logs in the Journal.

You have to hover or click the first (and colored) Activity toolbar icon,
and then click the far right, Log collector icon in the sub toolbar.  That
will reveal a 'Capture information' button in the icon palette.

A log-nn.zip entry will appear in the Sugar Journal.
Hovering its icon there will reveal some 'Copy to' options in the menu list
of the icon palette.

Or, if you open Browse in SoaS and visit or create a ticket at
https://bugs.sugarlabs.org/
the 'Attach file' button (under the Attachments dropdown list control) will
reveal an 'Add Attachment to Ticket #' page with a 'Chose File' button.
 That button will open a view of your Journal from which you can select the
Journal entry for the log-nn.zip file.

   --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] [Sugar-devel] [ASLO] Release Log-36

[Frederick Grose]

On Tue, Nov 19, 2013 at 8:42 AM, Sugar Labs Activities 
activit...@sugarlabs.org wrote:

 Activity Homepage:
 http://activities.sugarlabs.org/addon/4056

 Sugar Platform:
 0.96 - 0.100

 Download Now:
 http://activities.sugarlabs.org/downloads/file/28827/log-36.xo

 Release notes:
 Fix: SL #4407 Log: collector fails to collect files (Frederick Grose)
 Updated translations


 Sugar Labs Activities
 http://activities.sugarlabs.org


This fixes log collection in SoaS and Fedora 20 installations.

https://bugs.sugarlabs.org/ticket/4407
tar ball: http://download.sugarlabs.org/sources/sucrose/fructose/Log/
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] Etoys in Sugar was: SoaS v10 testing and a few minor issues with 0.100

[Frederick Grose]

On Tue, Nov 19, 2013 at 12:39 PM, Peter Robinson pbrobin...@gmail.comwrote:

 On Tue, Nov 19, 2013 at 5:33 PM, Gonzalo Odiard gonz...@laptop.org
 wrote:
  
   - The eToys activity (version 116) does not start properly
 then displays
 « cannot find image file: squeak, did you run 'inisqueak-m' ? »


This was ticketed here,
https://bugs.sugarlabs.org/ticket/4415


 
  The eToys developers are basically unresponsive, I'm in two minds
  whether we even bother to ship it because they can't be bothered doing
  things like updating to the latest sugar by migrating away from
  sugar-presence-service/ which was deprecated a long time ago.
 
 
 
  But this looks like a different problem, right?

 TBH I have no idea, I've not had the time to look closely at eToys
 because a lack of response from the maintainer or anyone bothering to
 test or improve it makes me prioritise things that are easy for me to
 fix where I actually get responses. Last release I removed it from the
 main wheel because it wasn't a decent experience.

 Peter
 ___
 SoaS mailing list
 SoaS@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/soas

___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] First boot to Sugar fails

[Frederick Grose]

On Tue, Sep 24, 2013 at 1:11 PM, Thomas Gilliard satelli...@gmail.comwrote:

  On 09/24/2013 09:59 AM, Frederick Grose wrote:

  Tested with
 http://download.fedoraproject.org/pub/alt/releases/test/20-Alpha/Spins/x86_64/Fedora-Live-SoaS-x86_64-20-Alpha-4.isoloaded
  onto a Live USB device with livecd-iso-to-disk.

  The first boot takes one to a console login prompt.

  After
 # yum install lightdm

  then after rebooting, one is taken to a graphical liveuser login prompt
 followed by the Sugar user prompt.

 --Fred


  Fred: look at this wiki page:
 http://wiki.sugarlabs.org/go/Fedora_20#SoaS_86_64-dm_.28remix.29

 http://wiki.sugarlabs.org/go/Fedora_20#SoaS_f20-Alpha-1


Yes.  Install lightdm was not necessary.

After login: liveuser at the console,
$ startx

was sufficient to proceed to the Sugar user prompt.

--Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] Run livecd-iso-to-disk in the source environment with chroot

[Frederick Grose]

This version of livecd-iso-to-disk is reworked to use the source root
filesystem in a chroot by default, along with the livecd-iso-to-disk script
embedded in the source.  A --nochroot as well as a --avoidsourcescript
option are available for cases where the launching filesystem and/or
installation script is called for.

One can load a Live USB by these steps:
 1. mounting the source.iso
 2. determine its loop device, /dev/loopN
 3. call /mountpoint/LiveOS/livecd-iso-to-disk /dev/loopN /dev/target

All 3 steps could be avoided by providing some appropriate autorun scripts
for the iso, or including some standard install scripts that could be
invoked by clicking on them in Nautilus.

By mounting the source.iso LiveOS filesystem in a chroot enviroment, the
current version of software components, including the installation script,
on the source can be used for installation.  (If syslinux-extlinux is not
in the source, ext234,btrfs target devices will have to use the --nochroot
option and a system with the proper bootloader.)  An --avoidsourcescript
option is also added to allow installation with alternative scripts.

This new version of livecd-iso-to-disk prefers builtin functions, finds and
offers to unmount mounted targets, and reorders some compatibility checks
in order to bailout early, if needed.

If this passes further testing (the DVD and netinst installer paths are
untested), I can submit incremental patches for these changes.

Link to the reworked livecd-iso-to-disk script,
https://bugzilla.redhat.com/attachment.cgi?id=610112

Filed on this ticket,
https://bugzilla.redhat.com/show_bug.cgi?id=663986


Testing and comments would be appreciated.

--Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Run livecd-iso-to-disk in the source environment with chroot

[Frederick Grose]

On Wed, Sep 5, 2012 at 6:40 PM, Frederick Grose fgr...@gmail.com wrote:

 This version of livecd-iso-to-disk is reworked to use the source root
 filesystem in a chroot by default, along with the livecd-iso-to-disk script
 embedded in the source.  A --nochroot as well as a --avoidsourcescript
 option are available for cases where the launching filesystem and/or
 installation script is called for.

 One can load a Live USB by these steps:
  1. mounting the source.iso
  2. determine its loop device, /dev/loopN
  3. call /mountpoint/LiveOS/livecd-iso-to-disk /dev/loopN /dev/target

 All 3 steps could be avoided by providing some appropriate autorun scripts
 for the iso, or including some standard install scripts that could be
 invoked by clicking on them in Nautilus.

 By mounting the source.iso LiveOS filesystem in a chroot enviroment, the
 current version of software components, including the installation script,
 on the source can be used for installation.  (If syslinux-extlinux is not
 in the source, ext234,btrfs target devices will have to use the --nochroot
 option and a system with the proper bootloader.)  An --avoidsourcescript
 option is also added to allow installation with alternative scripts.

 This new version of livecd-iso-to-disk prefers builtin functions, finds
 and offers to unmount mounted targets, and reorders some compatibility
 checks in order to bailout early, if needed.

 If this passes further testing (the DVD and netinst installer paths are
 untested), I can submit incremental patches for these changes.

 Link to the reworked livecd-iso-to-disk script,
 https://bugzilla.redhat.com/attachment.cgi?id=610112

 Filed on this ticket,
 https://bugzilla.redhat.com/show_bug.cgi?id=663986


 Testing and comments would be appreciated.

 --Fred


The script can be tested on an existing source.iso by invoking it with the
--avoidsourcescript option, which will complete the installation using the
launched script in the chroot instead of the the onboard version of
livecd-iso-to-disk.

The script could also be copied to the /LiveOS/ directory in the device
filesystem of an installed Live USB, and then called from the from the
mount point for that device, such as,
/run/media/liveuser/MyUSBname/LiveOS/livecd-iso-to-disk /dev/MyUSBnode
/dev/target, where MyUSBname is the mount point directory name and
MyUSBnode is the /dev filesystem node, such as, sdc1 or sdd1, etc.

 --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Update SoaS Page on Wiki?

[Frederick Grose]

On Sat, Jun 2, 2012 at 11:55 AM, Thomas Gilliard satel...@bendbroadband.com
 wrote:

 Fred;

 Should we update   web page on wiki
  
 http://wiki.sugarlabs.org/go/**Sugar_on_a_Stickhttp://wiki.sugarlabs.org/go/Sugar_on_a_Stick
 to:
  
 http://wiki.sugarlabs.org/go/**Sugar_on_a_Stick/Quandonghttp://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Quandong?

 (I am not the one to do this.)

 I have updated the Download  and announcement links, but the bottom
 section of the page needs to be  updated.

 Cordially;

 Tom Gilliard
 satellit_


I generally wait for a separate announcement on soas@lists.sugarlabs.org,
and clearly, Peter has a lot on his plate.

I was actually hoping that the Etoys packaging could get sorted first, and
that Quandong were delayed like Coconut (but hopefully no as long).  But I
don't have an idea of how long that would take.

Perhaps Kalpa would have some time to help, so I've copied him in, along
with the list.

--Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] /dev/live, /mnt/live, LiveOS/home.img unavailable in Fedora-17

[Frederick Grose]

On Mon, Apr 30, 2012 at 12:32 AM, Frederick Grose fgr...@gmail.com wrote:

 On Thu, Mar 29, 2012 at 8:51 PM, Frederick Grose fgr...@gmail.com wrote:

 On Mon, Mar 26, 2012 at 12:02 PM, Frederick Grose fgr...@gmail.comwrote:

 Please note that the current Fedora-17-Beta-TC2-Live images lack
 some traditional Live CD/USB features.

 See this bug report.
 https://bugzilla.redhat.com/show_bug.cgi?id=740280

 {...}



The --home-size-mb NNN option of livecd-iso-to-disk produced a
 /LiveOS/home.img
 filesystem for the liveuser's home directory.

 This feature made possible the --encrypted-home option, which would
 secure the privacy of a user directory on a Live USB system.

 The home.img filesystem was also read/write/delete without consuming the
 LiveOS overlay.  This is important for non-short-term Live USB deployments,
 such as Sugar on a Stick, where overlay exhaustion can be a significant
 problem.



  {...}



Adam Williamson has patched fedora-live-base.ks, but
testingFedora-17.TC5-x86_64-Live-SoaS.iso
shows that a home.img filesystem is not mounted.

Adam's patches need to be applied to fedora-live-mini.ks in order to fix Sugar
on a Stick and any other builds based on fedora-live-mini.ks

Comment added to bug:
https://bugzilla.redhat.com/show_bug.cgi?id=740280#c47

 --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] /dev/live, /mnt/live, LiveOS/home.img unavailable in Fedora-17

[Frederick Grose]

On Thu, Mar 29, 2012 at 8:51 PM, Frederick Grose fgr...@gmail.com wrote:

 On Mon, Mar 26, 2012 at 12:02 PM, Frederick Grose fgr...@gmail.comwrote:

 Please note that the current Fedora-17-Beta-TC2-Live images lack
 some traditional Live CD/USB features.

 See this bug report.
 https://bugzilla.redhat.com/show_bug.cgi?id=740280

 /dev/live was a link to the installation partition on the Live USB, such
 as /dev/sdc1,
 or /dev/sr0 on a Live CD/DVD.

 How would a script determine this partition without human input?

 /mnt/live was a convenient mounting of the installation partition
 filesystem.
 It allowed easy access to pre-existing content on the Live USB device or
 to
 the /LiveOS and /syslinux directories.

 The --home-size-mb NNN option of livecd-iso-to-disk produced a
 /LiveOS/home.img
 filesystem for the liveuser's home directory.

 This feature made possible the --encrypted-home option, which would
 secure the privacy of a user directory on a Live USB system.

 The home.img filesystem was also read/write/delete without consuming the
 LiveOS overlay.  This is important for non-short-term Live USB deployments,
 such as Sugar on a Stick, where overlay exhaustion can be a significant
 problem.

 Is there a workaround for these (missing) features?

--Fred


 This patch restores the lost features:

 commit 1580cddaea504efd68c5e10fee70e09d7e81d86b
 Author: Frederick Grose fgr...@sugarlabs.org
 Date:   Thu Mar 29 16:27:30 2012 -0400

 Mount live device on /mnt/live, link it to /dev/live

 This enables the mounting of /LiveOS/home.img, if present.

 diff --git a/fedora-live-base.ks b/fedora-live-base.ks
 index 0b14fec..0cf0fb2 100644
 --- a/fedora-live-base.ks
 +++ b/fedora-live-base.ks
 @@ -88,10 +88,22 @@ touch /.liveimg-configured
  # Make sure we don't mangle the hardware clock on shutdown
  ln -sf /dev/null /etc/systemd/system/hwclock-save.service

 +findmount() {
 +local info=()
 +while read -a info; do
 +if [[ ${info[4]} == $1 ]]; then
 +echo ${info[8]}
 +break;
 +fi
 +done  /proc/self/mountinfo
 +}
 +
  # mount live image
 -if [ -b \`readlink -f /dev/live\` ]; then
 +livedev=$(findmount /run/initramfs/live)
 +if [[ -b $livedev ]]; then
 mkdir -p /mnt/live
 -   mount -o ro /dev/live /mnt/live 2/dev/null || mount /dev/live
 /mnt/live
 +   mount -o ro $livedev /mnt/live 2/dev/null || mount $livedev /mnt/live
 +   ln -s $livedev /dev/live
  fi

  livedir=LiveOS
 @@ -220,7 +232,7 @@ if strstr \`cat /proc/cmdline\` CDLABEL= ; then
  # io errors due to not being able to get files...
  #cat /sbin/halt  /dev/null
  #cat /sbin/reboot  /dev/null
 -#/usr/sbin/eject -p -m \$(readlink -f /dev/live) /dev/null 21
 +#/usr/sbin/eject -p -m \$livedev /dev/null 21
  #echo Please remove the CD from your drive and press Enter to finish
 restarting
  #read -t 30  /dev/console
  FOE


With Fedora-17.TC2-x86_64-Live-Desktop.iso we have
/run/initramfs/livedev as a symlink to the block device for the source
partition 
/run/initramfs/live as the mount point for that filesystem.

This substitute patch enables the mounting of home.img and swap.img filesystems
with the substitute paths:

(Tested as applied to /etc/rc.d/init.d/livesys on an installed Live USB.)


commit e2a04b06093fcea1b0c6ecfc59847adc08d08137
Author: Frederick Grose fgr...@sugarlabs.org
Date:   Mon Apr 30 00:03:02 2012 -0400

Substitute /run/initramfs/live for /mnt/live.

This is needed to enable mounting of home.img and swap.img in
Fedora 17 LiveOS installations.

diff --git a/fedora-live-base.ks b/fedora-live-base.ks
index 0b14fec..54df915 100644
--- a/fedora-live-base.ks
+++ b/fedora-live-base.ks
@@ -88,12 +88,6 @@ touch /.liveimg-configured
 # Make sure we don't mangle the hardware clock on shutdown
 ln -sf /dev/null /etc/systemd/system/hwclock-save.service

-# mount live image
-if [ -b \`readlink -f /dev/live\` ]; then
-   mkdir -p /mnt/live
-   mount -o ro /dev/live /mnt/live 2/dev/null || mount /dev/live /mnt/live
-fi
-
 livedir=LiveOS
 for arg in \`cat /proc/cmdline\` ; do
   if [ \${arg##live_dir=} != \${arg} ]; then
@@ -109,8 +103,9 @@ if ! strstr \`cat /proc/cmdline\` noswap  [ -n
\$swaps ] ; then
 action Enabling swap partition \$s swapon \$s
   done
 fi
-if ! strstr \`cat /proc/cmdline\` noswap  [ -f
/mnt/live/\${livedir}/swap.img ] ; then
-  action Enabling swap file swapon /mnt/live/\${livedir}/swap.img
+if ! strstr $(cat /proc/cmdline) noswap 
+[[ -f /run/initramfs/live/${livedir}/swap.img ]] ; then
+  action Enabling swap file swapon
/run/initramfs/live/${livedir}/swap.img
 fi

 mountPersistentHome() {
@@ -125,8 +120,8 @@ mountPersistentHome() {
 mountopts=-t jffs2
   elif [ ! -b \$homedev ]; then
 loopdev=\`losetup -f\`
-if [ \${homedev##/mnt/live} != \${homedev} ]; then
-  action Remounting live store r/w mount -o remount,rw /mnt/live
+if [[ ${homedev##/run/initramfs/live} != ${homedev} ]]; then
+  action Remounting live store r

Re: [SoaS] /dev/live, /mnt/live, LiveOS/home.img unavailable in Fedora-17

[Frederick Grose]

On Mon, Mar 26, 2012 at 12:02 PM, Frederick Grose fgr...@gmail.com wrote:

 Please note that the current Fedora-17-Beta-TC2-Live images lack
 some traditional Live CD/USB features.

 See this bug report.
 https://bugzilla.redhat.com/show_bug.cgi?id=740280

 /dev/live was a link to the installation partition on the Live USB, such
 as /dev/sdc1,
 or /dev/sr0 on a Live CD/DVD.

 How would a script determine this partition without human input?

 /mnt/live was a convenient mounting of the installation partition
 filesystem.
 It allowed easy access to pre-existing content on the Live USB device or to
 the /LiveOS and /syslinux directories.

 The --home-size-mb NNN option of livecd-iso-to-disk produced a
 /LiveOS/home.img
 filesystem for the liveuser's home directory.

 This feature made possible the --encrypted-home option, which would secure
 the privacy of a user directory on a Live USB system.

 The home.img filesystem was also read/write/delete without consuming the
 LiveOS overlay.  This is important for non-short-term Live USB deployments,
 such as Sugar on a Stick, where overlay exhaustion can be a significant
 problem.

 Is there a workaround for these (missing) features?

--Fred


This patch restores the lost features:

commit 1580cddaea504efd68c5e10fee70e09d7e81d86b
Author: Frederick Grose fgr...@sugarlabs.org
Date:   Thu Mar 29 16:27:30 2012 -0400

Mount live device on /mnt/live, link it to /dev/live

This enables the mounting of /LiveOS/home.img, if present.

diff --git a/fedora-live-base.ks b/fedora-live-base.ks
index 0b14fec..0cf0fb2 100644
--- a/fedora-live-base.ks
+++ b/fedora-live-base.ks
@@ -88,10 +88,22 @@ touch /.liveimg-configured
 # Make sure we don't mangle the hardware clock on shutdown
 ln -sf /dev/null /etc/systemd/system/hwclock-save.service

+findmount() {
+local info=()
+while read -a info; do
+if [[ ${info[4]} == $1 ]]; then
+echo ${info[8]}
+break;
+fi
+done  /proc/self/mountinfo
+}
+
 # mount live image
-if [ -b \`readlink -f /dev/live\` ]; then
+livedev=$(findmount /run/initramfs/live)
+if [[ -b $livedev ]]; then
mkdir -p /mnt/live
-   mount -o ro /dev/live /mnt/live 2/dev/null || mount /dev/live /mnt/live
+   mount -o ro $livedev /mnt/live 2/dev/null || mount $livedev /mnt/live
+   ln -s $livedev /dev/live
 fi

 livedir=LiveOS
@@ -220,7 +232,7 @@ if strstr \`cat /proc/cmdline\` CDLABEL= ; then
 # io errors due to not being able to get files...
 #cat /sbin/halt  /dev/null
 #cat /sbin/reboot  /dev/null
-#/usr/sbin/eject -p -m \$(readlink -f /dev/live) /dev/null 21
+#/usr/sbin/eject -p -m \$livedev /dev/null 21
 #echo Please remove the CD from your drive and press Enter to finish
restarting
 #read -t 30  /dev/console
 FOE
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] Python segfault on firstboot of sugar associated with recent Fedora pycairo package update

[Frederick Grose]

After updating pycairo from 1.8.8-2.fc14 to 1.8.10-4.fc16, Sugar fails to
launch on firstboot.

/var/log/messages shows a line such as,
Mar 18 13:05:04 localhost kernel: [   35.702384] python[1435]: segfault at
0 ip   (null) sp 7fffde3be248 error 14 in python[40+1000]
(The final 8 sp address characters vary on each failure.)

This is observed with Sugar on a Stick F15 and F16 versions updated with
yum update from the Fedora repository.

Downgrading pycairo fixes the problem.

   --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] [Testing] I would like feedback on the How_to_use_the_IRC_Application wiki page

[Frederick Grose]

On Tue, Dec 13, 2011 at 8:41 AM, Thomas C Gilliard 
satel...@bendbroadband.com wrote:

 I just wrote this wiki page:
 http://wiki.sugarlabs.org/go/**Sugar_Creation_Kit#How_to_use_**
 the_IRC_Applicationhttp://wiki.sugarlabs.org/go/Sugar_Creation_Kit#How_to_use_the_IRC_Application


corrected link:
http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/How_to_use_IRC

   (Annotated screen shots that show you how to use the IRC application)

 My question:
 Is this a useful way to build guides for beginners?

 Also these pages: (English and Spanish)
 http://wiki.sugarlabs.org/go/**Sugar_Creation_Kit#**
 Introduction_to_the_Sugar_**Interfacehttp://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Introduction_to_the_Sugar_Interface
  (3 linked wiki pages of Annotated Screen-shots )

 I think as it is a wiki these provide a way for users to participate in
 updating in these guides.

 I would like feedback on this project.

 Cordially;

 Tom Gilliard
 satellit_ on #sugar IRC
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] SoaSv6 - Last stages

[Frederick Grose]

On Thu, Oct 27, 2011 at 11:13 AM, Peter Robinson pbrobin...@gmail.comwrote:

 Hi All,

 We're in the final stages of SoaSv6. It would be good for people to
 test and see if I've missed any issues. I believe we're in pretty good
 shape for this release. In fact I think its going to be one of our
 better releases. We've had no major breakages due to upstream this
 cycle and Fedora is locking down for the final run to release so we're
 past the possibility of that (thankfully!).

 To create it run the following command. Note you need to correct the
 image name for the downloaded version, and also update the device name
 for your relevant usb key.

 sudo livecd-iso-to-disk --format --efi Fedora-SoaS-Image-Name.iso /dev/sdz

 I'm interested in feedback on how it works on Intel based Mac's as the
 vast majority of Mac boot issues should be resolved with this release.
 We have a nice increase in the number of Activities shipping which
 should make it more interesting.

 I look forward to your feedback.

 Peter

 i386 http://koji.fedoraproject.org/koji/taskinfo?taskID=3459573
 x96-64 http://koji.fedoraproject.org/koji/taskinfo?taskID=3459574
 ___


Considering the risk to flash hardware described here,
http://wiki.laptop.org/go/How_to_Damage_a_FLASH_Storage_Device
(with updated discussions in this thread from March 2011,
http://www.mail-archive.com/devel@lists.laptop.org/msg26369.html
describing newer trends),

Is it reasonable to consider the --format install option only necessary for
Intel Macintosh systems or others requiring EFI boot, and for situations
where the flash device would be shared between such systems and other PCs
supporting factory (FAT-formatted) devices?

--Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] ToDo and Activity additions for SoaS v6

[Frederick Grose]

On Sun, Oct 9, 2011 at 4:01 PM, Peter Robinson pbrobin...@gmail.com wrote:

 Hi All,

 v6 is looking quite good. I fixed the last outstanding issue in my
 ToDo list today which was issues with Surf running.


filed yesterday,
http://bugs.sugarlabs.org/ticket/3176



{...}



Does anyone else have suggestions for SoaS in general for the upcoming
 v6 (Pineapple) release? Are there any additions Activities people
 would like to see added?


The Tam Tam Suite is a strong offering.

--Fred

{...}



Regards,
 Peter

___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] [PATCH 1b] substitute was: [PATCH 1/5] Support Live image mounting in fs.py

[Frederick Grose]

Patch 1b of 2 substitute patches to replace an earlier patch with new
features:

commit 3501e953449d17a53b669bb80bf4e96d8a8e4b25
Author: Frederick Grose fgr...@sugarlabs.org
Date:   Sat Sep 17 17:29:03 2011 -0400

Provide a new LiveImageMount class for mounting a LiveOS filesystem.

Mount the LiveOS filesystem with its own or a substitute overlay.
Provide mounting options for read-write or read-only overlays.
This supports image customization.

diff --git a/imgcreate/fs.py b/imgcreate/fs.py
index e71032e..6d04c4a 100644
--- a/imgcreate/fs.py
+++ b/imgcreate/fs.py
@@ -684,6 +684,103 @@ class DeviceMapperSnapshot(object):
 except ValueError:
 raise SnapshotError(Failed to parse dmsetup status:  + out)

+
+class LiveImageMount(object):
+A class for mounting a LiveOS image installed with an active
overlay.
+
+def __init__(self, disk, mountdir, overlay=None, tmpdir='/tmp',
ops=None):
+self.disk = disk
+self.mountdir = mountdir
+self.overlay = overlay
+self.tmpdir = tmpdir
+self.ops = ops
+self.__created = False
+self.squashmnt = None
+self.homemnt = None
+self.mntlive = None
+
+def __create(self, ops=None):
+if self.__created:
+return
+self.liveosdevmnt = DiskMount(self.disk,
+  os.path.join(self.tmpdir, 'device'),
ops=ops)
+self.liveosdevmnt.mount(ops)
+liveosdir = os.path.join(self.liveosdevmnt.mountdir, 'LiveOS')
+sqfs_img = os.path.join(liveosdir, 'squashfs.img')
+if os.path.exists(sqfs_img):
+self.squashloop = LoopbackDisk(sqfs_img, None, ['-r'])
+self.squashmnt = DiskMount(self.squashloop,
+ os.path.join(self.tmpdir, 'squash'),
ops='ro')
+self.squashmnt.mount('ro')
+rootfs_img = os.path.join(self.squashmnt.mountdir,
+  'LiveOS', 'ext3fs.img')
+else:
+rootfs_img = os.path.join(liveosdir, 'ext3fs.img')
+if not os.path.exists(rootfs_img):
+raise SnapshotError(Failed to find a LiveOS root image.)
+self.imgloop = LoopbackDisk(rootfs_img, None, ['-r'])
+if not self.overlay:
+for f in os.listdir(liveosdir):
+if f.find('overlay-') == 0:
+self.overlay = os.path.join(liveosdir, f)
+break
+self.cowloop = LoopbackDisk(self.overlay, None, ops)
+self.dm_liveimage = DeviceMapperSnapshot(self.imgloop,
self.cowloop,
+ ops)
+self.dm_livemount = DiskMount(self.dm_liveimage, self.mountdir,
+  ops=ops)
+home_img = os.path.join(liveosdir, 'home.img')
+if os.path.exists(home_img):
+homedir = os.path.join(self.mountdir, 'home')
+self.homemnt = LoopbackMount(home_img, homedir, ops=ops)
+self.__created = True
+
+def mount(self, ops=None):
+if ops is None:
+ops = self.ops
+try:
+self.__create(ops)
+if not self.liveosdevmnt.mounted:
+self.liveosdevmnt.mount(ops)
+if self.squashmnt and not self.squashmnt.mounted:
+self.squashmnt.mount('ro')
+self.dm_livemount.mount(ops)
+if self.homemnt:
+self.homemnt.mount(ops)
+mntlivedir = os.path.join(self.mountdir, 'mnt', 'live')
+if not os.path.exists(mntlivedir):
+os.makedirs(mntlivedir)
+self.mntlive = BindChrootMount(self.liveosdevmnt.mountdir,
+   '', mntlivedir, ops)
+self.mntlive.mount(ops)
+except MountError, e:
+self.cleanup()
+raise SnapshotError(Failed to mount %s : %s % (self.disk, e))
+
+def remount(self, ops):
+try:
+self.liveosdevmnt.remount(ops)
+if self.homemnt:
+self.homemnt.remount(ops)
+self.mntlive.reremount(ops)
+except MountError, e:
+self.cleanup()
+raise SnapshotError(Failed to remount %s as %s : %s %
+(self.disk, ops, e))
+
+def cleanup(self):
+if self.mntlive:
+self.mntlive.unmount()
+if self.homemnt:
+self.homemnt.cleanup()
+self.dm_livemount.unmount()
+self.dm_liveimage.remove()
+if self.squashmnt:
+self.squashmnt.cleanup()
+self.liveosdevmnt.cleanup()
+self.__created = False
+
+
 def create_image_minimizer(path, image, compress_type, target_size = None,
tmpdir = /tmp):
 



On Thu, Apr 14, 2011 at 12:02 PM, Frederick Grose fgr...@gmail.com wrote:

 [Patch 1/5]
 Author: Frederick Grose fgr...@sugarlabs.org
 Date:   Thu Apr 14 09:29:14 2011

Re: [SoaS] [Sugar-devel] new SoaSv5 test image - Last change to test andfix issues

[Frederick Grose]

On Mon, Jun 13, 2011 at 5:14 PM, Peter Robinson pbrobin...@gmail.comwrote:

 {...}


 4) Main issue #2: activities only start 50% of the time. This is true
 for *all* activities. It's not clear why an activity will start one time and
 not another (it prints didn't start message). With Mango Lassi, this
 happens occasionally/rarely for me; here it happens *a lot*.


 Yes, I'm seeing this on a LiveUSB key but not on a standard Fedora 15
 install with sugar (same release), it seems to have only started recently,
 or maybe regressed more recently,

This problem also occurs with Sugar in standard Fedora-15 Desktop (Linux
Dell 2.6.38.7-30.fc15.x86_64, fully updated) when the Sugar environment is
selected at login.

I noticed from the yum.log that dbus-libs was updated:


Jun 01 22:32:44 Installed: 1:dbus-libs-1.4.6-4.fc15.i686

https://bugs.sugarlabs.org/ticket/2892#comment:3

 --Fred


 but I'm not sure of what the fix is. It really needs a Sugar dev to look
 closer at it but they don't seem to be interested at the moment.


 I thought maybe this had something to do with the USB drives I'd made with
 LiveUSB Creator. It doesn't. I created two: one 2GB, one 4GB with all memory
 protected.


 It might be something to do with the live image vs a full install. It
 almost seems timing oriented.



{...}



Peter
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] new SoaSv5 test image - Last change to test and fix issues

[Frederick Grose]

On Sun, Jun 12, 2011 at 3:49 PM, Peter Robinson pbrobin...@gmail.comwrote:

 Hi All,

 {...}

 NOTE: This is the last chance to test and get things fixed. Please provide
 concise details to any issues in reply to this mail.

 Cheers,
 Peter


Observed on http://fedora.roving-it.com/SoaSv5-20110612-x86_64.iso md5sum
ed4f053f5cac185532e6e7c1d68e34fb, installed with the onboard
livecd-iso-to-disk script.

Clicking on the Network icon changes the control panel's toolbar to include
the 'Network' icon, title, Cancel,  OK buttons, but nothing else loads on
the panel.

The Cancel and OK buttons don't function. (One must select another panel
item and Cancel or OK from there.)
shell.log segment in the ticket,
http://bugs.sugarlabs.org/ticket/2894

--Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] new SoaSv5 test image - Last change to test and fix issues

[Frederick Grose]

On Sun, Jun 12, 2011 at 3:49 PM, Peter Robinson pbrobin...@gmail.comwrote:

 Hi All,

 I was hoping to have this out over a week ago but I had a slight diversion
 via hospital which delayed proceedings.

 So below are links to a new pair (32 and 64 bit) of images for your testing
 pleasure.

 http://fedora.roving-it.com/SoaSv5-20110612-x86_64.iso
 http://fedora.roving-it.com/SoaSv5-20110612-i686.iso

 The network issue is still there, its partially working from the work that
 I did with some assistance from John Dulaney. I've included another utility
 to enable initial configuration of a wireless access point and from there it
 will auto connect and should mostly work. There's issues with the main
 network view and in the control panel but it seems no one else cares enough
 to assist me in getting it fixed. To configure an AP run the command
 nm-connection-editor from a terminal as the standard user (not root).

 I don't believe there are any other major blockers for this release. If you
 believe there to be any issues speak up now and provide fixes for it.

 NOTE: This is the last chance to test and get things fixed. Please provide
 concise details to any issues in reply to this mail.

 Cheers,
 Peter


x86_64.iso installed with onboard livecd-iso-to-disk.

Surf, Terminal, Log, Physics, Clock, Record, Turtle Art failed to launch,
all with error logs similar to this:

** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox)
Traceback (most recent call last):
  File /usr/bin/sugar-activity, line 21, in module
main.main()
  File /usr/lib/python2.7/site-packages/sugar/activity/main.py, line 158,
in main
create_activity_instance(activity_constructor, activity_handle)
  File /usr/lib/python2.7/site-packages/sugar/activity/main.py, line 37,
in create_activity_instance
activity = constructor(handle)
  File /usr/share/sugar/activities/Terminal.activity/terminal.py, line 54,
in __init__
activity.Activity.__init__(self, handle)
  File /usr/lib/python2.7/site-packages/sugar/activity/activity.py, line
328, in __init__
warn_if_none=False)
  File /usr/lib/python2.7/site-packages/sugar/presence/presenceservice.py,
line 89, in get_activity
dbus_interface=CONN_INTERFACE_ACTIVITY_PROPERTIES)
  File /usr/lib/python2.7/site-packages/dbus/proxies.py, line 68, in
__call__
return self._proxy_method(*args, **keywords)
  File /usr/lib/python2.7/site-packages/dbus/proxies.py, line 140, in
__call__
**keywords)
  File /usr/lib/python2.7/site-packages/dbus/connection.py, line 630, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message
did not receive a reply (timeout by message bus)
Exited with status 1, pid 1765 data (None, open file 'fdopen', mode 'w'
at 0x333bed0, '9ade639fd64cdc11fe37828faffb0dc269f9a4ba')

shell.log was filled with lines like the following:

Traceback (most recent call last):
  File /usr/lib/python2.7/site-packages/dbus/connection.py, line 589, in
msg_reply_handler
*message.get_args_list()))
  File /usr/lib/python2.7/site-packages/jarabe/model/neighborhood.py, line
212, in __error_handler_cb
error))
RuntimeError: Error when calling BuddyInfo.GetActivities:
org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout
by message bus)


Pippy, Etoys, Speak, Calculate, Chat, Memorize, Write, Abacus,  IRC did
successfully launch.

See https://bugs.sugarlabs.org/ticket/2892 for the logs.

--Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] [PATCH 1/5] Support Live image mounting in fs.py

[Frederick Grose]

[Patch 1/5]
Author: Frederick Grose fgr...@sugarlabs.org
Date:   Thu Apr 14 09:29:14 2011 -0400

   Support Live image mounting.

   Provide DiskMount with mount options, DeviceMapperSnapshot with a
device attribute, and a new LiveImageMount class.

diff --git a/imgcreate/fs.py b/imgcreate/fs.py
index d5307a2..0871182 100644
--- a/imgcreate/fs.py
+++ b/imgcreate/fs.py
@@ -324,7 +324,6 @@ class LoopbackDisk(Disk):
 self.device = None


-
class SparseLoopbackDisk(LoopbackDisk):
 A Disk backed by a sparse file via the loop module.
def __init__(self, lofile, size):
@@ -377,11 +376,12 @@ class Mount:

class DiskMount(Mount):
 A Mount object that handles mounting of a Disk.
-def __init__(self, disk, mountdir, fstype = None, rmmountdir = True):
+def __init__(self, disk, mountdir, fstype=None, rmmountdir=True,
ops=None):
Mount.__init__(self, mountdir)

self.disk = disk
self.fstype = fstype
+self.ops = ops
self.rmmountdir = rmmountdir

self.mounted = False
@@ -435,6 +435,8 @@ class DiskMount(Mount):
 args = [ /bin/mount, self.disk.device, self.mountdir ]
if self.fstype:
 args.extend([-t, self.fstype])
+if self.ops:
+args.extend(['-o', self.ops])

rc = call(args)
 if rc != 0:
@@ -530,6 +532,7 @@ class ExtDiskMount(DiskMount):
 self.__resize_filesystem(size)
return minsize

+
class DeviceMapperSnapshot(object):
 def __init__(self, imgloop, cowloop):
self.imgloop = imgloop
@@ -541,6 +544,7 @@ class DeviceMapperSnapshot(object):
def get_path(self):
 if self.__name is None:
return None
+return self.device
return os.path.join(/dev/mapper, self.__name)
 path = property(get_path)

@@ -569,6 +573,7 @@ class DeviceMapperSnapshot(object):
 string.join(args,  ))

self.__created = True
+self.device = os.path.join('/dev/mapper', self.__name)

 def remove(self, ignore_errors = False):
if not self.__created:
@@ -610,6 +615,89 @@ class DeviceMapperSnapshot(object):
except ValueError:
 raise SnapshotError(Failed to parse dmsetup status:  + out)

+
+class LiveImageMount(object):
+A class for mounting a LiveOS image installed with an active
overlay.
+
+def __init__(self, disk, mountdir, overlay, tmpdir='/tmp'):
+self.disk = disk
+self.mountdir = mountdir
+self.overlay = overlay
+self.tmpdir = tmpdir
+self.__created = False
+self.squashmnt = None
+self.homemnt = None
+self.mntlive = None
+
+def __create(self):
+if self.__created:
+return
+self.liveosdevmnt = DiskMount(self.disk,
+   os.path.join(self.tmpdir, 'device'))
+self.liveosdevmnt.mount()
+liveosdir = os.path.join(self.liveosdevmnt.mountdir, 'LiveOS')
+sqfs_img = os.path.join(liveosdir, 'squashfs.img')
+if os.path.exists(sqfs_img):
+self.squashloop = LoopbackDisk(sqfs_img, None)
+self.squashmnt = DiskMount(self.squashloop,
+   os.path.join(self.tmpdir, 'squash'))
+self.squashmnt.mount()
+rootfs_img = os.path.join(self.squashmnt.mountdir,
+  'LiveOS', 'ext3fs.img')
+else:
+rootfs_img = os.path.join(liveosdir, 'ext3fs.img')
+if not os.path.exists(rootfs_img):
+raise SnapshotError(Failed to find a LiveOS root image.)
+self.imgloop = LoopbackDisk(rootfs_img, None)
+self.overlay = os.path.join(liveosdir, self.overlay)
+self.cowloop = LoopbackDisk(self.overlay, None)
+home_img = os.path.join(liveosdir, 'home.img')
+self.dm_liveimage = DeviceMapperSnapshot(self.imgloop,
self.cowloop)
+self.dm_livemount = DiskMount(self.dm_liveimage, self.mountdir)
+if os.path.exists(home_img):
+homedir = os.path.join(self.mountdir, 'home')
+self.homemnt = LoopbackMount(home_img, homedir)
+self.__created = True
+
+def mount(self):
+try:
+self.__create()
+if not self.liveosdevmnt.mounted:
+self.liveosdevmnt.mount()
+if not self.squashmnt.mounted:
+self.squashmnt.mount()
+self.dm_livemount.mount()
+if self.homemnt:
+self.homemnt.mount()
+mntlivedir = os.path.join(self.mountdir, 'mnt', 'live')
+if not os.path.exists(mntlivedir):
+os.makedirs(mntlivedir)
+self.mntlive = BindChrootMount(self.liveosdevmnt.mountdir,
+   '', mntlivedir)
+self.mntlive.mount()
+except MountError, e:
+raise SnapshotError(Failed to mount %s : %s % (self.disk, e

[SoaS] [PATCH 3/5] Liveimage-mount within running LiveOS instance

[Frederick Grose]

[Patch 3/5]
Author: Frederick Grose fgr...@sugarlabs.org
Date:   Thu Apr 14 10:37:13 2011 -0400

Support usage within a booted LiveOS instance.

Provide functions to add loop devices and remove then on exit, a
LiveImageMountError(Exception) class for better error handling, and
random device mapper names.

diff --git a/tools/liveimage-mount b/tools/liveimage-mount
index 80d67d1..1ee5b16 100755
--- a/tools/liveimage-mount
+++ b/tools/liveimage-mount
@@ -23,10 +23,13 @@
 import os
 import sys
 import stat
+import time
 import getopt
+import random
 import tempfile
 import subprocess

+extra_loops = []

 def usage(ecode):
 print Usage:
@@ -40,6 +43,18 @@ def usage(ecode):
 and [ARGS] = [arg1[ arg2[ ...]]]\n
 sys.exit(ecode)

+class LiveImageMountError(Exception):
+An exception base class for all liveimage-mount errors.
+def __init__(self, msg):
+Exception.__init__(self, msg)
+def __str__(self):
+try:
+return str(self.message)
+except UnicodeEncodeError:
+return repr(self.message)
+
+def __unicode__(self):
+return unicode(self.message)

 def call(*popenargs, **kwargs):
 '''
@@ -62,43 +77,57 @@ def call(*popenargs, **kwargs):
 return rc


-def rcall(args, env=None):
+def rcall(args, stdin=None, stderr=True, env=None):
+out, err, p, environ = None, None, None, None
 if env:
 environ = os.environ.copy()
 environ.update(env)
-else:
-environ = None
 try:
-p = subprocess.Popen(args, stdout=subprocess.PIPE,
- stderr=subprocess.PIPE, env=environ)
-out, err = p.communicate()
+p = subprocess.Popen(args, stdin=subprocess.PIPE, env=environ,
+ stdout=subprocess.PIPE,
stderr=subprocess.PIPE)
+out, err = p.communicate(stdin)
 except OSError, e:
-raise CreatorError(uFailed to execute:\n'%s'\n'%s' % (args, e))
+raise LiveImageMountError(uFailed executing:\n'%s'\n'%s' % (args,
e))
 except:
-raise CreatorError(uFailed to execute:\n'%s'
-\renviron: '%s'\nstdout: '%s'\nstderr: '%s'\nreturncode:
'%s' %
-(args, environ, out, err, p.returncode))
+raise LiveImageMountError(uFailed to execute:\n'%s'
+   \renviron: '%s'\nstdout: '%s'\nstderr:
'%s' %
+  (args, environ, out, err))
 else:
-if p.returncode != 0:
-raise CreatorError(uError in call:\n'%s'\nenviron: '%s'
-\rstdout: '%s'\nstderr: '%s'\nreturncode: '%s' %
-(args, environ, out, err, p.returncode))
+if p.returncode != 0 and stderr:
+raise LiveImageMountError(u'''Error in call:\n'%s'\nenviron:
'%s'
+\rstdout: %s\nstderr: %sreturncode: %s''' %
+   (args, environ, out, err, p.returncode))
 return out


-def get_device_mountpoint(path):
-Return the device and mountpoint for a file or device path.
+def get_loop(path):
+Return the loop device for a given mount point path.
+
+loopdevice = None
+for loop in rcall(['/sbin/losetup', '-a']).splitlines():
+info = loop.split()
+if path == info[2].strip('()'):
+loopdevice = info[0].rstrip(':')
+break
+return loopdevice
+
+
+def add_loop(n=8):
+Add a loop device.
+
+while os.path.exists('/dev/loop%s' % n):
+n += 1
+os.mknod('/dev/loop%s' % n, 0660 | stat.S_IFBLK, os.makedev(7, n))
+extra_loops.extend(['/dev/loop%s' % n])
+return '/dev/loop%s' % n

-info = list()
-info[0:5] = [None] * 6
-if os.path.exists(path):
-st_mode = os.stat(path).st_mode
-if stat.S_ISBLK(st_mode) or os.path.ismount(path):
-devinfo = rcall(['/bin/df', path]).splitlines()
-info = devinfo[1].split(None)
-if len(info) == 1:
-info.extend(devinfo[2].split(None))
-return [info[0], info[5]]
+
+def loop_setup(path):
+Make and associate a loop device with an image file or device.
+
+loop = add_loop()
+call(['/sbin/losetup', loop, path])
+return loop


 def main():
@@ -145,18 +174,16 @@ def main():
 img_type = 'blk'
 imgloop = None
 overlayloop = None
+liveosmnt = tempfile.mkdtemp(prefix='livemnt-device-')
 else:
 img_type = 'iso'
-
-if img_type is 'blk':
-liveosmnt = tempfile.mkdtemp(prefix='livemnt-device-')
-if img_type is 'iso':
 liveosmnt = tempfile.mkdtemp(prefix='livemnt-iso-')

 liveosdir = os.path.join(liveosmnt, 'LiveOS')
 homemnt = None
 dm_cow = None
 mntlive = None
+rmmntdir = None

 command = args[2:]
 verbose = not command
@@ -164,13 +191,12 @@ def main():
 squashmnt = tempfile.mkdtemp(prefix='livemnt-squash-')
 squashloop = None
 imgloop = None
-losetup_args = ['/sbin

[SoaS] [PATCH 5/5] Document --copy-home --include options

[Frederick Grose]

[Patch 5/5]
Author: Frederick Grose fgr...@sugarlabs.org
Date:   Thu Apr 14 11:12:38 2011 -0400

Document --copy-home and --include options.

diff --git a/docs/livecd-iso-to-disk.pod b/docs/livecd-iso-to-disk.pod
index 7ef0c14..5550fc6 100644
--- a/docs/livecd-iso-to-disk.pod
+++ b/docs/livecd-iso-to-disk.pod
@@ -6,7 +6,7 @@ livecd-iso-to-disk - installs bootable Live images onto
USB/SD storage devices.

 =head1 SYNOPSIS

-Blivecd-iso-to-disk  [--help] [--noverify] [--format] [--reset-mbr]
[--efi] [--skipcopy] [--force] [--xo] [--xo-no-home] [--timeout time]
[--totaltimeout time] [--extra-kernel-args args] [--multi] [--livedir
dir] [--compress] [--skipcompress] [--swap-size-mb size]
[--overlay-size-mb size] [--home-size-mb size] [--delete-home]
[--crypted-home] [--unencrypted-home] source target device
+Blivecd-iso-to-disk  [--help] [--noverify] [--format] [--reset-mbr]
[--efi] [--skipcopy] [--force] [--xo] [--xo-no-home] [--timeout time]
[--totaltimeout time] [--extra-kernel-args args] [--multi] [--livedir
dir] [--compress] [--skipcompress] [--swap-size-mb size]
[--overlay-size-mb size] [--home-size-mb size] [--delete-home]
[--crypted-home] [--unencrypted-home] [--copy-home] [--include file s]
source target device

 Simplest

@@ -135,6 +135,20 @@ Specifies the default option to encrypt a new
persistent home directory if --hom

 Prevents the default option to encrypt a new persistent home directory.

+=item --copy-home
+
+This option allows one to copy a persistent home folder from one LiveOS
image to the target image.  Changes already made in the source home
directory will be propagated to the new image.
+
+=over 4
+
+WARNING: User-sensitive information, such as password cookies and user and
application data, will be copied to the new image! Scrub this information
before using this option.
+
+=back
+
+item --include path s
+
+This option allows one to copy one or more file or directory paths from the
outer source filesystem to the same path on the target.  Multiple paths
should be specified in one string, i.e., --include path1 path2 ...
+
 =back

 =head1 CONTRIBUTORS
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] SoaS v5 status

[Frederick Grose]

On Tue, Apr 5, 2011 at 1:13 AM, Peter Robinson pbrobin...@gmail.com wrote:

 Hi All,

 Sorry for a lot of the recent radio silence. In short I've been
 travelling a lot and work and my personal life took over pretty close
 to completely since FUDCon at the end of January :-(

 That said I've spent some time over the last couple of days to fix up
 and  update some SoaS bits and as of the next compose the Fedora 15
 live image should be working [1].

 Those impatient people can boot up the current release and when it
 boots to the login screen do a Ctrl + Alt + F2 login as root, run
 rpm -e openbox, do a Ctrl + Alt + F8 and then login and you should
 get a lovely sweet Sugar :-D

 So next on the SoaS release ToDo list is the following:
 - List of shipped (and working) Activities
 - Release name (Suggestions?)


http://wiki.sugarlabs.org/go/Features/Soas_V5/
http://git.sugarlabs.org/~FGrose/sugar-logos/coconut

- Testing.


I have a pending set (in a few days) of commits to livecd-tools,
https://bugzilla.redhat.com/show_bug.cgi?id=448030#c24
that will provide many of the features I've proposed.
(I'm testing the various code paths now.)

http://git.sugarlabs.org/~FGrose/soas/sugar-clone-extensions

--Fred


 Cheers,
 Peter

 [1] http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/

___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] [Announce] Rebuild/Refresh a custom SoaS iso from a running stick

[Frederick Grose]

Announcing: SoaS-remix

SoaS-remix is a bundle of edit-liveos.py and supporting scripts to make
testing and use easier.

SoaS-remix includes a late alpha version of edit-liveos.py with a
launcher named 'livecd-disk-to-iso', and temporary versions of fs.py,
live.py, creator.py (pending livecd-tools acceptance).

The SoaS-remix bundle will inject itself into the image, unbundle itself
into /tmp, launch edit-liveos.py (with editable options), then cleanup
/tmp on completion.

The Sugar Clone extensions are now in a Sugar on a Stick repository
clone at http://git.sugarlabs.org/~FGrose/soas/sugar-clone-extensions.

Get the SoaS-remix bundle:

  wget http://people.sugarlabs.org/fgrose/SoaS-remix

See more about the project and a usage recipe at:
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone

Testing would be appreciated.

 --Fred

On Fri, Jan 28, 2011 at 4:07 AM, Frederick Grose fgr...@gmail.com wrote:

 We are a good ways closer to being able to
 Support cloning of a customized SoaS image directly from that running
 image, which is the SoaS spin F15 feature proposal #4 on this page,
 http://wiki.sugarlabs.org/go/Features/Soas_V5/

 If your SoaS machine has 4+ GiBytes disc space (as is commonly available on
 an attached hard drive that you could mount in your SoaS instance), then
 this alpha version python script, edit-liveos.py,
 http://people.sugarlabs.org/fgrose/edit-liveos

 (based on the livecd-tools, edit-livecd), and a copy or rsync will let you
 build a new, custom installation .iso file from your running SoaS instance.

 I've tested the script on SoaS in F13 and F14, and with some filesystem
 hacks (this is my first python project), it will run to completion.

 I've booted the F14 version and confirmed that the system overlay file was
 refreshed and the system and user customizations had transferred. See this
 screenshot of 'About my Computer':
 http://people.sugarlabs.org/fgrose/My%20computer.png

 Customization of SoaS spins have been a long-sought goal of the project.
  See, for example,
 http://wiki.sugarlabs.org/go/Features/Feature_SoaS_customization, and all
 the work Satellit has contributed toward the Sugar Creation Kit,
 http://wiki.sugarlabs.org/go/Sugar_Creation_Kit

 There remain many supporting tasks to be completed before we have an
 integrated product.

 1. The edit-liveos.py script depends on rsync, which has to be
installed on SoaS first.
 2. The livecd-iso-to-disk script needs to be amended to transfer the
home.img file from the new source.iso
 3. Other supporting installation scripts and a Sugar Activity are
needed to simplify the use of the onboard image builder.

 Some of the above are addressed in Sugar Clone,
 http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone
 which is a quick way to achieve customization without any disc resources
 beyond those on the Sugar Stick itself.

 I imagine that further refinements of these tools will allow us to
 automatically monitor the system overlay consumption and advise the Learner
 to run a refresh rebuilds their personal system or provides a fresh one
 from the School Server.

 Please see the Sugar Clone page to see the project goals and plans, and
 please help test the new, edit-liveos script!

--Fred

___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] [Announce] Rebuild/Refresh a custom SoaS iso from a running stick

[Frederick Grose]

We are a good ways closer to being able to
Support cloning of a customized SoaS image directly from that running
image, which is the SoaS spin F15 feature proposal #4 on this page,
http://wiki.sugarlabs.org/go/Features/Soas_V5/

If your SoaS machine has 4+ GiBytes disc space (as is commonly available on
an attached hard drive that you could mount in your SoaS instance), then
this alpha version python script, edit-liveos.py,
http://people.sugarlabs.org/fgrose/edit-liveos

(based on the livecd-tools, edit-livecd), and a copy or rsync will let you
build a new, custom installation .iso file from your running SoaS instance.

I've tested the script on SoaS in F13 and F14, and with some filesystem
hacks (this is my first python project), it will run to completion.

I've booted the F14 version and confirmed that the system overlay file was
refreshed and the system and user customizations had transferred. See this
screenshot of 'About my Computer':
http://people.sugarlabs.org/fgrose/My%20computer.png

Customization of SoaS spins have been a long-sought goal of the project.
 See, for example,
http://wiki.sugarlabs.org/go/Features/Feature_SoaS_customization, and all
the work Satellit has contributed toward the Sugar Creation Kit,
http://wiki.sugarlabs.org/go/Sugar_Creation_Kit

There remain many supporting tasks to be completed before we have an
integrated product.

1. The edit-liveos.py script depends on rsync, which has to be
   installed on SoaS first.
2. The livecd-iso-to-disk script needs to be amended to transfer the
   home.img file from the new source.iso
3. Other supporting installation scripts and a Sugar Activity are
   needed to simplify the use of the onboard image builder.

Some of the above are addressed in Sugar Clone,
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone
which is a quick way to achieve customization without any disc resources
beyond those on the Sugar Stick itself.

I imagine that further refinements of these tools will allow us to
automatically monitor the system overlay consumption and advise the Learner
to run a refresh rebuilds their personal system or provides a fresh one
from the School Server.

Please see the Sugar Clone page to see the project goals and plans, and
please help test the new, edit-liveos script!

   --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] SoaS windows USB builder

[Frederick Grose]

On Fri, Jan 21, 2011 at 4:14 PM, Kevin Gordon kgordon...@gmail.com wrote:


 Folks:

 It would appear that the fix which now allows the Fedora Windows USB
 builder to now correctly create a bootable USB stick of the most recent F14
 based SoaS USB (with syslinux 4.03),  the app now no longer properlry
 creates the previous SoaS versions (the berries) from the spin ISO's, that
 will boot.

 Workaround appears to be to use the same methodology as before but in the
 case where one wants to create older version bootable usb's,  one now
 manually copies an  *older* 3xx syslinux into the windows working directory
 before doing the build

 Full instructions for this method are listed in this SoaS digest in
 previous posts.  If one didn't keep their old syslinux, its available in the
 archives at http://www.kernel.org/pub/linux/utils/boot/syslinux/

 KG


Other workarounds discovered,

a. Enter linux0 at the boot: prompt for SoaS 1-3 installed with Syslinux 4.0
by Fedora Live USB Creator 3.9.3
http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg18957.html

b. replace vesamenu.C32 in the /syslinux folder on the USB device with a
copy from the isolinux folder in a SoaS 1-3 iso file.  This worked for me
with Mirabelle.

  --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] network issues

[Frederick Grose]

On Sun, Jan 9, 2011 at 7:53 AM, roberto robert...@gmail.com wrote:

 On Fri, Dec 17, 2010 at 1:37 PM, Peter Robinson pbrobin...@gmail.com
 wrote:
 
  You can do that by running the command (as root) service
  NetworkManager status and if that has issues do a service
  NetworkManager restart to (re)start the service. Also what sort of
  network device is it, wireless network adapters usually use wlan0 etc.
  Did you have to add a driver to make it work to that point?
 
  Peter

 i've run
 # service NetworkManager status
 and it issued the daemon was correctly running;
 i've restarted it anyway; no troubles

 moreover, if i try
 # iwlist scan
 my wireless AP is correctly seen and recognized but if i move with F1
 to the network view then nothing appears about my AP; only three
 Ad-Hoc wireless network without any specific name


Consider http://bugs.sugarlabs.org/ticket/2023
http://bugs.sugarlabs.org/ticket/2023
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Mango Lassi USB Boot issue

[Frederick Grose]

On Mon, Dec 20, 2010 at 10:49 PM, Rajiv Bhushan rajiv.bhus...@gmail.comwrote:



 Tom,

 Since I did not wish to go through the chores of installing Virtual Box
 and then running Fedora in it, I decided to burn a Sugar Mango Lassi CD, and
 then to use livecd-iso-to-disk

 As per the instructions, I booted up the CD, loaded Sugar, went to terminal
 activity, became root, and changed directory to /LiveOS

 So far so good.

 I executed the following command as stated in the instructions -- the USB
 Flash Drive was in /dev/sdc1

 ./livecd-iso-to-disk --reset-mbr --overlay-size-mb 300 --home-size-mb 175
 --delete-home --unencrypted-home /dev/live /dev/sdc1

 The system came back promptly with the livecd-iso-to-disk usage options

 In other words, the options I was passing to the program were incorrect!

 when I did a ls /dev

 I did not find /dev/live listed. I did see a /dev/cdrom listed, but no
 /dev/live

 In other words, where is the iso source, that is supposed to be copied to
 the Flash drive?


A symbolic link connecting /dev/live to /dev/sr0 was a standard LiveOS
feature that failed to make it into SoaS Mango Lassi.

You can use the /dev/cdrom symbolic link or /dev/sr0 directly.

I will update the wiki.

Thanks for testing!--Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] the final sprint to SoaS 4

[Frederick Grose]

On Thu, Oct 14, 2010 at 4:03 AM, Peter Robinson pbrobin...@gmail.comwrote:

 Hi All,

 We're on the final sprint to SoaS v4

 Adam Williamson has created some testing guidelines for Fedora QA for
 Sugar desktop testing. You can find details here [1] and feedback
 would be greatly appreciated so we can improve this for the Fedora 15
 / SoaS v5 cycle.

 [1]
 https://fedoraproject.org/wiki/Test_Results:Fedora_14_Final_TC1_Desktop

 From the discussion (that I remember) that Simon, Thomas and I had the
 other night these were the issues we had:
 - Terminal issues - fixed with vte 0.26.1 release that will be in
 stable tomorrow
 - Physics issues - New version here please test
 https://admin.fedoraproject.org/updates/sugar-physics-7-1.fc14
 - gnome-keyring issue. Not fixed yet. Helped wanted. I'm going to try
 and get time to look at this further today.
 - Read issue - Going to look at it today

 Looking through the rest of the list here [2] I'm not sure if there's
 anything else that's not specific to the XO hardware other than issues
 with Paint and Colors which I'm not sure what the status is.

 If there's anything else please speak up NOW!.

 Regards,
 Peter

 [2]
 http://bugs.sugarlabs.org/query?status=acceptedstatus=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=statuscol=typecol=prioritycol=milestonecol=componentkeywords=~olpc-0.90



1.  What about this query?

http://bugs.sugarlabs.org/query?status=acceptedstatus=assignedstatus=newstatus=reopenedgroupdesc=1group=milestonecomponent=SoaSorder=prioritycol=idcol=summarycol=componentcol=statuscol=typecol=prioritycol=milestonecol=reportercol=timecol=changetime



2.  Please also note this suggestion about abrt filling the overlay by
writing to /var/cache/abrt/ :

http://www.mail-archive.com/soas@lists.sugarlabs.org/msg01696.html

Sascha, suggested that it would have been better to resolve some deeper
problems, but lacking that resolution is no reason to destroy a whole
installation by exhausting the overlay.


3.  Please relocate the placement of livecd-iso-to-disk as described in
http://bugs.sugarlabs.org/ticket/2197

This can make some installations and replication easier.


4.  Please consider including the rsync package.  This will support ad hoc
replication of liveos images, see
http://lists.fedoraproject.org/pipermail/livecd/2010-August/006098.html.


Thank you!
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] LiveOS on PPC was: Get Sugar landing page

[Frederick Grose]

On Tue, Sep 14, 2010 at 5:06 PM, pbrobin...@gmail.com
pbrobin...@gmail.comwrote:

 On Tue, Sep 14, 2010 at 9:57 PM, Walter Bender walter.ben...@gmail.com
 wrote:
  On Tue, Sep 14, 2010 at 4:52 PM, pbrobin...@gmail.com
  pbrobin...@gmail.com wrote:
  On Tue, Sep 14, 2010 at 9:45 PM, Walter Bender walter.ben...@gmail.com
 wrote:
  On Tue, Sep 14, 2010 at 4:33 PM, pbrobin...@gmail.com
  pbrobin...@gmail.com wrote:



{...}

 There are two problems with the Mac platform:
 1) Linux doesn't support 32 bit platforms from 64 bit EFI systems.
 This is a kernel issue and is the case on all platforms. Someone I
 know at one of the major server companies was going to have a look at
 this for me as all their new servers will be 64 bit and are EFI based
 and while they will only support 64 bit on them they have customers
 that will want to run 32 bit. I've followed up but not heard anything
 back.

 2) Graphics support due to some random way the Mac platform deals with
 its GPU initialisation. This will be fixed for F-14 (and so SoaSv4).
 The patches might also fix #1 but I don't have Macs to test.

 # 2 should be in the F-14 beta so testers would be welcome on 64 bit
 and it would be interesting to see if it also fixes #1 as well.


What about PowerPC Macs?

These lines from
http://git.fedorahosted.org/git/?p=livecd;a=blob;f=imgcreate/live.py;h=9153e1010b5e8da1bc90c8a8fd5a558840903db5;hb=HEAD
suggest that they were once supported:

 879 http://git.fedorahosted.org/cgi-bin/gitweb.cgi#l879arch =
rpmUtils.arch.getBaseArch()
 880 http://git.fedorahosted.org/cgi-bin/gitweb.cgi#l880if arch in
(i386, x86_64):
 881 http://git.fedorahosted.org/cgi-bin/gitweb.cgi#l881
LiveImageCreator = x86LiveImageCreator
 882 http://git.fedorahosted.org/cgi-bin/gitweb.cgi#l882elif arch in (ppc,):
 883 http://git.fedorahosted.org/cgi-bin/gitweb.cgi#l883
LiveImageCreator = ppcLiveImageCreator
 884 http://git.fedorahosted.org/cgi-bin/gitweb.cgi#l884elif arch in
(ppc64,):
 885 http://git.fedorahosted.org/cgi-bin/gitweb.cgi#l885
LiveImageCreator = ppc64LiveImageCreator
 886 http://git.fedorahosted.org/cgi-bin/gitweb.cgi#l886 else:
 887 http://git.fedorahosted.org/cgi-bin/gitweb.cgi#l887raise
CreatorError(Architecture not supported!)

--Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] Installing Activities question

[Frederick Grose]

From a new question on the wiki:
http://wiki.sugarlabs.org/go/Sugar_help#on_Sugar_activities

I downloaded Sugar on a Stick and ran it on my computer -- however, the
project I'm working with is about the Calculate activity. I found how to
download the Calculate activity from your Activities page, however I don't
know how to take that downloaded activity and incorporate it into my USB
device/environment. So my question is: How can I take a downloaded activity
and use it with Sugar on a Stick?

There are a number of ways to install new Activities into Sugar:

   1. Using the Browse Activity in Sugar, navigate to the *Sugar Activity
   Library* (http://activities.sugarlabs.org), find the Activity you want
   and click the 'Download Now' button. In Sugar, you should see an alert that
   counts down the transfer. Once the download is saved, a new alert offers to
   show the new Activity in your Journal. Clicking the 'Show in Journal' button
   will take you to a detail view of the ActivityName.xo entry. Clicking the
   icon at the top left of this view will launch the Activity. The Home view
   favorites and Journal will show the new Activity installed.
   2. If the Activity is downloaded to another computer, the downloaded
   activity is contained in the ActivityName.xo file that is saved on the
   computer that did the download. If you have another USB device, copy that
   file to the root folder, /, at the base of your USB device. Then boot
   Sugar on a Stick and go to the Journal. When the second USB device is
   inserted, it should appear in the bottom bar of the Journal. Clicking on the
   USB device icon will show its contents. Drag the ActivityName.xo file to
   the Journal icon at the far left of the bottom bar. Then click on the
   Journal icon and the ActivityName.xo entry will display at the top of the
   Journal. Click the icon for ActivityName and it will launch.
   3. If the downloaded ActivityName.xo file is copied to the SoaS USB
   device, and that device is booted into Sugar, one may use the Terminal
   activity to unzip the file into the /home/liveuser/Activities folder using
   these commands: cd /home/liveuser/Activities/ (The /home/liveuser/ path
   may be substituted with /home/olpc/ on an XO.) unzip
   /mnt/live/ActivityName.xo (The /mnt/live/path-to-.xo may be substituted
   with an accessible ActivityName.xo path.) The Activity will appear in
   the Home view favorites, and after it has been launched, it will appear in
   the Journa


This is a good candidate for the FAQ,
http://wiki.sugarlabs.org/go/Sugar_Labs/FAQ#Activities, once the community
has had a chance to refine the text.
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Semantic_Forms are they on Our Wiki?

[Frederick Grose]

On Tue, Aug 24, 2010 at 8:24 AM, Thomas C Gilliard 
satel...@bendbroadband.com wrote:

 http://www.mediawiki.org/wiki/Semantic_Forms

 Fred;

 Is this something we have or could add to our wiki.


Semantic Forms are available in the OLPC wiki.  How about demonstrating your
proposal there?

 --Fred


 I am manually building forms now but the editing process is probably too
 daunting for the average user.

 jlaska on #fedora-qa thought this might be a possible improvement to
 media-wiki for testing tables for Soas.

 examples:

 http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table#Activity_Test_Results

 http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick_release_process#Test_Matix

___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] /var/cache/abrt is an overlay killer

[Frederick Grose]

/var/cache/abrt is another directory that can quickly fill the operating
system overlay file.  In testing I've noticed 10s to 100s of megabytes in
coredumps in subdirectories of /var/cache/abrt/.

The abrt application doesn't present itself in Sugar, so a use model
allowing for a non persistent cache seems reasonable.

Lines 263 to 268 of
http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/fedora-live-mini.ks
# make it so that we don't do writing to the overlay for things which
# are just tmpdirs/caches
mount -t tmpfs -o mode=0755 varcacheyum /var/cache/yum
mount -t tmpfs tmp /tmp
mount -t tmpfs vartmp /var/tmp
[ -x /sbin/restorecon ]  /sbin/restorecon /var/cache/yum /tmp /var/tmp
/dev/null 21

adding
mount -t tmpfs -o mode=0755 varcacheabrt /var/cache/abrt

would serve to preserve overlay life.
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] Move root's home to /home/root

[Frederick Grose]

olpc-utils-1.0.27 has just implemented this (
http://dev.laptop.org/ticket/6700).
Beyond the advantages cited in the ticket, moving root's home to /home/root
will save valuable overlay space when one has configured a persistent home
directory. See http://wiki.sugarlabs.org/go/LiveOS_image.

--Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] [Testing] gcc installation issue in Fedora-13-Live-Soas.iso image on Virtual Box

[Frederick Grose]

Earlier responses:

On Thu, Aug 5, 2010 at 19:10, Frederick Grose fgr...@gmail.com wrote:
 On Thu, Aug 5, 2010 at 12:51 PM, kushan athukorala
 kushan.athukor...@gmail.com wrote:

 Hello,

 I am using Fedora-13-Live-Soas.iso image on a Oracle Virtual Box for
 automated test designs for OLPC activities.

 When I try to 'yum install gcc', the system hangs while updating
 glibc-common library.

 Does anyone has faced this issue before and appreciate a solution if any?

 --
 Cheers,
 Kushan Athukorala

 Boosting available memory and storage space may make a difference.
 See
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/VirtualBox/Preparing_a_disk_image#Installing_VirtualBox_Guest_Additions
 for
 some experiences.
 Enlarging the overlay size with --overlay-size-mb 1024 and the VM memory
 allocation may help provide headroom for the installation.
--Fred

I agree, but even then, I don't recommend using soas for that. What
about just installing Fedora 13 then install sugar, development tools,
etc?

Regards,

Tomeu

On Thu, Aug 5, 2010 at 1:27 PM, Gary Martin garycmar...@googlemail.comwrote:

 Hi Kushan,


 On 5 Aug 2010, at 17:51, kushan athukorala kushan.athukor...@gmail.com
 wrote:


 Hello,

 I am using Fedora-13-Live-Soas.iso image on a Oracle Virtual Box for
 automated test designs for OLPC activities.

 When I try to 'yum install gcc', the system hangs while updating
 glibc-common library.


 I've  not installed gcc, but for me usually that is a sign that yum has run
 out of memory. The various builds don't usually have any swap memory set as
 solid-state memory doesn't last as long when used for many/repeated write
 cycles. That's also one of the reasons yum is not usually used for regular
 users to upgrade and install activities in Sugar.


If SoaS is booted on a computer with a Linux swap partition on its hard
drive, SoaS will use it.
See this extract from my SoaS boot.log:

%G %GWelcome to Fedora
Press 'I' to enter interactive startup.
Starting udev: udevd-work[693]: '/usr/bin/vmmouse_detect' unexpected exit
with status 0x000b

udevd-work[696]: '/usr/bin/vmmouse_detect' unexpected exit with status
0x000b

%G [60G[  OK  ]
Setting hostname localhost.localdomain:  [60G[  OK  ]
Setting up Logical Volume Management:   No volume groups found
[60G[  OK  ]
Checking filesystems
[60G[  OK  ]
Mounting local filesystems:  [60G[  OK  ]
Enabling local filesystem quotas:  [60G[  OK  ]
Enabling /etc/fstab swaps:  [60G[  OK  ]
Entering non-interactive startup
Enabling swap partition /dev/sda5 [60G[  OK  ]
Mounting persistent /home Remounting live store r/w [60G[  OK  ]
[60G[  OK  ]

Also, one may test with this command:

[r...@localhost ~]# cat /proc/swaps
FilenameTypeSizeUsedPriority
/dev/sda5   partition29409200-1

Though, this doesn't apply directly to a virtual machine, which probably has
memory managed by the host.

--Fred


Make sure you have just Terminal open in Sugar to save memory, or even
 better, run you from the text console, ctrl+alt+F1 (ctrl+alt+F3 to get back
 to the Sugar GUI again). Heavy users of yum often add an extra sd card or
 USB, and set that as swap space, though your test environment will behave
 somewhat differently in high memory use situations.

 --Gary

 Does anyone has faced this issue before and appreciate a solution if any?

 --
 Cheers,
 Kushan Athukorala

 OLPC Automation Team
 Virtusa QA


___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Proposed feature for Soas-v4 : Remixability

[Frederick Grose]

On Tue, Jul 27, 2010 at 10:17 AM, Caryl Bigenho cbige...@hotmail.comwrote:

  Hi Tom,

 I love this idea!  {...}  It would be really nice to be able to create
 sticks with special focus like this for targeted projects.


Sugar Clone, http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone, is a
short-cut method to customize a SoaS installation that works with a
single-word command.  It would probably serve the targeted-project,
special-focus case.

   --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] SoaS filesystems was: Re: Sugar on a Stick Meeting on Monday at 1900 UTC

[Frederick Grose]

On Mon, Jul 19, 2010 at 6:13 PM, pbrobin...@gmail.com
pbrobin...@gmail.comwrote:

 On Mon, Jul 19, 2010 at 10:48 PM, Frederick Grose fgr...@gmail.com
 wrote:
  On Mon, Jul 19, 2010 at 5:37 PM, Walter Bender walter.ben...@gmail.com
  wrote:
 
  On Mon, Jul 19, 2010 at 1:06 PM, Frederick Grose fgr...@gmail.com
 wrote:
   On Mon, Jul 19, 2010 at 10:41 AM, Mel Chua m...@melchua.com wrote:
  
   I'm going to have to miss today's meeting, but as an update on my
 task
   from last week: http://bugs.sugarlabs.org/ticket/1798#comment:22
  
  
   See this comment added
   to http://bugs.sugarlabs.org/ticket/1798#comment:23 :
  
   School-based deployments may want to take advantage of the persistent
   /home/
   directory installation instead of the persistent OS overlay. The
   persistent
   home folder is not a write-once, ever-diminishing storage space.
  
   For consistency and stability reasons, the school may want to leave
 out
   the
   persistent OS overlay (using a temporary overlay on each boot) and
 just
   use
   the persistent /home/ directories to save the Learners' Journals and
   settings.
  
   If a school-wide system change were desired, the Sticks could be
   upgraded
   with a simple exchange of the /LiveOS/squashfs.img file in the base
 file
   system of each device or stick, perhaps, even triggered by the School
   Server.
 
 
 
  {...}
 
 
 
  if the size of the image changes
  dramatically, are there any issues regarding how space may have been
  allocated?
 
  Yes, I imagine that if all free space were allocated to the home.img file
  and a new, larger squashfs.img needed to fit on the disc, it would fail.
 
 
  {...}
 
 
 
   storage space optimization is discussed on this
   page,  http://wiki.sugarlabs.org/go/LiveOS_image.
 
  On that page, there are some reasons suggested for leaving some free
 space
  outside of the LiveOS installation.

 We're looking to have an option added to the liveusb-creator to select
 an option Use entire stick for image (or something similar) which
 would then get rid of the sqashfs all together and install the ext3
 partition straight to the usb stick so there's no issues with corrupt
 overlays and other related issues as it will be a plain filesystem
 straight onto a usb stick so there'll be no weird fu in between.

 Cheers,
 Peter


That is great for those with sufficient storage space.  There are some
compromises that suggest to me that SoaS should continue to fully support
LiveOS installations even if we choose to support a non-Live installation.

First is file space:

Using the --skipcompress option in the livecd-iso-to-disk installation
script results in a pristine installation that consumed 1.49 GB on disc, and
requires reformatting the USB/SD device to ext234. (I was testing on an
ext2-formatted disc in VirtualBox.)

With a fat32 formatted disc, the pristine image consumed 0.481 GB on disc.

On a 2-GB stick,  1.5 GB of space could be available for Sugar Activities or
other content such as textbooks with a LiveOS installation vs 0.5 for the
non-Live installation.

In the future, we hope to install SoaS onto smart phones and
other pocket-able devices where small images sizes will be even more
important.

Second, related to file space, is the speed of installation, replication,
and system sharing:

Installation onto the fat32 disc took 2:12 minutes:seconds on VirtualBox vs.
5:06 for the ext2 disc.  The smaller LiveOS image makes system installation,
backups, sharing quicker.

Third is reliability:

For non-specific USB/SD devices, the OLPC engineers recommend that one keep
the factory formatting,
see http://wiki.laptop.org/go/How_to_Damage_a_FLASH_Storage_Device

One may say that unexpected crashing from a overfilled persistent overlay is
a reliability problem.  Re-examining the failure report in
http://bugs.sugarlabs.org/ticket/1798#comment:18, the worst failure reported
suggests that in a classroom setting, the LiveOS installations worked
*reliably* for several months before the overlay filled up.  It seems,
rather, that there was insufficient understanding of the system limitations
and how to work with them.  I would be upset too, if a mountain highway
suddenly, and without warning, changed from 2 to 1 lane right at the hairpin
turn of an outer switchback and I was in the inner lane.

If one chooses to use a LiveOS persistent overlay, its consumption can be
easily monitored, and a Journal backup and restore scheduled around a system
refresh.  It is probably even be more reliable to install without an
operating system overlay, and use the volatile one created on each boot from
the read-only filesystem.

Fourth is versatility:

Not having the device's default filesystem format makes the device less
versatile for other applications and systems outside of the Sugar
environment.  One would have a much harder time sharing files with
Windows-based computers, for example.

The greater storage capacity made available with the LiveOS, allowing one to
use more

Re: [SoaS] [SugarClone] -was Re: You scream, I scream, ...

[Frederick Grose]

On Tue, Jul 6, 2010 at 11:44 PM, Frederick Grose fgr...@gmail.com wrote:

 Another small update is available for Sugar Clone, a tool to clone a
 customized Sugar on a Stick installation onto another USB stick.


Re: http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone


Available at:


http://people.sugarlabs.org/fgrose/SugarClone



New:


1. Substituted the underlying modified_livecd-iso-to-disk shell script
   to match the proposed updates to livecd-iso-to-disk for the Fedora
   livecd-tools component.



 2. The above includes the copy-home and copy-overlay options as before,
   but fixes a few logic bugs while warning about the available free
   space for the installation.


3. It also updates the local variable names to match the more general
   scope of the image exchange (for example, $SRC replaces $ISO and
   $TGTDEV replaces $USBDEV).

4. Updated the internal usage help messages.  The option --help displays
   the complete manual.

5. Standardized the Bash conditional expression and list pipeline style
 to the more modern, [[ Expression  Expression ]] format.
 (See http://wiki.bash-hackers.org/syntax/ccmd/conditional_expression.)
 This means that variables within the special double brackets need not
 be quoted, and the old, test-type operators -a, -o should not be used.


6. Standardized the whitespace to make the code much more readable.



Test Usage:


1. Before booting the SoaS device that will be the source of the new

Sugar Clone, copy the SugarClone script to the root, '/', folder at

the base of the filesystem for the device, or, to /mnt/live (from

the perspective of a running LiveOS image).


2. Boot the computer from the USB stick into SoaS, and insert, or have

a second USB device inserted, into the computer.


3. In the Terminal Activity of that running SoaS image, enter the

command,


  /mnt/live/SugarClone


If there is more than one USB/SD storage device available, a menu of
the devices will appear allowing you to select the target device.


The scripts will copy the currently running image to the target device. When
that device is booted, a new, Sugar Learner sign-in will be triggered.  The
previously customized Journal and operating system will be present on the
Sugar Clone.



On a running LiveOS image, the root folder of the USB/SD device is

 available at the /mnt/live mount point.  The SugarClone script can be
obtained (assuming Internet connectivity) as follows:



1. In the Terminal Activity, change the working directory:


   cd /mnt/live


2. wget http://people.sugarlabs.org/fgrose/SugarClone


3. chmod +x SugarClone


at this point, you may simply execute


   SugarClone



See http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone for

 more information.



Notes:


See http://wiki.sugarlabs.org/go/LiveOS_image for more information

 on optimizing file storage for LiveOS images.  Information and

 suggestions there may be particularly relevant for SoaS deployments

 that want to use the stock LiveOS installation with greater capacity

 for Activity storage with a longer lifetime for the write-once,

 ever-diminishing persistent overlay.


See also the http://wiki.sugarlabs.org/go/Activities/Toaster project,

 which aims to make a graphical Sugar Activity for cloning Sugar images.


  --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Upgrading Sticks

[Frederick Grose]

On Tue, Jul 13, 2010 at 1:40 PM, Raffael Reichelt 
raffael.reich...@googlemail.com wrote:

 Sorry if this is a stupid question, but I was wondering if  there is a
 way to update an existing stick, e.g., Strawberry to Mirabelle.

 Regards,
 Raffael


That is a good question!

To preserve your Journal contents, consider this recent message,
http://www.mail-archive.com/de...@lists.laptop.org/msg24150.html.

Also see http://wiki.sugarlabs.org/go/LiveOS_image for some background
information on alternate installation options.  The Live USB Creator methods
do not create a separate Home directory, and so, will more rapidly consume
the persistent storage area on the stick.

If the storage capacity of your stick is large enough (4+ gigabytes), you
may want to consider a non-compressed filesystem install (sometimes called a
full install) without the write-once overlay of the LiveOS that is used
for operating system changes, but you'll have to sort through the various
experiments here,
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation/Variations.

Tell us more about your experiences!  An easier installation and upgrade
path with instructions is surely needed.

--Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Problem with Mirabelle and USB Boot

[Frederick Grose]

On Thu, Jul 1, 2010 at 4:51 PM, Marc Karasek marckara...@gmail.com wrote:

  OK,

 To prevent it name the sticks Fedora prior to putting the image on them.
 (This step should be added to the online instructions.)


Before doing this we need a discussion of why naming the device 'Fedora' is
needed.

The Fedora instructions,
http://fedoraproject.org/wiki/How_to_create_and_use_Live_USB, do not have
this requirement.

 --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Kernel Panic on EXT4 in SoaS when installing GCC

[Frederick Grose]

On Sun, Jun 27, 2010 at 6:54 AM, Peter Lambrechtsen plambrecht...@gmail.com
 wrote:

 I have downloaded the 32Bit version of SoaS running on Fedora 13 and
 installed it into two different VMWare instances (Workstation and ESXi),
 along with Virtual Box and have the same problem.

 It seems that when I try and install GCC using yum within the SoaS image I
 have transferred onto the local disk following these instructions:
 http://wiki.sugarlabs.org/go/VirtualBox/Preparing_a_disk_image

 As soon as it's finished installing the gcc-common update, I get a Kernel
 Panic in EXT4.

 Any ideas as to why the update to gcc causes EXT4 to panic???


This might be of interest:

-- Forwarded message --
From: VirtualBox announcements vbox-annou...@virtualbox.org
Date: 2010/6/25
Subject: [vbox-announce] Announcement: VirtualBox 3.2.6 released
To: vbox-annou...@virtualbox.org


Hi,

today Oracle released VirtualBox 3.2.6, a maintenance release of
VirtualBox 3.2 which improves stability and fixes regressions.

This release introduces a check for the file system where the disk
images are installed and automatically enables the VM host I/O cache
if an ext4 filesystem or an xfs filesystem is detected. The purpose
of this check is to work around a bug in the Linux kernel which can
lead to data corruption under certain circumstances. Only Linux hosts
are affected.

See the Changelog at

 http://www.virtualbox.org/wiki/Changelog

for a complete list of all changes. You can download the binaries
here:

 http://download.virtualbox.org/virtualbox/3.2.6/

Kind regards,

Frank
--
Dr.-Ing. Frank Mehnert

Sitz der Gesellschaft:
Sun Microsystems GmbH, Sonnenallee 1, 85551 Kirchheim-Heimstetten
Amtsgericht München: HRB 161028
Geschäftsführer: Jürgen Kunz

___
vbox-announce mailing list
vbox-annou...@virtualbox.org
http://vbox.innotek.de/mailman/listinfo/vbox-announce
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Kernel Panic on EXT4 in SoaS when installing GCC

[Frederick Grose]

On Sun, Jun 27, 2010 at 6:10 PM, Peter Lambrechtsen plambrecht...@gmail.com
 wrote:

 On Mon, Jun 28, 2010 at 3:16 AM, Peter Robinson pbrobin...@gmail.comwrote:



...

 With the overlay of 200MB, is it better to have more or less space for the
 overlay?

 What would your memory and disk recommendations be for the ideal 32Bit VM.

 And what options should I use with the livecd to disk:


 /livecd-iso-to-disk --overlay-size-mb 200 --home-size-mb 200 --delete-home
 --unencrypted-home /dev/live /dev/sda1

 ??


See  http://wiki.sugarlabs.org/go/LiveOS_image for some information on the
storage options.
Also http://fedoraproject.org/wiki/Livecd-iso-to-disk.pod has more help
information for the script.

With VirtualBox3.2.6 in a Lynx 64-bit host and a Fedora 32-bit guest, I
tested the Fedora-14 soas-i386-20100613.15.iso (no longer available, but
should be similar to the builds at
http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/) using this
installation script,

/LiveOS/livecd-iso-to-disk --overlay-size-mb 1000 --home-size-mb 200
--delete-home --unencrypted-home /dev/live /dev/sda1

The command,

 dmsetup status

 before and after

yum install dkms gcc

yielded these results: 21376/2048000 and 868152/2048000 (512-byte segments)

So it looks like at least 425 MiBytes of overlay is required for that
installation.

then after

./VboxLinuxAdditions-x86.run

dmsetup status showed 928872/204800 or 454 MiBytes of the overlay consumed.

--Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Please consider including the script livecd-iso-to-disk in root of Soas-v4-Mango-lassi

[Frederick Grose]

On Fri, Jun 18, 2010 at 2:58 PM, Peter Robinson pbrobin...@gmail.comwrote:

 On Fri, Jun 18, 2010 at 6:59 PM, Thomas C Gilliard
 satel...@bendbroadband.com wrote:
  Sebastian;
 
  Please consider including the script livecd-iso-to-disk in the root of
  Soas-v4-Mango-lassi


 We do include it already it SoaS-v3, ...


(from http://www.mail-archive.com/soas@lists.sugarlabs.org/msg01256.html):


 On Mon, Apr 26, 2010 at 5:22 PM, Peter Robinson pbrobin...@gmail.comwrote:

  ...
 

 
 
   Please include the script, livecd-iso-to-disk, which is packaged in
   Fedora.
   It has been included in soas-strawberry.iso and
   soas-2-blueberry.iso (in the /LiveOS directory) but has not been in the
   Mirabelle soas-i386-date.iso files so far.
   This will enable on-board replication of SoaS images.
 
  I'll add it to my todo list. I believe its part of the livecd-tools.
 

 Thanks for including this script.

 I just noticed though that it is the only file in the squashed file system
 /LiveOS directory.

 The intention was to have it in the device /LiveOS directory, alongside
 osmin.img and squashfs.img.

 In that location, it is easily accessible from outside the LiveOS image,
 such as through a loop mount,
 and can be used as an installation and replication tool for the image.

 Sorry for not being more clear last time.

 Thank you!   --Fred

 Tom may also be suggesting that having the script in the device's primary
filesystem would be more useful.

   Thanks,   --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Please consider including the script livecd-iso-to-disk in root of Soas-v4-Mango-lassi

[Frederick Grose]

On Fri, Jun 18, 2010 at 4:30 PM, Thomas C Gilliard 
satel...@bendbroadband.com wrote:

 ...



It will work better if script is located in  /  of compressed fs.
 not in /mnt/live/LiveOS


I suggested it would be more useful in the primary device filesystem because
it could be more easily accessed without booting the image, and still be
accessed from the running image as shown below.



 Frederick Grose wrote:

 ...

 I just noticed though that it is the only file in the squashed file system 
 /LiveOS directory.

 The various file systems are easily confused. The SquashFS I refer to just
above is the system that is the active root system for the booted Live USB
image.  So, for example, in the booted SoaS in Terminal:

[r...@localhost ~]# ls -la /LiveOS/
total 32
drwxr-xr-x.  2 root root  4096 May 13 16:01 .
dr-xr-xr-x. 22 root root  4096 Jun 18 21:18 ..
-rwxr-xr-x.  1 root root 23040 May 13 16:01 livecd-iso-to-disk

--Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] [Marketing] Possible style for upstream/downstream diagram

[Frederick Grose]

On Wed, Jun 2, 2010 at 10:03 PM, John Tierney jtis4...@hotmail.com wrote:

   ...

 Possibly a Workflow/Mindmap/Timeline Project Map ...


See  the graphic diagram on
http://wiki.sugarlabs.org/go/Marketing_Team/Project_Visualization (it's a
large file, so viewing the full resolution file to see the details may take
some time.)

It displays the cyclic nature of the collaborative processes.

   --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] [Sugar-devel] SOAS-3: Final Activity List - Attention needed!

[Frederick Grose]

On Mon, Apr 26, 2010 at 5:22 PM, Peter Robinson pbrobin...@gmail.comwrote:

 ...




  Please include the script, livecd-iso-to-disk, which is packaged in
  Fedora.
  It has been included in soas-strawberry.iso and
  soas-2-blueberry.iso (in the /LiveOS directory) but has not been in the
  Mirabelle soas-i386-date.iso files so far.
  This will enable on-board replication of SoaS images.

 I'll add it to my todo list. I believe its part of the livecd-tools.


Thanks for including this script.

I just noticed though that it is the only file in the squashed file system
/LiveOS directory.

The intention was to have it in the device /LiveOS directory, alongside
osmin.img and squashfs.img.

In that location, it is easily accessible from outside the LiveOS image,
such as through a loop mount,
and can be used as an installation and replication tool for the image.

Sorry for not being more clear last time.

Thank you!   --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] [SugarClone] -was Re: You scream, I scream, ...

[Frederick Grose]

A maintenance update is now available at

http://people.sugarlabs.org/fgrose/SugarClone.



New:


1. Records the remix details for the Sugar Clone in the new build file
   that displays in the 'My Settings' 'About my computer'.

   For example,

   Build: Remixed soas-i386-20100501.07.iso in a Sugar Clone prepared
by SoaS-Mirabelle-May on 03 May 2010
  Sugar on a Stick 3 (Mirabelle)
  Fedora release 13 (Goddard)

   Sugar: 0.88.0


2. Bug fixes


   b. Improved support for cloning from one attached device to

   another.



Test Usage:


1. Before booting the SoaS device that will be the source of the new

SugarClone, copy the SugarClone script to the root '/' folder at

the base of the filesystem for the device, or, to /mnt/live (from

  the perspective of a running LiveOS image).


2. Boot the USB stick into SoaS and insert a second USB device into

 the computer running that SoaS image.


3. In the Terminal Activity of that running SoaS image, enter the

command,


  /mnt/live/SugarClone


If there is more than one USB/SD storage device available, a menu of
the devices
will appear to allow you to select the target device.


The scripts will copy the currently running image to the target device. When
that device is booted, a new, Sugar Learner sign-in will be triggered.  The
previously customized Journal and operating system will be present on the
Sugar Clone image.


On a running LiveOS image, the root folder of the USB/SD device is

 available at the /mnt/live mount point.  The SugarClone script

 can be obtained (assuming Internet connectivity) as follows:



1. In the Terminal Activity, change the working directory:


   cd /mnt/live


2. wget http://people.sugarlabs.org/fgrose/SugarClone


3. chmod +x SugarClone


at this point, you may simply execute


   SugarClone



See http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone for

 more information.



Notes:


See http://wiki.sugarlabs.org/go/LiveOS_image for more information
on optimizing file storage on LiveOS images.

  --Fred





___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Live media installers -was: sugar on a stick

[Frederick Grose]

On Mon, Apr 26, 2010 at 12:37 PM, Sascha Silbe 
sascha-ml-ui-sugar-s...@silbe.org wrote:

 On Mon, Apr 26, 2010 at 10:19:17AM -0400, Frederick Grose wrote:

  Please note this recent advisory concerning Unetbootin:

 https://fedoraproject.org/w/index.php?title=How_to_create_and_use_Live_USBdiff=166544oldid=166026


  From that page:

 Unetbootin does not work.
 The Fedora Project has received numerous bug reports relating to using
 Fedora Live USB keys made with
 unetbootin. Please use the official livecd-tools or liveusb-creator
 referenced above to make Fedora Live USB
 keys This warning will be removed when we can confirm these bugs are
 fixed.


 Do you know details, by any chance?
 There are 112 open bugs [1] which doesn't look too good, though several of
 them are of the Please support distro X kind. It's more the amount of
 Undecided bugs that makes it look bad...
 It might nevertheless be better to help fix unetbootin rather than build
 our own tool.


 [1] https://bugs.launchpad.net/unetbootin/+bugs


Paul has updated the advisory,
https://fedoraproject.org/w/index.php?title=How_to_create_and_use_Live_USBdiff=nextoldid=166544,
to,

{{admon/warning | Unetbootin may not work | The Fedora Project has received
 numerous reports relating to using Fedora Live USB keys made with
 unetbootin.  You may want to use the official livecd-tools or
 liveusb-creator referenced above to make Fedora Live USB keys.}}


I have no other information, sorry.--Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] [SugarClone] -was Re: You scream, I scream, ...

[Frederick Grose]

On Sat, Apr 24, 2010 at 8:41 AM, Thomas C Gilliard 
satel...@bendbroadband.com wrote:



...

 QUESTION:
 Do I need the modified_livecd-iso-to-disk script with this new version to
 be on the USB?


No, SugarClone has it bundled in itself, but after running SugarClone, it
will leave a copy of modified_livecd-iso-to-disk in the root
directory of the device (or in /mnt/live of the LiveOS image.)


 ONE PROBLEM on Acer Aspire One:
 Turns out the SD adapter uses the PCIe bus
 and is not recognized by Sugar or your Scripts
 SD only is seen if mounted in a Lexar SD to USB adapter

 Can this be fixed, is it worth it, as SD cannot boot anyway?

 * On a EeePC900 with the same USB and SD the SD is seen and the script(s)
 work.



...


Send me the output of the attached script when run on the computer
with the PCIe bus.

  --Fred


storageDevices
Description: Binary data
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] [SugarClone]

[Frederick Grose]

On Tue, Apr 20, 2010 at 11:10 AM, Thomas C Gilliard 
satel...@bendbroadband.com wrote:

 ...

 I added these files to opened cd on desktop of my Dell 520n desktop by

  drag drop into opened USB

  modified_livecd-iso-to-disk
 newSugarStick
 transferSugarImage
 SugarClone

 Downloaded from http://people.sugarlabs.org/fgrose/
 Properties/permissions changed to allow executing file as program

 Sucessfully made customized copy to second 2 GB Firefly USB by entering

command in booted soas-i386-20100418 USB



 sugar-terminal:

 /mnt/live/SugarClone

 record 66-3 worked in copy also

 these 4 files need to be included in the soas spin...


Only 2 files are needed,
modified_livecd-iso-to-disk
SugarClone

I've removed the others.

Even those will be replaced soon with updates.

Folks should remember that these files are for testing purposes.
Please be advised.
Yesterday, I had to reformat one of my USB drives because it got
corrupted when a loop-mounted filesystem failed to close on
shutdown during testing.

The scripts are not supposed to overwrite device data unless
requested.
   --Fred


 Tom Gilliard
 satellit

___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Weekly status report - Mon 19/04/10

[Frederick Grose]

On Mon, Apr 19, 2010 at 8:53 AM, Peter Robinson pbrobin...@gmail.comwrote:

 Hi All,

 ...



Also please note we are now in count down to release so over the next
 ten days I'll be finalising the set of the Activities to be included
 with the final release.

 Over the coming week I hope to be able to test/verify/resolve the
 following issues I have on my list:
 - Presence service
 - Read crash (If some one can provide an offending document of
 document type that would be helpful).
 - Follow up on the Write issue
 - Fix the lack of plymouth theme on boot.

 Is anyone else aware of any other issues that need to be addressed?


If we are talking about SoaS, I propose that we include the 2 utility
scripts,

  modified_livecd-iso-to-disk
  SugarClone

(http://people.sugarlabs.org/fgrose/)

in the root folder of the image (alongside the directories . .. EFI
isolinux LiveOS ).

They give SoaS the ability to propagate a customized image of itself.

They have received some testing and approval, and I will have
updated versions to finalize soon.

 --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Weekly status report - Mon 19/04/10

[Frederick Grose]

On Mon, Apr 19, 2010 at 10:41 AM, Peter Robinson pbrobin...@gmail.comwrote:

 On Mon, Apr 19, 2010 at 3:38 PM, Frederick Grose fgr...@gmail.com wrote:



...



 
  If we are talking about SoaS, I propose that we include the 2 utility
  scripts,
modified_livecd-iso-to-disk
SugarClone
  (http://people.sugarlabs.org/fgrose/)
  in the root folder of the image (alongside the directories . .. EFI
  isolinux LiveOS ).
  They give SoaS the ability to propagate a customized image of itself.
  They have received some testing and approval, and I will have
  updated versions to finalize soon.

 Are they packaged in Fedora?


Not yet. Assistance is needed.

I've submitted some patches to update Fedora's livecd-iso-to-disk,
https://bugzilla.redhat.com/show_bug.cgi?id=448030,
https://bugzilla.redhat.com/show_bug.cgi?id=582051, but
those won't be complete and reviewed in time.  So I propose in the
interim, that only SoaS include the newer versions of the scripts.

SugarClone is SoaS specific at this time.

See http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone for more
information.

 --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] [SugarClone] -was Re: You scream, I scream, ...

[Frederick Grose]

On Thu, Apr 15, 2010 at 7:18 PM, Thomas C Gilliard 
satel...@bendbroadband.com wrote:

 ...
 dragged scripts into USB opened on PC


I think you mean booted here instead of opened, if you booted the USB
device.
(Opening would refer to a file or file system, such as reading a file or
directory
from a mounted device such as the USB on /media/FEDORA.)


  http://people.sugarlabs.org/fgrose/
  modified_livecd-iso-to-disk
  SugarClone

 Transcript of Duplication to 2nd 2GB SD follows:

 [r...@localhost live]# /mnt/live/SugarClone
 cloneArgs:
 liveArgs: --noverify --copy-overlay --delete-home --copy-home
 This Live USB/SD device was detected.

One USB/SD storage device was detected:

   usb..USB2.0..CardReader SD0../dev/sdd../media/FEDORA..FEDORA..2-GB
 EXIT

   That's where we'll load the SugarClone.
   /dev/sdd

 mv: failed to preserve ownership for `/mnt/live/owner.key': Operation not
 permitted
 mv: failed to preserve ownership for `/mnt/live/owner.key.pub': Operation
 not permitted


I believe that this is an indication that the key files are being tampered
with by a user
other than the owner.  The files are moved anyway.


  Updating boot config file
 --noverify --copy-overlay --delete-home --copy-home
 Copying live image to USB stick
 Copied overlay.
 Updating boot config file
 Installing boot loader
 USB stick set up as live image!
 Success! Your Sugar image is ready.

 [r...@localhost live]#

 Worked Fine!

 Name on boot is changed to
  Welcome to soas-i386-20100414.22 in a SugarClone prepa, (rest is off
 screen)


Open 'My Settings', 'About my computer' to see the full build information.


  requested name and color
 then went to sugar desktop with Analyze application I installed from ASLO
 via browse on previous USB.
 and journal all contents.

 Tom Gilliard
 satellit


Thanks for testing!  --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] [SugarClone] -was Re: You scream, I scream, ...

[Frederick Grose]

On Thu, Apr 15, 2010 at 11:40 PM, Thomas C Gilliard 
satel...@bendbroadband.com wrote:

 mv: failed to preserve ownership for `/mnt/live/owner.key':

  Operation not permitted

  mv: failed to preserve ownership for `/mnt/live/owner.key.pub':

  Operation not permitted



 I believe that this is an indication that the key files are being

 tampered with by a user other than the owner. The files are moved

 anyway.



I thought it was because I did not specify the option to keep user id


SugarClone (through modified_livecd-iso-to-disk) copies everything in the
persistent overlay and /home folder, it it exists.  This would include the
private owner.key file if it weren't moved to outside of the LiveOS folder
before the modified_livecd-iso-to-disk script is called.

The key files are restored to their regular location before the
SugarClone script exits.

If the --keepuser option is requested, the key files will not be moved
before copying, and the SugarClone will be owned by the source image's
owner.  This would be used when the owner wanted a backup or archive of
their image.

  --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] You scream, I scream, we all scream for Mirabelle ice cream in a SugarClone

[Frederick Grose]

On Tue, Apr 13, 2010 at 2:31 PM, Frederick Grose fgr...@gmail.com wrote:

 On Tue, Apr 13, 2010 at 1:13 PM, Thomas C Gilliard 
 satel...@bendbroadband.com wrote:

 ...


  1-)
 command: /mnt/live/SugarClone

 It found my 4GB SD  in drive /dev/sdd1
 from the booted USB /dev/sdc1
  worked and found cardreader SD as only device
 but had error message about permissions for ssd files (2)
 It went on to do successful install to SD.


 More testing with SD devices is needed.


I've uploaded a new version of SugarClone for testing the detection and
selection
of SD (MMC) devices.  The menu of available devices shows the following
information:

n.  bus..vendor..model..device..mount..label..size-GB

For example,

1.  usb..SanDisk..Cruzer../dev/sdb../media/SANDISK..16-GB
2.  mmc../dev/mmcblk0../media/SD_CARD..SD_CARD..8-GB

when read on my XO-1.
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] [SugarClone] -was Re: You scream, I scream, ...

[Frederick Grose]

On Wed, Apr 14, 2010 at 3:38 PM, Thomas C Gilliard 
satel...@bendbroadband.com wrote:

  Tested with these results:
 ( booted soas ...405 USB with new SugarClone and
 modified_livecd-iso-to-disk scripts in /mnt/live/ )

 root terminal:
 /mnt/live/SugarClone

 I get :

  One USB/SD storage device was detected
  usb..USB2.0..cardreader SD)../dev/sdd../media/Fedora.. 2-GB EXIT

  That is where we'll load the SugarClone
  /dev/sdd

  [r...@localhost live]#

 No further action occurs..?


Sorry... Forgot to remove a debugging 'exit' command.  There's a new
version at http://people.sugarlabs.org/fgrose/SugarClone that should run.

Your SD card reader may be connected on the computer's usb bus, so the
SD card line may be prefixed with 'usb' instead of the 'mmc' bus that the
XO-1 uses.

If you have a second device connected, the menu will pause for your
selection of a device.  That may help you examine what it finds.

 --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] [SugarClone] -was Re: You scream, I scream, ...

[Frederick Grose]

On Wed, Apr 14, 2010 at 4:15 PM, Thomas C Gilliard 
satel...@bendbroadband.com wrote:

  still not working





 No further action occurs..?

 Sorry again...  This time I taste tested.

http://people.sugarlabs.org/fgrose/SugarClone has the new script.

   --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] You scream, I scream, we all scream for Mirabelle ice cream in a SugarClone

[Frederick Grose]

Was: Duplicating SoaS with customization.

New work:

1. Reduced the 3 earlier scripts to 2 that provide a means to
   duplicate a running SoaS image together with its customizations in
   a persistent overlay or home folder.

   modified_livecd-iso-to-disk
   SugarClone

   These are available at http://people.sugarlabs.org/fgrose/.

2. Automated detection of attached USB storage devices and provide a
   selection menu if there are more than one.

3. Maintained a simple command line for the default case:

  /mnt/live/SugarClone

   (even as the default liveuser account).

4. Provided input auditing for advanced uses.

5. Embedded a much more complete usage document available as an option:

  /mnt/live/SugarClone --help

6. Tested and updated more code paths.

7. Adopted satellit's suggestion to update the boot menu Welcome title.
   And updated the 'About my Computer' Build information so this is
   available at run time.


Test Usage:

1. Before booting the SoaS device that will be the source of the new
   SugarClone, copy the script files above to the root '/' folder at
   the base of the filesystem (not the /root folder).
2. Boot the USB stick into SoaS and insert a second USB device into the
   computer running that SoaS image.
3. In the Terminal Activity of that running SoaS image, enter the command,

  /mnt/live/SugarClone

The scripts will copy the currently running image to the second device.
When the second device is booted, a new Sugar Learner sign in will be
triggered, and the customized Journal and operating system will be present.

Step 1 above, from the perspective of the learner inside a currently
running SoaS image, would be different:  The root folder of the USB
device would be reached through the /mnt/live mount point.  The scripts
could be obtained (assuming Internet connectivity) as follows:

1. In the Terminal Activity, change the working directory:

   cd /mnt/live

2. wget http://people.sugarlabs.org/fgrose/modified_livecd-iso-to-disk

   wget http://people.sugarlabs.org/fgrose/SugarClone

3. chmod +x modified_livecd-iso-to-disk

   chmod +x SugarClone


Possible Use Case:

1. A teacher wants to prepare a SoaS image with a custom set of installed
   Activity bundles or a Journal of Activity instances for an upcoming
   class term.
2. The teacher modifies their current working image by adding or deleting
   Activity bundles from their Home view and adding or removing Journal
   entries with specific content, even saving distributable ebooks, or
   bookmarks in Browse instances that are named for specific sets of local
   web destinations (a class portal perhaps for deployments lacking
   Internet connectivity).
3. The teacher scrubs out any personal passwords or other history that
   should not be shared in the new copies.
4. Following customization, a fresh or recycled USB stick that is inserted
   into the computer running the customized SoaS image can become the
   SugarClone.

Step 5 assumes that Usage step 1 has been performed either directly or by
the SoaS packagers.

These scripts have been tested with SoaS-Mirabelle (available at
http://alt.pub/alt/nightly-composes/soas/http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/)
but should work with other versions of SoaS.

The current version of the scripts have the /bin/bash shell specified
without the -x (xtrace) option.  Set this option, #!/bin/bash -x in the
first line of the script to aid testing.  When set, they will show a lot
of output on the screen as they run.

The scripts are copied to the new SugarClone devices prepared with these
scripts so that they can easily propagate themselves.  This also applies to
all new SoaS installations that are prepared with these scripts (using
--image source options).


Needed:

1. More review and testing.
2. Submission of the modified_livecd-iso-to-disk script upstream.
3. Modifications for Intel Macintosh computers.
4. A way to automatically identify extra partitions on devices with more
   than one available partition.
5. A way to automatically identify live media images on secondary devices
   and partitions that could be used as sources for a SugarClone.
6. Bundling of the scripts for convenience until they are included in
   SoaS.
7. A Sugar Activity that calls the scripts.

These all should help us better prepare a SoaS customization kit.

--Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] You scream, I scream, we all scream for Mirabelle ice cream in a SugarClone

[Frederick Grose]

On Tue, Apr 13, 2010 at 1:13 PM, Thomas C Gilliard 
satel...@bendbroadband.com wrote:

 ...



* installed SugarClone via wget to /mnt/live/
 (still using already installed 3 files from previous DL)


The older modified_livecd-iso-to-disk was used.


  1-)
 command: /mnt/live/SugarClone

 It found my 4GB SD  in drive /dev/sdd1
 from the booted USB /dev/sdc1
  worked and found cardreader SD as only device
 but had error message about permissions for ssd files (2)
 It went on to do successful install to SD.


More testing with SD devices is needed.

 ...



3-) used resulting USB to write to new SD it could not find /dev/sdd1
 looked for /dev/sde1

 4-) did wget of modified_livecd-iso-to-disk (new version)
 used new 2GB SD formatted fat16 boot flag
 error: /dev/sde1 /media/target.x
 mount: you must specify the file system type..
 exit clean
 ..
 exit 1

 questions:
 Are there a new and old version of the modified_livecd-iso-to-disk  script?


Yes, changes were made to the usage() function (option --help) and other
error or help messages.  Also fixed some bugs with the --skipcopy option.


  what is happening here?


Just guessing that mounting is easier when the volume is registered in the
file system table in /etc/fstab (http://en.wikipedia.org/wiki/Fstab), and
that may have differed.

From the SugarClone file,

OPTIONS

--image source   (default: /dev/live)
The running live image device , another partition
holding a live image, or the path to an .iso file bearing a live
image.

(This allows one to specify another device partition recognized by the
computer, such
as, /dev/sdc1 or /dev/sd(x)n , as the source for the SugarClone.  One may
also specify
an .iso image file of a LiveOS distribution, such as
/path/to/soas-i386-20100408.01.iso
that one may have on their system or attached drive.  The parameter is use
on line
755 of SugarClone (at the very end of the file when
modified_livecd-iso-to-disk is called).

--builder name
The name of the builder of the customized SugarClone. Default:
someone

--mntpnt wdir   (default: /mnt/live)
The filesystem directory mount point for the source holding the
build
scripts, SugarClone and modified_livecd-iso-to-disk.

(This is an interim and limited method to specify a path to files on the
source or other
device.  This is mainly for testing, unless a good use case arises.)

--help
Displays usage information and exits.

The target device is selected by SugarClone from the list of USB storage
devices it
finds by querying the hardware abstraction layer of the computer using
'hal-find-by-capability' and 'hal-get-property'.  The selected device is
saved in the variable, TARGETDEV.

 ${TARGETDEV}1 is used as a parameter at the end on line 755, as well as on
lines
680, 682, where SugarClone copies itself to the new device filesystem for
future use.

Hope that helps,  --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

[SoaS] Duplicating SoaS with customization -was: Call for Testing: Duplicating SoaS via CMD

[Frederick Grose]

As requested in http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/TODO,
https://bugzilla.redhat.com/show_bug.cgi?id=448030, and
http://bugs.sugarlabs.org/ticket/74, the following 3 scripts provide a
testable
means to duplicate a running SoaS image that may have been customized
(in its persistent overlay or home folder):

modified_livecd-iso-to-disk
transferSugarImage
newSugarStick

These are available at http://people.sugarlabs.org/fgrose/.

Test Usage:

1. Copy the script files above to the root '/' folder at the base of the
   filesystem on a SoaS USB stick known to run Sugar.
2. Boot the USB stick into SoaS and insert a second USB device into the
   computer running that SoaS image.
3. In the Terminal Activity of that running SoaS image, enter the command,

  /mnt/live/newSugarStick

  (At this point in development, the transferSugarImage script assumes
that
   the second device is mounted and recognized as /dev/sdc1.  You may
   confirm this by executing the command,
  mount
   and checking for the lines that return your second device's name and
   device partition, such as /dev/sdc1.)

The scripts will copy the currently running image to the second device. When
the second device is booted, a new Sugar Learner sign in will be triggered,
but
the customized Journal and operating system will be present.


Possible Use Case:

1. A teacher wants to prepare a SoaS image with a custom set of installed
   Activity bundles or a Journal of Activity instances for an upcoming class
   term.
2. The teacher modifies their current working image by adding or deleting
   Activity bundles from their Home view and adding or removing Journal
   entries with specific content, even saving bookmarks in Browse instances
   that are named for specific sets of web destinations.
3. The teacher scrubs out any personal passwords or other history that
should
   not be shared in the new copies.
4. Following customization, a fresh or recycled USB stick is inserted into
the
   computer running the customized SoaS image.
5. The Sugar Terminal Activity is opened and this command is entered:

   /mnt/live/newSugarStick

Step 5 assumes that Usage step 1 has been performed either directly or by
the SoaS packagers.

Presently, the transferSugarImage script is hard-coded to run the
modified_livecd-iso-to-disk installation script with these options:

   --noverify  To avoid the need for verification software--a running
image
   is its own form of verification.
   --copy-overlay  This duplicates the customizations on the source image
   operating system, including those in the home folder if
   there was no separate, persistent home.
   --delete-home   This is required to confirm deletion of a persistent home
   folder, if it exists on the target device.
   --copy-home This duplicates the customizations on the source image
   home folder, if it exists.

The modified_livecd-iso-to-disk script has a new option, --help, which
displays
its usage instructions.

These scripts have been tested with SoaS-Mirabelle (available at
http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/).

The scripts have have the /bin/bash shell specified with the -x (xtrace)
option set
to aid in testing.  That means they will show a lot of output on the screen
as they
run.

The scripts are copied to new SoaS devices prepared with these scripts so
that they can propagate themselves.

Needed:

1. Review and testing.
3. Submission of modified_livecd-iso-to-disk upstream
2. A way to determine the name of the secondary USB device partition
automatically
   in the transferSugarImage script.
3. A Sugar Activity that calls the scripts.

These steps should help us prepare a SoaS customization kit.

--Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] [SoaS via CMD] Duplicating SoaS with customization -was: Call for Testing: Duplicating SoaS via CMD (Testing Need Help on commands)

[Frederick Grose]

On Tue, Apr 6, 2010 at 6:41 PM, Thomas C Gilliard 
satel...@bendbroadband.com wrote:

 ...

 Test Usage:

 1. Copy the script files above to the root '/' folder at the base of the
filesystem on a SoaS USB stick known to run Sugar.

 I tried this:

 ...

 copied 3 scripts to /root of running 405 USB
 in root terminal:


Sorry for the confusion, the base of the file system is sometimes called
the root denoted by '/'.  I didn't mean the /root folder, which is the
home folder for the root user. From within the running SoaS image, it is
mounted on the /mnt/live/ folder.  For example, this command,

   ls -la /mnt/live/

will display the contents of the root directory of the USB device
partition, while

   ls -la /

will display the contents of the root of the live image filesystem
(in the squashfs.img file that was loaded on installation of the live
image).

That would explain the missing file message.

 /mnt/live/newSugarStick

 I tried this and get
 No such file or directory

Thanks for testing!

 --Fred
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Call for Testing: Duplicating SoaS via CMD (Please Help with modified_livecd-iso-to-disk script)

[Frederick Grose]

On Tue, Mar 30, 2010 at 8:27 AM, Thomas C Gilliard 
satel...@bendbroadband.com wrote:
 Frederick:

 I have been trying to make this work...
 I created with liveusb-creator a 4GB USB with persistence 2400 of iso
 soas328; using a usb 500GB HD install of f13 Beta1 Gnome + sugar
 rebooted with the new USB
 in sugar terminal:
 su -
 yum install wget gedit
 wget http://(path to soas nightly composes/soas/..328
 (loaded in /home/liveuser/)
 opened with gedit soas@lists.sugarlabs.org from a 2nd USB in sugar frame
 saved it in /home/liveuser/
 chmod 077 modified_livecd-iso-to-disk script
 If I do a ls I see both in /home/liveuser
 then I get lost on how to use your script

 I tried in root:
 /home/liveuser/modified_livecd-iso-to-disk --noverify --delete-home
 --extra-kernel-args selinux=0 --copy-overlay /dev/live /dev/sde1

 new target usb is /dev/sde1 formatted ext3 with boot flag
  I got this error msg

 mount:
 wrong fs type, bad option, bad superblock on /dev/loo5,
 missing codepage, or helper program, or other error

 Cleaning up to exit...

I don't know about that error. To avoid some filesystem-media-related
problems, I have kept the factory formatting on my USB devices as
recommended here,
http://wiki.laptop.org/go/How_to_Damage_a_FLASH_Storage_Device.

I have a 16-GB SanDisk Cruzer and 16-GB Toshiba USB drives. I once manually
reformatted the SanDisk to remove the U3 partition, but after reading the
article, I got the SanDisk utility (
http://kb.sandisk.com/app/answers/detail/a_id/240/kw/usb%20flash%20drive%20u3/r_id/101834)
to
restore the factory format. For the record, the SanDisk device is formatted
as W95 FAT32 (0x0b), and the Toshiba - W95 FAT32 (LBA) (0x0c) according to
my disc utility.


 Do I have to use your script to create the USB? vs using graphical
 liveusb-creator to make this work?

No, the script works from either installation method. I sometimes test with
the Windows Live USB Creator.

New work:

I've added some user input checking and played with the
/home/liveuser/.sugar/default/owner.key and .key.pub files (which don't seem
to be installed by the Windows Live USB Creator).

These new lines before and after the copy of the overlay file,
+  chown root:root /home/liveuser/.sugar/default/owner.key
/home/liveuser/.sugar/default/owner.key.pub
+  mv /home/liveuser/.sugar/default/owner.key $USBMNT/$LIVEOS/owner.key
+  mv /home/liveuser/.sugar/default/owner.key.pub
$USBMNT/$LIVEOS/owner.key.pub
+  cp $CDMNT/LiveOS/$OVERLAYFILE $USBMNT/$LIVEOS/$OVERLAYFILE ||
exitclean
+  mv $USBMNT/$LIVEOS/owner.key /home/liveuser/.sugar/default/owner.key
+  mv $USBMNT/$LIVEOS/owner.key.pub
/home/liveuser/.sugar/default/owner.key.pub
+  chown liveuser:liveuser /home/liveuser/.sugar/default/owner.key
/home/liveuser/.sugar/default/owner.key.pub
+  chmod 600 /home/liveuser/.sugar/default/owner.key
+  chmod 644 /home/liveuser/.sugar/default/owner.key.pub

had the result that the newly booted cloned image presented with a new Sugar
user screen.  Once the Home view appeared, the old Activity icon colors and
Journal were present.  Be careful though, because a saved password cookie in
Browse for my Gmail was transferred to the new image.

The new, Sugar-specific script and diff are attached.

Thanks for testing!

 --Fred


diff
Description: Binary data


modified_livecd-iso-to-disk
Description: Binary data
___
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

Re: [SoaS] Call for Testing: Duplicating SoaS via CMD

[Frederick Grose]

On Sun, Mar 28, 2010 at 12:55 PM, Sebastian Dziallas sebast...@when.com wrote:

 Hi all,

 it would be great if somebody could give this standard procedure a try
 and confirm whether it works or not, so that we can react appropriately
 upon a ticket. You'll need two USB keys for this.

 (1) use Fedora's LiveUSB Creator to prepare the first key with SoaS

 (2) boot the first key and apply some changes as in:

        (a) change the language
        (b) download a number of activities

 (3) plug in the second USB key and determine its mount point

 (4) run as root on the first key: yum install livecd-tools (might or
 might not be already present, depending on which SoaS version you use)

 (5) execute the following command from the terminal on the first key:

        livecd-iso-to-disk --overlay-size-mb 300 /dev/sr0 /dev/sdc1

 (in which case /dev/sdc1 would be the mount point of the second key)

 Does this [ ] WORK or [ ] FAIL? Please let us know!

 Thanks,
 --Sebastian
 ___
 SoaS mailing list
 SoaS@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/soas

I've tested a different approach with some success for customizing and
replicating a LiveUSB image:

1. Downloaded 
http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/soas-i386-20100327.19.iso

2. In Fedora13 (32-bit), ran this script:
    modified_livecd-iso-to-disk --overlay-size-mb 400 --delete-home
--extra-kernel-args selinux=0 /path_to_soas-i386-20100327.19.iso
/dev/sdb1

3. Booted the LiveUSB device1 and made a few changes.

4. Mounted a second USB device2 on an extended USB port on my monitor,
confirmed its partition name as /dev/sdc1, then unmounted it.

5. Mounted my Fedora13 partition (/dev/sda1) onto the device1 LiveUSB
image, and ran this script in the Sugar Terminal:
   /mnt/F13/home/account/.../ modified_livecd-iso-to-disk --noverify
--delete-home --extra-kernel-args selinux=0 --copy-overlay /dev/live
/dev/sdc1

6. Shutdown and swapped USB devices in order to boot device2 from the
motherboard USB port.

7. Confirmed that I had a replicated image with the copied overlay file.

8. More testing needed.

The modified script is attached.

Here is the diff from the current tools_livecd-iso-to-disk:

--- tools_livecd-iso-to-disk.sh
+++ modified_livecd-iso-to-disk
@@ -308,6 +308,9 @@
   overlaysizemb=$2
   shift
   ;;
+ --copy-overlay)
+    copyoverlay=1
+    ;;
--home-size-mb)
   checkint $2
            homesizemb=$2
@@ -481,6 +484,13 @@
  tbd=0
fi
livesize=$(du -s -B 1M $check | awk {'print $1;'})
+if [ ! -n $copyoverlay ]; then
+  OVERLAYFILE=overlay-$( /sbin/blkid -s LABEL -o value $ISO )-$(
/sbin/blkid -s UUID -o value $ISO )
+  if [ -f $check/$OVERLAYFILE ]; then
+     copyoverlaysize=$(du -s -B 1M $check/$OVERLAYFILE | awk {'print $1;'})
+     livesize=$(($livesize - $copyoverlaysize))
+  fi
+fi
if [ -n $skipcompress ]; then
    if [ -e $CDMNT/LiveOS/squashfs.img ]; then
if mount -o loop $CDMNT/LiveOS/squashfs.img $CDMNT; then
@@ -572,8 +582,16 @@
  if [ -f $CDMNT/LiveOS/osmin.img ]; then
      cp $CDMNT/LiveOS/osmin.img $USBMNT/$LIVEOS/osmin.img || exitclean
  fi
+  if [ -n $copyoverlay ]; then
+      OVERLAYFILE=overlay-$( /sbin/blkid -s LABEL -o value $ISO )-$(
/sbin/blkid -s UUID -o value $ISO )
+      cp $CDMNT/LiveOS/$OVERLAYFILE $USBMNT/$LIVEOS/$OVERLAYFILE || exitclean
+  fi
fi

+# copy this installer script to enable the new installation to
replicate the image
+SCRIPT=$(readlink -f $0)
+cp -f $SCRIPT $USBMNT/$LIVEOS/livecd-iso-to-disk
+
# DVD installer copy
if [ $isotype = installer ]  [ -z $skipcopy ]; then
      echo Copying DVD image to USB stick
@@ -582,7 +600,18 @@
      cp $ISO $USBMNT/
fi

-cp $CDMNT/isolinux/* $USBMNT/$SYSLINUXPATH
+# adjust syslinux sources for replication of installed images between
filesystem types
+if [ -d $CDMNT/isolinux/ ]; then
+    cp $CDMNT/isolinux/* $USBMNT/$SYSLINUXPATH
+elif [ -d $CDMNT/syslinux/ ]; then
+    cp $CDMNT/syslinux/* $USBMNT/$SYSLINUXPATH
+    if [ -f $CDMNT/syslinux/extlinux.conf ]; then
+        mv $USBMNT/$SYSLINUXPATH/extlinux.conf
$USBMNT/$SYSLINUXPATH/isolinux.cfg
+    elif [ -f $CDMNT/syslinux/syslinux.cfg ]; then
+        mv $USBMNT/$SYSLINUXPATH/syslinux.cfg
$USBMNT/$SYSLINUXPATH/isolinux.cfg
+    fi
+fi
+
BOOTCONFIG=$USBMNT/$SYSLINUXPATH/isolinux.cfg
# Set this to nothing so sed doesn't care
BOOTCONFIG_EFI=
@@ -594,6 +623,9 @@
  rm -f $USBMNT/EFI/boot/grub.conf
fi

+# restore boot config file to base state before updating
+sed -i -e s/root=[^ ]*/root=CDLABEL=name/ -e s/liveimg .*
quiet/liveimg quiet/ $BOOTCONFIG $BOOTCONFIG_EFI
+
echo Updating boot config file
# adjust label and fstype
sed -i -e s/CDLABEL=[^ ]*/$USBLABEL/ -e s/rootfstype=[^
]*/rootfstype=$USBFS/ -e s/LABEL=[^ ]*/$USBLABEL/ $BOOTCONFIG
$BOOTCONFIG_EFI
@@ -617,6 +649,11 @@
    fi
    sed -i -e s/liveimg/liveimg overlay=${USBLABEL}/ $BOOTCONFIG
$BOOTCONFIG_EFI
    sed -i -e s/\ ro\ /\ rw\ / $BOOTCONFIG  $BOOTCONFIG_EFI
+elif [ -n $copyoverlay ]; then
+