Frederick Grose wrote:
On Mon, Apr 19, 2010 at 8:53 AM, Peter Robinson <[email protected]>wrote:

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.
This works great on acer aspire one.

I have used master Soas 421 USB to make clone. And then used the clone to make a third USB. All work well..

added by drag drop on PC desktop to opened Soas 421 USB
(same as installing to /mnt/live directory of Booted USB):
http://people.sugarlabs.org/fgrose/
  modified_livecd-iso-to-disk
  SugarClone

Tom Gilliard
satellit
....................................................................
Also:
Nightly Composes Soas 421 is almost unchanged from previous Soas 418:

Presence service is non-functional
write writes to header
loaded record-67.xo from ASLO with browse. Works fine except no audible audio.


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

     --Fred

------------------------------------------------------------------------

_______________________________________________
SoaS mailing list
[email protected]
http://lists.sugarlabs.org/listinfo/soas
_______________________________________________
SoaS mailing list
[email protected]
http://lists.sugarlabs.org/listinfo/soas

Reply via email to