In between various complications, I have been working on getting an
initial rebase of the XS packages and build infra to F11.
After much wrangling with revisor, comps and image-creator, I have an
initial installer iso and an image that boots on the XO-1. The XO
image tests reasonably well, I haven
Working on the OLPC XS rebase to F11 -- I end up with random bits of
gnome and kde, brought in by PolicyKit, which wants a
PolicyKit-authentication-agent.
Yum only seems to know of KDE and Gnome authentication-agents.
How does PK handle users logging in in a VT? What is the
authentication agent t
2009/10/23 Martin Langhoff :
>> - a script to simplify eth0 configuration
>
> How does that work?
http://hg.olenepal.org/NEXS_scripts/file/tip/netsetup.sh
>> Notes on self test:
>> - 32 tests performed, to check that: hostname has been set, both
>> ethernet interfaces present, all the regular X
On Fri, Oct 23, 2009 at 7:35 AM, Daniel Drake wrote:
> Here are the customizations we're making on top of XS-0.6 here in
> Nepal. This version will start being distributed to the field on
> Monday.
Thanks for posting this!
> Kickstart file modifications:
These are as I'd expect a local deployme
xs-activation-httphandler.py does:
lease = myoat.get_lease(sn, 300)
if lease is not None:
myoat.mark_served_lease(sn)
resp["lease"] = lease
However, get_lease doesn't look like it will ever return None.
Instead, it returns False if there is no lease. So we