Re: [Server-devel] updates

2009-02-08 Thread Martin Langhoff
On Fri, Feb 6, 2009 at 1:05 PM, Jerry Vonau jvo...@shaw.ca wrote:
 I'm going to back-port the minihal.py (index 6d4e6de..8ab93d4 100644)
 fix to what I have going on here.

Cool!

 the cf card, this should be almost be good to go, just have to write a
 post part in the kickstart file to setup the olpc.fth file. The trick to
 getting this all working is to plug in the external drive in after
 anaconda loads up to the language screen, keeps from messing with OFW's
 and the kernel's drive ordering. An external hard drive could be
 boot-able if you set up the olpc.fth file on the first partition as long
 as it is not lvm, so this opens up that avenue also. I used that method
 to load the stock updated os on to the XO.

When you say external drive, do you mean the SD card or another bit of media?

 I've add the need modules and firmware to support the cf card and the
 on-board wireless into anaconda's build routine. I get prompted to
 configure the on-board wireless lan now..(yet to be tested). Guess I
 should bz that one too. Should this be successful, live updates at
 install time could be possible. Then how would we like the on-board
 interface to come up as? Part of the mesh,
 or let it be available to be configured for internet access by default?

A mesh device, our goal is to have a School Server, so we'll want it
as a mesh gateway antenna... but we'll wipe those files away and setup
our wonky configuration from xs-config, right?

 I should have an updated patch set later this weekend.

Cool - I had this thread marked as to review/test/merge but I now
realise you are still working on it.

let me know how it goes!


m
-- 
 martin.langh...@gmail.com
 mar...@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] xs-activation-server over IPv6

2009-02-08 Thread Martin Langhoff
On Fri, Feb 6, 2009 at 7:51 AM, Daniel Drake d...@laptop.org wrote:
 Thanks. The modification required is in
 /etc/sysconfig/network-scripts/ifcfg-lanbond0

 change:
IPV6INIT=no
 to
IPV6INIT=yes
IPV6ADDR_SECONDARIES=fe80::abcd:ef01/64

That is the hardcoded address that the XO tries to reach. I want this
to work on mesh and a/b/g, but the address is link-local, so options:

1 - we can use fe80::abcd:ef01/64 for mshbond0 (which means it works
with old XO builds) and fe80::abcd:ef02/64 (note the 2) for lanbond0

2 - we can assign the same addr to lanbond0 _and_ mshbond0. The kernel
handles it alright, but userland finds it weird. For starters, xinetd
doesn't like the idea.

Even if we can get xinetd to dance, #2 looks fairly fragile, the kind
of thing upstream is going to say even if it's technically possible,
don't do that!.

So initially I am going with #1-- do you think you can tweak the
initrd a bit more to poke at ef01 over mesh, and ef02 over abg?
Looking at activate.py, adding it to the array in try_network()...

cheers,



m
-- 
 martin.langh...@gmail.com
 mar...@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] Network addressing for activation-over-IBSS

2009-02-08 Thread Martin Langhoff
On Mon, Feb 9, 2009 at 5:57 PM, Martin Langhoff
martin.langh...@gmail.com wrote:
 Done. The 'olpcxs-testing' repo now has an xs-config (0.6.0.4.g...)
 that includes this commit. Should be good for your APs which need a
 range for administration and activation.

http://wiki.laptop.org/go/XS_Network#Network_devices

Our handing out of dhcp leases from different (potential) servers, and
various interfaces is a bit of a gnarly thing.

For the time being, I've documented the IPv4 addresses and ranges, as
well as these 2 new IPv6 hardcoded link-local addresses. Going
forward, we can get rid of a lot of complexity by forgetting the many
servers thing, specially wrt mesh.

By which I mean: If we are using mesh, we are strictly in a
single-server environment. Small school, la la la.

cheers,


m
-- 
 martin.langh...@gmail.com
 mar...@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel