8,288
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + + + − ==Sugar on a Stick Improve Deployability==+ − + + − + − SugarLabs Ticket 74 - http://dev.sugarlabs.org/ticket/74 Line 16:
Line 18: − + − ''Failure Modes''+ − − # Gets stuck at Fedora Login − ## With liveuser prefilled <br>I was able to repeatably create this failure when I was testing a version of schoolserver.py that had a typo in it. − ## With nothing prefilled <br> This error has successfully been replicated by Restarting multiple times. − # Bug in initramfs /init detected. Dropping to a shell. Good luck! bash: no job control in this shell. <br> Stick abuse, like putting it through the washing machine, seems to precipitate this type of failure. − # Freezes during use of an activity. Rebooting on the same computer doesn't help it still freezes on the same activity. One time we rebooted on a different computer and it worked. − − − We don't know the root causes but we have plenty of theories. − − Sticks will always fail. There will always be multiple causes for failure. This problem has to be addressed like a process engineering issue. Is stick failure a major cost in time or money? Find the largest cause of failure. Fix that to improve yield. Is stick failure a major cost in time or money? Find the the remaining largest cause of failure..... − − This summer we had probably 10 sticks fail for 35 students. That is a major cost in time and money. The most common unrecoverable failure mode was stuck at Login. − − ====We need a more robust files system==== − − It has been shown that if you take a stick that is stuck at login and you copy over a fedora-overlay file from a working stick, the stick will boot again. Thus we are confident that the problem is corruption of the overlay file. − − ''Next Steps'' - Try some alternate file structures. − − # Create a Fedora Full Install USB Stick, restart it a bunch of times and see if it does better. How much space will the Fedora Full Install take?<br>So far its > 4GB http://wiki.sugarlabs.org/go/VMware#Full_Install_with_F11_Net_install_CD_to_USB_Stick − # Create an Open Suse USB Stick, restart it multiple times and see if it fails. How much space does it use? − − ''Background Links'' − Thread from the Fedora Forum: [[http://forums.fedoraforum.org/showthread.php?t=221719]] − − Here is an idea for an alternative USB Format: [[http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/USB_format]] − − Also see Ticket 907 [[http://dev.sugarlabs.org/ticket/907]] − − A 2 GB USB is about $.60 more then a 1GB stick. If we need to compress less to get robustness its ok for us to require a 2GB USB. A 4GB stick is about $2.50 more then a $1GB Stick. − − ''Theories that have evidence against them'' − − Dave Bauer was able to replicate the failure easily by restarting a Sugar stick. This means its probably not: − − * The Bulk Copier, Dave doesn't have one. − * The older slower computers and USB 1 ports we are using at the GPA. − − ====Sticks are damaged during formatting or burning==== − − http://wiki.laptop.org/go/How_to_Damage_a_FLASH_Storage_Device [[http://wiki.laptop.org/go/How_to_Damage_a_FLASH_Storage_Device]] − − There was a detailed discussion thread back in February at: http://lists.laptop.org/pipermail/devel/2009-February/022987.html − − If we understood how to win and we had our own stick creation activity perhaps we would have less failures. − − ====Sticks are of poor quality==== − − Here is an explanation of two processes used to create USB sticks: http://www.solutiongrove.com/blogger/2008/09/08/there-are-two-type-of-usb-flash-memory-slc-and-mlc [[http://www.solutiongrove.com/blogger/2008/09/08/there-are-two-type-of-usb-flash-memory-slc-and-mlc]] − − ====Sticks are being improperly removed==== − − Yes they are, but its not at all clear to me that that correlates with the sticks that are failing. − − ====There is a bug around restarting==== − It is very common to fail after a restart, the system forgets its supposed to go to Sugar. See ticket 1069 [[http://dev.sugarlabs.org/ticket/1069]] − + − + + − + − + − A floppy helper would reduce it. A VM solution might also reduce it.+ − Tickets+ − * Ticket 598 Boot Helper Virtual Machine [[http://dev.sugarlabs.org/ticket/598]] − * Ticket 907 change the format we use for the USB stick [[http://dev.sugarlabs.org/ticket/907]] − * Ticket 597 Floppy Boot Helper [[http://dev.sugarlabs.org/ticket/597]] + + + + − + − − This is an the general todo list for SoaS. If you've any ideas or requests, please add them here. − − − {| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" − |-style="background:#787878; color: white;" − | '''Task Name''' || '''Priority''' || '''Status/Notes''' − |- − | solicit USB key donations from companies || 1 || info needed − |- − | allow direct recreation of USB keys (cloning) || 2 || needs testing [http://bugzilla.redhat.com/show_bug.cgi?id=448030] − |- − | add additional activities, if requested || 3 || get them on [http://activities.sugarlabs.org/ a.sl.o] − |- − | work on a keyboard layout control panel || 3 || work in progress [http://dev.sugarlabs.org/ticket/473] − |- − | be able to backup and restore from a School Server || 3 || to be worked out − |- − | support printers, scanners, cameras || 3 || to be worked out − |- − | activity for cloning USB Sticks and .iso files (cloning)|| 3 || to be worked out [http://dev.sugarlabs.org/ticket/74#comment:3] − |} − − Here's a list with completed tasks; feel free to move them from the table above. − − {| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" − |-style="background:#787878; color: white;" − | '''Task Name''' || '''Status/Notes''' − |- − | get SoaS included in [http://fedorahosted.org/liveusb-creator/ liveusb-creator] || done − |- − | create a virtual appliance (builds) || done [http://lists.sugarlabs.org/archive/sugar-devel/2009-March/012747.html] [http://dev.sugarlabs.org/ticket/114] − |- − | release a helper CD for boot from USB || done [http://dev.sugarlabs.org/ticket/265] − |- − | add sample content || done - add more if needed − |- − | fix blockers for release || most important point, check rawhide, as it progresses towards beta − |- − | update remaining RPMs || good progress done so far − |- − | check localization support || done − |- − | get artwork and branding together || done − |- − | change default Browse location || done − |- − |} − [[Category:TODO]]+
refresh a bit
<noinclude>{{GoogleTrans-en}}{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792}}</noinclude>
<noinclude>{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792}}
[[Category:TODO]]</noinclude>
==Sugar on a Stick deployability==
The good news is Sugar on a Stick is being successfully used in Schools around the world now! Based on these experiences this is a list of some of the known challenges that people may face piloting Sugar on a Stick right now. September is start of school in the US, so we expect to see an increase in teachers trying Sugar. We want to be ready with suggestions and work arounds as people face these challenges.
===Make it easier for a teacher or school to customize a spin and then copy it for a hundred kids===
===Make it easier to customize===
Make it easier for a teacher or school to customize a spin and then copy it for a hundred kids.
Tickets on this topic:
Tickets on this topic:
Red Hat - https://bugzilla.redhat.com/show_bug.cgi?id=448030 - RFE: create a bootable Live USB stick from the running livecd
Red Hat - http://bugzilla.redhat.com/show_bug.cgi?id=448030 - RFE: create a bootable Live USB stick from the running livecd, also Sugar Labs Ticket {{Bug|74}}.
''Use Case''
''Use Case''
It would be great if the teacher could use an inexpensive USB hub to burn more then one stick at a time.
It would be great if the teacher could use an inexpensive USB hub to burn more then one stick at a time.
===Sticks are dying a lot - Make sticks more robust===
===Stick failure===
Discussions of stick failure and alternative file structures is now at [[../Stick Layout]]
===Backup and recovery===
===Backup and recovery===
Ham and Dave from Solution Grove are making progress on this. You can track progress on ticket 916 [[http://dev.sugarlabs.org/ticket/916]]
Ham and Dave from Solution Grove are making progress on this. You can track progress on ticket {{bug|916}}
===What is a reasonable expectation for the role of the XS in Sugar on a Stick deployments in the next 6 months?===
===Role of the XS in SoaS deployments===
What is a reasonable expectation for the role of the XS in Sugar on a Stick deployments in the next 6 months?
===Collaboration is unreliable and thus frustrating===
===Collaboration is unreliable and thus frustrating===
Its working fairly well in the wired network at the GPA lab, but no other use case seem to work reliably.
Its working fairly well in the wired network at the GPA lab, but no other use case seem to work reliably. We need to expand the Poets Guide to [[Collaboration]] to give people hints on how to set up a scenario that will work for them.
===Using a CD helper takes a lot of prep time before and after class===
===Using a CD helper===
Using a CD helper takes a lot of prep time before and after class.
A floppy helper would reduce it. A VM solution might also reduce it. A network boot helper would also reduce it, for PCs that support a network boot.
'''Tickets'''
* Ticket {{Bug|598}} - Boot Helper Virtual Machine
* Ticket {{Bug|907}} - change the format we use for the USB stick
* Ticket {{Bug|597}} - Floppy disc Boot Helper
See also [[Sugar on a Stick/Goals]].
See also [[Sugar on a Stick/Goals]].
*[[Gardner Pilot Academy#Critical Path Technical Issues]]
* [[Gardner Pilot Academy#Critical Path Technical Issues]]
{{Transclude|Improve Sugar on a Stick}}