Translations: French

Introduction

The custom installer is needed so that the network will work during the install. This allows a full Debian system to be installed over the network, not just a base system, as would otherwise be possible with the standard installer.

Overview

The exact process for mastering the image linked from DebianEeePC/HowTo/Install basically followed DebianInstaller/Modify/CustomKernel to build a Lenny installer. A few extra steps were required to include the atl2 module. The following instructions assume a sid build system. You may wish to prepare a sid chroot to do this using cdebootstrap or debootstrap so that your build system will not be 'tainted' by the installation of the kernel for the custom installer.

Automated build

The process is automated with the build-eeepc.sh script available at git://git.debian.org/git/debian-eeepc/installer.git web, though to make it work in a sid chroot, a few things are missing:

do_symlinks = Yes
do_initrd = Yes

apt-get update
apt-get install locales
dkpg-reconfigure locales

cp build-eeepc.sh sid/
chroot sid/
touch /etc/fstab
mount -t proc proc /proc
mount -t sysfs sys /sys

* and build:

./build-eeepc.sh

If all goes well, after a while test/debian-eeepc.img should be created.

If it doesn't go well, please contact us on the mailing list or via irc. We dont neccesarily keep the script constantly up to date, so if you notice errors, we would be happy to know.

Conclusion

It is a good idea to test the initial boot stages with qemu just to see if it works correctly without any very noticible glitches, then testing it by dd'ing to a usb or sd card.

DebianEeePC/HowTo/CustomInstaller (last edited 2008-05-12 14:28:29 by BenArmstrong)