Re: [Sugar-devel] Sugar on a Stick on XOs for XO Lending Libraries?
On Tue, Aug 18, 2009 at 1:01 PM, Caroline Meekscarol...@solutiongrove.com wrote: Hi, I'm curious if we are to the point technically where an XO lending library could create a stick for an XO borrower and lend them the XO. The borrower could then use Sugar and he XO on the stick. If they liked using Sugar they could keep the stick with all their work and continue using it on their home computer after they returned the XO. Seems like a cool idea, but I haven't been following the technical issues around SoaS on the XO enough to know if its technically feasible? Thanks, Caroline Would be nice, if it works. I have not tried it with the recent releases of SoaS (= Strawberry), but pre Strawberry it did not work. The main problem is that the underlying live-cd code assumes it is always running on the same computer. On first boot it does some specific adaptations for the XO-1 (i.e. change xorg.conf) which make it not work when booted later on a non-XO. Same thing the other way around, when first booted on a 'normal' pc it will not work on the XO-1. Again, all this was my experience with pre Strawberry versions of SoaS. If this is working now, then please correct me. Anyway, if it is not fixed yet, then this is one of the things SoaS has to address sooner than later in order to live up to all the publicity that you can take your work with you and boot it on any (Intel) computer. Hope I am being too pessimistic Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Who's interested in testing a new installer for SoaS?
I am interested in testing it (mainly on VMs (Fusion and VirtualBox) on Mac and QEMU on Windows) Ton van Overbeek On Sat, Aug 8, 2009 at 12:00 PM, Sebastian Dziallassebast...@when.com wrote: Hi everybody, I'm looking for some volunteers to test the hard disk installation with the latest SoaS snapshot and newly designed installer. Since this upstream project is really in the early stages of development but also concerns a pretty critical part of SoaS, I'd prefer getting some testing before throwing it in a snapshot and possibly breaking stuff. If you're interested and aware of the risk, please drop me a line. Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Call for Help: SoaS Display Manager (Auto-Login)
Regarding getting auto-login to work after restarting X. Yesterday I looked at the slim sources and it seems at first sight easy to add auto login of the default user after the first login. Any interest in me trying to implement this? If we use an extra option to slim we could push this change upstream to Fedora and then we do not have to maintain our own manager (olpc-dm). But maybe Sebastian is already happy with a working olpc-dm. Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] SoaS Getting stuck at the Fedora Login Screen
On Tue, Jul 28, 2009 at 8:07 PM, Caroline Meekscarol...@solutiongrove.com wrote: This week I'm focusing on issue that make it hard to deploy SoaS. One of these is stick failures. I believe there is more then one cause to stick failures so I'm going to try to attack them one a time, we don't have to get it to 0 but right now its a major disruption, almost every class someone has a broken stick. The most common sort of failure mode seems to be that the stick gets stuck at the Fedora Login Screen. Any ideas what is happening? 1. Why do we go there at all during reboot? 2. Sometimes it goes there without liveuser filled in, then its impossible to continue. 3. Sometimes if has liveuser but when you press return it takes you back to the login screen. I wonder if we just have a bug somewhere and its not the sticks fault at all? One of the things causing this is the way the livecd (and the derived usb) are set up. They are set up with auto-login into the liveuser account at cold boot. However this (auto-login) does not work on X-session restart (=restarting Sugar). Hence you end up with the Fedora login screen. Just an explanation, no solution (yet). Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] TuxPaint and saving to journal (Was: Duplication of effort)
On Mon, Jul 27, 2009 at 6:00 PM, Luke Faraonel...@faraone.cc wrote: snip There were some emails in the past on how Tux Paint can't save to the Journal so you can't use it with Memorize, etc. Odd, it used to. So, is the solution to fix the bug, or to rewrite Tux Paint? TuxPaint has never been able to save drawings to the journal. I have volunteered to try to add this to TuxPaint, but in order to do this I need the low-level dbus interface to the journal (or glib-dbus interface). This does not seem to be documented anywhere. Even the python API does not seem to be documented. The only thing I can find are the copy to/from journal python functions. Where is the stable(?) API to the journal/datastore described? Especially with all the discussions about tagging, sorting, etc. I'd like to know which parts of the API are stable and which are subject to change. Hope somebody has some pointers, either to docs or to code in other C activities. Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TuxPaint and saving to journal (Was: Duplication of effort)
On Mon, Jul 27, 2009 at 7:43 PM, Luke Faraonel...@faraone.cc wrote: On Mon, Jul 27, 2009 at 19:36, Ton van Overbeek tvoverb...@gmail.com wrote: I need the low-level dbus interface to the journal (or glib-dbus interface). This does not seem to be documented anywhere. Isn't http://wiki.laptop.org/go/Activity_DBus_API#Keeping_and_Resuming what you want? Yes, but it was/is not clear to me if this up-to-date. I also would have hoped/expected that this type of information would be available on wiki.sugarlabs.org instead of wiki.laptop.org. Anyway, for keeping/resuming I would need the equivalent C/C++ interface, but by following the python code I can probably figure it out. (Tried to look at Etoys, but I do not fancy to leam smalltalk ;-)) Ton ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TuxPaint and saving to journal (Was: Duplication of effort)
On Mon, Jul 27, 2009 at 8:40 PM, Edward Cherlinecher...@gmail.com wrote: Actually, I see Sugar API documentation at http://api.sugarlabs.org/ including Module dbus_helpers. Does this help? Yes, but ... The API docs at api.sugarlabs.org are generated directly from the code by doxygen. dbus_helpers states explicitly that it is not stable. From sugar.datastore.dbus_helpers source code: - 19 20 UNSTABLE. Should be internal to the datastore module. 21 - Is there a (semi-)stable low level dbus spec for the datastore? Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Paint improvements?
On Thu, Jul 9, 2009 at 11:46 AM, Aleksey Limalsr...@member.fsf.org wrote: On Thu, Jul 09, 2009 at 07:28:09AM -0500, David Farning wrote: On Wed, Jul 8, 2009 at 5:41 PM, Aleksey Limalsr...@member.fsf.org wrote: On Wed, Jul 08, 2009 at 06:26:00PM -0400, Caroline Meeks wrote: Nod, I've done that for Memorize and maybe we will for Paint too. It will take some thought to get it right and I've got a lot on my plate right now. Worth it if it turns into code but right now I'm wondering what is the best path forward? Sugarizing Tux, Improving Paint or adding features to Colors? It mostly depends on what programmers out there are interested. If Tuxpaint satisfies all needs and new features list for Paint and Colors! is not short, I guess its much easier to add save-to-journal feature to Tuxpaint. I am in occasional contact with Bill Kendrick the lead developer for tuxpaint. I try to reach out to him and the rest of the tuxpaint team to work more closely with Sugar Labs. The save-to-journal feature shouldn't be a problem(since this will be local change in Tuxpaint's code). The relly hard problem is sharing mode in Tuxpaint. There is a ticket for this reason - #887 -- Aleksey As someone who has hacked on Albert Cahalan's original XO-1 port of Tuxpaint (see the tuxpaint entry on http://wiki.laptop.org/go/Activities/All) I'd be glad to help with further sugarizing tuxpaint. What I did was to adapt it to the rainbow requirements for the XO-1 (store data in the right directories, etc.) and proper startup from the ring. No integration with the journal or implementation of sharing. Note that a full installation of tuxpaint is very big, due to all the examples and translations. Probably too big for a 1G stick SoaS. Aleksey, what are your ideas about integration with the journal? Provide a python glue layer? Or implement it directly in C? Anyway, let me know what I can do. Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Strawberry VDI, please
Follow up on my previous message. Turned out it was my own mistake. I had already a sugar-strawberry VM booting from the iso and with an empty harddisk also named sugar-strawberry.vdi. When creating my new VM the hard disk ended up to point to the empty one, not to the vdi file extracted from the zip. After pointing to the right hard disk file it booted fine. In the meantime I have upgraded to Virtualbox 2.2.4 for Mac OSX, but I am pretty sure it would have worked on 2.2.2 if I had used the correct vdi file. The default boot in Virtualbox shows the text screen, not the graphic boot screen. You'll have to add some vga=xxx option to the boot command to get a larger screen and then the graphic sugar logo (3 dots) and the XO logo for the remainder of the circle are shown. Speak has problems with sound. Sound is intermittent and selecting an other face exits the activity. I have similar erratic behavior when using the strawberry iso in a VMware fusion VM. Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] Important: Please test the new Snapshot!
On Sun, Jun 21, 2009 at 10:06 AM, Simon Schampijersi...@schampijer.de wrote: snip And another snapshot on our way to the final image. The ring has been adjusted to display as well Record, Paint and Labyrinth by default. http://download.sugarlabs.org/soas/snapshots/2/Soas2-200906211228.iso A few first impressioms for Soas2-200906211228.iso: - Labyrinth is *not* a favorite (i.e. not in the ring) at first boot. - All tamtam activities are gone, intentional ??? Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Problem using sugar-update-control to update large (100+ MB) activity bundles
On Mon, Jun 15, 2009 at 9:25 AM, Bryan Berrybr...@olenepal.org wrote: I would like to know if the newer version of sugar-control-update http://git.sugarlabs.org/projects/sugar-update-control/repos/mainline/blobs/master/src/model.py only transfers the differences between the new and old bundles, thus making the update process much faster. I have stared at the code myself for about 30 minutes and I can't tell. If the newer version of the sugar-update-control is much faster, how much trouble would it be to backport it to 0.82, if even possible? Bryan, Looking at the model.py code in git it seems the full bundle is downloaded since it uses urlretrieve. So nothing has changed w.r.t. downloading compared with 0.82. Please correct me if I am wrong. Could you use something like rsync to update the Epaati bundle? That only transfers the differences. Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] New Snapshot Incoming!
On Mon, May 4, 2009 at 11:05 AM, Sebastian Dziallas sebast...@when.com wrote: Hi folks, there's another new snapshot ready! Here are the links: * For the Image: http://download.sugarlabs.org/soas/snapshots/2/Soas2-200905031329.iso * For the Appliance: http://download.sugarlabs.org/soas/appliances/soas2-20090503.zip The appliance has undergone major changes, meaning that it might not work. Both are based on the current Rawhide state, which should be rather stable. Now this is important: Please test the activities. Recommend new ones you want to see on SoaS. Report issues to our trac instance. And please submit your hardware profile, following the instructions here: http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Hardware I'll post a more detailed e-mail with an overview of our plans for the upcoming release candidate soonish. Thanks and happy testing! --Sebastian Tried the applicance. Boots OK in both VMWare Fusion 2.0.4 and VirtualBox 2.2.2 on my MacBookPro. Wanted to submit the corresponding harware profiles but smoltSendProfile does not seem to exist in the applicance (soas2-20090503.zip). Correct, or am I looking in the wrong place? Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] USB stick has to be labeled FEDORA when using Boot Helper CD, persistent storage not used
On Mon, Apr 20, 2009 at 1:32 PM, Caroline Meeks solutiongr...@gmail.com wrote: On Sat, Apr 18, 2009 at 9:38 PM, Ton van Overbeek tvoverb...@gmail.com wrote: When using the latest Boot Helper CD (http://people.sugarlabs.org/sdz/soas-boot.iso) the USB stick has to be labeled FEDORA, otherwise the boot hangs. When you created the stick with liveusb creator and included a persistent storage on the stick, this persistent storage will *not* be used when booting via the CD (reason: the initrd from the CD is used and it uses the USB stick as an overlay, the extra overlay needed for the persisten storage is not used, since the CD does not know the label/UUID for the persistent storage file). I just tested booting from CD plus USB and it seemed to use persistent storage ok. Can you confirm its not remembering things when you boot with the boot helper CD. This is an important bug if it exists and a tricky one if its not consistent. Thanks, Caroline It does work as you describe. When getting my original USB stick to boot with the boot helper CD I had only renamed the stick, but not changed the relevant part of the overlay name to FEDORA. Today I reran liveusb-creator *after* labeling the stick as FEDORA. Now the persistent overlay was created with the correct name and SoaS remembers my settings and the journal between boots with the boot helper CD. Updated the wiki page http://wiki.sugarlabs.org/go/Sugar_on_a_Stick accordingly. Ton ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [SoaS] USB stick has to be labeled FEDORA when using Boot Helper CD, persistent storage not used
When using the latest Boot Helper CD (http://people.sugarlabs.org/sdz/soas-boot.iso) the USB stick has to be labeled FEDORA, otherwise the boot hangs. When you created the stick with liveusb creator and included a persistent storage on the stick, this persistent storage will *not* be used when booting via the CD (reason: the initrd from the CD is used and it uses the USB stick as an overlay, the extra overlay needed for the persisten storage is not used, since the CD does not know the label/UUID for the persistent storage file). Any chance this can be fixed for the Boot Helper CD case ? Should I file a ticket about this (no persistent storage when using the Boot Helper CD) ? I edited the SoaS wiki page and added this information. With the Boot Helper CD and a properly labeled SoaS USB stick I was able to boot into Sugar on my Windows XP virtual machine in VMware Fusion on my brand new Macbook Pro. Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows
On Thu, Mar 12, 2009 at 9:55 PM, S Page skierp...@gmail.com wrote: On Thu, Mar 12, 2009 at 4:04 PM, Dave Bauer dave.ba...@gmail.com wrote: I haven't found an easy way to get QEMU working with acceleration on OS X. QEMU on Windows is also confused, or I am. http://sugarlabs.org/go/Supported_systems/Windows still points to Wade's fine bundle and detailed steps from Ton van Overbeek but both are to run OLPC 8.2.0 images which is old Sucrose. Meanwhile http://wiki.laptop.org/go/Emulating_the_XO/Quick_Start/Windows and its parent have lots of information about QEMU, but mostly out-of-date. I put today's SoaS2 ISO in my dusty old qemu 0.9.0 directory on Windows XP. I think you use -cdrom Soas2-200903121944.iso to make it work. C:\Qemu net start kqemu The KQEMU virtualisation module for QEMU service was started successfully. C:\Qemuqemu.exe -L . -m 256 -kernel-kqemu -soundhw es1370 -net user -net nic,model=rtl8139 -cdrom Soas2-200903121944.iso Version mismatch between kqemu module and qemu (00010400 00010300) - disabling kqemu use Maybe that's why it's mind-blowingly slow to boot. Note there is a break between qemu 0.9.1 and later w.r.t which kqemu module to use. See http://www.nongnu.org/qemu/download.html. kqemu 1.3.0pre11 for qemu = 0.9.1 kqemu 1.4.0pre1 for later (i.e. my private version and for 0.10.1) QEMU 0.10 is out, but the two Japanese URLs don't have Windows binaries. Some random person at http://qemu-forum.ipi.fi/viewtopic.php?f=5p=14435 has a Windows build, while a compatible kqemu accelerator is nowhere to be found. I always had problem with -kernel-kqemu. Usually things work with only user mode acceleration. I did try the 0.10 version you referenced with Soas2-200903061846.iso, but the boot only worked up to the start of X, then it crashed. Have not tried the 20090312 version yet. There is a QEMU 0.9.1 Windows binary, I don't know if available kqemu works for it. Emulating OLPC OS Images with QEMU has been difficult on any platform ever since the 3DNow! extensions problem arose, I think that's why Wade and Ton van Overbeek made special binaries. But maybe old versions of qemu/kqemu are fine for SoaS images. I think we are working towards a solution, just not as quickly as we would like. The story of the life since the Industrial Revolution ;-) Regards, -- =S Page I will be off-line till April 10 (holidays down-under), but then I should have a shining new 17 inch MacBook Pro with VMWare Fusion, so I should be able to try out both Windows and Mac versions. Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] Booting SoaS on a PC and on an XO with the same stick (Yes, it can be done)
On Tue, Mar 10, 2009 at 11:34 AM, Dave Bauer dave.ba...@gmail.com wrote: Hi, I used liveusb-creator 3.6.3 on windows to create SoaS-20090305 and it works fine on my Acer laptop, and virtualbox. I tried to boot from the USB with my XO and I got no signature for our key list found I have my developer key installed in /security/develop.sig I also tried copying the key to /security/develop.sig on the USB but got the same message. Is there a step to get the SoaS to boot on the XO that I am missing? Thanks Dave What does a verbose boot on your XO say (Keep the 'v' game key pressed when powering the XO on until asked to release the game keys) ? Open Firmware should report finding your developer key before even trying to load the ramdisk and booting linux. Also make sure your stick has not been booted on an other computer before booting on the XO (i.e. first boot after creating the stick with liveusb-creator on the XO). Alernatively you have to delete (as root) /.liveusb-configured and /.liveusb-late-configured before shutting down and then boot on your XO. Right now I can only say, it works for me ... Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] Booting SoaS on a PC and on an XO with the same stick (Yes, it can be done)
Thanks Luke. Works as advertised ;-). The SoaS2 iso (Soas-200903051021.iso, Fedora 11 based) when processed with liveusb-creator 3.6 boots nicely on my Dell Precision M60 laptop. I can also confirm that the extraneous backslashes in boot/olpc.fth are gone and that boot/olpc.fth is generated by default == USB sticks produced on Windows with liveusb-creator 3.6 are directly bootable on an XO-1 (provided the boot on the XO-1 is the first boot after generating the stick with liveusb-creator). Thanks again for the release. Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] SoaS sticks produced with liveusb-creator 3.6 on Windows are bootable on the XO
See subject. I edited the Sugar on a Stick/Installation/OLPC page accordingly. Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [SoaS] Shutdown/Restart does not work after X-server restart
Just filed bug #498 on dev.suharlabs.org: --+- After a restart of X (e.g. after a settings change in the control panel) the shutdown and restart options in the panel on the home/friends/neighborhood screens become inoperative. You have to shut down from a terminal. From shell.log: -- dbus.exceptions.DBusException: org.freedesktop.Hal.Device.PermissionDeniedByPolicy: org.freedesktop.hal .power-management.shutdown-multiple-sessions auth_admin -- (action, result) -- Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] The Road to SoaS-2: A new Snapshot!
Generated the usb stick on Windows using liveusb-creator 3.2 with the '-x' option to get the boot/olpc.fth file. Edited the olpc.fth file to get rid of the extraneous backslashes (Luke already fixed this in git, but no updated windows version of liveusb-creator has been created yet). First tried to boot it on my Dell laptop (Precision M60, Pentium-M, 1920x1200 res). Got the three bars to complete, but then a blank screen and no X windows. no Sugar. Could not get a text console (Ctrl-Alt-F[1-6] did not work). Then reflashed the stick and tried to boot it on the XO. Got the nice graphical plymouth boot which took a loong time to complete (much much longer than a SoaS-1 image). Again a blank screen and no X. Here I could get to the text consoles. Noticed there was a cursor which could be moved over the screen with the XO touchpad. dmesg did not show any obvious clues. Xorg.0.log showed at the end: - (II) GEODE: Driver for AMD Geode Chipsets: Geode LX, Geode GX (EE) No devices detected. Fatal server error: no screen found - The XO specific xorg.conf file was created in /etc/X11 and read by the X server.. All in all not very successful. I hope you can use this info. Ton van Overbeek ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [SoaS] Booting SoaS on a PC and on an XO with the same stick (Yes, it can be done)
While browsing the liveusb-creator source on https://fedorahosted.org/liveusb-creator/browser I noticed that it should be possible to boot SoaS directly on the XO. So I tried with the Soas-200903011706.iso image using liveusb-creator 3.2 on Windows. I had to start from the commandline in order to pass in the needed -x (or --xo) option. This option copies the boot/olpc.fth forth file on the stick which the XO firmware needs for booting. However using this stick, the boot on the XO failed. Turned out there were a few too many backslashes in the olpc.fth file. (diffs in attached olpc.fth.diff file). Removing them made the boot succeed, but no good X configuration for the XO. So I created /etc/X11/xorg.conf from the XO specific one in /etc/rc.d/init.d/livesys-late (See http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/soas-base.ks). I have not investigated while it was not created in the first place, but this stick was first booted on my Dell Precision M60 laptop and later on the XO. Anyway, with the xorg.conf in place it booted properly into Sugar on both the XO and my Dell laptop. No details yet about what works and what does not on the XO, but WiFi seems to work. I suggest to update liveusb-creator to have the '-x' option turned on by default in both the windows and fedora versions, at least for the one advertised on http://sugarlabs.org/go/Sugar_on_a_Stick/Installation. By the way, why don't we use liveusb-creator for Linux on that page ??? The olpc.fth file in liveusb-creator should be fixed (remove the extraneous backslashes). My XO firmware is Q2E18. Also somehow the xorg.conf needed for the XO should be created automatically on the XO. I will try to track down why it did not for me. I hope this is useful info for the SoaS project. Ton van Overbeek olpc.fth.diff Description: Binary data ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] Booting SoaS on a PC and on an XO with the same stick (Yes, it can be done)
On Tue, Mar 3, 2009 at 2:34 PM, Luke Macken lmac...@redhat.com wrote: On Tue, Mar 03, 2009 at 01:54:27PM -0500, Ton van Overbeek wrote: [...] I suggest to update liveusb-creator to have the '-x' option turned on by default in both the windows and fedora versions, at least for the one advertised on http://sugarlabs.org/go/Sugar_on_a_Stick/Installation. I have no problem enabling --xo mode by default. The olpc.fth file in liveusb-creator should be fixed (remove the extraneous backslashes). I fixed this issue in changeset 379c7f825c6348d188a93283e9840c7d783dbd02 a while back, but have yet to push out a new windows release. I will try to spin up a new release this week. luke Looking forward to it. Thanks for the quick reply. Ton ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Journal empty in Soas-200902231225 and what is Soas-200902241809.iso in snapshots/2/ ?
On Thu, Feb 26, 2009 at 3:11 AM, Simon Schampijer si...@schampijer.de wrote: Ton van Overbeek wrote: When trying out Soas-200902231225 the journal stays empty. Anybody else seen this ? Also in http://download.sugarlabs.org/soas/snapshots/2/ there is now a Soas-200902241809.iso. What is this ? Is there a changelog or buildlog somewhere for the various Soas versions? Ton van Overbeek Maybe you see http://dev.sugarlabs.org/ticket/72 which was kindly fixed by Tomeu yesterday. Cheers, Simon Yes, it is the same bug. I see the same error message in the logs (shell.log) as in the ticket. I also have a large screen (1920x1200), so this is most certainly the same bug. Is there alreadys a SoaS snapshot with this fix included ? Ton ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
