Talk:Customizing NAND images
If you want to create a new image from scratch, see Building custom images.
This is all useful information; it would be nice to collect a list of scripts people have written for parts of this customization that could turn into a config interface. 18.85.19.49 12:38, 3 July 2007 (EDT)
Patches gratefully accepted. --18.85.18.130 15:07, 3 July 2007 (EDT)
Article outdated
We here at Porto Alegre are using this procedure to create custom image files with local content. But we have notice the need of extras steps than those described in the article. For example, we have laptops with US keyboard and Brazilian keyboard, so we had to delete the /.olpc-configure file to ensure that the machine would run the olpc-configure script in the first boot. With the new crc verification, there is also the need to generate a new .crc file, since modification were made in the image. So, I think that this article needs to be updated. Juliano 19:50, 5 August 2007 (EDT)
To "customize" the XO
I thought this dialog from the devel list would be interesting to share, as it answers some FAQs:
> Because OLPC is sold to general public using "Give 1 Get 1" G1G1, is it possible to customize OLPC: > 1. Disable internal Flash Drive, and boot from external USB hard disk / external CD-ROM drive. > 2. Boot to console mode (svgalib). > 3. Install Fedora, Mandriva or other Linux/BSD distro, FreeDOS. Use TWM / IceWM windows manager. > Is the above ideas possible?
OLPC does not have a conventional BIOS, so any software that depends on one will not work.
3 is possible provided you replace the standard Linux kernel with one including the OLPC patch set. I've also been told that Minix works.
I doubt the BSDs already support our hardware, but wouldn't be hard. FreeDOS would be problematic because the OFW does not emulate BIOS services and does not provide 16bit support. But maybe you can get LinuxBIOS to boot from OFW and then you're done!
Several people booted regular Fedora 7 and Ubuntu Feisty off USB drives. I think the only change needed was installing the kernel package. The RPM is available from us, a dpkg should be easy to produce with the Debian kernel development tools.
When enough of our patches will be merged upstream, and the OLPC hardware gets more widely available, I'd expect the mainstream distros to offer out of the box OLPC support.
> Because OLPC is sold to general public using "Buy 2 Get 1" G1G1,
The answers below are unrelated to the fact that it is being sold.
> is it possible to customize OLPC:
XO-1 is the identifier for the hardware, OLPC is the identifier for the project.
> 1. Disable internal Flash Drive,
No. But if it did not contain the essential boot components (such as /boot/olpc.fth) it would be ignored, and so you would have the same net effect.
> and boot from external USB hard disk
Yes. The external USB storage would need to have the essential boot components (such as /boot/olpc.fth). This is how we load new versions at the moment.
> / external CD-ROM drive.
Don't know. A PC boot structure would not work, only the XO specific boot structure would work. I've not tested it, and I don't know if anyone has.
> 2. Boot to console mode (svgalib).
Not sure. I think not. Let us know how it goes, we're curious. The XO kernel has framebuffer support for the LCD. Suggest you use that instead. Try it in emulation now.
> 3. Install Fedora, Mandriva or other Linux/BSD distro, FreeDOS.
Only if those distributions add support for XO, or if you add the support yourself. For example we have a way to install Debian documented on the Wiki. As Bernardo has said, minimum capability would be the Linux kernel patched and built for XO. The kernel built for ordinary PC is not appropriate. Many services provided by a PC BIOS are not provided by the XO firmware.
> Use TWM / IceWM windows manager.
Yes, that works fine, once the barriers above are overcome.
> Is the above ideas possible?
Yes, with work. Let us know how you go. It isn't part of OLPC mission though, and now is not the time for us to concentrate on it.
