Hi, On 03.05.2008 16:52, Ricardo Carrano wrote: > While the support is not there, NYC is considering disabling NetworkManager > but this is not a good solution for (1) the XO will not boot into sugar and >
That would be a bug. > (2) collaboration will not work, because the mesh view will be broken. > That would be a bug as well. > They are interested in a way (quick workaround) of doing the configuration > manually in a persistent manner and still be able to collaborate. Any ideas? > > Btw, note that: > - Manually editing networks.cfg won't work because the scanning (the > blinking icon phase in the mesh view) is passive. So, if the AP do not > broadcast its SSID it is like it is not there. > - Manually associating to the AP would work but NetworkManager prevents > dhcp from working. > It should be possible to manually associate with the AP, then kill NetworkManager with SIGKILL so it can't mess things up during termination. After that, dhcp should no longer present a problem. > I have a feeling that enabling support to cloaked APs may be quicker than > hatching a workaround, but to do it fast we would need help in the NM part. > I was completely surprised when I read that NetworkManager is needed to boot into sugar. I can't think of any scenario where that dependency would make sense. Regards, Carl-Daniel _______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
