New autoreinstallation scripts with activation support.

Bert Freudenberg bert at
Mon Jul 16 06:01:43 EDT 2007

So I admit to not reading your mail carefully at first but just  
followed the updated instructions at the Wiki. Notes follow:


Worked for me. After NAND flashing, the machine automatically  
proceeded to boot (I was at q2c18 already). I think formerly a note  
was shown to please remove the USB drive and power down? Anyway I  
ripped out the drive while the kernel was booting ... is that okay?

Additionally, "LEASES.XO" was generated on the USB drive. What data  
is in there? Should that file be kept secret? Isn't "*.xo" reserved  
for activity bundles? Or is the uppercase .XO significantly different  
form lowercase .xo? Anyway, I think this should be mentioned in the  


Then I wondered why I did to notices any "activation", and why there  
was no "/secure" directory after booting.

Finding nothing in the instructions, I read your mail again. Ah. Dumb  
me ;) Will boot again with drive plugged in ...


One thing that would make it a tiny bit simpler would be sym-linking  
the img and crc file to 'nandXYZ.img' and 'nandXYZ.crc' in the  
download directory at RedHat ... a little script could do that once  
for all previous versions and the build script for each new one.

- Bert -

On Jul 16, 2007, at 5:39 , C. Scott Ananian wrote:

> I've created new autoreinstallation scripts which create a stub
> activation lease on the usb key during the update process, so that the
> activation procedure can exercise the 'activate from usb key' code
> path on first boot.  The updated procedure is here:
> The new procedure doesn't require you to manually edit olpc.fth to use
> it for a different firmware version or build number: just put the new
> build or firmware in /boot and the upgrade script will use it.
> Please test the autoreinstallation process and let me know if you find
> problems.  Also verify that a file named 'keylist' is placed on your
> USB key by the autoreinstallation process.
>   --scott
> Chris: your upgrade procedure which backs up the users files in /home
> should be tweaked to also protect the files in /security to ensure
> that the activation lease isn't clobbered during the upgrade.

More information about the Devel mailing list