<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Adam<br>
<br>
The original proposal was to provide a method for an XO to be
registered to multiple school servers simultaneously. That doesn't
seem to relate to any <br>
of your use cases. My concern is increasing the complexity of use by
our students. We shouldn't force a configuration decision or action
on the user unless absolutely necessary.<br>
<br>
As a developer, I am moving an XO to different servers daily. The
process requires deleting known_hosts and registering with the new
server. Not too hard for the exceptional case of a teacher using
multiple school servers - shouldn't justify every child in the
various schools having to deal with the network control section.<br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 04/14/2016 08:30 AM, Adam Holt
wrote:<br>
</div>
<blockquote
cite="mid:CAHaBuGcStSVjfjAzTApq5G_W5HtPXfB3i2GD6Vcj7EXsba8aig@mail.gmail.com"
type="cite">
<div dir="ltr">On Wed, Apr 13, 2016 at 8:17 PM, Tony Anderson <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>></span>
wrote:<br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">James<br>
<br>
I can't think of a use case for an XO to access multiple
school servers.</blockquote>
<div><br>
</div>
<div>Apologies am not following all the details of this
conversation, but just to point out some of our newer work
in Haiti will experiment with XO laptops moving between
different school servers, in off-campus computer club(s),
librar(ies), and at school, etc.<br>
<br>
</div>
<div>Likewise there are definitely teachers who work in
multiple schools, and need to bring their main XO to each
school, impressive!<br>
</div>
<div><br>
</div>
<div>Also some schools campuses are just too large to tie in
all the IT infra together, with buildings just too far
apart. So there will be several inexpensive school
servers likely in these schools, who do not want to
network their buildings together at this point.<br>
</div>
<div><br>
</div>
<div>Finally George Hunt is advising us on how to construct
even more mobile servers too, based on a large USB battery
packs supporting Raspberry Pi 3 (or XO-4 or whatever)
permitting increasingly ruggedized knowledge hotspots.<br>
<br>
</div>
<div><i>Not sure how we will deal with naming all these
different school servers coming down the pike, but
definitely something to start thinking about now, a
great question :}</i><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">If a
school is so large (> 200 XOs), the easy solution is
two school servers. However, the XOs access the
schoolserver based on SSID and so users can be divided to
their own schoolserver by the connection - defining the
LAN.<br>
<br>
The OLE Nepal solution clearly satisfies the requirement
to avoid any unnecessary configuration option or
'onboarding' step.<br>
<br>
The current placement of the code has been working for
years. Showing the server in the network section was added
at a late release, as I recall because the register menu
item disappeared after registration and so a user did not
know for sure if the XO was registered. This was later
fixed with 'register again' so putting the name in the
network section is now redundant.<span class="im HOEnZb"><br>
<br>
Tony<br>
<br>
On 04/14/2016 07:35 AM, James Cameron wrote:<br>
</span><span class="im HOEnZb">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Apr 13, 2016 at 06:13:42PM -0500, Jerry Vonau
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On April 13, 2016 at 5:37 PM James Cameron <<a
moz-do-not-send="true"
href="mailto:quozl@laptop.org" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:quozl@laptop.org">quozl@laptop.org</a></a>>
wrote:<br>
<br>
<br>
On Thu, Apr 14, 2016 at 02:44:25AM +0530, Manash
Raja wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
Hi Jerry,<br>
<br>
Please don't forget
jarabe/desktop/schoolserver.py is involved, I<br>
personally would prefer that code to be
moved into<br>
control-panel/network.<br>
Others please chime with your thoughts on
this one.<br>
<br>
Yes, if register option is brought to network
section, then it will<br>
provide<br>
better space for managing multiple different XS
servers.<br>
</blockquote>
Yes, add registration function to the network
section, or move server<br>
to a new section ... but for ease of first-use
where only one server<br>
is present, the register option can remain on the
main menu.<br>
<br>
(Why do I suggest a new section? The Network
section has become<br>
cluttered with radio device controls, access point
cache control,<br>
jabber server, social help, and soon proxy
settings.)<br>
<br>
</blockquote>
Wouldn't the backup related fields be more relevant
in the backup section<br>
of control-panel? Maybe the 'new' proxy settings
could have its own control<br>
panel section also?<br>
</blockquote>
Yes, yes.<br>
<br>
</blockquote>
<br>
</span>
<div class="HOEnZb">
<div class="h5">
_______________________________________________<br>
Sugar-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Sugar-devel@lists.sugarlabs.org"
target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a moz-do-not-send="true"
href="http://lists.sugarlabs.org/listinfo/sugar-devel"
rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel<br
clear="all">
<br>
-- <br>
</a>
<div class="gmail_signature">
<div dir="ltr"><a moz-do-not-send="true"
href="http://lists.sugarlabs.org/listinfo/sugar-devel"
rel="noreferrer" target="_blank">Unsung Heroes
of OLPC, interviewed live @ </a><a
moz-do-not-send="true"
href="http://unleashkids.org" target="_blank"><a class="moz-txt-link-freetext" href="http://unleashkids.org">http://unleashkids.org</a></a>
!</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Sugar-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>