School server: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
Line 18: Line 18:
*[[School Identity Manager]]
*[[School Identity Manager]]
*[[XS Installing Software]] has instructions for installing the latest School Server images
*[[XS Installing Software]] has instructions for installing the latest School Server images
*[[XS_Building_Software]]
*[[XS_Software_Repositories]]
*[[XS_LiveCD]]
*[[XS_Server_Software]]
*[[XS_Installing_Software]]
*[[XS_Server_P2P_Cache]]


== See also ==
== See also ==
Line 32: Line 38:
[[Category:Software ideas]]
[[Category:Software ideas]]
[[Category:SchoolServer]]
[[Category:SchoolServer]]
[[Category:Hardware]]

Revision as of 16:16, 11 October 2007

  This page is monitored by the OLPC team.
  english | 한글 | español HowTo [ID# 69721]  +/-  


When we deploy one laptop per child, we must also provide additional infrastructure extending the capabilities of the laptops. While the laptops are largely self-sufficient, a mesh portal providing connectivity and shared resources greatly extends their utility.

These persistent services required by OLPC laptops could conceivably be implemented in a fully distributed manner. They are , however, currently provided more economically by a centralized local resource, the school server. The functions provided by this server are open to debate, but at a minimum they include internet communication and storage resources to the school's wireless mesh.

Currently, the School server is described by these documents:

See also