[SoaS] [SugarClone] -was Re: You scream, I scream, ...
Thomas C Gilliard
satellit at bendbroadband.com
Sat Apr 24 08:41:42 EDT 2010
Tested Your new SugarClone script.
It works fine.
* Used on 4GB USB Firefly*:
./livecd-iso-to-disk --format --reset-mbr --overlay-size-mb 2000
* Removed and then reinserted USB in Ubuntu 9.04
* Copy/Paste 2 scripts to opened USB on Desktop:
*Inserted and booted USB on Acer Aspire One
found Target USB and made clone sucessfully.
Boot Screen no longer appears (Plymouth?)
(I just get horizontal bars >f13)
I am not sure that this is an improvement....(I liked the Boot Screen)
Do I need the modified_livecd-iso-to-disk script with this new version
to be on the USB?
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
They are a GREAT improvement!
> One problem with acer aspire one:
> It will not boot from an SD slot (see notes below), but works well
> with a USB.
> My lexar SD to USB adapter lets an SD boot but then it sticks out the
> side. : /
> This works on the EeePc900 as SD is on the USB bus...
> Tom Gilliard
> Can the Acer one boot from the SD storage slot?
> I see no evidence with european or north american models of the
> ability to boot from SD readers. There is no mention of this feature
> in any BIOS
> release notes. I am running the latest BIOS available to canadian
> modles v3009. v3114 is the latest for european. Neither mention SD
> boot in release notes nor does my v3009 give any SD boot options of
> any kind with cards in either slot. Nor is the GRUB bootloader able to
> access SD cards (afaik) =D
> Turns out the SD adapter uses the PCIe bus and the BIOS only supports
> booting directly from USB devices
Frederick Grose wrote:
> Not yet final, but ready for more testing is a new version of SugarClone,
> 1. Reduced the previous 2 scripts to 1 bundle for more convenient,
> single-file distribution. (It expands on execution to run the device
> selection script and then, the modified_livecd-iso-to-disk
> installation script.)
> 2. Updates the boot screen title and 'About my Computer' build
> information with SugarClone build information from the source image
> and the Sugar Learner account name. (Leaves the source files
> 3. Provides more auditing of inputs (more code paths tested).
> 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 (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
> If there is more than one USB/SD storage device available, a menu of the
> devices will appear for selection of 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 SugarClone 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
> 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/SugarClone
> 3. chmod +x SugarClone
> See http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone for more
> The SugarClone bundle was prepared with the bundle script
> (at .../fgrose/bundle).
> The older scripts are renamed with a date suffix.
> Embedded help, which describes the script and its usage in more detail,
> is available (just after the stock header) in the script file.
> SoaS mailing list
> SoaS at lists.sugarlabs.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SoaS