Customizing NAND images
This document describes how to create a jffs2 image from a laptop's internal NAND, producing an image that can be flashed onto a different XO. The laptop that is being backed up is the "host" laptop, and the laptop receiving the contents of the host laptop is the "target" laptop.
- Make the modifications on the host laptop that you want to be present in the generated image. If you've logged into Sugar and want the user to see the welcome/login prompt again, see the Section #Forcing Sugar to reprompt for name and colors. If you plan to use the image in laptops with different languages and keyboard layouts, you should delete also the file /.olpc-configured. This will force the system to run the olpc-configure script in the next boot.
- IMPORTANT: Make sure you delete these files in /etc/ssh:
ssh_host_dsa_key ssh_host_dsa_key.pub ssh_host_key ssh_host_key.pub ssh_host_rsa_key ssh_host_rsa_key.pub
- Insert a Windows-formatted (VFAT) USB disk into the host laptop, and reboot.
- At the "Type any key to interrupt automatic startup" key, press a key. At the "ok" prompt, type "save-nand disk:\nand.img" and press return. The contents of the NAND will be backed up to the nand.img file on the USB disk. The "ok" prompt will return when the copy has finished, and you can then power the laptop off with the power button.
- Since build 406, you need a checksum file to successfully upgrade the system. To create the CRC file see the Section #Creating CRC file.
- Move to the "target" laptop, and insert the USB disk. Again, interrupt at the prompt, and at the ok prompt type "copy-nand disk:\nand.img". This will copy from nand.img to the internal NAND. When back at the ok prompt, power off, remove the USB disk, and power on again to load from the new NAND image.
Sometimes you may want to define the default language for the system, either for use or while localizing.
The /etc/sysconfig/i18n file defines the LANG variable that Sugar will use.
Timezone information is stored in the file /etc/timezone. For example, the east coast of the US is "America/New_York". This name references files found in /usr/share/zoneinfo, that control the system's timezone and daylight savings time behavior.
Installing TrueType or OpenType Fonts
Either install as root prepackaged font package(s) from the Fedora repository as outlined below, or install the fonts in a subdirectory of /usr/share/fonts/ttf and run the fc-cache -f command afterwards.
To remove an activity from the build, delete the desired directory from: /usr/share/activities:
rm -r TamTam.activity (for example)
To add an activity, install it in this same directory.
If the manufacturing data does not match the keyboard you need, you can set the keyboard type.
To change the symbol mapping of the keyboard, follow the following steps:
- After the system has booted, press ctrl+alt+f1 (f1 is the same as the "mesh-view" key);
- Login in as root (no password required);
- Open the file /etc/X11/xorg.conf for editing (use vi or any editor you are comfortable with);
- In the first InputDevice Section do the following modifications:
- To change the default language, e.g., from English to Spanish:
- Modify XkbLayout Setting from "us" to "es" (use "pt" for Portuguese, "ng" for Nigerian language support, etc.);
- Add an XkbOptions Option with the value "olpc";
- To add a second language, e.g., English and Arabic:
- Modify XkbLayout Setting from "us" to "us,ara" (use "ru" for Cyrillic, "ur" for Urdu, "th" for Thai, etc.);
- Add an XkbOptions Option with the value "olpc2,olpc";
- To change the default language, e.g., from English to Spanish:
- Save and close the file;
- Either reboot the machine or restart X by issuing a "/sbin/telinit 3" command, followed by the "/sbin/telinit 5" command.
After you make the modifications, the two lines in xorg.conf should be similar to one of the following:
|l10n for spanish||l10n for english / arabic|
Section "InputDevice" Option "XkbLayout" "es" Option "XkbOptions" "olpc"
Section "InputDevice" Option "XkbLayout" "us,ara" Option "XkbOptions" "olpc2,olpc"
|After X is restarted, the default language will be Spanish (es).||After X is restarted, the default language will be English (us); you will be able to switch to Arabic (ara) using the key.|
Installing packages from the Fedora repositories using yum
Sugar is based off of Fedora and as such has a large amount of packages available to add to the base system. The tool used to do this is called yum. Because of memory constraints it is best to drop into run mode 3 which stops X. To do this log in as root either in the developer console or one of the virtual terminals and type this command:
X should exit and you should find yourself either at a login prompt or in the same virtual terminal. Log in as root if you are not already. To install or upgrade a package you simply use this command:
yum upgrade <package name>
To search for available packages you can use this command:
yum search <keyword>
More information about using yum with fedora can be found here.
Installing Flash, Java, MP3 codecs, MPEG4, patented codecs
These Restricted Formats have problems that makes it difficult or impossible for OLPC to preinstall, but you may be able and interested in deploying systems with these preinstalled.
(Note that the Adobe Flash plugin 184.108.40.206 is known to work and 220.127.116.11 is known not to work.)
Helix (Real) Media Player
The Helix media activity page covers installation of this activity and its associated codecs.
Forcing Sugar to reprompt for name and colors
You can always edit:
However, there may be times when you may want to force Sugar to prompt for a new name and colors as if with a new machine. You can do this by deleteing the configuration file and the SHH keys in the ./sugar/default directory.
rm /home/olpc/.sugar/default/config rm /home/olpc/.sugar/default/owner.key rm /home/olpc/.sugar/default/owner.key.pub
- The above process does not clean out the Journal data repository—the additional step of deleteing the directory /home/olpc/.sugar/default/datastore will empty the Journal;
rm -r /home/olpc/.sugar/default/datastore
- This process does force the generation of new keys, which will potentially have (an adverse) impact on access to backup files on the school server.
Creating CRC file
First, you need to download and compile pilgrim
git clone git://git.fedoraproject.org/git/pilgrim cd pilgrim/crcimg make
File:Crcimg.sh - Linux crcimg executable
After, you can from the command prompt create the crc from your custumized image
Output is in myfile.crc