We have an experimental XS-0.6 ext3 image that boots and seems to work correctly as an XS would, on XO1.0 hardware.
Grab the image from
The sha1 of the file is
- Grab a fast SD card, at least 4GB
- Uncompress the image with gzip -d
- Identify the device node for the first partition -- usually
- Using fdisk, make the first partition at least 4GB, type 83 (linux) and bootable
dd if=OLPC-School-Server-<version>-i386.img of=/dev/<device> bs=1M
resize2fs /dev/<device> # this expands the FS to take all the space in the partition
Now the SD card should just boot on any unlocked 1.0 XO.
Note: Expect the first boot to take considerable time, as the Moodle database gets initialized.
Completing the installation
- Set a password for the root user.
- Follow the Initial Configuration steps outlined in XS_Installing_Software .
- It's probably a wise idea to avoid using Squid on the XO hardware.
Help is needed with...
- Testing of the XS functionality
- Getting a vanilla F9 kernel+initrd to boot
- External disk setup: scripts to setup an external disk to handle /library and swap. Should be hooked up with the usbmount triggers.
- Load testing and tuning of memory settings in apache and postgres -- how many users can reasonably use ejabberd & Moodle with our limited memory?
- Scripts to auto-configure usb-ethernet adapters as eth0
- Scripts to auto-configure USB "3G" adapters (usually appearing as ppp devices)
- Scripts to switch from mesh portal to hostap
Building the image
- checkout olpc-xs-builder
- wget http://xs-dev.laptop.org/xs/OLPC-School-Server-0.5.2-i386.iso
- sudo ./util/mkext3img OLPC-School-Server-0.5.2-i386.iso imgbuilder/anaconda-f9.ks
These notes are based on using XS 0.6d []. The image was uncompressed and written to a 8GB microSD card (class4). The microSD card was plugged into a XO using a SD adapter. Note that the XO had developer keys so that it could boot from the SD card. Also note, that the install was updated from the olpcxs-testing repo using 'yum --enablerepo=olpcxs-testing update'
We also installed [munin] ('yum install munin munin-node' followed by 'chkconfig --levels 345 munin-node on' and '/etc/init.d/munin-node start') to keep track of performance. The charts below were produced by Munin via rrdtool. Munin makes itself available at http://schoolserver/munin/
We did not set up any swap partitions and Squid was not turned on for this test.
Overall performance is acceptable for the 10 XOs we had in the pool, although bulk of the XOs were either routing to the Internet (eth0 via USB-to-Ethernet) or collaborating across XOs via Gabble. They were not using Moodle extensively. Initial Moodle access does tend to be slow. Performance may improve with a class 6 card (we did not have access to a class 6 card). Other points of interest are the point when we ran yum update, and when the XOs register and access the schoolserver link, leading to Moodle. There's also the corresponding CPU usage below.
From an end-user perspective, the XS-on-XO held up throughout the test (about 4 hours) while continuously serving 10 XOs. The users did not complain about any slowdown of the network, collaboration problems, etc. ejabberd did not fail throughout the test.