Re: [Server-devel] [Sugar-devel] GPA XS Report

2009-07-08 Thread Dave Bauer
On Tue, Jul 7, 2009 at 10:27 PM, Caroline Meekssolutiongr...@gmail.com wrote:


 On Tue, Jul 7, 2009 at 10:20 PM, Martin Langhoff martin.langh...@gmail.com
 wrote:

 On Wed, Jul 8, 2009 at 9:46 AM, Anurag Goelagoe...@gmail.com wrote:
  We booted several computers with SoaS and changed the
  network settings from the default (jabber.sugarlabs.org) to the IP
  address
  on the XS. After doing this, the computers in the computer lab still
  would

 That is a workaround to the missing register button in SoaS, right?

 no, we are still just trying to get the machines in the lab to see the
 Jabber Server in the lab via the server setting in the control panel.

 I think some of your comments below may still be relevant but I don't
 entirely understand.


 I suspect that part of the problem is that you are using the IP
 address. Sugar will see whatever DNS or IP addr you provide there and
 will try to connect to jabber and create an account as follows:

  - machine-id@jabberservername

 On XO hardware, machine-id is the serialnumber. On other hw, it
 creates a random string on first boot.

 The problem with the scheme is that jabber on the XS expects a very
 specific jabber servername for the account: its own name (as given to
 domain_config) prefixed with 'schoolserver.'

OK, we can workaround this two ways,

Use schoolserver as the jabber server name in the settings then
1) set the IP in /etc/hosts as a quick hack to make sure things work
2) set up the SoaS to use the built in DNS on the XS.

Using the DNS seems problematic, probably due to my lack on knowledge.
If we do that we need to defer to the network DNS for everything
except the schoolserver hostname. If kids take the stick home, what
happens with the DNS if we put the XS into resolv.conf? The SoaS is
not getting DHCP from the schoolserver due to the setup where the XS
is just inserting into the same LAN as the clients.

Dave


 If the name doesn't match that format, then it breaks.

 The workaround is to use schoolserver.mydomain in the SoaS control
 panel. A more proper solution is probably to bring back 'registration'
 :-)

 hth,



 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
 ___
 Sugar-devel mailing list
 sugar-de...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel



 --
 Caroline Meeks
 Solution Grove
 carol...@solutiongrove.com

 617-500-3488 - Office
 505-213-3268 - Fax

 ___
 Sugar-devel mailing list
 sugar-de...@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel





-- 
Dave Bauer
d...@solutiongrove.com
http://www.solutiongrove.com
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] [Sugar-devel] GPA XS Report

2009-07-08 Thread Martin Langhoff
On Wed, Jul 8, 2009 at 10:39 PM, Dave Bauerdave.ba...@gmail.com wrote:
 OK, we can workaround this two ways,

 Use schoolserver as the jabber server name in the settings then
 1) set the IP in /etc/hosts as a quick hack to make sure things work
 2) set up the SoaS to use the built in DNS on the XS.

I'd strongly recommend avoid touching /etc/hosts or /etc/resolv.conf
on every SoaS.

 Using the DNS seems problematic, probably due to my lack on knowledge.

The changes are trivial -- a list of ~8 names need to resolve to the
XS's internal address. DNS can be complicated, but this is
completely trivial.

Get those names added to the existing DNS server, and you're sorted.

 If we do that we need to defer to the network DNS for everything
 except the schoolserver hostname. If kids take the stick home, what
 happens with the DNS if we put the XS into resolv.conf?

resolv.conf gets re-written by NM all the time. Hardcoding it is no go.

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] [Sugar-devel] GPA XS Report

2009-07-08 Thread Caroline Meeks
On Wed, Jul 8, 2009 at 7:32 AM, Martin Langhoff
martin.langh...@gmail.comwrote:

 On Wed, Jul 8, 2009 at 10:39 PM, Dave Bauerdave.ba...@gmail.com wrote:
  OK, we can workaround this two ways,
 
  Use schoolserver as the jabber server name in the settings then
  1) set the IP in /etc/hosts as a quick hack to make sure things work
  2) set up the SoaS to use the built in DNS on the XS.

 I'd strongly recommend avoid touching /etc/hosts or /etc/resolv.conf
 on every SoaS.

  Using the DNS seems problematic, probably due to my lack on knowledge.

 The changes are trivial -- a list of ~8 names need to resolve to the
 XS's internal address. DNS can be complicated, but this is
 completely trivial.

 Get those names added to the existing DNS server, and you're sorted.


I think here is the rub.  What is the existing DNS server and how would we
get access to it? Certainly Boston Public Schools is not going to put
something in their DNS server for us.  Is there a workaround?



  If we do that we need to defer to the network DNS for everything
  except the schoolserver hostname. If kids take the stick home, what
  happens with the DNS if we put the XS into resolv.conf?

 resolv.conf gets re-written by NM all the time. Hardcoding it is no go.

 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




-- 
Caroline Meeks
Solution Grove
carol...@solutiongrove.com

617-500-3488 - Office
505-213-3268 - Fax
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel