<br><br><div class="gmail_quote">On Mon, Feb 8, 2010 at 5:30 AM, Sebastian Dziallas <span dir="ltr"><<a href="mailto:sebastian@when.com">sebastian@when.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi all,<br>
<br>
thanks to the awesome work of Kevin Fenzi and others, we've now nightly<br>
builds of Sugar on a Stick available. That means you can check the state<br>
of it on a daily basis here:<br>
<br>
<a href="http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/" target="_blank">http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/</a><br>
<br>
Whenever there's no .iso file available, this is due to a failure in the<br>
build process, which we'll need to investigate then.<br>
<br>
It also represents the current state of activities, giving me the<br>
opportunity to invite you to join our packaging & reviewing effort:<br>
<br>
<a href="https://fedoraproject.org/wiki/Sugar_Activities" target="_blank">https://fedoraproject.org/wiki/Sugar_Activities</a></blockquote><div><br></div><div><br></div><div>One thing to note about the Fedora 13 SoaS builds is that we now have the native rt2x00 upstream wireless drivers enabled so there shouldn't need to be any third party repositories enabled for them to work, not that its guaranteed that they will, but I would be interested to hear feedback from those that have one of the various Atom based eeePCs that have this hardware. I had a quick attempt at them a couple of weeks ago and while the wifi was detected by NetworkManager I couldn't associate with my WPA1 AP (I have had numerous issues with it before so I wasn't surprised) and there's been updates and fixes since and I've travelling for a month so it might have improved or be localised to my AP.</div>
<div><br></div><div>Peter</div></div><br>