Re: [Sugar-devel] Fwd: [XSCE] Re: Client side Moodle transparent auth broken in 13.2.0 stable
On Tue, Aug 6, 2013 at 3:32 PM, Jerry Vonau je...@laptop.org.au wrote: This behavior was noted with XO-1s only, all others(1.5,1.75,4) appear work fine in testing. That is _very_ weird. Does the affected unit have any problem reading its own serial number or uuid? Does the Sugar Control Panel show the serial number correctly? cheers, m -- martin.langh...@gmail.com - ask interesting questions - don't get distracted with shiny stuff - working code first ~ http://docs.moodle.org/en/User:Martin_Langhoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Fwd: [XSCE] Re: Client side Moodle transparent auth broken in 13.2.0 stable
On 11 August 2013 10:14, Martin Langhoff martin.langh...@gmail.com wrote: On Tue, Aug 6, 2013 at 3:32 PM, Jerry Vonau je...@laptop.org.au wrote: This behavior was noted with XO-1s only, all others(1.5,1.75,4) appear work fine in testing. That is _very_ weird. Does the affected unit have any problem reading its own serial number or uuid? Does the Sugar Control Panel show the serial number correctly? Good to hear from you Martin. Just to finish this thread off, I was not able to reproduce this behavior with the XO-1s that I have. This appears to affect Anna's machines only. Thanks for the hints to what might be the root cause. Jerry ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
olpc-os-builder
Hi All: Is anybody else having trouble running OOB in the last day? I'm now getting this traceback when trying to run OOB: Reading repository information for http://mock.laptop.org/repos/local.13.2.0-xo1.75 Reading package information from http://mock.laptop.org/repos/local.13.2.0-xo1.75/repodata/primary.xml.gz Reading repository information for http://mock.laptop.org/repos/local.13.2.0 Reading package information from http://mock.laptop.org/repos/local.13.2.0/repodata/primary.xml.gz Traceback (most recent call last): File /opt/git/oob-xs/modules/yumcfg/kspost.50.yumcfg.py, line 29, in module fd = ooblib.cachedurlopen(url + /repodata/primary.xml.gz) File /opt/git/oob-xs/lib/ooblib.py, line 156, in cachedurlopen urlfd = urllib2.urlopen(url) File /usr/lib/python2.7/urllib2.py, line 126, in urlopen return _opener.open(url, data, timeout) File /usr/lib/python2.7/urllib2.py, line 406, in open response = meth(req, response) File /usr/lib/python2.7/urllib2.py, line 519, in http_response 'http', request, response, code, msg, hdrs) File /usr/lib/python2.7/urllib2.py, line 444, in error return self._call_chain(*args) File /usr/lib/python2.7/urllib2.py, line 378, in _call_chain result = func(*args) File /usr/lib/python2.7/urllib2.py, line 527, in http_error_default raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) urllib2.HTTPError: HTTP Error 404: Not Found ERROR: Failure in KspostStage: module yumcfg, part kspost.50.yumcfg.py, error code 1 * OLPC OS builder v7.0.0 Just wondering what could be causing this issue for me. Jerry ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Fwd: [XSCE] Re: Client side Moodle transparent auth broken in 13.2.0 stable
On Sun, Aug 11, 2013 at 1:15 PM, Jerry Vonau je...@laptop.org.au wrote: Good to hear from you Martin. Just to finish this thread off, I was not able to reproduce this behavior with the XO-1s that I have. This appears to affect Anna's machines only. Thanks for the hints to what might be the root cause. Thanks for the greeting! I had a season of detox after some severe burnout. I'm spending this weekend at Fedora Flock for personal enjoyment, and it's brought me back to the OLPC topic. About Anna's machines -- I suspect either an old OFW or bad/broken/misconfigured manufacturing data. cheers, m -- martin.langh...@gmail.com - ask interesting questions - don't get distracted with shiny stuff - working code first ~ http://docs.moodle.org/en/User:Martin_Langhoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Fwd: [XSCE] Re: Client side Moodle transparent auth broken in 13.2.0 stable
On Sun, Aug 11, 2013 at 3:20 PM, Martin Langhoff martin.langh...@gmail.com wrote: On Sun, Aug 11, 2013 at 1:15 PM, Jerry Vonau je...@laptop.org.au wrote: Good to hear from you Martin. Just to finish this thread off, I was not able to reproduce this behavior with the XO-1s that I have. This appears to affect Anna's machines only. Thanks for the hints to what might be the root cause. Thanks for the greeting! I had a season of detox after some severe burnout. I'm spending this weekend at Fedora Flock for personal enjoyment, and it's brought me back to the OLPC topic. Welcome back! I look forward to seeing your head and opinions poking up now and again :) About Anna's machines -- I suspect either an old OFW or bad/broken/misconfigured manufacturing data. cheers, m -- martin.langh...@gmail.com - ask interesting questions - don't get distracted with shiny stuff - working code first ~ http://docs.moodle.org/en/User:Martin_Langhoff ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- David Farning Activity Central: http://www.activitycentral.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[Server-devel] Clarifying some XSCE issues.
After a couple of eventful, and fruitful, weeks with XSCE, I would like to to clarify a few points where our message seemed to be unclear. -- Emphasis on small deployments. As a community, there is currently an emphasis towards small deployments. Due to their limited bureaucracies, we have been able to establish very quick turnaround times for feedback and fixes. This has enabled us to keep our rate of development quite high. The design and implementation of XSCE should scale from 1 school to 100,000 schools. There is currently an Ansible rewrite ( http://www.ansibleworks.com/docs/ ) in process. We believes that the use of ansible as a configure management tool has the potential to reduce the maintenance required at large deployments. A team of developers at AC is working on this now with the goal of landing in the beginning of the 0.5 release cycle -- Emphasis on ARM. XSCE runs on any hardware which runs Fedora 18. The current releases heavily favored XOs because they were a logical starting point from a Quality Assurance perspective. Debugging is an order of magnitude easier when testers and developers are running the same equipment. Starting with XOs enabled us to focus on school server developments rather than hardware quirks. Each quarterly release we have added additional hardware types. This is allowing the project to scale gradually to more and more device types without overwhelming developers and testers. -- Core OS. The decisions to base on Fedora was not taken lightly. If we wanted to run on XO-4s we had to run on a recent Fedora. The second issue is the fact that most of the interesting low powered servers are ARM based. Moving forward, our goal is to use the flexibility of the ansible provisioning system to be able to configure XSCE on fedora and CentOS. On an interesting note, we have been contacted by a team of ARM on CentOS developers who offered to work with us to get CentOS a a couple of ARM based servers. -- Our goals is not to tell anyone what they should do. We have avoided discussions on public lists such as this to avoid the temptation for people to tell us what to do... or for us to tell them what to do. Instead, we have focused on adding value. We hope to add value to the ecosystem. We hope that adding value earns us influence. In exchange we invite people to participate in the XSCE project by adding value. That value will help them earn influence within the project. I hope this help clarify some of the issues that have come up over the past couple of days. -- David Farning Activity Central: http://www.activitycentral.com ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] Re: Root fs on XO1
On Sat, Aug 10, 2013 at 03:05:18PM -0400, George Hunt wrote: Thanks everybody for your responses. I learned a lot yesterday by trying things you all suggested. James' idea of using a XO1.5, and devalias. . .,fs-update . . to populate an SD card was quick, and booted on a 1.5. I tried copying the /boot directory of a XO1 to this SD, and it appeared that the signed kernel was recognized, loaded, but dracut issued a warning that root argument was empty. So then I read up on dracut. My guess is that the drivers to read the SD card were missing from the initramfs. I don't think that is likely. The SD card driver is integrated with the kernel, and is not a module. (verified on 13.2.0 here). Rather, I guess that our dracut-modules-olpc package simply hasn't got scripted support for swinging the kernel over to a root filesystem on the SD card on XO-1. http://dev.laptop.org/git/users/dsd/dracut-modules-olpc/ http://dev.laptop.org/git/users/dsd/dracut-modules-olpc/tree/30olpc-boot/olpc-boot-cmdline.sh The above script is where the decision is made, and XO-1 SD card is not in the case statement, because we didn't add this support. So yes, specifying a root filesystem using the command line may be a workaround. Then I started following James' suggestion, looking into olpc-os-builder. There's an sd_image option which can be enabled. I could not determine if enabling that would also enable booting from an external USB flash/hard disk, but it seems worth a try. The lack of support in dracut-modules-olpc would still need fixing, in my opinion. The sd_image option will make a .zd but XO-1 doesn't have fs-update. (I'm still toying with the idea of a WD Passport -- external hard disk as the supported option for the XO1 XSCE). I've avoided that brand because of extra features of the product, in case they interfere. Does it work okay? (Extra features of consumer backup drives _might_ involve changes to the device in terms of the USB descriptors, such as those required for a push button to start backup software, or CD-ROM images of the software, so I've tended to select drives that either don't mention the software, or are marketed as expansion rather than backup.) I'm not yet clear whether it would be any simpler to insist that XO1's be unlocked before installing XSCE. It's easy to modify the kernel command line via olpc.fth, (which I verified to be ignored on a locked XO) but maybe getting the right drivers in the initramfs is the hard part. I still have lots more to learn. I really suggest you disable-security. Unless you have a real or industrial need for the security system, it will just hurt you over and over. -- James Cameron http://quozl.linux.org.au/ ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
