School server: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
(→‎See also: "debug networking")
Line 29: Line 29:
* [[IRC]] - #schoolserver on irc.oftc.net
* [[IRC]] - #schoolserver on irc.oftc.net
* [[Troubleshooting School Servers]]
* [[Troubleshooting School Servers]]
* [[Mesh Debug|How to debug in a crowded environment]]
* [[Mesh Debug|How to debug networking in a crowded environment]]
* [[School server/School district networks]]
* [[School server/School district networks]]
* [[Bitfrost]] Security and Identity model
* [[Bitfrost]] Security and Identity model

Revision as of 04:49, 22 November 2007

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


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