Re: [SoaS] [SugarClone] -was Re: You scream, I scream, ...
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] [SugarClone] -was Re: You scream, I scream, ...
Fred: I just tested new script: Several possible problems with error handling with the new script: 1-) live USB was 4GB tried to write to 2GB USB error : too small to write, shutdown Inserted new 4GB fat 32 with no boot flag cd /mnt/live/SugarClone No such file or directory Reboot USB and Directory is there. 2-) live USB was 4GB tried to write to fat 32 4 GB USB (no boot flag) error: no boot flag* cd /mnt/live No such file or directory Reboot USB and Directory is there. 3-) live USB was 4GB write to fat 32 4 GB USB with boot flag set* SugarClone works fine It looks like your error shutdown of script leaves the /mnt/live directory in a changed state Cleaning up to exit not totally working * your script error instructions for setting boot flag with parted: '.. # /sbin/parted /dev/sdc (parted) toggle N boot (error: expects partition number)? ... I used Gparted on USB externally then retried it and it worked fine. Note: script fails to make bootable USB if it is a SanDisk Cruzer 4GB that has a hidden U3 partition. (only removable in windows if done prior to using it in linux) (I guess it writes grub to wrong place) Gparted does not see this partition at all *These are in Cheap multi-packs at Cosco and may not even be marked that they contain the U3 partition. Script worked great on a normal USB SugarClone is a great Idea! Tom Gilliard satellit Frederick Grose wrote: 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 ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] [SugarClone] -was Re: You scream, I scream, ...
I would recommend using Blueberry at this time. http://wiki.sugarlabs.org/go/Sugar_on_a_Stick This e-mail was reporting on a new script to use with a beta of the next version of Soas v3-Mirabelle. which is slated to be released in several weeks. This script allows customization of a live USB stick of Sugar and then duplication to multiple copies with the changes a teacher has made to it. Each clone will ask for a new name and identification color for the student's Avitar. It can be used now on Blueberry-v2-Soas look at http://wiki.sugarlabs.org/go/Category:Live_USB#Duplicating_SoaS_with_customization for more information. Cordially; Tom Gilliard satellit on IRC freenode #sugar Bend Oregon george pope wrote: I'm here oin Ghana and though neither a Sugar expert nor teacher I'm trying to reccomend SOAS to school friends in Accra. Is this premature? george pope kokrobite ghana On Tue, May 4, 2010 at 12:48 PM, Thomas C Gilliard satel...@bendbroadband.com wrote: Fred: I just tested new script: Several possible problems with error handling with the new script: 1-) live USB was 4GB tried to write to 2GB USB error : too small to write, shutdown Inserted new 4GB fat 32 with no boot flag cd /mnt/live/SugarClone No such file or directory Reboot USB and Directory is there. 2-) live USB was 4GB tried to write to fat 32 4 GB USB (no boot flag) error: no boot flag* cd /mnt/live No such file or directory Reboot USB and Directory is there. 3-) live USB was 4GB write to fat 32 4 GB USB with boot flag set* SugarClone works fine It looks like your error shutdown of script leaves the /mnt/live directory in a changed state Cleaning up to exit not totally working * your script error instructions for setting boot flag with parted: '.. # /sbin/parted /dev/sdc (parted) toggle N boot (error: expects partition number)? ... I used Gparted on USB externally then retried it and it worked fine. Note: script fails to make bootable USB if it is a SanDisk Cruzer 4GB that has a hidden U3 partition. (only removable in windows if done prior to using it in linux) (I guess it writes grub to wrong place) Gparted does not see this partition at all *These are in Cheap multi-packs at Cosco and may not even be marked that they contain the U3 partition. Script worked great on a normal USB SugarClone is a great Idea! Tom Gilliard satellit Frederick Grose wrote: 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 ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas ___
Re: [SoaS] [SugarClone] -was Re: You scream, I scream, ...
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] [SugarClone] -was Re: You scream, I scream, ...
Fred; Used new SugarClone loaded by itself into USB: (Drag drop into opened USB on Ubuntu 9.04 desktop) Then Booted Acer Aspire One with it.) sugar-terminal: -- [liveu...@localhost ~]$ /mnt/live/SugarClone clone options: installer options: This Live USB/SD device was detected: usb..Lexar..JD FireFly../dev/sdb../mnt/live..LIVE..1.9-GiB One USB/SD storage device is available: usb..Lexar..JDFireFly../dev/sdc../media/LIVE..LIVE..1.9-GiB That's where we'll load the SugarClone. /dev/sdc1 Source is on a vfat partition. Builder: soas-426 Updating boot config file. There is 89.7 % of the 1200 MiBytes in LiveOS persistent storage that is free on both the Source Target devices. Calling: /tmp/modified_livecd-iso-to-disk --noverify --copy-overlay --delete-home --copy-home /dev/live /dev/sdc1 Already set up as live image. Deleting old OS in fifteen seconds... Copying live image to USB stick Copied overlay. Updating boot config file Installing boot loader USB stick set up as live image! Cleaning up to exit... Waiting for devices to settle... Done... You may use your Sugar Clone now! [liveu...@localhost ~]$ -- Cloned Custom USB works fine. Opens up with Sugar Name screen Remembers wireless login Has contents of journal from master USB (the modified script is added to /mnt/live after running SugarClone script.) Tom Gilliard satellit Frederick Grose wrote: On Fri, Apr 23, 2010 at 1:48 AM, Frederick Grose fgr...@gmail.com wrote: Not yet final, but ready for more testing is a new version of SugarClone, http://people.sugarlabs.org/fgrose/SugarClone. New: 1. Reports the portion of persistent overlay or home folder storage that remains on the file systems. This will help Learners manage their storage resources and learn ways to economize limited resources. (See notes below.) 2. Uses the /tmp/ directory, which is on a RAM file system in LiveOS images, to run the installation scripts and save temporary mount points and files. This conserves the write-once persistent over- lay 2. Bug fixes a. Allows multiple options to be entered. 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 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 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: The Fedora LiveOS system allows for persistent storage in 3 ways: 1. A general persistent overlay - a compressed, write-once, fixed-size file space that will save updates and changes the LiveOS image (Activities, operating system changes, anything written in the LiveOS file space. 2. Persistent Home folder - a re-sizable (with difficulty), uncompressed, optionally-encryptable, file space for anything that goes in the Learner's /home/ folder (all the Sugar Activities, logs, and good stuff). 3. The device's original partition file space - outside of the LiveOS file tree, but accessible through the /mnt/live folder mount point. There, one will find the boot configuration files and anything else one had on the device before loading SoaS. Any file one might want to carry on the stick, without consuming the other limited file spaces, may be saved here (limited by device capacity). The standard persistent overlay is needed for operating system changes and updates. But, one may find many advantages to installing Sugar on a Stick with a persistent
Re: [SoaS] [SugarClone] -was Re: You scream, I scream, ...
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
Re: [SoaS] [SugarClone] -was Re: You scream, I scream, ...
Frederick Grose wrote: On Sat, Apr 24, 2010 at 8:41 AM, Thomas C Gilliard satel...@bendbroadband.com mailto: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. ACER Aspire ONE 250 GB HD Dual Boot: W7 Home Premium and Ubuntu 9.10: Desktop$ ./storageDevices bus..vendor..model..device pci..ATA..TOSHIBA MK2555GS../dev/sda in Ubuntu 9.10 terminal an d in root terminal with card in slot (Linux does not see the SD, it may require a driver, it appears in windows 7) Desktop# mount /dev/sda7 on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw) none on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type tmpfs (rw,mode=0755) none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) none on /dev/shm type tmpfs (rw,nosuid,nodev) none on /var/run type tmpfs (rw,nosuid,mode=0755) none on /var/lock type tmpfs (rw,noexec,nosuid,nodev) none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) none on /proc/fs/vmblock/mountPoint type vmblock (rw) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev) gvfs-fuse-daemon on /home/robert/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=) Tom Gilliard satellit --Fred ___ 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] [SugarClone] -was Re: You scream, I scream, ...
Fred; Tested Your new SugarClone script. It works fine. * Used on 4GB USB Firefly*: ./livecd-iso-to-disk --format --reset-mbr --overlay-size-mb 2000 /home/robert/Desktop/soas-i386-20100421.18.iso /dev/sd(*) * Removed and then reinserted USB in Ubuntu 9.04 * Copy/Paste 2 scripts to opened USB on Desktop: modified_livecd-iso-to-disk SugarClone *Inserted and booted USB on Acer Aspire One su /mnt/live/SugarClone found Target USB and made clone sucessfully. Note: 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) QUESTION: 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 script(s) work. They are a GREAT improvement! Thanks Tom Gilliard satellit 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 satellit = 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, http://people.sugarlabs.org/fgrose/SugarClone. New: 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 unmodified.) 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 command, /mnt/live/SugarClone 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 information. Notes: 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. --Fred ___ 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] [SugarClone] -was Re: You scream, I scream, ...
soas-i386-20100414.22.iso written to 2GB USB Same behavior: continous restart from wheel on graphics startup after bars f13 This seems to fix it: IRC log(edited): * soas-9ad7 (~...@2002:42dc:6d04:0:21f:c6ff:fe8f:d3a) has joined #sugar soas-9ad7 soas-i386-20100414 on 2GB USB * soas-9ad7 is now known as satellit_414 satellit_414 to get it to boot: * init 3 at boot esctabadd init 3 to boot line * log in: liveuser * su - * update sugar-artwork-0.88.0-2.fc13.i686.rpm : rpm -Uvh http://kojipkgs.fedoraproject.org/packages/sugar-artwork/0.88.0/2.fc13/i686/sugar-artwork-0.88.0-2.fc13.i686.rpm *yum install gdm* hal* (gdm* (7pkgs) hal* (6pkgs)) satellit_414 reboot satellit_414 Now it works and IRC starts fine. *installed analyze from ASLO in browse satellit_414 local xmpp only (no presence service in log) satellit_414 has quit (Remote host closed the connection) * Tom Gilliard satellit ... dragged scripts into USB opened on PC 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 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) 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 ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] [SugarClone] -was Re: You scream, I scream, ...
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 wrote: 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.) Actually I insert the usb into a usb slot in my ubuntu 9.04 PC tower (Dell520n) which auto opens the USB and then I drag the script files from the desktop into the opened USB from the PC desktop. I do set the properties of the files first to all read- write and allow executing as a program. (This is equivalent to copying the files to the /mnt/live/ directory in a booted soas USB.) 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. I thought it was because I did not specify the option to keep user id 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 ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] [SugarClone] -was Re: You scream, I scream, ...
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] [SugarClone] -was Re: You scream, I scream, ...
still not working. If I insert a USB plus the SD, I get 5 item list If i select a number eg: 1 you chose: usb..Lexar..USB choice #1, /dev/sde [r...@localhost live]# No further action occurs..? Frederick Grose wrote: 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 ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] [SugarClone] -was Re: You scream, I scream, ...
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
