Tiny Core Linux/Reversion

From OLPC

Jump to: navigation, search

A procedure for reverting an XO with OLPC OS to pristine filesystem configuration, as if it had just been installed, using Tiny Core Linux.

On the reverted laptops, identity, registration, Journal, post-install activities, and all customisations are lost.

On the pristine laptop, customisations are kept, and passed to the reverted laptops.

Note: works for XO-1.5, XO-1.75, and XO-4, reverting the internal storage. For XO-1, requires an SD card, and reverts the filesystem on the SD card, leaving the internal storage unchanged.

Contents

Requirements

  • an XO to act as a server,
  • any number of XO to act as client to undergo reversion,
  • a Tiny Core Linux bootable USB drive (tested with the 2014-06-17 build, git hash 9a9e70c),
  • a wireless or wired network.

Setup for Server

xo-server
  • note the displayed IP address.

Setup for Clients

  • boot into Tiny Core Linux,
  • remove the USB drive,
  • configure wireless,
  • restore the filesystem to pristine state:
xo-revert ${IP}
(where ${IP} is the IP address or host name of the server as displayed above)
  • reboot:
reboot

Ad-hoc Wireless

The above procedure depends on a wireless access point. If one is not available, an ad-hoc network may be set up, but this requires more care to set unique IP addresses. In place of the method above:

iwconfig eth0 mode ad-hoc channel 1 essid pq
ifconfig eth0 1.1.1.1

Change the last digit for each laptop added to the ad-hoc network.

The additional time cost of doing this begins to approach the cost of fs-update, so investment in a remastered USB drive with ad-hoc scripts may be more appropriate.

Timings

Reversion of three XO-4 that had been booted into 13.2.1 cost about 50s each as compared to 7m using fs-update. This increased to 1m 42s when done all at once, due to network and server contention.

Reversion of three XO-1.5 that had been booted once into 10.1.3 os860 cost 1m 45s each as compared to 17m using fs-update and over half an hour using NANDblaster.

Reversion of an XO-1 SD card that had been booted once into 13.2.1 cost 1m 20s compared to a substantial time using fs-update.

Optimisation

Using /versions/pristine

Since a local pristine copy of the build exists, it can be used first to reduce the data required:

rsync --archive --delete \
    /mnt/mmcblk0p2/versions/pristine/860 \
    /mnt/mmcblk0p2/versions/run/

However, since /home/olpc is not present in this pristine copy, the full rsync is still required. In the test case, the local copy cost 16s, followed by the full rsync at cost of 1m, a saving of about 15s.

Using a non-XO server

An XO as a server lacks memory and bandwidth. A larger server can be used.

  • copy the filesystem from the pristine laptop to a server, by running these commands on the server:
sudo mkdir /tmp/p1 /tmp/p2
sudo rsync -avP rsync://$IP/p1 /tmp/p1
sudo rsync -avP rsync://$IP/p2 /tmp/p2
  • set up an rsyncd.conf or merge with an existing rsyncd.conf,
cat << EOF > /tmp/rsyncd.conf
[p1]
        path = /tmp/p1
        uid = root
        gid = root
[p2]
        path = /tmp/p2
        uid = root
        gid = root
EOF
  • if rsync is not running, start the server
sudo rsync --daemon --config /tmp/rsyncd.conf
  • note the IP address of the server,
  • use xo-revert on each laptop, specifying the IP address of the server.

Not for Upgrades

Do not use this technique for operating system upgrades where the change is significant; especially if the operating system build number changes. It is faster to use fs-update. As an example, 10.1.2 to 10.1.3 takes three hours, because of the amount of filesystem change. The delay is due to the filesystem writes to storage; the wireless is mostly idle, transferring only 993 MB over the three hours.

Personal tools
  • Log in
  • Login with OpenID
About OLPC
About the laptop
About the tablet
Projects
OLPC wiki
Toolbox
In other languages