fai-3.4.8ubuntu5/0000775000000000000000000000000012106070335010502 5ustar fai-3.4.8ubuntu5/VERSION0000664000000000000000000000025711562212376011566 0ustar VERSIONSTRING="$(shell perl -e 'while (<>) { /^(\S+).*\((.*)\)/ and print uc($$1) . " $$2, "; if (/ --.*,\s+(.*)\s\d+:/) { print "$$1" ; exit } }' $(SRCDIR)debian/changelog)" fai-3.4.8ubuntu5/conf/0000775000000000000000000000000011711761027011435 5ustar fai-3.4.8ubuntu5/conf/grub.cfg0000664000000000000000000000410411562212376013056 0ustar ## grub2 configuration set default=4 set timeout=20 if loadfont /boot/grub/ascii.pf2 ; then insmod png set gfxmode=640x480 insmod gfxterm insmod vbe terminal_output gfxterm fi if background_image /boot/grub/fai.png ; then set color_normal=black/black set color_highlight=red/black set menu_color_normal=black/black set menu_color_highlight=black/yellow else set menu_color_normal=white/black set menu_color_highlight=black/yellow fi # make sure we can access partitions insmod part_msdos insmod part_gpt if [ ${iso_path} ] ; then set loopback="findiso=${iso_path}" fi menuentry "+------------------------------------------------------+" { set gfxpayload=1024x768 linux /boot/vmlinuz boot=live } menuentry "| FAI-CD (c) Thomas Lange, lange@debian.org |" { set gfxpayload=1024x768 linux /boot/vmlinuz boot=live } menuentry "| _VERSIONSTRING_ |" { set gfxpayload=1024x768 linux /boot/vmlinuz boot=live } menuentry "+------------------------------------------------------+" { set gfxpayload=1024x768 linux /boot/vmlinuz boot=live } menuentry "Fully Automatic Installation - demohost (pw: installme)" { set gfxpayload=1024x768 linux /boot/vmlinuz boot=live FAI_FLAGS="verbose,createvt" FAI_ACTION=install hostname=demohost initrd /boot/initrd.img } menuentry "Fully Automatic Installation with GNOME (pw: installme)" { set gfxpayload=1024x768 linux /boot/vmlinuz boot=live FAI_FLAGS="verbose,createvt" FAI_ACTION=install hostname=gnomehost initrd /boot/initrd.img } menuentry "Fully Automatic Installation - faiserver (pw: installme)" { set gfxpayload=1024x768 linux /boot/vmlinuz boot=live FAI_FLAGS="verbose,createvt" FAI_ACTION=install hostname=faiserver initrd /boot/initrd.img } menuentry "FAI rescue system, no installation" { set gfxpayload=1024x768 linux /boot/vmlinuz boot=live FAI_FLAGS="verbose,createvt" FAI_ACTION=sysinfo hostname=demohost initrd /boot/initrd.img } menuentry "Boot OS of first partition on first disk" { set root=(hd0,1) chainloader +1 } fai-3.4.8ubuntu5/conf/make-fai-nfsroot.conf0000664000000000000000000000263411711760251015451 0ustar # these variables are only used by make-fai-nfsroot(8) # here you can use also variables defined in fai.conf # directory on the install server where the nfsroot for FAI is # created, approx size: 390MB, also defined in bootptab or dhcp.conf NFSROOT=/srv/fai/nfsroot # TFTP directory for FAI files TFTPROOT=/srv/tftp/fai # location of the configuration space on the install server FAI_CONFIGDIR=/srv/fai/config # Add a line for mirrorhost and installserver when DNS is not available # on the clients. This line(s) will be added to $nfsroot/etc/hosts. #NFSROOT_ETC_HOSTS="192.168.1.250 yourinstallserver" # Parameter for debootstrap: " " FAI_DEBOOTSTRAP="squeeze http://cdn.debian.net/debian" # the encrypted (with md5 or crypt) root password on all install clients during # installation process; used when log in via ssh; default pw is: fai FAI_ROOTPW='$1$kBnWcO.E$djxB128U7dMkrltJHPf6d1' # location of a identity.pub file; this user can log to the install # clients in as root without a password; only useful with FAI_FLAGS="sshd" #SSH_IDENTITY=/home/admin/.ssh/identity.pub # directory of hooks to be sourced at the end of make-fai-nfsroot, # i.e they have to be shell scripts. #NFSROOT_HOOKS=/etc/fai/nfsroot-hooks/ # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # following lines should be read only for most of you FAI_DEBOOTSTRAP_OPTS="--exclude=info,dhcp-client --include=aptitude" fai-3.4.8ubuntu5/conf/NFSROOT0000664000000000000000000000172311711761023012511 0ustar # package list for creating the NFSROOT PACKAGES aptitude nfs-common fai-nfsroot module-init-tools ssh rdate lshw portmap rsync lftp less dump reiserfsprogs e2fsprogs usbutils hwinfo psmisc pciutils hdparm smartmontools parted mdadm lvm2 dnsutils ntpdate dosfstools jove xfsprogs xfsdump procinfo dialog discover console-setup console-common iproute udev subversion liblinux-lvm-perl # needed for the simple examples cfengine2 libapt-pkg-perl # you should not edit the lines below # architecture dependend list of packages that are installed PACKAGES aptitude I386 grub-pc lilo read-edid linux-image-server # packages for lenny: # linux-image-486 aufs-modules-2.6-486 PACKAGES aptitude AMD64 grub-pc lilo linux-image-server # packages for lenny: # linux-image-2.6-amd64 aufs-modules-2.6-amd64 PACKAGES aptitude IA64 elilo gnu-efi efibootmgr PACKAGES aptitude SPARC silo sparc-utils PACKAGES aptitude ALPHA aboot PACKAGES aptitude POWERPC linux-image-2.6-powerpc yaboot fai-3.4.8ubuntu5/conf/apt.conf0000664000000000000000000000074511562212376013100 0ustar // This file is used in the chroot environment from install_packages // (called by rcS_fai) // Options for apt-get for FAI APT { // Options for apt-get Get { Assume-Yes "true"; Fix-Missing "true"; Show-Upgraded "true"; Purge "true"; // really purge! Also removes config files List-Cleanup "true"; ReInstall "false"; }; }; DPkg { Options { "--abort-after=4711"; // a magic number in cologne ;-) "--force-confdef"; } }; fai-3.4.8ubuntu5/conf/menu.lst.boot-only0000664000000000000000000000153511562212376015054 0ustar # grub menu.lst for fai-cd # Boot automatically after some secs. timeout 30 color light-gray/black light-gray/red default 6 title | root (cd) title +------------------------------------------------------+ root (cd) title | FAI-CD (c) Thomas Lange, lange@debian.org | root (cd) title | boot-only CD _VERSIONSTRING_ | root (cd) title +------------------------------------------------------+ root (cd) title | root (cd) title | title boot from local disk rootnoverify (hd0) chainloader +1 title Fully Automatic Installation kernel /boot/vmlinuz root=/dev/nfs _NFSROOT_ boot=live FAI_FLAGS="verbose,sshd,createvt" FAI_ACTION=install initrd /boot/initrd.img title FAI rescue system, no installation kernel /boot/vmlinuz root=/dev/nfs _NFSROOT_ boot=live FAI_FLAGS="verbose,sshd,createvt" FAI_ACTION=sysinfo initrd /boot/initrd.img fai-3.4.8ubuntu5/conf/live.conf0000664000000000000000000000146111562212376013247 0ustar # /etc/live.conf - configuration file for live-initramfs(7) export BUILD_SYSTEM="Debian" export UNIONTYPE="aufs" export NOAUTOLOGIN="Yes" export NOFASTBOOT="Yes" export SELINUX_INIT="No" export NOSUDO="Yes" export NOUSER="Yes" export NOXAUTOCONFIG="Yes" export NOFSTAB="Yes" export NOHOSTS="Yes" export NOACCESSIBILITY="Yes" export NOAPPARMOR="Yes" export NOAPTCDROM="Yes" export NOCONSOLEKEYBOARD="Yes" export NOKPERSONALIZER="Yes" export NOKWALLET="Yes" export NOLANGUAGESELECTOR="Yes" export NOLOCALES="Yes" export NONETWORKING="Yes" export NOPERSISTENT="Yes" export NOPOWERMANAGEMENT="Yes" export NOPRESEED="Yes" export NOPROGRAMCRASHES="Yes" export NORESTRICTEDMANAGER="Yes" export NOTIMEZONE="Yes" export NOUPDATENOTIFIER="Yes" export NOXAUTOLOGIN="Yes" export NOXSCREENSAVER="Yes" export NOGNOMEPANEL="Yes" fai-3.4.8ubuntu5/conf/menu.lst0000664000000000000000000000235711562212376013136 0ustar # grub menu.lst for fai-cd # Boot automatically after some secs. timeout 30 color light-gray/black light-gray/red default 6 title | root (cd) title +------------------------------------------------------+ root (cd) title | FAI-CD (c) Thomas Lange, lange@debian.org | root (cd) title | _VERSIONSTRING_ | root (cd) title +------------------------------------------------------+ root (cd) title | root (cd) title | title boot from local disk rootnoverify (hd0) chainloader +1 title Fully Automatic Installation - demohost (pw: installme) password installme kernel /boot/vmlinuz boot=live FAI_FLAGS="verbose,createvt" FAI_ACTION=install hostname=demohost initrd /boot/initrd.img title Fully Automatic Installation with GNOME (pw: installme) password installme kernel /boot/vmlinuz boot=live FAI_FLAGS="verbose,createvt" FAI_ACTION=install hostname=gnomehost initrd /boot/initrd.img title Fully Automatic Installation - faiserver (pw: installme) password installme kernel /boot/vmlinuz boot=live FAI_FLAGS="verbose,createvt" FAI_ACTION=install hostname=faiserver initrd /boot/initrd.img title FAI rescue system, no installation kernel /boot/vmlinuz boot=live FAI_FLAGS="verbose,createvt" FAI_ACTION=sysinfo hostname=demohost initrd /boot/initrd.img fai-3.4.8ubuntu5/conf/fai.conf0000664000000000000000000000271011562212376013045 0ustar # $Id$ # /etc/fai/fai.conf -- configuration for FAI (Fully Automatic Installation) # how to access the fai config space # If undefined here, make-fai-nfsroot/fai-setup will use default value # nfs:///$FAI_CONFIGDIR # supported URL-types: nfs, file, cvs, cvs+ssh, svn+file, svn+http, # git, git+http, hg+http, tarball via http #FAI_CONFIG_SRC=nfs://yourservername/path/to/config/space # LOGUSER: an account on the install server which saves all log-files # and which can change the kernel that is booted via network. # Configure .rhosts for this account and PAM, so that root can log in # from all install clients without password. This account should have # write permissions for /srv/tftp/fai. For example, you can use write # permissions for the group linuxadm. chgrp linuxadm /srv/tftp/fai;chmod # g+w /srv/tftp/fai. If the variable is undefined, this feature is disabled. # Define it, to enable it, eg. LOGUSER=fai LOGUSER= # set protocol type for saving logs. Values: ssh, rsh, ftp FAI_LOGPROTO=ssh # Access to Debian mirror via NFS mounted directory # If FAI_DEBMIRROR is defined, install clients mount it to $MNTPOINT #FAI_DEBMIRROR=yournfs debianmirror:/path/to/debianmirror # The following variables are read only for almost every user. # Do not change them unless you know what you are doing! # mount point where the mirror will be mounted MNTPOINT=/media/mirror # the local configuration directory on the install client FAI=/var/lib/fai/config fai-3.4.8ubuntu5/conf/fai_modules_off0000664000000000000000000000104611562212376014504 0ustar # turn error messages of modprobe off alias block-major-8 off alias block-major-13 off alias block-major-22 off alias block-major-33 off alias block-major-34 off alias block-major-36 off alias block-major-48 off alias block-major-49 off alias block-major-50 off alias block-major-51 off alias block-major-52 off alias block-major-53 off alias block-major-54 off alias block-major-55 off alias block-major-72 off alias block-major-73 off alias block-major-104 off alias block-major-105 off alias net-pf-10 off alias net-pf-11 off alias net-pf-18 off fai-3.4.8ubuntu5/conf/upstart-fai.conf0000664000000000000000000000024611562212376014547 0ustar # fai - start the fully automatic installation description "start fully automatic installation" start on local-filesystems console output task exec /usr/sbin/fai fai-3.4.8ubuntu5/conf/dhclient-fai.conf0000664000000000000000000000042311562212376014634 0ustar # $Id$ # fai configuration for dhclient v3 request subnet-mask, domain-name-servers, domain-name, host-name, routers, time-servers, ntp-servers, nis-domain, nis-servers, tftp-server-name; send dhcp-max-message-size 2048; timeout 30; retry 2; initial-interval 1; fai-3.4.8ubuntu5/conf/sources.list0000664000000000000000000000075011711756352014024 0ustar # These lines should work for many sites # A more comprehensive example is at /usr/share/doc/fai-doc/examples/etc deb http://archive.ubuntu.com/ubuntu precise main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu precise-security main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu precise-updates main restricted universe multiverse # repository that may contain newer fai packages for squeeze #deb http://fai-project.org/download squeeze koeln fai-3.4.8ubuntu5/THANKS0000664000000000000000000000455511562212376011436 0ustar These people helped to improve FAI by submitting code, manuals, bug reports, patches or good suggestions: Jason Aten jaten@ucla.edu Sune Rastad Bahn srb@dmi.dk Daniel Baumann daniel@debian.org Diego Biurrun diego@biurrun.de Phil Biondi biondi@cartel-securite.fr Julien BLACHE jblache@debian.org Frédéric Boiteux fboiteux@prosodie.com Waldemar Brodkorb fai@waldemar-brodkorb.de Tobias Burnus tobias.burnus@physik.fu-berlin.de Luk Claes luk.claes@ugent.be Bruce Edge bedge@troikanetworks.com Jonas Eriksson zqad@hpc2n.umu.se Era Eriksson era@iki.fi Stephane Fritsch stephane.fritsch@rte-france.com Mattias Gaertner gaertner@informatik.uni-koeln.de Sébastien Gallet sgallet@ibourgogne.net Thomas Gebhardt gebhardt@hrz.uni-marburg.de Sergio Gelato Sergio.Gelato@astro.su.se Niklaus Giger ngiger@mus.ch Henning Glawe glaweh@physik.fu-berlin.de James Golovich james@wwnet.net Constantin Hellweg hellweg@informatik.uni-koeln.de Sebastian Hetze s.hetze@linux-ag.com Jürgen Kahnert Juergen.Kahnert@desy.de Derrick Karpo derrick_karpo@intuit.com Christian Kern kernch@in.tum.de Ronan Keryell Ronan.Keryell@enst-bretagne.fr Christoffer Kugg kugghjul@gmail.com Felix Kühling fxkuehl@gmx.de Holger Levsen holger@layer-acht.org Paul Lussier p.lussier@comcast.net Marc Martinez lastxit+fai@technogeeks.org Eric Mumpower nocturne@permabit.com Riccardo Murri murri@dmmm.uniroma1.it Florian Möllers floria.moellers@jpberlin.de Paul Nijjar pnijjar@utm.utoronto.ca Ulrike Nitzsche U.Nitzsche@ifw-dresden.de Darshaka Pathirana dpat@syn-net.org Raphaël Pinson raphink@ubuntu.com Thomas Pöhnitzsch thpo@foobar-cpa.de Robin Powell rpowell@looksmart.net Michael Prokop mika@grml.org Ake Sandgren Ake.Sandgren@hpc2n.umu.se Michal Svamberg svamberg@civ.zcu.cz Timo Schnibbe Timo.Schnibbe@bertelsmann.de Andreas Schockenhoff asc@gmx.li Ulrich Scholler scholler@fnb.tu-darmstadt.de Andreas Schuldei andreas@debian.org Martin Schulte msfai@guug.de Andreas Sindermann sinder@thp.Uni-Koeln.DE Henning Sprang henning_sprang@gmx.net Geert Stappers Geert.Stappers@xs4all.nl Michael Tautschnig mt@debian.org Arto Teras arto.teras@hip.fi Björn Torkelsson torkel@pdc.kth.se Diane Trout diane@caltech.edu Colin Tuckley colintu@gmail.com Chad Walstrom chad@debian.org Ingo Wichmann iw@linuxhotel.de Richard Wonka Richard.Wonka@googlemail.com Niall Young niall@chime.net.au Alexander Zangerl az@bond.edu.au fai-3.4.8ubuntu5/doc/0000775000000000000000000000000011562213321011246 5ustar fai-3.4.8ubuntu5/doc/QUESTIONNAIRE0000664000000000000000000000403411562212376013231 0ustar FAI QUESTIONNAIRE ----------------- http://fai-project.org/questionnaire last edited: november 5, 2010 I'm very interested in your experiences with fai, bug reports, new ideas,... Please send this questionnaire to fai@fai-project.org All replies to this questionnaire are available at http://fai-project.org/reports thanks in advance Thomas Lange ---------------------------------------------------------------- How many hosts have you installed using fai? Which version of fai are you using? Which version are you using as your install kernel? (eg.: plain Debian kernel) (eg.: custom build kernel 2.6) Which types of hosts are you installing with fai? (eg.: desktops, cluster nodes, notebooks, web server, mail server,...) How do you boot your hosts? via network (PXE, DHCP): using FAI-CD: from USB stick: Does the default install kernel recognize all your hardware? Which drivers are missing? Do you manage your configuration space under version control? How big is your config space (Mbytes, # of files)? cd (/usr/local/share/fai by default) du -sh --exclude=.svn --exclude=basefiles find ! -type d | grep -v svn|grep -v cvs|wc -l How many files do you have in ../config/files? find files ! -type d | grep -v svn|grep -v cvs|wc -l What types of scripts are you using for local customization? (shell, perl, cfengine, puppet, expect,...) What is the business of your company/organization (please add name and link)? You can also add some words, how you are using FAI in your company. Additional comments: Do you have some nice pictures of your installation? I would like to mention your name or email address and your company's name on the FAI web page where I like to collect all questionnaires of the FAI users. May I publish your name? May I publish your email (it will be obfuscated to fool the spamers)? May I publish the name of your company? May I publish the logo of your company? May I publish your pictures? ---------------------------------------------------------------- fai-3.4.8ubuntu5/doc/includes/0000775000000000000000000000000011562212376013065 5ustar fai-3.4.8ubuntu5/doc/includes/faisetup.txt0000664000000000000000000000574511562212376015461 0ustar ---- faiserver[~]# fai-setup -v Using configuration files from /etc/fai Creating FAI nfsroot in /srv/fai/nfsroot/live/filesystem.dir. By default it needs more than 380 MBytes disk space. This may take a long time. Creating base system using debootstrap version 1.0.10lenny1 Calling debootstrap lenny /srv/fai/nfsroot/live/filesystem.dir http://cdn.debian.net/debian . Creating base.tgz . Upgrading /srv/fai/nfsroot/live/filesystem.dir . nfs-common fai-nfsroot module-init-tools ssh rdate lshw portmap rsync lftp less dump reiserfsprogs e2fsprogs usbutils hwinfo psmisc pciutils hdparm smartmontools parted mdadm lvm2 dnsutils ntpdate dosfstools jove xfsprogs xfsdump procinfo dialog discover console-tools console-common iproute udev subversion liblinux-lvm-perl cfengine2 libapt-pkg-perl grub lilo read-edid linux-image-486 install_packages: reading config files from directory /etc/fai install_packages: read config file NFSROOT . . `/etc/fai/NFSROOT' -> `/srv/fai/nfsroot/live/filesystem.dir/etc/fai/NFSROOT' `/etc/fai/apt' -> `/srv/fai/nfsroot/live/filesystem.dir/etc/fai/apt' `/etc/fai/apt/sources.list' -> `/srv/fai/nfsroot/live/filesystem.dir/etc/fai/apt/sources.list' `/etc/fai/fai.conf' -> `/srv/fai/nfsroot/live/filesystem.dir/etc/fai/fai.conf' `/etc/fai/live.conf' -> `/srv/fai/nfsroot/live/filesystem.dir/etc/fai/live.conf' `/etc/fai/make-fai-nfsroot.conf' -> `/srv/fai/nfsroot/live/filesystem.dir/etc/fai/make-fai-nfsroot.conf' `/etc/fai/menu.lst' -> `/srv/fai/nfsroot/live/filesystem.dir/etc/fai/menu.lst' Shadow passwords are now on. Removing `local diversion of /usr/sbin/update-initramfs to /usr/sbin/update-initramfs.distrib' update-initramfs: Generating /boot/initrd.img-2.6.26-2-486 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays. W: mdadm: failed to auto-generate temporary mdadm.conf file. W: mdadm: no configuration file available. `/srv/fai/nfsroot/live/filesystem.dir/boot/vmlinuz-2.6.26-2-486' -> `/srv/tftp/fai/vmlinuz-2.6.26-2-486' `/srv/fai/nfsroot/live/filesystem.dir/boot/initrd.img-2.6.26-2-486' -> `/srv/tftp/fai/initrd.img-2.6.26-2-486' DHCP environment prepared. If you want to use it, you have to enable the dhcpd and the tftp-hpa daemon. Removing `local diversion of /sbin/discover-modprobe to /sbin/discover-modprobe.distrib' make-fai-nfsroot finished properly. <=== * No diversion `any diversion of /sbin/discover-modprobe', none removed Log file written to /var/log/fai/make-fai-nfsroot.log Re-exporting directories for NFS kernel daemon.... You have no FAI configuration space yet. Copy the simple examples with: cp -a /usr/share/doc/fai-doc/examples/simple/* /srv/fai/config Then change the configuration files to meet your local needs. Please don't forget to fill out the FAI questionnaire after you've finished your project with FAI. FAI setup finished. <=== * Log file written to /var/log/fai/fai-setup.log ---- fai-3.4.8ubuntu5/doc/includes/bootlog.txt0000664000000000000000000000053411562212376015275 0ustar ---- # cat /tmp/fai/boot.log netdevices_all="eth0" netdevices_up="eth0" netdevices="eth0" BROADCAST='192.168.1.255' DOMAIN='localdomain' DNSSRVS='192.168.1.1' DNSSRVS_1='192.168.1.1' HOSTNAME='demohost' IPADDR='192.168.1.12' NETWORK='192.168.1.0' GATEWAYS='192.168.1.250' GATEWAYS_1='192.168.1.250' SERVER='faiserver' NETMASK='255.255.255.0' ---- fai-3.4.8ubuntu5/doc/includes/bootexample.txt0000664000000000000000000000636211562212376016154 0ustar ---- Managed PC Boot Agent (MBA) v4.00 . . Pre-boot eXecution Environment (PXE) v2.00 . . DHCP MAC ADDR: 00 04 75 74 6E 4A DHCP.../ CLIENT IP: 192.168.1.12 MASK: 255.255.255.0 DHCP IP: 192.168.1.250 GATEWAY IP: 192.168.1.254 PXELINUX 3.71 (Debian-2008-09-06) Copyright (C) 1994-2008 H. Peter Anvin UNDI data segment at: 0009D740 UNDI data segment size: 3284 UNDI code segment at: 00090000 UNDI code segment size: 24C0 PXE entry point found (we hope) at 9D74:00F6 My Ip address seems to be C0A801C0 192.168.1.12 ip=192.168.1.12:192.168.1.250:192.168.1.254:255.255.255.0 TFTP prefix: fai/ Trying to load pxelinux.cfg/01-00-04-75-74-6e-4a Trying to load pxelinux.cfg/C0A801C0 Loading vmlinuz-2.6.26-2-486.....................Ready. Loading initrd.img-2.6.26-2-486.................................. Ready Uncompressing Linux... OK, booting the Kernel. Linux version 2.6.26-2-486 (Debian 2.6.26-4) . . Done. Mounting root file system..... eth0: link up RPC: Registered upd transport module. RPC: Registered tcp transport module. aufs 20080714 . . Begin: Running /scripts/live-premount ... done. IP-Config: eth0 hardware address 00:0c:29:c9:81:38 mtu 1500 DHCP RARP IP-Config: eth0 guessed broadcast address 192.168.1.255 IP-Config: eth0 complete (from 192.168.1.250): address: 192.168.1.12 broadcast: 192.168.1.255 netmask: 255.255.255.0 gateway: 192.168.1.254 dns0 : 192.168.1.250 dns1 : 192.168.8.9 host : demohost domain : informatik.uni-koeln.de rootserver: 192.168.1.250 rootpath: filename : pxelinux.0 Begin: Trying netboot from 192.168.1.250:/srv/fai/nfsroot ... Begin: Trying nfsmount -o nolock -o ro 192.168.1.250:/srv/fai/nfsroot /live/image ... . . ------------------------------------------------- Fully Automatic Installation - FAI FAI 3.3, 03 Nov 2009 (c) 1999-2009 Thomas Lange ------------------------------------------------- Calling task_confdir Kernel parameters: initrd=initrd.img-2.6.26-2-486 ip=dhcp root=/dev/nfs nfsroot=/srv/fai/nfsroot \ boot=live FAI_FLAGS=verbose,sshd,createvt FAI_ACTION=install \ FAI_CONFIG_SRC=nfs://kueppers/srv/fai/config BOOT_IMAGE=vmlinuz-2.6.26-2-486 Reading /tmp/fai/boot.log FAI_FLAGS: verbose sshd createvt FAI_CONFIG_SRC is set to nfs://kueppers/srv/fai/config Configuration space kueppers:/srv/fai/config mounted to /var/lib/fai/config Calling task_setup Calling task_setup FAI_FLAGS: verbose sshd createvt Fri Oct 30 14:34:37 UTC 2009 30 Oct 14:34:37 ntpdate[3279]: step time server 134.95.4.129 offset 5.691554 sec Press ctrl-c to interrupt FAI and to get a shell Calling task_defclass fai-class: Defining classes. Executing /var/lib/fai/config/class/10-base-classes. 10-base-classes OK. Executing /var/lib/fai/config/class/20-hwdetect.source. . . 50-host-classes OK. List of all classes: DEFAULT LINUX I386 FAIBASE DHCPC DEMO GRUB demohost LAST Calling task_defvar Executing FAIBASE.var ++ FAI_ALLOW_UNSIGNED=1 ++ CONSOLEFONT= ++ KEYMAP=us-latin1 ++ UTC=yes ++ TIMEZONE=Europe/Berlin ++ ROOTPW='$1$kBnWcO.E$djxB128U7dMkrltJHPf6d1' ++ STOP_ON_ERROR=700 ++ USE_SETUP_STORAGE=1 Loading keymap(s) us-latin1 ...done. Calling task_action FAI_ACTION: install Performing FAI installation. All data may be overwritten! ---- fai-3.4.8ubuntu5/doc/error-levels0000664000000000000000000000054611562212376013630 0ustar error codes used by subroutine task_error: normal or info messages: 1xx, 2xx warnings: 3xx, 4xx minor errors: 5xx, 6xx errors: 7xx, 8xx The faimond-gui has 4 icons for the error levels. The variable $STOP_ON_ERROR (default 700) will define that return codes that are greater the this value will stop the installation. fai-3.4.8ubuntu5/doc/pixmaps.svg0000664000000000000000000015026011562212376013465 0ustar image/svg+xml Pixmaps for faimond fai-3.4.8ubuntu5/doc/FAQ0000664000000000000000000000373611562212363011616 0ustar Sat, 11 Mar 2006 17:19:05 +0100 This is a very short FAQ. Please get involved and feel free to send patches after your questions have been answered on the FAI mailing list! Q: I'm new to FAI. How should I start ? A: Read the FAI guide and this FAQ. Start with the simple examples FAI_CONFIGDIR. Install the stable distribution on your first clients! (See next question.) Q: I try to install testing or sid (unstable) and something goes wrong. A: testing and sid change every day. So it's possible that your problems are solved today or tomorrow. You should try again. It's recommendable to use a local mirror and freeze it when you found a working install. But we also recommend to use stable and local backport repositories whenever possible. Q: Where do I find the FAI mailing list ? A: There is a section "Mailing list" on the FAI homepage at http://fai-project.org Please use your favorite search engine to search for your questions before posting to the list! Also don't post complete logs. Most times it's sufficient to describe the setup (which version of fai, which version of debian on the fai server and which version to be installed with fai) and to post the part of the log(s) where the error occurs. Or provide logfiles on a webserver and post a link. Q: Is there an online FAI FAQ ? A: No, but we have a FAI Wiki. http://wiki.fai-project.org/ Q: I cannot login via ssh to my install client(s) anymore. It used to work but stopped working suddenly. Example: > ssh root@demohost @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! A: After you have reinstalled FAI on your server a new ssh host key is generated. This also happens when you call "fai-setup" or "make-fai-nfsroot". Remove the relevant line from ~/.ssh/known_hosts and try again. fai-3.4.8ubuntu5/doc/links.html0000664000000000000000000000260311562212376013266 0ustar

FAI links



  fai-3.4.8ubuntu5/doc/fai-guide.txt0000664000000000000000000031616311562212376013664 0ustar //// -*- Doc -*- //// FAI Guide (Fully Automatic Installation) ======================================== Thomas Lange 3.0.5, Mon, 08 Nov 2010 15:45:36 +0100 :faiver: 3.3 :nfsrootsize: 380 :mirrorsize: 22 //// => _ ' => + =>` ` (wie manref) => _ //// .Abstract FAI is a non-interactive system to install, customize and manage Linux systems and software configurations on computers as well as virtual machines and chroot environments, from small networks to large infrastructures and clusters. This manual describes the Fully Automatic Installation package. This includes the installation of the package, planning and creating of the configuration and how to deal with errors. (c) 2000-2010 Thomas Lange (c) 2005 Henning Glawe .Copyright This manual is free software; you may redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. This is distributed in the hope that it will be useful, but *without any warranty*; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details. A copy of the GNU General Public License is available as '/usr/share/common-licenses/GPL' in the Debian GNU/Linux distribution or on the World Wide Web at http://www.gnu.org/copyleft/gpl.html[the GNU website] You can also obtain it by writing to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA == [[introduction]]Introduction //// -MT: general comments: - dirinstall is only mentioned at the end - mailinglists, IRC channel should be mentioned //// === [[availability]]Availability Homepage:: http://fai-project.org FAI wiki:: http://wiki.fai-project.org Download:: http://fai-project.org/download Entry for 'sources.list':: `http://fai-project.org/download lenny koeln` Mailing list:: https://lists.uni-koeln.de/mailman/listinfo/linux-fai Feedback:: Send feedback and comment to mailto:fai@fai-project.org[] or to the mailing list. Bugs:: Use the Debian bug tracking system (BTS) http://bugs.debian.org for reporting errors. User visible changes:: http://fai-project.org/NEWS Source tree:: You can access the subversion repository containing the newest developer version of FAI using the following commands `svn co svn://svn.debian.org/svn/fai/trunk fai` Source tree via http:: http://svn.debian.org/wsvn/fai/ Now read this manual, then enjoy the fully automatic installation and your saved time. === [[motivation]]Motivation Have you ever performed identical installations of an operating system several times? Would you like to be able to install a Linux cluster with dozens of nodes single handedly? Repeating the same task again and again is boring -- and will surely lead to errors. Also a whole lot of time could be saved if the installations were done automatically. An installation process with manual interaction does not scale. But clusters have the habit of growing over the years. Think long-term rather than planning just a few months into the future. In 1999, I had to perform an installation of a Linux cluster with one server and 16 clients. Since I had much experience doing automatic installations of Solaris operating systems on SUN SPARC hardware, the idea to build an automatic installation for Debian was born. Solaris has an automatic installation feature called JumpStart footnote:[Solaris 8 Advanced Installation Guide at http://docs.sun.com]. In conjunction with the auto-install scripts from Casper Dik footnote:[http://www.science.uva.nl/pub/solaris/auto-install], I could save a lot of time not only for every new SUN computer, but also for re-installation of existing workstations. For example, I had to build a temporary LAN with four SUN workstations for a conference, which lasted only a few days. I took these workstations out of our normal research network and set up a new installation for the conference. When it was over, I simply integrated the workstations back into the research network, rebooted just once, and after half an hour, everything was up and running as before. The configuration of all workstations was exactly the same as before the conference, because everything was performed by the same installation process. I also used the automatic installation for reinstalling a workstation after a damaged hard disk had been replaced. It took two weeks until I received the new hard disk but only a few minutes after the new disk was installed, the workstation was running as before. And this is why I chose to adapt this technique to a PC cluster running Linux. === [[overview]]Overview and concepts FAI is a non-interactive system to install, customize and manage Linux systems and software configurations on computers as well as virtual machines and chroot environments, from small networks to large infrastructures and clusters. You can take one or more virgin PCs, turn on the power and after a few minutes Linux is installed, configured and running on the whole cluster, without any interaction necessary. Thus, it's a scalable method for installing and updating a cluster unattended with little effort involved. FAI uses the Debian GNU/Linux distribution and a collection of shell and Perl scripts for the installation process. Changes to the configuration files of the operating system can be made by cfengine, shell, Perl and expect scripts. FAI's target group are system administrators who have to install Linux onto one or even hundreds of computers. Because it's a general purpose installation tool, it can be used for installing a Beowulf cluster, a rendering farm or a Linux laboratory or a classroom. Also large-scale Linux networks with different hardware or different installation requirements are easy to establish using FAI. But don't forget to plan your installation. Chapter <> has some useful hints for this topic. First, some terms used in this manual are described. install server:: The host where the package 'fai-server' is installed. It provides several services and data for all install clients. In the examples of this manual this host is called 'faiserver'. install client:: A host which will be installed using FAI and a configuration provided by the install server. Also called client for short. In this manual, the example hosts are called 'demohost, nucleus, atom01, atom02,...' configuration:: The details of how the installation of the clients should be performed. All configuration data is stored in a certain directory structure and is also called configuration space or config space for short. It includes information about: * Hard disk layout * Local file systems, their types, mount points and mount options * Software packages * Keyboard layout, time zone, NIS, Xorg configuration, remote file systems, user accounts, printers ... nfsroot:: A file system located on the install server. It's the complete file system for the install clients during the installation process. All clients share the same nfsroot, which they mount read only. === [[work]]How does FAI work The install client which will be installed using FAI, is booted via network card or from CD or USB stick. It gets an IP address and boots a Linux kernel which mounts its root file system via NFS from the install server. After the kernel is loaded, the FAI startup script performs the automatic installation which doesn't need any interaction. First, the hard disks will be partitioned, file systems are created and then software packages are installed. After that, the new installed operating system is configured to your local needs using some scripts. Finally the new operating system will be booted from the local disk. The details of how to install the computer (the configuration) are stored in the configuration space on the install server. Configuration files are shared among groups of computers if they are similar using the class concept. So you need not create a configuration for every new host. Hence, FAI is a scalable method to install a big cluster with a great number of nodes. FAI can also be used as a network rescue system. You can boot your computer, but it will not perform an installation. Instead it will run a fully functional Debian GNU/Linux without using the local hard disks. Then you can do a remote login and backup or restore a disk partition, check a file system, inspect the hardware or do any other task. //// MT: here the class concept should be described, move the entire section here. //// === [[features]]Features * A fully automated installation can be performed. * Very quick unattended installation. * Update of running systems without re-installation. * Easy creation of a virtualization environment or a chroot * Hosts can boot from network card, CD, USB stick. * Simple creation of the CD and USB stick. * PXE with DHCP and BOOTP boot methods are supported. * Lilo and grub support. * ReiserFS, ext3 and XFS file system support. * Software RAID and LVM support. * Automatic hardware detection. * Remote login via ssh during installation process possible. * Two additional virtual terminals available during installation. * All similar configurations are shared among all install clients. * Log files for all installations are saved to the installation server. * Shell, Perl, expect and cfengine scripts are supported for the configuration setup. * Access to a Debian mirror via NFS, FTP or HTTP. * Can be used as a rescue system. * Flexible system through easy class concept. * Diskless client support. * Easily add your own functions via hooks. * Easily change the default behavior via hooks. == [[impatient]]Quickstart - For the impatient user So, you do not like to read the whole manual? You like to try an installation without reading the manual? OK. Here's how to succeed in a few minutes. * Install the package 'fai-quickstart' on your install server (see <>). * Edit 'fai.conf' run fai-setup -v and read its output. * Install the simple examples into the configuration space: ---- $ cp -a /usr/share/doc/fai-doc/examples/simple/* /srv/fai/config/ ---- * Get the MAC address of your demo host. * Add your host (try to name it 'demohost') to 'dhcpd.conf' and '/etc/hosts' (= your DNS) on the FAI server. * When using PXE, tell the install client to boot the install kernel and perform an installation during the next boot by calling `fai-chboot` on the install server. ---- fai-chboot -IFv demohost ---- * If you want to try FAI without setting up a PXE+DNS+DHCP-environment: put the host names into '/etc/hosts' inside the nfsroot at '/srv/fai/nfsroot' and use a CD/DVD to boot the client. * Boot your demo host and enjoy the fully automatic installation. * If the installation has finished successfully, the computer should boot a small Debian system. You can login as user _demo_ or _root_ with password _fai_. But now don't forget to read chapters <>, <> and <>! == [[inst]]Installing FAI === [[requirements]]Requirements //// MT: split this section to mark the specific requirments: - boot media - source of the root file system - config source //// The following items are required for an installation via FAI. A computer:: The computer must have a network interface card footnote:[If you install from USB stick or CD you do not need a network card]. Unless a diskless installation should be performed a local hard disk is also needed. No floppy disk, CD-ROM, keyboard or graphics adapter is needed. DHCP server:: The clients need one of these daemons to obtain boot information. TFTP server:: The TFTP daemon is used for transferring the kernel to the clients. It's only needed when booting from network card with a boot PROM. NFS-Root:: It is a directory which contains the whole file system for the install clients during installation. It must be exported via NFS, so the install clients can mount it. It will be created during the setup of the FAI package and is also called *nfsroot*. Debian mirror:: Access to a Debian mirror is needed. A local mirror of all Debian packages or an `apt-proxy(8)` is recommended if you install several computers. Configuration space:: This directory tree, which contains the configuration data, is mounted via NFS by default. But you can also get this directory from a revision control system like CVS, subversion or Git. The NFS server will be enabled automatically when installing the _fai-server_ package. === [[debian-mirror]]How to create a local Debian mirror //// MT: move this section near the end of the chapter, it's not as important //// The script `mkdebmirror` footnote:[You can find the script in '/usr/share/doc/fai-doc/examples/utils/'] can be used for creating your own local Debian mirror. This script uses the script `debmirror(1)`. A partial Debian mirror only for i386 architecture for Debian 5.0 (aka lenny) without the source packages needs about {mirrorsize}GB of disk space. Accessing the mirror via HTTP will be the default way in most cases. To see more output from the script call +mkdebmirror -v+. A root account is not necessary to create and maintain the Debian mirror. You can use the command `fai-mirror(1)` for creating a partial mirror that only contains the software packages that are used in the classes in your configuration space. A partial mirror containing all package for the simple examples from the package fai-doc will only need about 440MB of disk space. To use HTTP access to the local Debian mirror, install a web server and create a symlink to the local directory where your mirror is located: ---- faiserver# apt-get install apache2 faiserver# ln -s /files/scratch/debmirror /var/www/debmirror ---- Create a file `sources.list(5)` in '/etc/fai/apt' which gives access to your Debian mirror. An example can be found in '/usr/share/doc/fai-doc/examples/etc'. Also add the IP-address of the HTTP server to the variable +$NFSROOT_ETC_HOSTS+ in 'make-fai-nfsroot.conf' when the install clients have no DNS access. //// MT: some link to a signing howto would be nice //// === [[faisetup]]Setting up FAI To setup a FAI install server you need at least the packages _fai-server_ and _fai-doc_. The package _fai-quickstart_ contains dependencies on all required packages for an install server. Do not install the package _fai-nfsroot_ on a normal system. This package can only be installed inside the nfsroot. If you would like to install all packages that are useful for a FAI install server, use the following command ---- # aptitude install fai-quickstart Reading Package Lists... Done Building Dependency Tree Reading extended state information Initializing package states... Done Reading task descriptions... Done The following NEW packages will be installed: apt-move{a} isc-dhcp-server{a} fai-doc{a} fai-quickstart fai-server{a} genisoimage{a} inetutils-inetd{a} nfs-kernel-server{a} openssh-server{a} syslinux-common{a} tftpd-hpa{a} 0 packages upgraded, 11 newly installed, 0 to remove and 0 not upgraded. Need to get 2593kB of archives. After unpacking 8561kB will be used. Do you want to continue? [Y/n/?] ---- The configuration for the FAI package (not the configuration data for the install clients) is defined in 'fai.conf'. Definitions that are only used for creating the nfsroot are located in 'make-fai-nfsroot.conf'. Edit these files before calling 'fai-setup'. These are important variables in 'make-fai-nfsroot.conf': FAI_DEBOOTSTRAP:: For building the nfsroot there's the command called `debootstrap(8)`. It needs the location of a Debian mirror and the name of the distribution (etch, lenny, sid) for which the basic Debian system should be built. NFSROOT_ETC_HOSTS:: If you use HTTP or FTP access to the Debain mirror, add its IP-address and the name to this variable. For a Beowulf master node, add the name and IP-address of both networks to it. This variable is not needed when the clients have access to a DNS server. These are important variables in 'fai.conf': FAI_CONFIG_SRC:: This variables described how to access the configuration space on the install clients. It's an Universal Resource Identifier (URI). Currently supported methods are: - +nfs://host/path/to/exported/config+ The config space is mounted from host via NFS. - +cvs[+ssh]://user@host/path/to/cvsroot module[=tag]+ The config space is received from a cvs checkout. - +svn://user@host/svnpath+ The config space checked out from a subversion repository. Also supported are svn+file, svn+http, svn+ssh, svn+https and checkouts without a user name. - +git://host/path+ The config space checked out from a git repository, host can be empty. Also supported is git+http. - +http://host/path/tarfile+ The config space will be downloaded from the given location via HTTP. Furthermore +path/tarfile.md5+ will be downloaded and the md5sum will be checked. +tarfile+ will be extracted by `ftar(8)`, and thus needs to have a recognized suffix, such as .tar.gz. If +$FAI_CONFIG_SRC+ is undefined in 'fai.conf', then the default is to use an NFS mount from the fai install server onto the install client. It's the same as +nfs://`hostname`/$FAI_CONFIGDIR+ with the host name determined on the install server. Remember that this directory must be exported to all install clients, so that all files can be read by root. FAI_DEBMIRROR:: If you have NFS access to your local Debian mirror, specify the remote file system. It will be mounted to +$MNTPOINT+, which must also be defined. It's not needed if you use access via FTP or HTTP. A list of variables used by FAI can be found at http://wiki.fai-project.org/index.php/Variables. The content of '/etc/fai/apt/sources.list' and +$FAI_DEBMIRROR+ are used by the install server and also by the clients. If your install server has multiple network cards and different host names for each card (as for a Beowulf server), use the install server name which is known by the install clients. FAI uses `debootstrap(8)` and `apt-get(8)` to create the nfsroot file system in '/srv/fai/nfsroot'. It needs about {nfsrootsize} of free disk space. After editing 'fai.conf' and 'make-fai-nfsroot.conf' call `fai-setup`. include::includes/faisetup.txt[] A complete example of 'fai-setup.log' is available on the FAI web page. It's important that you find both lines that are marked with an asterisk in your output. Otherwise something went wrong. If you'll get a lot of blank lines, it's likely that you are using _konsole_, the X terminal emulation for KDE which has a bug. Try again using _xterm_. The warning messages from dpkg about dependency problems can be ignored. If you have problems running fai-setup, they usually stem from `make-fai-nfsroot(8)`. Adding '-v' gives you a more verbose output which may help you pinpoint the error. The output is written to '/var/log/fai/make-fai-nfsroot.log'. It may help to enter the chroot environment manually using this command. ---- faiserver# chroot /srv/fai/nfsroot/live/filesystem.dir ---- The setup routine adds some lines to '/etc/exports' to export the nfsroot and the configuration space to all hosts that belong to the netgroup _faiclients_. If you already export a parent directory of these directories, you may comment out these lines, since the kernel NFS server has problems exporting a directory and one of its subdirectories with different options. All install clients must belong to this netgroup, in order to mount these directories successfully. Netgroups are defined in the file '/etc/netgroup' or in the corresponding NIS map. An example can be found in '/usr/share/doc/fai-doc/examples/etc/netgroup'. For more information, read the manual pages `netgroup(5)` and the NIS HOWTO. After changing the netgroups, the NFS server has to reload its configuration. Use the following command: ---- faiserver# /etc/init.d/nfs-kernel-server reload ---- The setup also creates the account _fai_ (defined by +$LOGUSER+) if not already available. So you can add a user before calling `fai-setup(8)` using the command `adduser(8)` and use this as your local account for saving log files. The log files of all install clients are saved to the home directory of this account. If you boot from network card, you should change the primary group of this account, so this account has write permissions to '/srv/tftp/fai' in order to change the symbolic links to the kernel image which is booted by a client. //// MT: the log files - which ones? Give a little explanation here //// After that, FAI is installed successfully on your server, but has no configuration for the install clients. Start with the examples from _/usr/share/doc/fai-doc/examples/simple/_ using the copy command above and read <>. Before you can set up a DHCP daemon, you should collect some network information of all your install clients. This is described in section <>. When you make changes to 'fai.conf', 'make-fai-nfsroot.conf' the nfsroot has to be rebuilt by calling `make-fai-nfsroot(8)`. If you only like to install a new kernel to the nfsroot add the flags _-k_ or _-K_ to +make-fai-nfsroot+. This will not recreate your nfsroot, but only updates your kernel and kernel modules inside the nfsroot or add additional packages into the nfsroot. === [[troublefaisetup]]Troubleshooting the setup The setup of FAI adds the _fai_ account, exports file systems and calls `make-fai-nfsroot(8)`. If you call _make-fai-nfsroot -v_ you will see more messages. When using a local Debian mirror, it's important that the install server can mount this directory via NFS. If this mount fails, check '/etc/exports' and '/etc/netgroup'. == [[booting]]Preparing booting Before booting the client for the first time, you have to choose which medium you use for booting. Normally, you will configure the computer to boot via network card. The preferred method for booting is using PXE. PXE is the Preboot Execution Environment which most modern network cards support. Also booting from CD-ROM or from an USB stick is easy to set up. === [[pxeboot]]Booting from network card with a PXE conforming boot ROM Almost all modern bootable network cards support the PXE boot environment. Some network cards (e.g. on notebooks) have a fixed boot configuration, so they can only use the PXE boot protocol. This requires a PXE Linux boot loader and a special version of the _TFTP_ daemon, which is available in the Debian package +tftpd-hpa+. First, install following additional needed packages: ---- faiserver# apt-get install isc-dhcp-server syslinux-common tftpd-hpa ---- Then set up the DHCP daemon. A sample configuration file can be found in '/usr/share/doc/fai-doc/examples/etc/dhcpd.conf'. Copy this file to '/etc/dhcp/dhcpd.conf'. The install client then loads the pxelinux boot loader which receives its configuration via TFTP from a file in the directory '/srv/tftp/fai/pxelinux.cfg' (defined by the variable +$TFTPROOT+ in 'make-fai-nfsroot.conf'). Using the command `fai-chboot(8)` you can define which kernel will be loaded by the PXE Linux loader and which additional parameters are passed to this kernel. You should read the manual pages, which give you some good examples. See '/usr/share/doc/syslinux/pxelinux.doc' for more detailed information. === [[bootfloppy]]Creating a boot floppy If your network card can't boot by itself, you can create a small boot floppy that uses etherboot, which will provide the PXE feature for your network card. So you can use DHCP and TFTP to get the install kernel that was created with `mknbi-linux(8)`. A lot of ethernet cards support booting via ethernet if a special boot EPROM is inserted or booted from floppy provided by http://rom-o-matic.net. In depth documentation about booting via ethernet may be found at http://www.etherboot.org. === [[cdboot]]Booting from a CD-ROM It's possible to perform an automatic installation from CD-ROM without an install server. The CD-ROM contains all data needed for the installation. The command `fai-cd(8)` puts the nfsroot, the configuration space and a subset of the Debian mirror onto a CD-ROM. The partial mirror is created using the command `fai-mirror(1)` which contains all packages that are used by the classes used in your configuration space. A sample ISO image is available at http://fai-project.org/fai-cd. === [[usbboot]]Booting from USB stick Using the command `fai-cd(8)` you can also create a bootable USB stick. First, format your stick with an ext2 file system (ext3 makes no sense on flash memory devices). Then mount it. After that call: ---- faiserver# fai-cd -m /path/to/mirror -u /path/to/mounted/stick ---- Then unmount the USB stick. The USB stick must be formatted with an ext2 file system. VFAT is not yet supported. Currently the file system that will be written onto the stick is not compressed. === [[mac]]Collecting Ethernet addresses Now it's time to boot your install clients for the first time. They will fail to boot completely, because no BOOTP or DHCP daemon is running yet or recognizes the hosts. But you can use this first boot attempt to easily collect all Ethernet addresses of the network cards. You have to collect all Ethernet (MAC) addresses of the install clients and assign a host name and IP address to each client. To collect all MAC addresses, now boot all your install clients. While the install clients are booting, they send broadcast packets to the LAN. You can log the MAC addresses of these hosts by running the following command simultaneously on the server: ---- faiserver# tcpdump -qtel broadcast and port bootpc >/tmp/mac.list ---- After the hosts have been sent some broadcast packets (they will fail to boot because `bootpd` isn't running or does not recognize the MAC address yet) abort `tcpdump` by typing _ctrl-c_. You get a list of all unique MAC addresses with these commands: ---- faiserver$ perl -ane 'print "\U$F[0]\n"' /tmp/mac.list|sort|uniq ---- After that, you only have to assign these MAC addresses to host names and IP addresses ('/etc/ethers' and '/etc/hosts' or corresponding NIS maps). With this information you can configure your `DHCP` daemon (see the section <>). I recommend to write the MAC addresses (last three bytes will suffice if you have network cards from the same vendor) and the host name in the front of each chassis. === [[bootdhcp]]Configuration of the DHCP daemon An example for `dhcpd.conf(5)` is available in '/usr/share/doc/fai-doc/examples/etc/dhcpd.conf', which is working with version 3.x of the DHCP daemon. Start using this example and look at all options used therein. The only FAI specific information inside this configuration file is to set _filename_ to _fai/pxelinux.0_ and to set _next-server_ and _server-name_. All other information is only network related data, which is used in almost all DHCP configurations. If you make any changes to the DHCP daemon configuration, you must restart the daemon. # /etc/init.d/isc-dhcp-server restart By default, the DHCP daemon writes its log files to '/var/log/daemon.log'. The command `fai-chboot(8)` is used for creating a per host configuration for the pxelinux environment. === [[bootmesg]]Boot messages When booting from network card with PXE you will see: include::includes/bootexample.txt[] When the copyright message of FAI is shown, the install client has mounted the nfsroot footnote:['/srv/fai/nfsroot' from the install server] to the clients' root directory. This is the whole file system for the client at this moment. After _task_confdir_ is executed, the configuration space is mounted via NFS. Before the installation is started (+$FAI_ACTION=install+) the computer beeps three times. So, be careful when you hear three beeps but you do not want to perform an installation! ==== [[booterror]]Troubleshooting the boot messages This is the error message you will see, when your network card is working, but the install server does not export the configuration space directory to the install clients, mostly a problem of missing permissions on the server side. ---- Begin: Mounting root file system... ... eth0: link up BusyBox v1.10.2 (Debian 1:1.10.2-1) Built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty: job control turned off (initramfs) ---- You will get a shell prompt and can look at the log files, for examples '/live.log' or '/tmp/net-eth0.conf'. You can also enter the initramfs shell for debugging if you append the parameter 'break' to the kernel command line. Use the following command on the install server to see which directories are exported from the install server (named faiserver): ---- $ showmount -e faiserver ---- The following error message indicates that your install client doesn't get an answer from a DHCP server. Check your cables or start the `dhcpd(8)` daemon with the debug flag enabled. ____ PXE-E51: No DHCP or BOOTP offers received Network boot aborted ____ If you get the following error message, the install kernel could not detect your network card, for example because of a missing driver: ____ Begin: Mounting root file system... ... Kernel panic - not syncing: Attempted to kill init! ____ Check the initrd in the nfsroot if the kernel driver of your network card is included there. === [[sysinfo]]Collecting other system information Now the clients have booted with +$FAI_ACTION+ set to _sysinfo_. Type _ctrl-c_ to get a shell or use _Alt-F2_ or _Alt-F3_ and you will get another console terminal, if you have added _createvt_ to +$FAI_FLAGS+. Remote login is available via the secure shell if _sshd_ is added to +$FAI_FLAGS+. The encrypted password is set with the variable +$FAI_ROOTPW+ in 'make-fai-nfsroot.conf' and defaults to "fai". You can create the encrypted password using `mkpasswd(1)` and use the `crypt(3)` or md5 algorithm. This is only the root password during the installation process, not for the new installed system. You can also log in without a password when using +$SSH_IDENTITY+. To log in from your server to the install client (named demohost in this example) use: ---- $ ssh root@demohost Warning: Permanently added 'demohost,134.95.9.200' to the list of known hosts. root@demohost's password: ---- You now have a running Linux system on the install client without using the local hard disk. Use this as a rescue system if your local disk is damaged or the computer can't boot properly from hard disk. You will get a shell and you can execute various commands (`dmesg`, `lsmod`, `df`, `lspci`, ...). Look at the log file in '/tmp/fai'. There you can find much information about the boot process. All log files from '/tmp/fai' are also written to the +$LOGSERVER+ (if not defined: the server defined by +$SERVER+ from _get-boot-info_) into the directory _~fai/demohost/sysinfo/_. //// More general: _~$LOGUSER/$HOSTNAME/$FAI_ACTION/_. //// Two additional symbolic links are created. The symlink 'last' points to the log directory of the last fai action performed. The symlinks 'last-install' and 'last-sysinfo' point to the directory with of the last corresponding action. Examples of the log files can be found on the FAI homepage. //// MT: I think it should be _~$LOGUSER/$HOSTNAME/$FAI_ACTION-\`DATE\`/_ //// FAI mounts all file systems it finds on the local disks read only. It also tells you on which partition a file '/etc/fstab' exists. When only one file system table is found, the partitions are mounted according to this information. Here's an example: ---- demohost:~# df Filesystem 1K-blocks Used Available Use% Mounted on rootfs 4099064 414088 3645296 11% / udev 10240 76 10164 1% /dev 192.168.1.250:/srv/fai/nfsroot 3905600 410976 3454944 11% /live/image aufs 4099064 414088 3645296 11% / tmpfs 193464 0 193416 0% /live tmpfs 193464 3112 190352 2% /live/cow faiserver:/srv/fai/config 3905600 410976 3454944 11% /var/lib/fai/config /dev/sda1 241116 74519 154149 33% /target /dev/sda9 4364212 139888 4179988 4% /target/home /dev/sda7 553376 16840 536536 4% /target/tmp /dev/sda8 2221628 275936 1832840 14% /target/usr /dev/sda6 577096 172924 374856 32% /target/var aufs 193464 2376 191243 2% /target/dev ---- *This method can be used as a rescue environment!* If you need a file system with read-write access use the `rwmount` command: ---- demohost# rwmount /target/home ---- === [[checkbootp]]Checking parameters from DHCP servers If the install client boots with action _sysinfo_, you can also check if all information from the DHCP daemon are received correctly. The received information is written to '/tmp/fai/boot.log'. An example of the result of a DHCP request can be found in <>. === [[reboot]]Rebooting the computer At any time you can reboot the computer using the command `faireboot`, also if logged in from remote. If the installation hasn't finished, use _faireboot -s_, so the log files are also copied to the install server. == [[instprocess]]Overview of the installation sequence The following tasks are performed during an installation after the Linux kernel has booted on the install clients. ____ confdir # get config space setup # early part of initialization defclass # define classes defvar # define variables action # evaluate FAI_ACTION install # Do the initial installation partition # partition the harddisks, create file systems mountdisks # mount the file systems extrbase # extract the minimal base.tgz mirror # get a Debian mirror via NFS debconf # do Debian preseeding prepareapt # preapre some apt-related files in target directory updatebase # Debian specific HOOK instsoft.FAIBASE # fcopy kernel-img.conf instsoft # install software packages configure # call customization scripts finish # do some cleanup, show installation time tests # call tests if defined chboot # call fai-chboot on the install server HOOK savelog.LAST # grep for error messages in all log files savelog # save log file to local dir and remote faiend # reboot host, eject CD if needed ____ ____ These are tasks, which are executed when a different action is performed dirinstal # install a chroot environment softupdate # do a system configuration without the partitioning part ____ You can also define additional programs or scripts which will be run on particular occasions. They are called _hooks_. Hooks can add additional functions to the installation process or replace the default subtasks of FAI. So it's very easy to customize the whole installation process. Hooks are explained in detail in <>. The installation time is determined by the amount of software but also by the speed of the processor and hard disk. Here are some sample times. All install clients have a 100Mbit network card installed. Using a 10 Mbit LAN does not decrease the installation time considerably, so the network will not be the bottleneck when installing several clients simultaneously. ____ Intel Core2 Duo , 2GB,SATA disk, 3 GB software 14 min Athlon XP1600+ , 896MB,SCSI disk, 1 GB software 6 min AMD-K7 500MHz , 320MB, IDE disk, 780 MB software 12 min PentiumPro 200MHz , 128MB, IDE disk, 800 MB software 28 min Pentium III 850MHz, 256MB, IDE disk, 820 MB software 10 min Pentium III 850MHz, 256MB, IDE disk, 180 MB software 3 min ____ === [[faimond]]Monitoring the installation You can monitor the installation of all install clients with the command `faimond(8)`. All clients check if this daemon is running on the install server (or the machine defined by the variable +$monserver+). Then, a message is sent when a task starts and ends. The fai monitor daemon prints this messages to standard output. There's also a graphical frontend available, called `faimond-gui(1)`. === [[bootkernel]]Booting the kernel The install client receives and loads the kernel and initial RAM disk. The kernel boots up and load the RAM disk. It does some hardware detection and then tries to figure where the root file system is located. When booting from network, this is determined by parameters from additional kernel parameters (_root=/dev/nfs_ and _nfsroot=/srv/fai/nfsroot_). When booting from CD-ROM or USB stick the kernel and initial RAM disk probes removable devices and tries to figure out where the root file system is located. This may also be a compressed file system (using squashfs). After the root file system is mounted read only, it is made writable by mounting a RAM disk via aufs (another unionfs) on top of it. So it's possible for programms or daemons to write to files inside a read only mounted file system. We are using the package `live-initramfs(7)` to mount the nfsroot and to make this file system writable using aufs. The package _live-initramfs_ is only needed inside the nfsroot and adds some initramfs hooks. === [[isetup]]Start and setup FAI //// MT: CVS, SVN missing //// After the install client has booted, only the script '/usr/sbin/fai' footnote:[Since the root file system on the clients is mounted via NFS, `fai` is located in '/srv/fai/nfsroot/live/filesystem.dir/usr/sbin' on the install server.] is executed. This is the main script which controls the sequence of tasks for FAI. No other scripts in '/etc/init.d/' are executed. Additional parameters are received from the DHCP daemon and the configuration space is made available via the configured method (an NFS mount by default) from the install server to '$FAI'. The setup is finished after additional virtual terminals are created and the secure shell daemon for remote access is started on demand. The variable +$FAI_CONFIG_SRC+ is used to get the FAI configuration space, which is very important, since FAI cannot proceed without the config space. === [[iclass]]Defining classes, variables and loading kernel modules Now the script `fai-class(1)` is used to define classes. Therefore several scripts in '$FAI/class/' are executed to define classes. All scripts matching _[0-9][0-9]*_ (they start with two digits) are executed in alphabetical order. Every word that these scripts print to the standard output are interpreted as class names. Scripts ending in _.source_ are sourced, so they can define new classes by adding these classes to the variable +$newclasses+. The output of these scripts is ignored. These classes are defined for the install client. You can also say this client belongs to these classes. A class is defined or undefined and has no value. Only defined classes are of interest for an install client. The description of all classes can be found in '/usr/share/doc/fai-doc/classes_description.txt'. It is advisable to document the job a new class performs. Then, this documentation is the base for composing the whole configuration from classes. The scripts `20-hwdetect.source` loads kernel modules on demand. The complete description of all these scripts can be found in <>. After defining the classes, every file matching _*.var_ with a prefix which matches a defined class is executed to define variables. There, you should define the variable +$FAI_ACTION+ and others. By default, +$FAI_ACTION+ is defined via the command `fai-chboot(8)`. === [[ipartition]]Partitioning local disks, creating file systems For disk partitioning exactly one disk configuration file from '$FAI/disk_config' is selected using classes. This file describes how all the local disks will be partitioned, where file systems should be created (and their types like ext2, ext3, reiserfs), and how they are mounted. It's also possible to preserve the disk layout or to preserve the data on certain partitions. The old tool for partitioning the hard disks is called `setup_harddisks`. This tool is deprecated. With FAI 3.2.8 the new partitioning tool called `setup-storage(8)` was added to FAI. It uses `parted(8)` for editing the partition table and now has support for software RAID and LVM. This tool uses a slightly different format for the configuration files in 'disk_config' than the old tool. Read the manual page for a detailed description of the new format. The variable _USE_SETUP_STORAGE_ now determines which tool to use. When set to 1 it uses the new tool which is now defined in 'FAIBASE.var' by default. During the installation process all local file systems are mounted relative to '/target'. For example '/target/home' will become '/home' in the new installed system. === [[ipackages]]Installing software packages When local file systems are created, they are all empty (except for preserved partitions). Now the Debian base system and all requested software packages are installed on the new file systems. First, the base archive is unpacked, then the command `install_packages(8)` installs all packages using `apt-get(8)` or `aptitude(1)` without any manual interaction needed. If a packages requires another package, both commands resolve this dependency by installing the required package. Classes are also used when selecting the configuration files in '$FAI/package_config/' for software installation. The format of the configuration files is described in <>. === [[icscripts]]Site specific customization After all requested software packages are installed, the system is nearly ready to go. But not all default configurations of the software packages will meet your site-specific needs. So you can call arbitrary scripts which adjust the system configuration. Therefore scripts which match a class name in '$FAI/scripts' will be executed. If '$FAI/scripts/'+classname/+ is a directory, all scripts that match _[0-9][0-9]*_ in this directory are executed. So it is possible to have several scripts of different types (shell, cfengine, ...) to be executed for one class. FAI comes with some examples for these scripts, but you can write your own Bourne, bash, Perl, cfengine or expect scripts. More information about these scripts are described in <>. === [[itests]]Automated tests After the customization scripts are executed, FAI will execute some tests if available. Using these test, you can check for errors of the installation or of the softupdate. Test scripts are called via `fai-do-scripts(1)` and should append it's messages to _$LOGDIR/test.log_. A Perl module including some useful subroutines can be found in _Faitest.pm_. A test can also define a new class for executing another tests during next boot via the variable +$ADDCLASSES+. === [[isavelog]]Save log files When all installation tasks are finished, the log files are written to _/var/log/fai/$HOSTNAME/install/_ footnote:['/var/log/fai/localhost/install/' is a link to this directory.] on the new system and to the account on the install server if +$LOGUSER+ is defined in 'fai.conf'. It is also possible to specify another host as log saving destination through the variable +$LOGSERVER+. If +$LOGSERVER+ is not defined, FAI uses the variable +$SERVER+ which is only defined during an initial installation (by get-boot-info). Make sure to set +$LOGSERVER+ in a _class/*.var_ script if you are using the action _softupdate_. Additionally, two symlinks will be created to indicated the last directory written to. By default log files will be copied to the log server using scp. You can use other methods to save logs to the remote server. The currently selected method is defined by the +$FAI_LOGPROTO+ variable in file 'fai.conf': rsh:: Use the rcp command to copy the log files to the log server. ftp:: This option saves logs to the remote FTP server defined by the +$LOGSERVER+ variable (+$SERVER+ value is used if not set). Connection to the FTP server is done as user +$LOGUSER+ using password +$LOGPASSWD+. The FTP server log directory is defined in +$LOGREMOTEDIR+. These variables are also defined in file 'fai.conf'. You need write access for the +$LOGREMOTEDIR+ on the FTP server. All files in the directory _/tmp/fai_ are copied to the FTP server following this example: ____ ftp://$LOGUSER:$LOGPASSWD@$LOGSERVER/$LOGREMOTEDIR/ ____ none:: Don't save the log file to the install server. === [[ireboot]]Reboot the new installed system At last the system is automatically rebooted if "reboot" was added to +$FAI_FLAGS+. Normally this should boot the new installed system from its second boot device, the local hard disk. To skip booting from network card, you can use the command `fai-chboot(8)` to enable localboot. == [[plan]]Plan your installation, and FAI installs your plans Before starting your installation, you should spend a lot of time in planning your installation. When you're happy with your installation concept, FAI can do all the boring, repetitive tasks to turn your plans into reality. FAI can't do good installations if your concept is imperfect or lacks some important details. Start planning the installation by answering the following questions: * Will I create a Beowulf cluster, or do I have to install some desktop machines? * What does my LAN topology look like? * Do I have uniform hardware? Will the hardware stay uniform in the future? * Does the hardware need a special kernel? * How should the hosts be named? * How should the local hard disks be partitioned? * Which applications will be run by the users? * Do the users need a queueing system? * What software should be installed? * Which daemons should be started, and what should the configuration for these look like? * Which remote file systems should be mounted? * How should backups be performed? You also have to think about user accounts, printers, a mail system, cron jobs, graphic cards, dual boot, NIS, NTP, timezone, keyboard layout, exporting and mounting directories via NFS and many other things. So, there's a lot to do before starting an installation. And remember that knowledge is power, and it's up to you to use it. Installation and administration is a process, not a product. FAI can't do things you don't tell it to do. But you need not start from scratch. Look at all files and scripts in the configuration space. There are a lot of things you can use for your own installation. A good paper called "Bootstrapping an Infrastructure" with more aspects of building an infrastructure is available at http://www.infrastructures.org/papers/bootstrap == [[config]]Installation details === [[c3]]The configuration space The configuration is the collection of information about how exactly to install a computer. The central configuration space for all install clients is located on the install server in '/srv/fai/config' and its subdirectories. This will be mounted by the install clients to '/var/lib/fai/config'. It's also possible to receive all the configuration data from a `cvs(1)`, subversion (`svn(1)`) or Git (`git(1)`) repository. The following subdirectories are present and include several files: _class/_:: Scripts and files to define classes and variables and to load kernel modules. _disk_config/_:: Configuration files for disk partitioning and file system creation. _debconf/_:: This directory holds all `debconf(8)` data. The format is the same that is used by `debconf-set-selections(8)`. _package_config/_:: Files with class names contain lists of software packages to be installed or removed. Files named '*.asc' are added to the key list of apt. _scripts/_:: Script for local site customization. _files/_:: Files used by customization scripts. Most files are located in a subtree structure which reflects the ordinary directory tree. For example, the templates for 'nsswitch.conf' are located in '$FAI/files/etc/nsswitch.conf' and are named according to the classes that they should match: '$FAI/files/etc/nsswitch.conf/NIS' is the version of '/etc/nsswitch.conf' to use for the NIS class. Note that the contents of the files directory are not automatically copied to the target machine, rather they must be explicitly copied by customization scripts using the `fcopy(8)` command. _basefiles/_:: Normally the file '/var/tmp/base.tgz' is extracted on the install client after the new file systems are created and before package are installed. This is a minimal base image, created right after calling debootstrap during the make-fai-nfsroot process on the install server. If you want to install another distribution than the nfsroot is, you can put a tar file into the subdirectory 'basefiles/' and name it after a class. Then the command `ftar(8)` is used to extract the tar file based on the classes defined. This is done in task _extrbase_. _hooks/_:: Hooks are user defined programs or scripts, which are called during the installation process. The can extend or replace the default tasks. The main installation command `fai(8)` uses all these subdirectories in the order listed except for hooks. The FAI package contains examples for all these configuration scripts and files in '/usr/share/doc/fai-doc/examples'. Copy the configuration examples to the configuration space and start an installation. These files need not belong to the root account. You can change their ownership and then edit the configuration with a normal user account. ---- # cp -a /usr/share/doc/fai-doc/examples/simple/* /srv/fai/config # chown -R fai /srv/fai/config ---- These files contain simple configuration for some example hosts. Depending on the host name used, your computer will be configured as follows: demohost:: A machine which needs only a small hard disk. This machine is configured with network (as DHCP client), and an account demo is created. gnomehost:: A GNOME desktop is installed, and the account demo is created. other host names:: Hosts with other host name will most notably use the classes FAIBASE, DHCPC and GRUB. Start looking at these examples and study them. Then change or add things to these examples. But don't forget to plan your own installation! === [[tasks]]The default tasks After the kernel has booted, it mounts the root file system via NFS from the install server and `init(8)` starts the script '/usr/sbin/fai'. This script controls the sequence of the installation. No other scripts in '/etc/init.d/' are used. The installation script uses many subroutines, which are defined in '/usr/lib/fai/subroutines'. All important tasks of the installation are called via the subroutine _task_ appended by the name of the task as an option (e.g. __task_instsoft__). The subroutine _task_ calls hooks with prefix *name* if available and then calls the default task (defined as __task___ in 'subroutines'). The default task and its hooks can be skipped on demand by using the subroutine _skiptask()_. Now follows the description of all default tasks, listed in the order they are executed. confdir:: The kernel appended parameters define variables, the syslog and kernel log daemon are started. The list of network devices is stored in +$netdevices+. Then additional parameters are fetched from a DHCP server and also additional variables are defined. The DNS resolver configuration file is created. + The location of the configuration space is defined by the variable +$FAI_CONFIG_SRC+. You can use NFS, cvs, svn or git to access the configuration space. See section <> for how to set the variable. + After that, the file '$FAI/hooks/subroutines' is sourced if it exists. Using this file, you can define your own subroutines or override the definition of FAI's subroutines. //// MT: there is no info about that at id="isetup" MT: config is also mounted/checked out in this task //// setup:: This task sets the system time, all +$FAI_FLAGS+ are defined and two additional virtual terminals are opened on demand. A secure shell daemon is started on demand for remote logins. defclass:: Calls `fai-class(1)` to define classes using scripts and files in '$FAI/class' and classes from '/tmp/fai/additional-classes' and the variable +$ADDCLASSES+. defvar:: Sources all files '$FAI/class/*.var' for every defined class. If a hook has written some variable definitions to the file '/tmp/fai/additional.var', this file is also sourced. action:: Depending on the value of +$FAI_ACTION+ this subroutine decides which action FAI should perform. The default available actions are: _sysinfo_, _install_ and _softupdate_. If +$FAI_ACTION+ has another value, a user defined action is called if a file '$FAI/hooks/$FAI_ACTION' exists. So you can easily define your own actions. sysinfo:: Called when no installation is performed but the action is _sysinfo_. It shows information about the detected hardware and mounts the local hard disks read only to '/target/+partitionname+' or with regard to a 'fstab' file found inside a partition. Log files are stored to the install server. install:: This task controls the installation sequence. You will hear three beeps before the installation starts. The major work is to call other tasks and to save the output to '/tmp/fai/fai.log'. If you have any problems during installation, look at all files in '/tmp/fai/'. You can find examples of the log files for some hosts in the download directory of the FAI homepage. softupdate:: This task, executed inside a running system via the `fai(8)` command line interface, performs a softupdate. See chapter <> for details. partition:: Calls `setup-storage(8)` to partition the hard disks and to create file systems. The task writes variable definitions for the root and boot partition and device (+$ROOT_PARTITION, $BOOT_PARTITION, $BOOT_DEVICE+) to '/tmp/fai/disk_var.sh' and creates an 'fstab' file. mountdisks:: Mounts the created partitions according to the created '/tmp/fai/fstab' file relative to +$FAI_ROOT+. extrbase:: Extracts a minimal system after that a chroot can be made into it. By default the base tar file '/var/tmp/base.tgz' will be extracted. The command `ftar -1v -s $FAI/basefiles /` is used for unpacking a different tar file depending on classes defined. This can be used for installing different Linux distributions than the one used for creating the nfsroot. The default file 'base.tgz' is a snapshot of a basic Debian system created by `debootstrap(8)` mirror:: If a local Debian mirror is accessed via NFS (when +$FAI_DEBMIRROR+ is defined), this directory will be mounted to +$MNTPOINT+. debconf:: Calls `fai-debconf(8)` to set the values for the debconf database. prepareapt:: Set up resolv.conf and some other files, for the next task updatebase. updatebase:: Updates the base packages of the new system and updates the list of available packages. It also fakes some commands (called diversions) inside the new installed system using `dpkg-divert(8)`. instsoft:: Installs the desired software packages using class files in '$FAI/package_config/'. configure:: Calls scripts in '$FAI/scripts/' and its subdirectories for every defined class. tests:: Calls test scripts in '$FAI/tests/' and its subdirectories for every defined class. finish:: Unmounts all file systems in the new installed system and removes diversions of files using the command `fai-divert`. chboot:: Changes the PXE configuration for a host on the install server which indicates which kernel image to load on the next boot from network card via TFTP. Therefore the `fai-chboot(8)` command is executed remotely on the install server. savelog:: Saves log files to local disk and to the account +$LOGUSER+ on +$LOGSERVER+ (defaults to the install server). faiend:: Wait for background jobs to finish (e.g. emacs compiling lisp files) and automatically reboots the install clients or waits for manual input before reboot. === [[setuproutines]]The setup routines of the install clients After the subroutine `fai_init` has done some basic initialization (create RAM disk, read 'fai.conf' and all subroutines definitions, set path, print copyright notice), the setup continues by calling the task _confdir_ and the task _setup_. The command `get-boot-info` is called to get all information from the DHCP server. This command writes the file '/tmp/fai/boot.log', which then is sourced to define the corresponding global variables. This is an example for this log file when using a DHCP server. include::includes/bootlog.txt[] Additional information is passed via the kernel command line or read from 'fai.conf'. When booting with PXE, command line parameters are created using `fai-chboot(8)`. If you do not boot from network card but from CD-ROM or USB stick, you may also give network parameters to the kernel via the kernel command line. Two interesting parameters are ---- nfsroot=:][,] ip=:::::: ---- Those parameters are described in the documentation of the Linux kernel sources in '/usr/src/linux/Documentation/nfsroot.txt'. ==== [[faiflags]]FAI flags The variable +$FAI_FLAGS+ contains a space separated list of flags. The following flags are known: verbose:: Create verbose output during installation. This should always be the first flag, so consecutive definitions of flags will be verbosely displayed. debug:: Create debug output. No unattended installation is performed. During package installation you have to answer all questions of the postinstall scripts on the client's console. A lot of debug information will be printed out. This flag is only useful for FAI developers. sshd:: Start the ssh daemon to enable remote logins. createvt:: Create two virtual terminals and execute a bash if _ctrl-c_ is typed in the console terminal. The additional terminals can be accessed by typing _Alt-F2_ or _Alt-F3_. Otherwise no terminals are available and typing _ctrl-c_ will reboot the install client. Setting this flag is useful for debugging. If you want an installation which should not be interruptible, do not set this flag. reboot:: Reboot the install client after installation is finished without typing RETURN on the console. This is only useful if you can change the boot image or boot device automatically or your assembly robot can remove the boot floppy via remote control :-) Currently this should only be used when booting from network card. initial:: Used by `setup-storage(8)`. Partitions marked with +preserve_reinstall+ are preserved unless this flag ist set. Often, this flag is set in a file 'class/*.var' by using setting 'flag_initial=1'. === [[classc]]The class concept //// MT: as marked above, this section should be put in chapter 1 //// Classes determine which configuration file to choose from a list of available templates. Classes are used in all further tasks of the installation. To determine which config file to use, an install client searches the list of defined classes and uses all configuration files that match a class name. It's also possible to use only the configuration file with the highest priority since the order of classes define the priority from low to high. There are some predefined classes (DEFAULT, LAST and the host name), but classes can also be listed in a file or defined dynamically by scripts. So it's easy to define a class depending on the subnet information or on some hardware that is available on the install client. The idea of using classes in general and using certain files matching a class name for a configuration is adopted from the installation scripts by Casper Dik for Solaris. This technique proved to be very useful for the SUN workstations, so I also use it for the fully automatic installation of Linux. One simple and very efficient feature of Casper's scripts is to call a command with all files (or on the first one) whose file names are also a class. The following loop implements this function in pseudo shell code: ---- for class in $all_classes; do if [ -r $config_dir/$class ]; then your_command $config_dir/$class # exit if only the first matching file is needed fi done ---- Therefore it is possible to add a new file to the configuration without changing the script. This is because the loop automatically detects new configuration files that should be used. Unfortunately cfengine does not support this nice feature, so all classes being used in cfengine also need to be specified inside the cfengine scripts. Classes are very important for the fully automatic installation. If a client belongs to class _A_, we say the class _A_ is defined. A class has no value, it is just defined or undefined. Within scripts, the variable +$classes+ holds a space separated list with the names of all defined classes. Classes determine how the installation is performed. For example, an install client can be configured to become an FTP server by just adding the class _FTP_ to it. Mostly a configuration is created by only changing or appending the classes to which a client belongs, making the installation of a new client very easy. Thus no additional information needs to be added to the configuration files if the existing classes suffice for your needs. There are different possibilities to define classes: . Some default classes are defined for every host: DEFAULT, LAST and its host name. . Classes may be listed within a file. . Classes may be defined by scripts. The last option is a very nice feature, since these scripts will define classes automatically. For example, several classes are defined only if certain hardware is identified. We use Perl and shell scripts to define classes. All names of classes, except the host name, are written in uppercase. They must not contain a hyphen, a hash or a dot, but may contain underscores. A description of all classes can be found in '/usr/share/doc/fai-doc/classes_description.txt'. host names should rarely be used for the configuration files in the configuration space. Instead, a class should be defined and then added for a given host. This is because most of the time the configuration data is not specific for one host, but can be shared among several hosts. === [[s2]]Defining classes The task _defclass_ calls the script `fai-class(1)` to define classes. Therefore, scripts matching _[0-9][0-9]*_ in _$FAI/class_ are executed. Additionally, a file with the host name may contain a list of classes. For more information on defining class, read the manual pages for `fai-class(1)`. The list of all defined classes is stored in the variable +$classes+ and saved to '/tmp/fai/FAI_CLASSES'. The list of all classes is transferred to `cfengine`, so it can use them too. The script '10-base-classes' (below is a stripped version) is used to define classes depending on the host name. First, this script defines the class with the name of the hardware architecture in uppercase letters. ---- 10-base-classes: # echo architecture and OS name in upper case. Do NOT remove these two lines uname -s | tr '[:lower:]' '[:upper:]' dpkg --print-architecture | tr /a-z/ /A-Z/ [ -f /etc/RUNNING_FROM_FAICD ] && echo "FAICD" # use a list of classes for our demo machine case $HOSTNAME in demohost) echo "FAIBASE GRUB DHCPC DEMO" ;; gnomehost) echo "FAIBASE GRUB DHCPC DEMO XORG GNOME";; *) echo "FAIBASE GRUB DHCPC" ;; esac ---- The script _20-hwdetect.source_ uses the default Debian commands to detect hardware and to load some kernel modules. If some specific hardware is found, it can also define a new class for it. You can find messages from modprobe in '/tmp/fai/kernel.log' and on the fourth console terminal by pressing _Alt-F4_. === [[classvariables]]Defining variables The task _defvar_ defines the variables for the install client. Variables are defined by scripts in _class/*.var_. All global variables can be set in 'DEFAULT.var'. For certain groups of hosts use a class file or for a single host use the file +$HOSTNAME+_.var_. Also here, it's useful to study all the examples. The following variables are used in the examples and may also be useful for your installation: FAI_ACTION:: Set the action fai should perform. Normally this is done by `fai-chboot(8)`. If you can't use this command, define it in the script 'LAST.var'. FAI_ALLOW_UNSIGNED:: If set to 1, FAI allows the installation of packages from unsigned repositories. CONSOLEFONT:: Is the font which is loaded during installation by `consolechars(8)`. KEYMAP:: Defines the keyboard map files in '/usr/share/keymaps' and '$FAI/files'. You need not specify the complete path, since this file will be located automatically. ROOTPW:: The encrypted root password for the new system. You can use `crypt(3)` or md5 encryption for the password. You can create the encrypted password using `mkpasswd(1)`. See <> for more info. UTC:: Set hardware clock to UTC if _$UTC=yes_. Otherwise set clock to local time. See `clock(8)` for more information. TIMEZONE:: Is the file relative to '/usr/share/zoneinfo/' which indicates your time zone. MODULESLIST::: Can be a multi line definition. List of modules (including kernel parameters) which are loaded during boot of the new system (written to /etc/modules). USE_SETUP_STORAGE:: If set to one (the default when using the class _FAIBASE_ the new partitioning tool `setup-storage(8)` will be used. Otherwise the old `setup_harddisks` program is used. === [[diskconfig]]Hard disk configuration Read the manual page of `setup-storage(8)` for a detailed description of the new format. This is used by default since FAI 3.2.8 or when setting the variable +$USE_SETUP_STORAGE+ to 1. === [[packageconfig]]Software package configuration //// MT: This section is pretty much a chaos: which commands belong to which package tools you say something about PRELOADRM and PRELOAD commands, but give no example and don't list them otherwise //// Before installing packages, fai will add the content of all files named _package_config/*.asc_ to the list of apt keys. If your local repository is signed by your keyid AB12CD34 you can easily add this key, so fai will use it during installation. Use this command for creating the '.asc' file: ---- faiserver$ gpg -a --export AB12CD34 > /srv/fai/config/package_config/myrepo.asc ---- The script `install_packages(8)` installs the selected software packages. It uses all configuration files in '$FAI/package_config' whose file name matches a defined class. The syntax is very simple. ---- # an example package class PACKAGES taskinst german PACKAGES aptitude adduser netstd ae less passwd PACKAGES remove gpm xdm PACKAGES aptitude GRUB lilo- grub PACKAGES dselect-upgrade ddd install a2ps install ---- Comments are starting with a hash (#) and are ending at the end of the line. Every command begins with the word _PACKAGES_ followed by a command name. The command defines which command will be used to install the packages named after this command. The list of all available commands can be listed using _install_packages -H_. Supported package tools are: _aptitude, apt-get, smart, y2pmsh, yast, yum, urpm, rpm_ hold:: Put a package on hold. This package will not be handled by dpkg, e.g not upgraded. install:: Install all packages that are specified in the following lines. If a hyphen is appended to the package name (with no intervening space), the package will be removed, not installed. All package names are checked for misspellings. Any package which does not exist, will be removed from the list of packages to install. So be careful not to misspell any package names. remove:: Remove all packages that are specified in the following lines. Append a + to the package name if the package should be installed. taskinst:: Install all packages belonging to the tasks that are specified in the following lines using `tasksel(1)`. You can also use _aptitude_ for installing tasks. aptitude:: Install all packages with the command `aptitude`. This will be the default in the future and may replace apt-get and taskinst. Aptitude can also install task packages. aptitude-r:: Same as aptitude with option _--with-recommends_. unpack:: Download package and unpack only. Do not configure the package. dselect-upgrade:: Set package selections using the following lines and install or remove the packages specified. These lines are the output of the command _dpkg --get-selections_. Multiple lines with lists of space separated names of packages follow the PACKAGES lines. All dependencies are resolved. Packages with suffix _-_ (eg. _lilo-_) will be removed instead of installed. The order of the packages is of no matter. If you like to install packages from another release than the default, you can append the release name to the package name like in _openoffice.org/etch-backports_. You can also specify a certain version like _apt=0.3.1_. More information on these features are described in `aptitude(8)`. A line which contains the _PRELOADRM_ commands, downloads a file using `wget(1)` into a directory before installing the packages. Using the _file:_ URL, this file is copied from +$FAI_ROOT+ to the download directory. For example the package `realplayer` needs an archive to install the software, so this archive is downloaded to the directory '/root'. After installing the packages this file will be removed. If the file shouldn't be removed, use the command _PRELOAD_ instead. It's possible to append a list of class names after the command for apt-get. So this _PACKAGE_ command will only be executed when the corresponding class is defined. So you can combine many small files into the file DEFAULT. WARNING! Use this feature only in the file DEFAULT to keep everything simple. See this file for some examples. If you want to remove a package name from a certain class was part of this class before, you should not remove the package name from the class file, but instead append a dash (-) to it. This will make sure that the package is remove during a softupdate on hosts which were installed using the old class definition which included this package name. If you specify a package that does not exist this package will be removed from the installation list when the command _install_ is used. === [[cscripts]] Customization scripts in _$FAI/scripts_ The default set of scripts in '$FAI/scripts' is only an example. But they should do a reasonable job for your installation. You can edit them or add new scripts to match your local needs. The command `fai-do-scripts(1)` is called to execute all scripts in this directory. If a directory with a class name exists, all scripts matching '[0-9][0-9]*' are executed in alphabetical order. So it's possible to use scripts of different languages (shell, cfengine, Perl,..) for one class. ==== [[shell]]Shell scripts Most scripts are Bourne shell scripts. Shell scripts are useful if the configuration task only needs to call some shell commands or create a file from scratch. In order not to write many short scripts, it's possible to distinguish classes within a script using the command _ifclass_. For copying files with classes, use the command `fcopy(8)`. If you want to extract an archive using classes, use `ftar(8)`. But now have a look at the scripts and see what they are doing. ==== [[perl]]Perl scripts Currently no Perl script are used in the simple examples for modifying the system configuration. ==== [[expect]]Expect scripts Currently no expect scripts are used in the simple examples for modifying the system configuration. ==== [[cfengine]]Cfengine scripts Cfengine has a rich set of functions to edit existing configuration files, e.g _LocateLineMatching, ReplaceAll, InsertLine, AppendIfNoSuchLine, HashCommentLinesContaining_. But it can't handle variables which are undefined. If a variable is undefined, the whole cfengine script will abort. Study the examples that are included in the fai package. More information can be found in the manual page `cfengine(8)` or at the cfengine homepage http://www.cfengine.org. === [[changeboot]]Changing the boot device Changing the boot sequence is normally done in the BIOS setup. But you can't change the BIOS from a running Linux system as far as I know. If you know how to perform this, please send me an email. But there's another way of swapping the boot device of a running Linux system. //// MT: recently, there has been some discussion on linux-fai, add a link to the archives //// So, normally the boot sequence of the BIOS will remain unchanged and your computer should always boot first from its network card and the second boot device should be the local disk. Then, it will get an install kernel image from the install server, when an installation should be performed, or we can tell pxelinux to boot from local disk. This is done using `fai-chboot(8)`. Here is how to set up a 3Com network card as first boot device. Enable LAN as first boot device in the BIOS. Boot From LAN First: Enabled Boot Sequence : C only Then enter the MBA setup of the 3Com network card and change it as follows: Default Boot Local Local Boot Enabled Message Timeout 3 Seconds Boot Failure Prompt Wait for timeout Boot Failure Next boot device This will enable the first IDE hard disk as second boot device after the network card. === [[hooks]]Hooks Hooks let you specify functions or programs which are run at certain steps of the installation process. Before a default task is called, FAI searches for existing hooks for this task and executes them. As you might expect, classes are also used when calling hooks. Hooks are executed for every defined class. You only have to create the hook with the name for the desired class and it will be used. If several hooks for a task exists, they are called in the order defined by the classes. If _debug_ is included in +$FAI_FLAG+ the option _-d_ is passed to all hooks, so you can debug your own hooks. If some default tasks should be skipped, use the subroutine _skiptask_ and a list of default tasks as parameters. The example 'partition.DISKLESS' skips some default tasks. The directory '$FAI/hooks/' contains all hooks. A hook is an executable file following the naming scheme 'taskname.CLASSNAME[.source]' (e.g. 'partition.DISKLESS' or 'partition.DISKLESS.source'), a task name and a class name separated by a dot, optionally followed by '.source'. The task name specifies which task to precede executing this hook, if the specified class is defined for the installing client. See section <> for a complete list of default tasks that can be used. In our example, the hook 'partition.DISKLESS' is called for every client belonging to the class _DISKLESS_ before the local disks would be partitioned. If it should become a diskless client, this hook can mount remote file systems via NFS and create a _/tmp/fai/fstab_. After that, the installation process will not try to partition and format a local hard disk, because a file '/tmp/fai/fstab' already exists. A hook of the form _hookprefix.classname_ can't define variables for the installation script, because it's a subprocess. But you can use any binary executable or any script you wrote. Hooks that have the suffix _.source_ (e.g. 'partition.DEFAULT.source') must be Bourne shell scripts and are sourced. So it's possible to redefine variables for the installation scripts. In the first part of FAI, all hooks with prefix _confdir_ are called. Since the configuration directory '$FAI' is mounted in the default task _confdir_, the hooks for this task are the only hooks located in +$nfsroot+'/$FAI/hooks' on the install server. All other hooks are found in '$FAI_CONFIGDIR/hooks' on the install server. //// MT: what about softupdate? //// All hooks that are called before classes are defined can only use the following classes: _DEFAULT $HOSTNAME LAST_. If a hook for class _DEFAULT_ should only be called if no hook for class +$HOSTNAME+ is available, insert these lines to the default hook: ---- hookexample.DEFAULT: #! /bin/sh # skip DEFAULT hook if a hook for $HOSTNAME exists scriptname=$(basename $0 .DEFAULT) [-f $FAI/hooks/$scriptname.$HOSTNAME ] && exit # here follows the actions for class DEFAULT . . ---- Some examples for what hooks could be used: - Use `ssh` in the very beginning to verify that you mounted the configuration from the correct server and not a possible spoofing host. - Do not mount the configuration directory, instead get a compressed archive via HTTP and extract it into a new RAM disk, then redefine +$FAI_LOCATION+. - Load kernel modules before classes are defined in '$FAI/class'. - Send an email to the administrator if the installation is finished. - Install a diskless client and skip local disk partitioning. See 'hooks/partition.DISKLESS'. === [[errors]]Looking for errors If the client can't successfully boot from the network card, use `tcpdump(8)` to look for Ethernet packets between the install server and the client. Search also for entries in several log files made by `tftpd(8)` and `dhcpd3(8)` : ---- faiserver$ egrep "tftpd|dhcpd" /var/log/* ---- Sometimes the installation seems to stop, but often there's only a postinstall script of a software package that requires manual input from the console. Change to another virtual terminal and look which process is running with tools like `top(1)` and `pstree(1)`. You can add _debug_ to _FAI_FLAGS_ to make the installation process show all output from the postinst scripts on the console and get its input also from the console. Don't hesitate to send an email to the mailing list or to mailto:fai@fai-project.org[] if you have any questions. Sample log files from successfully installed computers are available on the FAI homepage. === [[logfiles]]Log files FAI is creating several log files. During installation they are stored in '/tmp/fai' on the install client itself. At the end of the installation they will be copied to the install server (see <>). After the install client rebooted into his newly installed system, you can find the FAI logs in '/var/log/fai'. Log files are also created when doing the softupdate or dirinstall action. These a some log files which are created by FAI. FAI_CLASSES:: Contains a list of all classes defined. dmesg.log:: Output of the `dmesg` command. Contains useful messages of the kernel ring buffer. fai.log:: The main log file. Contains all important information. You should always read this file. boot.log:: A list of variables of network parameters, mostly defined by the DHCP daemon. format.log:: Output of the partition tool `setup-storage(8)`. shell.log:: Output of all shell scripts, that are used for customization. variables.log:: A list of all shell variables which are available during an installation. error.log:: A summary of possible errors in all log files. If the installation process finishes, the hook 'savelog.LAST.source' searches all log files for common errors and writes them to the file 'error.log'. So, you should first look into this file for errors. Also the file 'status.log' give you the exit code of the last command executed in a script. To be sure, you should look for more details in all log files. == [[beowulf]]How to build a Beowulf cluster using FAI This chapter describes the details about building a Beowulf cluster using Debian/GNU Linux and FAI. This chapter was written for FAI version 2.x for Debian woody and was not yet updated. The example configuration files were removed from the fai packages after FAI 2.8.4. For more information about the Beowulf concept look at http://www.beowulf.org. === [[beoplan]]Planning the Beowulf setup The example of a Beowulf cluster consists of one master node and 25 clients. A big rack was assembled which all the cases were put into. A keyboard and a monitor, which are connected to the master server most of the time, were also put into the rack. But since we have very long cables for a monitor and a keyboard, they can also be connected to all nodes if something has to be changed in the BIOS, or when looking for errors when a node does not boot. Power supply is another topic you have to think about. Don't connect many nodes to one power cord and one outlet. Distribute them among several breakout boxes and outlets. And what about the heat emission? A dozen nodes in a small room can create too much heat, so you will need an air conditioner. Will the power supplies of each node go to stand-by mode or are all nodes turned on simultaneously after a power failure? All computers in this example are connected to a Fast Ethernet switch. The master node (or master server) is called _nucleus_. It has two network cards. One for the connection to the external Internet, one for the connection to the internal cluster network. If connected from the external Internet, it's called _nucleus_, but the cluster nodes access the master node with the name _atom00_, which is a name for the second network interface. The master server is also the install server for the computing nodes. A local Debian mirror will be installed on the local hard disk. The home directories of all user accounts are also located on the master server. It will be exported via NFS to all computing nodes. NIS will be used to distribute account, host, and printer information to all nodes. All client nodes _atom01_ to _atom25_ are connected via the switch with the second interface card of the master node. They can only connect to the other nodes or the master, but can't communicate to any host outside their cluster network. So, all services (NTP, DNS, NIS, NFS, ...) must be available on the master server. I chose the class C network address _192.168.42.0_ for building the local Beowulf cluster network. You can replace the subnet 42 with any other number you like. If you have more than 253 computing nodes, choose a class A network address (10.X.X.X). In the phase of preparing the installation, you have to boot the first install client many times, until there's no fault in your configuration scripts. Therefore you should have physical access to the master server and one client node. So, connect both computers to a switch box, so one keyboard and monitor can be shared among both. === [[master]]Set up the master server The master server will be installed by hand if it is your first computer installed with Debian. If you already have a host running Debian, you can also install the master server via FAI. Create a partition on '/files/scratch/debmirror' for the local Debian mirror with more than {mirrorsize} GB space available. ==== [[beonetworkmaster]]Set up the network Add the following lines for the second network card to '/etc/network/interfaces': ---- # Beowulf cluster connection auto eth1 iface eth1 inet static address 192.168.42.250 netmask 255.255.255.0 broadcast 192.168.42.255 ---- Add the IP addresses for the client nodes. The FAI package has an example for this '/etc/hosts' file: ---- # create these entries with the Perl one liner # perl -e 'for (1..25) {printf "192.168.42.%s atom%02s\n",$_,$_;}' # Beowulf nodes # atom00 is the master server 192.168.42.250 atom00 192.168.42.1 atom01 192.168.42.2 atom02 ---- You can give the internal Beowulf network a name when you add this line to '/etc/networks': beowcluster 192.168.42.0 Activate the second network interface with: _/etc/init.d/networking start_. ==== [[beonis]]Setting up NIS Add a normal user account +tom+ which is the person who edits the configuration space and manages the local Debian mirror: # adduser tom # addgroup linuxadmin This user should also be in the group +linuxadmin+. # adduser tom linuxadmin First, set the NIS domainname name by creating the file '/etc/defaultdomain' and call `domainname(8)`. To initialize the master server as NIS server call _/usr/lib/yp/ypinit -m_. Also edit '/etc/default/nis' so the host becomes a NIS master server. Then, copy the file 'netgroup' from the examples directory to '/etc' and edit other files there. Adjust access to the NIS service. ---- /etc/ypserv.securenets: # Always allow access for localhost 255.0.0.0 127.0.0.0 # This line gives access to the Beowulf cluster 255.255.255.0 192.168.42.0 ---- Rebuild the NIS maps: ---- master# cd /var/yp; make ---- You will find much more information about NIS in the 'NIS-HOWTO' document. ==== [[beomirror]]Create a local Debian mirror Now the user +tom+ can create a local Debian mirror on '/files/scratch/debmirror' using `mkdebmirror`. You can add the option _--debug_ to see which files are received. This will need about 250 GB disk space for Debian 3.0 (aka woody). Export this directory to the netgroup _@faiclients_ read only. Here's the line for '/etc/exports': /files/scratch/debmirror *(ro) ==== [[fai1]]Install FAI package on the master server Add the following packages to the install server: ---- nucleus:/# apt-get install ntp tftpd-hpa dhcp3-server \ nfs-kernel-server etherwake fai nucleus:/# tasksel -q -n install dns-server nucleus:/# apt-get dselect-upgrade ---- Configure NTP so that the master server will have the correct system time. It's very important to use the internal network name +atom00+ for the master server (not the external name +nucleus+) in '/etc/dhcp3/dhcpd.conf' and 'make-fai-nfsroot.conf'. Replace the strings FAISERVER with _atom00_ and uncomment the following line in 'make-fai-nfsroot.conf' so the Beowulf nodes can use the name for connecting to their master server. ---- NFSROOT_ETC_HOSTS="192.168.42.250 atom00" ---- ==== [[bootp1]]Prepare network booting Set up the install server daemon as described in <>. If you will have many cluster nodes (more than about 10) and you will use _rsh_ in 'fai.conf' raise the number of connects per minute to some services in 'inetd.conf': ---- shell stream tcp nowait.300 root /usr/sbin/tcpd /usr/sbin/in.rshd login stream tcp nowait.300 root /usr/sbin/tcpd /usr/sbin/in.rlogind ---- The user +tom+ should have permission to create the symlinks for booting via network card, so change the group and add some utilities. ---- # chgrp -R linuxadmin /srv/tftp/fai; chmod -R g+rwx /srv/tftp/fai # cp /usr/share/doc/fai-doc/examples/utils/* /usr/local/bin ---- Now, the user +tom+ sets the boot image for the first beowulf node. ---- $ fai-chboot -IFv atom01 ---- Now boot the first client node for the first time. Then start to adjust the configuration for your client nodes. === [[beotools]]Tools for Beowulf clusters The following tools are useful for a Beowulf cluster: all_hosts:: Print a list of all hosts, print only the hosts which respond to a ping or the hosts which do not respond. The complete list of hosts is defined by the netgroup _allhosts_. Look at '/usr/share/doc/fai-doc/examples/etc/netgroup' for an example. rshall:: Execute a command on all hosts which are up via rsh. Uses `all_hosts` to get the list of all hosts up. You can also use the `dsh(1)` command (dancer's shell, or distributed shell). rup:: The command `rup(1)` shows briefly the CPU load of every host. clusterssh:: The package clusterssh allows you to control multiple ssh or rsh sessions at the same time. These are some common tools for a cluster environment: rgang:: For a huge cluster try `rgang`. It's is a tool which executes commands on or distributes files to many nodes. It uses an algorithm to build a tree-like structure to allow the distribution processing time to scale very well to 1000 or more nodes (available at http://fermitools.fnal.gov/abstracts/rgang/abstract.html). jmon:: For observing the resources of all clients (CPU, memory, swap,...) you can use `jmon(1)` which installs a simple daemon on every cluster node. ganglia:: This toolkit is very good for monitoring your cluster with a nice web frontend. Available at http://ganglia.sourceforge.net === [[wol]]Wake on LAN with 3Com network cards Wake on LAN is a very nice feature to power on a computer without having physical access to it. By sending a special ethernet packet to the network card, the computer will be turned on. The following things have to be done, to use the wake on LAN (WOL) feature. . Connect the network card to the Wake-On-LAN connector on the motherboard using a 3 pin cable. . My ASUS K7M motherboard has a jumper called _Vaux (3VSBSLT)_ which allows to select the voltage supplied to add-in PCI cards. Set it to _Add 3VSB_ (3 Volt stand by). . Turn on the wake on LAN feature in BIOS . For a 3Com card using the 3c59x driver you must enable the WOL feature using the kernel module option _enable_wol_. To wake up a computer use the command `etherwake(8)`. == [[arch]]FAI on other architectures If you want to use FAI on other architectures than i386 or amd64 you might need to take care of some things yourself. These are things that may have to be changed on other architectures: Boot loader:: There are scripts for setting up `lilo(8)` and `grub(8)`. Here you may add support for your specific boot loader. If you want to serve multiple nfsroot directories on one FAI server, you need to create specific config directories in '/etc' for fai, like '/etc/fai-sarge' and '/etc/fai-etch'. Then you need to set the +$NFSROOT+ variables to different directories and run ---- faiserver#make-fai-nfsroot -c /etc/fai-sarge ---- === [[archcross]]How to install i386 systems from an amd64 system To install a computer with a 32bit i386 system, you need an i386 nfsroot. Creating this 32bit nfsroot on an install server runnning amd64 is quiet simple. Install and setup the fai packages. Then copy your fai config files to a new subdirectory. ---- faiserver# cp -a /etc/fai /etc/fai-i386 ---- Edit the variable +$FAI_DEBOOTSTRAP_OPTS+ in '/etc/fai-i386/make-fai-nfsroot.conf' and add the option +--arch i386+. Also choose a different directory for your new nfsroot. Here are the two lines after editing. ---- NFSROOT=/srv/fai/nfsroot-i386 FAI_DEBOOTSTRAP_OPTS="--arch i386 --exclude=info" ---- Now call make-fai-nfsroot which creates the 32bit i386 nfsroot in '/srv/fai/nfsroot-i386' ---- faiserver# make-fai-nfsroot -v -C/etc/fai-i386 ---- Creating a partitial mirror using `fai-mirror(1)` that is needed for a bootable CD or USB stick is also possible on a different architecture. Due to a bug in apt-move (#441231), you have to specify the architecture when calling fai-mirror. ---- $ export MAXPACKAGES=800 $ fai-mirror -a i386 -v -cDEFAULT,FAIBASE,I386 /srv/mirror-i386 ---- That's all! === [[powerpc]]FAI on PowerPC There's some stuff on http://www.layer-acht.org/fai. Most notably there are hooks for partitioning and config-files to setup bootloaders for oldworld and newworld. === [[ia64]]FAI on IA64 There's one big IA64 Beowulf cluster running which was installed with FAI. Only the partitioning part has to be replaced by a short script, since sfdisk is not available on IA64. This should not be need any more since the patitioning tool `setup-storage(8)` works on all architectures, were parted is supported. === [[otherbase]]Installing other distributions using a Debian nfsroot You can install all sorts of Linux distributions from a single Debian nfsroot. Therefore you have to create a base.tgz of the distribution you like to install and place it info the `basefiles` directory. Then name it UBUNTU910.tar.gz for example. An install client which belongs to the class UBUNTU910 then extracts this base file into its empty file system. Additionally you have to adjust the 'sources.list' or similar configuration files which are needed for specifying the location of the package repository. //// rpmstrap mach (make a chroot) //// === [[odists]]FAI for Ubuntu, Suse, Redhat and Gentoo All FAI packages are available in Ubuntu and are used by a large number of people since many version. Many people are interested in FAI for other (mostly RPM based) Linux distributions. I made some research and it should not be much work to implement it. But I need more help to implement it. If you are interested and would like to help me, please send an email to mailto:fai@fai-project.org[]. A brief description how to install SLES9 with FAI is available at http://www.sourcecode.de/install_sles_with_fai. There are also some information in the faiwiki. === [[sparc]]FAI on SUN SPARC hardware running Linux Although FAI is architecture independent, there are some packages which are only available for certain architectures (e.g. silo, sparc-utils). SUN SPARC computers can boot from their boot prompt. To boot a SUN use: boot net:dhcp - ip=::::::dhcp You have to convert the kernel image from ELF format to a.out format. Use the program `elftoaout` (mentioned in the FAQ). The symlink to the kernel image to be booted is not the host name. A success report as of 2001 is available at http://www.opossum.ch/fai/. === [[solaris]]FAI for Solaris FAI has also been ported for use with SUN Solaris OS installations in cooperation with Solaris jumpstart. This was done using FAI 2.8.4 and Solaris 9. Get the FAI sources from FAI 2.8.4 and change to the 'sunos' directory. There you can call _make_ which creates the tarball '/tmp/fai-solaris.tar.gz'. You have to read the file 'README.sunos' and have some knowledge about Solaris jumpstart. The Solaris support was removed in FAI 2.9. The file format of the configuration files in 'disk_config' and 'package_config' are different than those for Linux. == [[advanced]]Advanced FAI === [[dirinstall]]Creating chroot and virtualization environments If you have some chroot environments to install, or a virtualization environment where you neither can nor want to run a normal Debian Installer in to get to a working system (for example, Xen guest domains), there is the FAI action _dirinstall_. By calling ---- faiserver# fai dirinstall ---- and using either the option _-c _ or _-N_ you get a FAI installation, without the partitioning action, right into the target directory. The host name for the target installation can be specified using _-u _ This, for example, can be used to combine FAI with the tool _xen-tools_, which helps you to build Xen guest domains. _xen-tools_ are very nice for generating configuration files and block devices for new guests based on simple commands and/or configuration files, but they can only assign one role per installation for customization. FAI-users need and want more, as they are used to have the class system. They get them even in xen-tools installations, by using the following code as a xen-tools role script: ---- #!/bin/sh TARGET=$1 CMD="fai -N -v -u ${hostname} dirinstall $TARGET" echo running $CMD $CMD ---- Then, you will want to set the variable _install=0_ the xen-tools config for that host (in previous versions of xen-tools, this was _no-install=1_). === [[softupdate]]Using FAI for updates FAI is even usable for system updates, using the same configuration as if initially installing. System update means updating the running system without doing a re-installation. An updated client will almost look like a newly installed machine, though all local data is preserved (except of course newer configuration files introduced in the FAI config). ==== [[aboutsoftupdate]]How does a softupdate work? Softupdate use the same configuration files as a new FAI installation. They even use the default FAI commands, so they behave _nearly_ in the same way as an installation, though some things are different: * By default the old list of classes (created during the initial installation) is used, so `fai-class` is not called to define a new list of classes. This can be changed by calling _fai -N softupdate_. * No partitioning and file system creation is performed. * The basesytem isn't bootstrapped. * FAI skips tasks only useful when installing, such as setting up a keymap or starting special daemons. * FAI doesn't prevent software packages to (re-)start daemons. * FAI doesn't reboot at the end of a softupdate. Except these changes, things are the same as when installing a new computer: . Define classes (by default use old list) and variables. . Update the installed packages. . Install new software. . Call configuration scripts. . Save the logfiles. ==== [[runsoftupdate]]How to run a softupdate As softupdate use the same infrastructure as a FAI installation, you even start them by using the same command `fai(8)` which is used for installation: ---- # fai -v softupdate ---- starts a softupdate. Make sure to set the variable +$LOGSERVER+ (done in a _class/*.var_ file) if fai should save the log files to a remote machine. ===== How to do mass softupdates Probably you don't want to run to each client and start a softupdate there locally, so a mechanism to start an update there has to be thought of. ===== Cron One possible solution is to use crontab entries on the clients to start an update, but in big installations you have to consider including a random-delay mechanism, because too many updates at the same time may produce too much traffic on your network. ===== Starting a softupdate remotely If you want more control when exactly a softupdate is run on the clients and maybe want to monitor it while it is running, you can install remote root login mechanisms on your clients, preferably using ssh in connection with a authorized key for root logins. Tools like _clusterssh_ allow you to login onto a group of clients at once and run _fai softupdate_ there, while the results can be seen immediately in the terminals started for each host. ==== [[confsoftupdate]]How to write a configuration suitable for softupdate When you want to do softupdate, you have to be even more careful when writing your configuration: it has to be *idempotent*, i.e. running all the scripts twice should result in the same system configuration as running them once. Some things to keep an eye on: - *Never* blindly append to files: $ echo $SOMETHING >> /etc/fstab is almost certainly wrong. Either check manually if the line already exists *before* appending or use the command `ainsl(1)`. This has a similar function to cfengine's _AppendIfNoSuchLine_ statement - Make use of FAI's environment variables to determine what to do in your configuration scripts! Some of the most important ones: +$FAI_CONFIG_SRC+:: is the URI of the configuration space. +$FAI_ROOT+:: points to the client's rootdir. In case of softupdate it's the root directory _/_ +$ROOTCMD+:: contains a command for _chrooting_ into the client. This is empty when doing softupdate (as _/_ is already our root...). +$FAI_ACTION+:: contains the currently executed action: * _install_ when installing. * _softupdate_ when updating - Restart daemons if needed: most daemons only read their configuration when starting; if you modify it, you need to make them reload it using .... $ROOTCMD invoke-rc.d $somedaemon reload .... or even restart them .... $ROOTCMD invoke-rc.d $somedaemon restart .... when the configuration for _$somedaemon_ has been changed footnote:[You can for example use `fcopy(8)`'s _postinst_ script support for doing this; if other things than _fcopy_ modify your conffiles, you have to keep track of the changes yourself.] - Other things like scheduling a reboot if a new kernel is installed ==== [[localconfsoftupdate]]What if there are locally changed config files? *Short: there shouldn't be any!* *Long:* _if_ you are using FAI _softupdate_ to update client's configuration, you shouldn't do any local changes on the install clients, because they may be lost while updating. Backup copies are done by fcopy only on the local disk. By default, they are written to the same directory as the original file, with _.pre_fcopy_ appended. If you want to save them together with the logfiles, add following line to your _class/DEFAULT.var_: .... FAI_BACKUPDIR=$LOGDIR/backup .... ==== [[detectlocalchanges]]How to detect locally changed files? If you are playing with local configuration changes _despite all the warnings contained in this section_, there must be a way to check what has been changed locally. A simple approach would be to use _debsums -e_, but this method fails miserably if you modify conffiles in your FAI scripts, because it only checks against the version contained in the Debian package. A better proposal is to setup/abuse `tripwire(8)` or `integrit(1)` to scan for local changes and notify you about them. == [[hints]]Various hints This chapter has various hints which may not always be explained in great detail. - To generate a md5 hash for the password use this _echo "yoursecrectpassword" | mkpasswd -Hmd5 -s_ - When using HTTP access to a Debian mirror, the local _/var_ partition on all install clients must be big enough to keep the downloaded Debian packages. Do not try with less than 250 Mbytes unless you know why. You can limit the number of packages installed at a time with the variable +$MAXPACKAGES+. - You can remove the red logo on the install client by simply calling `reset` once. If will also not appear if you create a file using this command on the install server: ---- touch /srv/fai/nfsroot/live/filesystem.dir/.nocolorlogo ---- - If you like to define some additional classes (for e.g. A,B,C) on the kernel command line add this: _ADDCLASSES=A,B,C_ - You can shorten some scripts by using one single fcopy command _fcopy -r /_. - If you rebuild the nfsroot, you will create a new ssh host key inside the nfsroot. Then logging in to an install client may fail, because the host key changes. You can use this: ---- $ ssh -o StrictHostKeyChecking=no root@installclient ---- - You can also delete the host entry on your install client in your _~/.ssh/known_hosts_ file by using the _ssh-keygen -R_ command. - In the tasks chboot and savelog, a connection using secure shell is opened to the FAI server (see <>). To ensure that this works non-interactively, a proper entry in 'NFSROOT/root/.ssh/known_hosts' must be created. When using fai-setup, this is done automatically, but it may require manual editing in case the name of your FAI server was not determined correctly. If you stumble over ssh connections that require typing "yes" to accept the host key during installation, please check the contents of your 'NFSROOT/root/.ssh/known_hosts file' - You can calculate the IP subnet address by using the nice tool ipcalc. Following example gives you the notation for a class C network (24) when the server network interface has the IP address 123.45.6.123 ---- $ ipcalc -nb 123.45.6.123 24|grep Network: ---- - You can merge two directories which contain configuration information, if one is a global one, and the other a local one. We use it to merge the templates from the FAI package, and our local configuration, which contains encrypted passwords and other information that should not be readable by others. If you remove a file in your local configuration, do not forget to remove this file also in the configuration space, otherwise it will still be used. - After calling `set_disk_info`, a list of all local hard disks is stored in +$disklist+. - Use `fai-divert -a` if a postinst script calls a configuration program, e.g. the postinst script for package apache calls apacheconfig, which needs manual input. You can fake the configuration program so the installation can be fully automatic. But don't forget to use `fai-divert -R` to remove all faked scripts. - During the installation you can execute commands inside the newly installed system in a chroot environment by using _chroot /target_ or just _$ROOTCMD_ followed by the command you want to call; for example _$ROOTCMD dpkg -l_ shows the packages installed on the new system. //// MT: has been said already The only task which has to be done manually for new hardware is to assign the MAC address to a host name and to an IP address, and to define classes for this host if the existing configuration files are not generic enough to deal with this new host. There's a tradeoff between writing a few large configuration scripts, or many short scripts, one for each class. Large scripts can distinguish classes by using case statements, the _ifclass_ test or with class mechanisms for _cfengine_ scripts. //// - If your computer can't boot from the network card, you do not always need to boot from floppy. Add the class _FAI_BOOTPART_ and FAI will automatically create a lilo or grub entry for booting the FAI bootfloppy from this partition. So you can start the re-installation without a boot floppy. This will also make the test phase shorter, since booting from hard disk is much faster than booting from floppy. You can also set a password for this boot menu. - How can I define classes on the kernel command line? + Read the man page of `fai-class(8)` - How to use a custom kernel inside the nfsroot? + Build your customized kernel by building a kernel package using `make-kpkg(8)` and use the option `--initrd`. Copy this Debian package to a local repository and add it to /etc/fai/sources.list. Add the name of your package to /etc/fai/NFSROOT. Then rebuild the nfsroot. - On http://www.layer-acht.org/fai you will find an example how to fully automatically install a system using the Debian Installer (d-i) in conjunction with FAI's softupdate (see <>). fai-3.4.8ubuntu5/doc/classes_description.txt0000664000000000000000000000364311562212376016066 0ustar Description of the classes Tue, 10 Jan 2006 18:02:19 +0100 -------------------------- If you want to find all files (except hostnames) that are classes try: find /srv/fai/config -type f | egrep '/[[:upper:][:digit:]_]+$' In cfengine scripts you can find class names using: egrep -r '[[:upper:][:digit:]_]+::' /srv/fai/config Shell scripts are using the commad ifclass. So use: egrep -r 'ifclass[[:space:]]+[[:upper:][:digit:]_]+' /srv/fai/config Class name used in Description ---------------------------------------------------- CHVDPSF A DHCPC PS do network configuration using dhcp-client GERMAN P packages for the german environment XFREE P packages for xfree server, fonts,... LILO S create lilo.conf, install lilo GRUB S install and configure grub FAI_BOOTPART S add fai boot menu to lilo.conf or grub's menu.lst LAST S remove backup files of cfengine, link /tmp if necessary, add nfs location of debian mirror to fstab FAIBASE C V PS minimal software list, configure base stuff (TODO: describe in more detail) FAISERVER DESFP setup install server with DHCP, TFTP, partial mirror, call fai-setup during first boot DEMO PS more demo packages, add account demo (pw: fai) NOMBR S install boot loader into root partition (not into MBR) Explanation of "used in": ------------------------- C = /fai/class/ V = used for *.var in /fai/class D = /fai/disk_config/ E = /fai/debconf/ P = /fai/package_config/ S = /fai/scripts/ F = /fai/files/ (used by fcopy) A = auto class (defined by a script) H = /fai/hooks The following classes should always be defined: LAST, DEFAULT (are defined by default) BOOT and maybe MBR Some classes depends on another class. For example, the class NTP is used in the script NETWORK. So both classes must be defined if the ntp configuration should be created. fai-3.4.8ubuntu5/doc/lenny-instructions.txt0000664000000000000000000000221611562212376015710 0ustar How to set up a FAI install server on Debian lenny using FAI 3.4.x ================================================================== FAI 3.4.x is ready-to-go for Debian Squeeze, but can also be used on a server running lenny. - Add this line to /etc/apt/sources.list: deb http://fai-project.org/download squeeze koeln - Install new FAI 3.4.x packages on your system - Replace any occurrences of 'squeeze' with 'lenny' in the following files: /etc/fai/make-fai-nfsroot /etc/fai/apt/sources.list - Add the aufs-modules package to /etc/fai/NFSROOT: < linux-image-486 > linux-image-486 aufs-modules-2.6-486 - Since fai 3.4.x is only available in the squeeze repository of fai-project.org (and depending on the date possibly also from Debian squeeze and unstable/sid) add this line to /etc/fai/apt/sources.list deb http://fai-project.org/download squeeze koeln - Call fai-setup -v or make-fai-nfsroot -v - In the config space you have to add the class GRUB (providing grub1) to your install clients instead of the class GRUB_PC (providing grub2). Have a look at class/50-host-classes. - When building a fai-cd, use option -G1. fai-3.4.8ubuntu5/doc/changelog.old0000664000000000000000000001070611562212376013712 0ustar this was a changelog/NEWS file before FAI was a real Debian package since fai-1.1beta3: please look at the changelog file -------------------------------------------------- fai-1.1beta2: june 20, 2000 - script faireboot for easy rebooting - package_config can now preload a file before installing a package (useful for realplayer, fai,..) - install_packages called in different ways depending on FAI_FLAGS (verbose,debug) for better debugging - a "mini howto" on the creation of a FAI Boot Floppy doc/fai-boot-floppy.txt - S24 echoes NONIS if no nisdomain is defined - allways call the new lilo ${target}/sbin/lilo - apt-get upgrade before installation of packages - define_classes is called when FAI_ACTION is sysinfo - two configuration examples: faiserver and faiclient01 - Class renamed: MAINTAINER -> DEBIAN_DEVEL - start-stop-daemon is now faked in a better way - fai.pl renamed to Fai.pm, new location - use make-fai-nfsroot if you do not want to mount /usr from a server (default) - some tests which nfs server you are using; only the user space nfs-server is supported until now - testsize (Fai.pm) tests if lower < size <= upper - blocksize of harddisk will now be determined in Fai.pm (not fixed to 512 bytes) -------------------------------------------------- fai-1.1beta1: - examples that are not used are now put into the subdirectory example - metapackages are used for software selection (package names task-*) - now using lprng instead of lpd (lpd always started daemon during installation) - class REBOOT removed. reboot can now be set via FAI_FLAGS (T172) or in class/S*.source - base2_X.tgz can now be retrieved via ftp and http using wget - NO second reboot is needed! S99finish.sh is obsolete - using the tools from kernel-package, now it's easy to create and install a kernel and his modules for a host. /fai/files/boot and /fai/files/modules not used any more, because we have a Debian package for the kernel - FAI now has serveral actions. If you only want some hardware information, you can get it without installing anything. See bootp tag $T171 or $FAI_ACTION (thanks to Thomas Gebhardt for this idea) - a lot of cfengine actions are now unnecessarily, because there's a finer selection of software (e.g. rstat-client, rstatd). Former these services must be disabled in inetd.conf - resolv.conf is used during installation - the full location of /usr is now defined in fai.conf - new options for setup_harddisk (-X -m) - totally new rewritten install_packages.pl - call lilo from $target; it's version must match with files in /boot - if the correct amount of memory is not detected, you can define it in $liloappend - a lot of software packages are gone, renamed, new or better one available so files in package_config also had changed (e.g. now lprng instead of lpd) - timezone is now a variable, not fixed in cfengine - you can now load a different keytable (e.g. german keyboard) -------------------------------------------------- FAI 1.0.1: january 19, 2000 - setup_harddispk.pl now calculates partition sizes more exactly, it checks all filesystems before mounting them (setup_harddisk.pl) It also mounts filesystems read-only if they should be preserved. Ignore error messages (read-only filesystem) when extracting base2_1.tgz. This is a feature, not a bug. It can handle different output of old and new sfdisk executables. - the link name to the (tftp) image for booting from local disk is now specified with $TFTPLINK; previously it was always a link to the file clusterimage (rcS,class/S*.source) - if host is in class MBR, lilo will write the master boot record (mbr) otherwise, mbr will be left intact and only the boot sector of the root partition is written (scripts/BOOT) - class LAST is now always the last class (S99last.sh) - S99var.source now S91var.source; variable definition depending on hosts should be defined after S91* (e.g. S99kueppers.sh) - start-stop-daemon is disabled during installation (rcS) - rcS is now a bash script, and trap also starts a bash (formerly sh script), the quit signal (ctrl-\) also calls trap - BOOTP tag T172 holds a space separated list of flags which will be set to 1 inside rcS (verbose, debug are now used) - installkernel now supports Adaptec AIC7xxx based SCSI controllers - Thomas Renard has done some work on FAI for Red Hat RPM Systems http://www.netcologne.de/~nc-renardth/fai/ - doc/links.html is a file which contains all important links, so you can easily click and jump to these pages fai-3.4.8ubuntu5/doc/Makefile0000664000000000000000000000250711562212376012723 0ustar #!/bin/make -s DOC = fai-guide MISC_DOC = classes_description.txt links.html changelog.old lenny-instructions.txt free: text html ps pdf # echo "`grep -c FIXME $(DOC).txt` FIXMEs left to fix:" # grep FIXME $(DOC).txt html: a2x --icons-dir=.a2x-icons --icons --copy --asciidoc-opt="-a toc -a toclevels=3" -f xhtml $(DOC).txt chunked: a2x --icons-dir=.a2x-icons --icons --copy --asciidoc-opt="-a toc -a toclevels=3" -f chunked $(DOC).txt pdf: a2x --icons -a toc -a toclevels=3 -f pdf $(DOC).txt rm -f $(DOC).xml $(DOC).fo ps: a2x --icons -a toc -a toclevels=3 -f ps $(DOC).txt rm -f $(DOC).xml $(DOC).fo # a2x uses lynx, maybe use w3m instead # which texwidth for text output? # asciidoc --doctype=article -a "toc" -a "toclevels=3" -f /etc/asciidoc/text.conf -b html4 -o - "f-guide.txt" | lynx -dump -stdin >"./f-guide.text" text: a2x --icons -a toc -a toclevels=3 -f text $(DOC).txt # for openoffice doc: html unoconv --show >/dev/null 2>&1 || exit "Please install the unoconv package." unoconv -f doc $(DOC).html all: free install: cp -dRp $(DOC)* $(DOCDIR) cp -p $(MISC_DOC) $(DOCDIR) clean: rm -rf .a2x-icons rm -f $(DOC).text $(DOC).html $(DOC).doc $(DOC).pdf $(DOC).xml $(DOC).ps docbook-xsl.css test: asciidoc --version > /dev/null 2>&1 || exit "Please install the asciidoc package." .PHONY: all test clean fai-3.4.8ubuntu5/README0000664000000000000000000000451211562212376011374 0ustar This is FAI (Fully Automatic Installation) for Linux FAIVERSIONSTRING FAI is a non-interactive system to install, customize and manage Linux systems and software configurations on computers as well as virtual machines and chroot environments, from small networks to large infrastructures and clusters. It's a tool for mass unattended Linux installation. You can take one or more virgin systems, turn on the power, and after a few minutes, the systems are installed, and completely configured to your exact needs, without any interaction necessary. Thus it's a scalable method for deploying and updating a Beowulf cluster or a network of workstations unattended with little effort involved. FAI uses the Debian distribution and a collection of shell and Perl scripts for the installation process. Changes to the configuration files of the operating system are made by cfengine, shell and Perl scripts. The home page for FAI is http://fai-project.org/ This release of FAI is tested with the Debian 6.0 release (called squeeze). FAI is free software, distributed under the terms of the GNU General Public License, version 2. For more information, see the file COPYING. There is no warranty, expressed or implied, associated with this product. Use at your own risk. Please read the file changelog for changes in new versions of FAI. Comments, bug reports, fixes, enhancements etc. are welcome. Send them to fai@fai-project.org Please fill out the questionnaire when you have finished a project using FAI. http://fai-project.org/questionnaire I'm looking for short success stories or reports, so new users can see how others are using FAI in several types of environment. There's also a mailing list for FAI available. Mails may be written in english or german. https://lists.uni-koeln.de/mailman/listinfo/linux-fai now enjoy FAI and your saved time Thomas ---------------------------------------------------------------------- Thomas Lange Institut fuer Informatik mailto:lange@informatik.Uni-Koeln.DE Universitaet zu Koeln Pohligstr. 1 Telefon: +49 221 470 5303 50969 Koeln Fax : +49 221 470 5317 1024D/AB9B66FD AEA6 A8C1 BD8E 67C4 8EF6 8BCA DC13 E54E AB9B 66FD ---------------------------------------------------------------------- Copyright (c) 1999-2011 Thomas Lange. All rights reserved. fai-3.4.8ubuntu5/pixmaps/0000775000000000000000000000000011562212376012173 5ustar fai-3.4.8ubuntu5/pixmaps/ok.gif0000664000000000000000000000514011562212376013273 0ustar GIF89a22çÿ    ! ',/356 8!9$9":%;"?'=#@$A%B &C!'D"(E#)F$*G%)K!,I&*L#/J"+M$,N%-O&0R(1S)2T*7R)3U+4W-7W'2Z)8X)3[*5\+6],8_.9`/:a0FZC;c17f3=j1>k2Dg_~WQŠ@mxgi|^TCVER“Hf…^X‘GpgZST•JtniˆahŒ^W™L[™GXšMhfZœOoŽg^Kn’dqi}†`ŸLr‘jt“l]¤P^¥Qv•m_¦Re¤Qw—ou™ke¦Ya©T‰‹ˆh§TeªOc«V{šrg¬Qb°Sj¬^Š•„i¯St¥m‘Žm­Y|¡qh°Zf´W„Ÿ~gµXk³]h¶YpµY‚§wk¸[‘œ‹—™–m»]rºcuº^¨‡v¼_‘§u½fŠ¯«ŠŸ¡žxÀi¡£ ˜¬Œ—®“Ák‚¿w‹¸†Ž¸€€Âs™°•’·†¤ª §©¦›²—³™ŠÄv©«¨–»‹‘Á¤´›‹Èž¾•¯±®–Ɔ±³¯–˃•Í‹·¹¶º¼¹¤Ï–ŸÒ˜©Ï¡Ô™¾À½¢Õš¨Óš©Ô›À¿ªÕœ«×ºÍ¹«Ù¥¶Ó°¬Ú¦¾ÌÀÇÉƳڨÈÊǵ۩¶Üª´Ý±¾Ú·ÆÖ¼¼Þ³ÎÐ;ߴÐÒÏ¿àµÀᶾã¾ÔÖÓÍÝÃÅâ¿ÐÛÉÖØÕÈäÁÉåÂÙÛ×ÊçÃØÞÔËèÄÏçËÑéÌÙäÒÞàÝÓëÏàâßÛëÑÙì×äæãåçäáìÙçéæèêçÞñÝæñßëîêíïìæôçèöêðóïïöêóõòòùîõ÷ôòü÷øû÷ûýúþÿüÿÿÿ!þ(C) Christoffer Jerkeby 2007!ù ÿ,22þÿ ü‡ƒ š7u֑ð¡œ7#º™HqE4hÌdÔhÆŒ˜0W”!*/]ºr©Ìõ«¥J”¼N¢Ô“fÌ›¾|ýâÕ2%Kš­ ì‘KgËœ9qmɴ鯜O‘&å%õ)°”Bÿ™ÆÕ0a`…qý*v¬Ù±^¥=Ë,×_ŸÆúw$nØbxóêË×nØ¿€ç…[L¬‰+ÀôšmùöWâÄŽ÷Jž\ŒiåĶ\$«Œ²g½Êv) =Z˜2Ó¨…q6—Ô>£‹žM»¶íÎÇðS}z¶if±;Öõ¨F%Ù²o+Ë—y^eÍF7]™µ~êœ>¶¼³lR’tþxšíL»mfèÓ£Ÿ½½öòÎöõó·oü÷Ì„Q’dã’³h£Ý_4h`4*cž2ãÌ×σ÷Lƒ 2Ñ4CÊ#’ä ‰2Ìè¡‚ .ÜÈ?þÌ—b?éØÌ,Œ<òˆ Ÿhã.FÓa3%ƒ"Š*>HÎ4ÇH"c†žHˆc4×0Ià5PBéd“MFÓŠ@þ¸Ï4Ó\(㌟LS͘dV£ä’Ry3÷üèfŠã\cË—æðI”xâiÍ5{òY¦5ÚúŒ6Õ<“ΛnÒSÍœt‚©Í£F*©¤×Tç5€î¹¢@zÃ(HNú(¦|^å¤Ý<ÚM<œ¢˜N(þ16:£'©JÚÍ­¸æª«®â´JŸ%²™ƒ*Ýxcì±Èë²·"kl±ô`ù¦-F;«8ÎŽ£í¶Újã ^pS©çHë&9Ö ›Š7â´+Î8Éþ %ÄÈȽõ)‰$ô´Ú(éÊhÃ+äLλÚ^Ë$±üˆ.¾Vãp†ªl°§ÊÈÉ4Õ‹I>­æƒ‰Ã3ªrÎÉ'_Óñ#˜D{ÎÊ_2R¿ÄMÈ:0Òˆ"Œ(ÒÈÓP?]ƒ*ê¨sŽ.N?È$íðãu?úŒÓ"c7òÇ8øà£ÏÚi¯Êø!ˆpûA7ÜpÓ@µþ:³ðáÇ!tR>ó>áÛÂx¸bøã…ƒÇâ”WŽÇå“ÇPŠ:»øÁÇ‹²;ï”þé¤C£w|ãÎëìľÎ:æBÇ{ì1tÄïÀÓñB*ÏèÇpÀAÇ(´ÏŽŽ9ÐGO ±Do½9ÜÄrmœqFɧ!¾ød|ßÂ%wœÑÆøp¤a 7ðc?üßpC 6Ü`£ÿþÜ “$C¸Àï}á€e øЂ|! g(ÃxÀLPÒ †7(zðƒÒGÈ…ð Z! O€¦p $ #>˜ iÔð†ÉÈ¡“ñ -¤P þY"†8Ä,HA \" R.H¡ˆXÈB¥`\ô¢Á¸â­¨E\x^8¢Ÿ Æ#’± S£F …*´q d<"¥P‡[àâx´cõˆÇD<Œqü£¢GBþñ è€!ÿ¸È'@á Npƒ,hA YXò’˜Dþ¸ÉM>   ¥Œ€„Q&¡0ÂTi&Œò•LHЀ V°¸Ìe.Ã@"$¡HŒ $SI2‹ Ìt ”Á„f2)LanaÈf'6ÁMnB™à3à N"áAB2ÐeA™çTg:ƒpNü€ ‘þȧ>óI%üà<ðlððÀ=(xPð@:°ÀºÐ ô 5€ht€Ð4 )!ÀƒÜ £9¸AIZƒ”Ô:hhK+0–Ú”¡:¸AKm`SžÖ`lȃPó†Ô 6Á j0ƒÌà©1p* bƒª¢`x*T£:U§® «Qª –`…%à(p VЂ¬àiE Xà‚¸¢ (XÁ XÌ•x] {×¼¦ ƒU TÀBĪ±„Mìb{Æ*¶)8Á Jp‚<@³'Hb«YÌ2´œ F°ZÖ’ #`þmlE`¬±#è@LÛÚV °­3Gà[Û&Ò·‰ ALð$Ò™ ø8àL8óð@v§ëÌî~  @%<Àì–×™ÔíîuÙÉ H·½ˆo|3øb€¾÷µ.°ß X ÿ€À2€ø˜€*P H´Á4½@úŠšZ€Á¨6< C`˜€D ÿ£Nq‡?üaO¸¯/–€ú ôuȱ%à€8 ?nP€<~@’sìã8ùPN@¥ü4@Ê PÀÀeð2` Pxp€"‹äÄ($Öœf `Ípàæ@@ì,;ß9ÎpN³H;fai-3.4.8ubuntu5/pixmaps/begin.gif0000664000000000000000000000527411562212376013756 0ustar GIF89a22çÿ    &$,#, '/&/)1*2+3(2+3,4 .;-5.60=/71>2?1:3@4A5B6C7D8D8E9F:G;HK ?L ?MEUCO!@NBTFWGXHY EWIZJ[K\M^N_ O`-KY"Pa#Qb$Rc%Sd&Te"Xn)Wh#Yo*Xi6Ub&\r‰ª[‚a€Žn}ƒc‚‘^…“TŠ›P‹¢f…“M¬u„ŠG•°V‘¨mŒ›U—³oŽsŽ˜†ˆ…g“¦k“ Yš·‚Ž^š±l˜«]žºŒ{– …”š‰•–g¢¹“•’m£´•–“‚§k¦½z¡¯n©ÀŽž¤t©»˜Ÿˆ£­q¬Ã€§µœž›ž Œ§±u°Ç„¬ºw²É ¥¨«µ¤¦£~³Å™¬¸˜¯´’±Á‚¸Ê‰µÉŸ¯¶«­ª¨®°‹¸ËŒ¹Ì¢²¸ºÍŽ»Î’ºÉ¼Ð½Ñ²´±’¿Ó“ÀÔ´¶³²·ºšÂЛÃÑœÄÒÅÔº¼¹ŸÇÖ¥ÅÕ É×»À¡ÊØ¢ËÙ¥ÍÛÂÄÀ¬ÌܧÏÝÃÈ˯Ïß´ÐÛÈÊǶÒÜ·ÓݸÔÞ»×áÌÒÔÅÕÜÑÓϾÚåÀÝçÂÞéÔÙÛÆßãØÚÖÏßæÑâèßáÝÔåëÝâäáãà×èîãåáÚêñÜìóçéæÞïõêìéâïðçíïåî÷ëîêíïëåòóîðíëñóîóöñóðòôñóõòðöøõ÷ô÷ùöõúýùû÷÷ýÿûýùüÿûþÿüÿÿÿ!þ(C) Christoffer Jerkeby 2007!ù ÿ,22þÿ üÄÌš:{âI˜N‡uÖq3QŽ7rÖÈÉÈFÇÍ”8Pˆ%X§`­Z¹ŠÕÊS)Y¶\©²fMš«`é„Ū§KX Œ²r¬X;[²še4R›¼û°®QonPÒåëµ®_ݹþ¿ní ¼0{ûøùË— ¼¯ð§ßÇßë×¢976ãþ«ÿþïûýÌ€º¸ß8ûø“ ?þ˜ó_¿sê² pÜ€‰1v( 1 Ó!0"’H¢4 ¦È`>æ€è¡‹ #Ì0‡Ì(2æ¨#11ÆH ããå—ÆcÌ0ºðÁ‡8`¢Œ2Ã(cŒ3mãŒ2b®Ù&2Ç(ƒ 2Z ŽlÎ)g"LfXÊ1Ëäy žt³æ1ˆæIç£Þô© ?üx“(žÄÐ sœ9¨4³&2ʘºæªÊÌÙ*2þ®6ƒÌ8–®ç7ÎÌé 2£ÀñF¡7¤’ë°ÄÛª3ǘškªÍ4SN­ f³k3¬ÌÇ™¢’šk3Ë4ãÌ2ËÀú-4àBcn¹æšk´þH[ɵÖ[Ê2é.ͽàFÓ 4ú6Ëo³èBƒ´û°Âäo„Šf+Ò\Óì4Í8< Ä 73qÅOlq3Ò¼­>—\[(†7”zÍ5_SN<ñÈó;ñ°ó:æ¬SŽ9ìÈ,sÌêäci‚ø\‚­Â£¦‚ò4ÕØãs> &¸4ƒ ª·´Óìîc$#g˜ÊÄØÐÊnŠ>Ýç>ú@’p¶²tƒ 6 Š­eÛ_çcÏ"À¦ÒM5ÝÀíöþÞ*ú<Ï!¢–œÍàú¤ÈÏáüè£øâŒ7Þ8>ãsÏ=öT>9å’ <Ç ©€ãM7åT.O>òŒnz騧®zé,·Ï<ðÀÃò:ëTrF·Ë€J6ÝÐÂG5±§<<ÂÃãN;ȧ£üòç49Î7ŸN8´7OŽ"cŒFö/È’ 1g„¯Š6á”oþùá£>9ß|£~ûé³ßþüßpó6€Æþ`Œá‚,ÕHƒöô†ð€DàÁ m8𤆲 /€¡ `ƒ R¡‡.x! ^°`½àÁÐ YHaB˜….d¡Ô°† gHCfä Y°tx…,¬` þbƒz˜C+ñˆT0"À@1`á Vb!žÁ jT‘XÌb1Ð@…*<¡ Vðâ¦8Šal¢›ø*Pá TxBÝØFA0#xÌ£yñ…9ÆQ nd‚JP‚'8Áq”£"Û(G%´Q L@”ˆ`ì"¼(F&‹QŒ`ãV ‚@Ê#Œ G@‚DpJTá•°t%*K©„T®¸Ü….qÁK\’‚ Dp%^I„a¦ò"€e*•y„"–EB‚I„!`ÂØ|…6µI Sh AçÆ9„p¡œAøÀÈyNvšÓœèôA8¿` St³žøþ$…#ŒððÀ?øxPô ?à€‚P€ös  èz0Pƒî€[ )ìÀ6ø)nÀÔ •©8°Á .`ä”M•ê h`ƒ`•©[åª ìÀˆ²>‚°RkpØ`n} h@ص®¨€[ájÔ@®2 Á lØÌÀ°‡µÁXBA°2@Á dð‚ÉÚU.xA 0 L /@aãj×dÖ˜¬fQ€¸@ˆþmeY+Ù2º Œ+@Á T‚¨à·*ˆÀB[FÖâö·»MrS°‚檠¹»Ý-py»œ`'H p{t7%h€À«‚`×%HÁw™{‚l÷ÛÁ*K0‚ €&ïô‹Luz °: €úŠ À"Aì_uXÁð@„Aà W¸Á–°…7lá (±:b``à€B3à dàÅØ8× ¼ôÅyÅ€0` \àÿˆÀ0àã!k <æq-`c `€ÇCv2(`%÷˜È¨@ªlDÀ˜R€ X @³€¦<0OàÍZv@$ ÌYo†@ Àg=CÀ€n@0ç?; !ÀÀç:Ѐ–³í0  Èt¦ é8@N@ $À ™ 0€`@b-k¸ZÖ¯vµ®qÀÖ¶Þ5ê;fai-3.4.8ubuntu5/pixmaps/fail.gif0000664000000000000000000000517311562212376013603 0ustar GIF89a22çÿ ! % ) * , - . / 3 6 57 8<9=>@FBGBHIJKLPMRUTL[WV_fJ'&aT$$hY#&ii Q()k`##l T*,s [*)o"M02a+,v"#g)(} x$$a/.€#"k,,g/0ƒ&$„'%j23]87l2/Š%'Y;?Œ<;ƒA@hONž8tMKoPQzMM“CAmSS˜AByQPkXU A@}PP™GE€RS¤DCwWX GH„UVr_\†XX‰ZZ¨OOxdbŒca«WUtonkhvxu•ki|wv°cb¢jg´gf}|ƒ~}¶ih˜vw²ln¨qs´miƒ…‚{|…‡„‹†…ªyy•‚„¡~€‹Š•‰‰°~~¥ƒ„Œ»{z’Œ½}{¾~|¥‰ˆ©‡ˆ’”‘Á€~¨Œ‹‘‘€©Œ•—”š•“ă‡ƒ¾‹‹šœ™ÃŠŒž›¡œ›ÆŒŽ¦š›ÇÈŽÅ’’Ç““¢¤¡É••¤¦£©¤¢Ê––¥§¤¯££Ì™˜©«¨®©¨Ïœ›«­ªµ©©Òž­¯¬Ï¢ ´¯­°²¯Ò¥¢³µ±Õ§¤¾±²Ïª«¹´²Ô¨«µ·´Ö«®Ó¯°¹»¸¾¹¸¼¾»×²³Á¼ºÙ´µ¿Á¾Áÿܷ¸ÆÁÀÞ¹ºÎÁÂÄÆÃËÅÄܾ½ÆÈÅÈÊÇàÂÁÔÇÇËÎÊÑÌÊäÆÄÎÐÌÓÎÍæÈÇÐÒÏãÌÉÙÓÒÔÖÓßÒÒÖØÕéÔ×ä×ØÜÞÛâÜÛÞàÝíàáåçäëåäðãäçéæóæç÷êêíïìóîìïñîöðïóõòùóòõ÷ôý÷öÿúøÿüûüþûþÿüÿÿÿ!þ(C) Christoffer Jerkeby 2007!ù ÿ,22þÿ ü÷ÂÊ™6p*„ó¦á›6#¶IC1Í™‹ÁhܨÑË—oì‰D²¤É“(Ob‰eË•/[’D”h ’–”Vê¤ÄsRÏI;{ê„Ére ¢2wFj$PÐЧP£êœä¨ÎMQsæÄäè‘QŽ>¢v”Ù³gÉ’Å´ +Û¶cãnŠ«v“XLfÙ^ð"vÞ»O#ùŒí\¼‡ã5ûéÓ\±|<Ì)L¹rå¾–ÏbFk&³¦Îš mÖš±³¡,£ êlkS©¤™M…ªö¨Ð‘’€”JUªßªT­Z•*?}Ç~§2U»¶oßÊ£§jõŽß¹UÏ{ƒJg ˆBćþÃÚþÛ¸¿~û–µÎ~|xöða½ëçoß¹TÄaá%JˆB°´¢ß,³À‹8ôWß2©h (¡¶¼ãÏ…žó ,«¨±„wŠ@h „âðƒáyè5!°¬¸b.b˜`9þÁÄ!(bK.»Øâ#8 ^h"}û“‹Gî¸c.GîBω&Ög].¨D±„• <’$“ĸs¢‚¢Í.»ðÈd“¶#?Q‚‰á2l,‘ÄL„°™»S&1O~f?ú4SfžyÚ’§;üùå>âðaå•Þ=BŒžyã‹1}úyž>ÖZ)Ÿmú¹8|x#!H:©¥«.c¦þçñ“5«sŒ<°† ŽI0)–’ # 1ÂøŒ1À¸ k?ÇY#ì2ô(ê§5q>#ýóIcB&ÙXcMÖ¾˜1±ÐK0íô…úð:±À¾ )–d8ݤ¢6À7Ò±Óý^ÛëþÏ×2!ðœI| 8n;ò÷ßØ Îù4ž>GžÏ=ì ÑëáF‘„~oî÷•ˆ#N ËÙ+FöãÌcÏëöÔ#û<´»>:–«.„ê™ïîûîTrN(šÿ¾ûæ™Q<Ì7ï|;î´=<ã„q¼ï½co„•³{A¤î;øBtÁM;뤿N:鳟Ž:ëÿ6aáø>ðÀÃýA迃ŠÀ‚8ÀýåoWÐÆ8Ô¡Žq,Ð ‡9È1rX°‚ä˜Æôg@ä <Øþ0 rð„ú»Â4ÆŽ’£…0¬F5ÂñÖ†ØG2°Âúpþ>¼8øA‚pT`Æ5¾Qk\Ôa5˜‘*$C†QŒF«`4`£ ÆÆ \ Œhã†h8£plã0²Æ&ðBÑH•¡ ="NpÁmà‚B aÆC>aɈ¤$#‰ŒdÔâ +p \ðY$£¿ød1F ÊW4á†Üd!%¤À)ˆ%'qÁ‹_ز¸Ô….zñŠ'œ@2HA Zð„W𢷨….jÁLf–â¿àn0FWÜ€“•-^ñþaŒ. Ä(ö)ÈZâû¸ H@‚œ/ È (²’Å:yÆÿ€Üä*+VÈSN´œ€(ÖËZ.€˜™\(ˆm?™`` @lÙÜe  Ëb³¬+f;ßyzŽ- ­;èB`ÂoI”8úÑŽ´¤'MéGƒ$ ;fai-3.4.8ubuntu5/pixmaps/minor.gif0000664000000000000000000000514011562212376014006 0ustar GIF89a22çÿ& .5 7# ;!;% ?$ A&D(G* I,K.L/P-O0 N0S0U1X3Y5\6`9a;W>#b<]> d=i<j=g@\C-dC%oAbG,hF#_H7]K8tEuFeK5mK,~H`PA{JpN)eS?^UJbSJƒLrQ7vS4‰QT,lYFl[MU}Z:‘X"uaH˜XŽ[/›Zmf_ž\" ^$‰dDtj_‚fOa$¤a mol˜d7§c"œg4jJ‘kE©e$o`{sm±f'“nNuwt­i'wxv—pJ³h)ŽrZµi#·k%­n1šsM™sS¹l'ŸrN¦qC‹xi»n)}|œwV—y[¼p1~¾q+ŸyX¹s2…€Ás&¯wD¡{ZÇr(Ãu'Ãu/œgÅv)¤~]…‡„Ëu+’†u‡‰†Ìw-½|>Ïy/±VŠŒ‰Ñz)Ä}B¥†hŒ¯‡`Ö~,Ø€/‘¢’”‘ÁˆSÛƒ1”–“±’s«”y¡–Š—™–Úˆ;ª”ÏŽUÝ‹D§š‰´–}œž›Æ”h¥–ž ¸™€Ÿ¡žÞ’H³‡Ã™q¶žƒß“Qµ Š£¥¢¸ …½ž…Öše«¥¤¦¨¥Þš[à›UÚa¨ª§Ì¡y°¨¡ª¬©×¢pͤŦ´¬¦·¬ ­¯¬¯±®À¬œÕª²´±ä§qæ©s¹´³¶¸µâ­zå®uܱŽ¹»¸æ°}ç±~Àº¹è²鳀괾À½éµˆë·Šä¹•Õ¾¨èºŠÂÄÁ黋̵꼌ÌĽ꽔뾕ÇÉÆíÀ—ãéîÁ˜ÊÌÉïÄ ìÈ¢ÎÐÍìÉ©æÌ°ëÊ°îË«ÑÓÐãνðÍ­òϯÕ×ÔéÒ»ôÑ°ßÖÏòÒ·ØÚÖôÓ¸õÔºÚÜÙñØ»ÞáÝóÛÅàâßòÝÌ÷ßÈ÷âÐçéæõçÔûåÔúçÜøíàîðíðóïûðãüôìõøôøú÷ÿúùûýúþÿüÿÿÿ!þ(C) Christoffer Jerkeby 2007!ù ÿ,22þÿ ü÷!ˆ–3l*<ðaC1Åh‘¨¥¢ÅŠT2jT2dà@”‚ùòµëׯ‘»|™ü•r—Ë—.ƒí ¶r¤Í•'Q¦4ð„J“Åp]´˜Ñ£F Å™“©Êb¾ŠéZ$pS1aŠÊu+×­Áhþ T)Ò³W³ V4Õ?º’]-–¬®\ºvï¢Íʵo_£\ç 36샕eÅ–)Fš 1cÅËŒI6²eË’/«» „œgG'3y2Rˉў]|ú($~Œ=›M›¶ìÚÍr‹®Í»öíÙÍj#‘ìßÏ/Km6´lîêÕË—¯Þ¼sÍ{×ÎN»” ’šþK«- ZvñЬ½Ë×Ï¿÷ýøõ›OÜöíÍÍk$(…$iÖ˜ €š`€ç¼ç?óÅ7ß‚ òC5Ô”'Í…( 5™ò$Ô@C͈!Rc …"ZS{¶è"„ü s ‰&Òx‹‡ýqrÍŽ<îHÍ5Öì˜|/ a|îð$Ï4ˆ‡à(¥”@9¤‘X.Øž;')e&Ozè_^fd6ô´—e–üøsÎ’×d³ ŽPr’ÍxfcÍè¬é§{ùäiK˜8¦pIžÜ\óM6ÜpCd‘üÌ£Î9꼃O‘ºÃœtâ¸'ß„*8¢¾_‘ôˆÚh£êäób{þüpÓ ¡t¦ ©¤–3ª:j¾(Ï8Úœ3N¨º–sŽ«.¾WN§t~jì7ê€ì8ô´ù">ÒŽ#-¥ßœóÍ8¼¹$ÌŠy‰±åLªŽ6­BJÍ0Ælx 7ë®{8ò`úK¹ßÂn9鞃Î9FJSî“ ÒÈ¥/žÃ¯­èLJ©8êÀSd>üñ‹ã“»¼š¿+€Â:âŒ,q‘êЪ± ¼ÚOƦÀ ;ï¨C37™Xó"?ƬLç“+¶(_'å® É;4¿“弪Ë!y4u ’‡ÕT³³ÏÖ\ïSJ€ ö&ÌÌ;Åä‘âè£Ï{üÜÃ(|ðG j罶þÞwlÃ=Û#¸(yÜA‡áqäaÂÑîèrG|¼aàñØS¹=¬ÄÇãšwîyçÞÄ#úèñ<¢Fq´¡FjíÎ1š¿AǼ>:/ª¿ñëjœþFïo˜¡†ä´c¼èíÄÓÇðf4o h¢Mó½ŸJ:í`Ÿ}:È€ñü÷Íc†÷\€Á䤓N8ä„þXÄFüX€àÏÏ_¾!á¬ßMûÝè°p…*`¡ R `x@)l"€  3¤@Á"P @Á)XÀ*`ƒØèF?Š Já ¬ ÑŒ¶°…Ñžð$ ¡ Ô€hHC H†þ³Æ ±ÑBe¬á @`’hÃ",¡â  `èDpâÀ h_« e?@b¾øÄ5ÃŒR.€A"`±Žu‚$pG;Ú?xÅ{‹^ôBŽŽøA~@„0Ò‘GP.&™‹IâB~Ø&7yMZàDؤ(wÐ…Kš2«ˆE,"‘„Üà®ÌT1ŠU¤²–« Å(\ùÊ^ö’€¥0}yBèR—¨ …2uIˆ1@a p¨Ä'Ž9ŠOXó˜P `ƒpӛݤ@fàMpr“›<&F1 vŽ‚î´&&AOxÖÓž“þ¨Ã6·yNÌ`+ üIP® +°"QD‚¡…ˆ("&ÚЈ6øC!*A˜` ©GS° (`ý(Ja`–šà @DdšQ™b¦iÐhnzÓ?¤!*õ¨GA R8(EiJ=ªT4!§;MƒT{ U©îAªRÅA 8À”`åj@À  «]Ý*X;€V®«pk\€®‚Uè€^; èõè+^ý:Vô•­à œ0…4Lá±ì¢``@ À,°În6³¨À° à•(mJ[ÚÌV !°þŒ0…ÙÒv¶>PA*Y ¼v€p›Y ˆ3¼õ-&À[àw¹Â.<0‚Xw#ÈÀ¢+\@@p€x Ü<P@  <@€Àxà€ Ä÷¼çõ.{Ѐð÷¿°xý«ßþ.€¿NÀ? pàÁppàÿ&@Ž°6Ü #à HÀ‡Eœ€  >Œ&öð‹[œ€àÅ5>q‹_\€#à(À@ @ÈÀ@`€ß8Èèq”`€$ È r–…<€+ ÉG&®,d|ðˆ$@ @ä. c†³ Ðd1‹yËDs—ó¼ç€È@³G;fai-3.4.8ubuntu5/pixmaps/bar.gif0000664000000000000000000000010711562212376013424 0ustar GIF89a2€vqoÿÿÿ!þ(C) Christoffer Jerkeby 2007,2„©Ë;fai-3.4.8ubuntu5/pixmaps/warning.gif0000664000000000000000000000510711562212376014332 0ustar GIF89a22çÿ*)0. 40 8/ 85:6<8 >: @;A<B=C>D?F@ GAHBICJDLFNGOHRJSKTLUMVNWOXP[R\S]T^U_UaWbXcZe[g\h]i^j_lambncocqeoe$sftguimg>wjxkzmypzm'{n }oxn4~pq€r‚sƒut-w(„v y!‡x"ƒz#Šzƒ|3Œ|ˆ~‰ Š€!~"‘€$Žƒ%„Œƒ3‘…’†“‡ •‰#ˆ‚p—‹%”Š3˜Œ&™'…‡„!’‹aŸ‘#‹Œw–L ’$•Rœ‘:¡“%¢”'Œ¤–(¥—*¦˜+£—9¨™#—’~©š$—Yª›.¬œ&­'”–“®ž(¯ *Ÿ™…±¡,§Ÿ[²¢-´£%µ¤&©¡\·¥'¯£Kœž›ª£^¢ †©£d¸§)­¤Y¡¢Œ«¥f­¦g»ª,¼«-¦¥Š®¨i½¬.»«>¿­0À®1¥§£Ã°*«ª´ªx³­mŲ,Ƴ-²Eµ°vÈ´/«­ª·²x½±y̸3ι+¸µ½³€»³‡Ïº,ɹK¿µƒÒ½/Ô¿1ÕÀ2ÖÁ3ÓÀDÒÀK×Â5Á½›ÛÅ.ÚÄ7ÝÆ0ÞÈ1ÙÆRâÊ5ųãÌ6ÔÈuäÍ7ÉȬæÏ:âÎRéÑ2×ÍÖÍ…ëÒ3ìÓ5îÕ7ÐβËÍÊêÔPñ×:òÙ;óÚ<ïÜ=ôÛ=óÛGìÝWØÖºÓÕÒñàRñá[ïÞvòãdóåmíá“ÛÝÚãß¼öãtñâ‡ÜÞÛôãóæuóè~ùæ~óé…ìæªøè†áäàúé‡øéëæÄãåâùêŽøê•ùë–÷ëœùíøî¥ùï¦÷ï¬ñíÊêìéùð­÷ð´úñ®øòµùó¶÷ó¼øô½þò½÷óÐúóÊýôÅòôñü÷Ôúûäÿùäÿûëùüøÿüíýüóþÿüÿÿÿ!þ(C) Christoffer Jerkeby 2007!ù ÿ,22þÿ ü§#ŒB*\ˆÐ ?õHœ(ÑŽÅ‹vÚp8PƬlÛº…ìF’䶓(SŠDYråÉ’)·aËõ§ã4oÛpfs 2fJœÞ‚âôÙ3ÈlANC$p–HoFà šÔ¨Õ?©j­ê¤.‚R‘vºÓªØ­hµv®ÛT_Â…'U\6¹ãÄÛ+N®Ô ~‡»+X®^o†ýZ诸¾y³õ ü¸òãr’1‹+Ù®gÊŽ++3RÈr¹rzQ[6}:µ^»¨É‰“=î´mت³["iïéläjs¶M\²7zø’+¿gn\präZ?†þx/¹fÁ’X¢>ÛyìÕÓ¡þëóG¾¼?tÏùž†î:ôpƈ1ÙîžzýûîË7O}ýrÿݧL1Ä$Ñ 9æ˜SŽ9B— ƒ*Ý9ûñ‡Ž‚Ö'¡{×L0Fd‚à9äx‰’hΉ*Vh;ç$á‰+²xÎ8ÁxXLž\x:?®ˆÎ'ú¸â:æôÃyïÄhÎ…®˜à‰ÊS LdbÎ:çp¹—'~f—N*¹$<4~©æšëXó¡‡zÂæœt~ébyï¨9$ÖXÌ0Å€ØIk²³Ž¡‡Ú¹¤?ð Z§4Á˜c¤<²c¨¥‡Zªi¢˜Zj&õdª©¦æ3Œ‡€*_&›Žêª«þë´s'yõ8z);ZI œ9&!Ê;ì¼Óè;Äûª¥ò°ó©yµÊ#O£æ¸©09 “j FˆO²Û:ëí·íÐ5R>‹²“ 7ÒC  ‘“#¯;Šò¬³ñÔ<ñ¼“Í2:ã.1÷,ºL0Öúù®¤Å¬*ÈSO=ßÊsŽ4WFj¥•9¼$¿9J µÄ¨úòp<×Ú§0WJú1Æóg ËVügŽ€*Œm')?¼Î›Äª¿0 ¬ãÑí=²ŽÙÖCÊãýñ‡ Oúî<ûìã=öh /AƒM /`ó² .Ä첋ټØRD'ôÐ3Ï4¸½¶Ú¼ÔËþÙ¶ô×€s}Ë.°ÐKá¶nøá…+‹ŸÌ33¶¾øá´°’¹,­ÎÊ7ê„.º:·°’Š+¨»rz*¬°ÒJ묧º ‘?#{릛ž ,©´"û*¹GÎðăóŠìÈ'¯|ò›àÐ <Ë3ŸÊ)²oRJ*› CÍöÐ@³=*¥l"þ&£o~ùãÿB$§Œ‚~úâ»O ü›ø’Ìýø' %§PÒÈ)hÄ&ØÿþcAüÀ2Œ  Q‹dü€#Áˆ 6¢ƒì GˆDP„!dÄ!FÈÂ=¨"0Œa,*qC¢††¸Ã!jÈÃ=Üá‡þwÈ V°Ãîawð!ñ Êá‡rpÃ"¤è7Èá‰u¨Ã²¸E.ºán¨Ã£‚lq‹p¨ÃÇXE9ÀV¬"AÇ:úÁ hpƒЀ†=ªá h`Ãþx†3€Á gèÀ þÈÇB2 `8ƒ †7Ò À„&7‰ 1á Yƒ(ÁJQ†2 §ìB4‚Qš’”¥ìBdJUv˜p„.w)†Y¢ò—Mø%*ƒ™…(X! A°`+`a™` fºÐ„`V³štèƒ6·Ù‡+D¡šVç7›ðÍ(”óš A5ÏIÎu’Ó˜ælš°†8Øóžqþ€9™pÍ&ðÓŸÕd‚@™°&@€Nh*Pò“L ÂB!J„"x¡ Íh€P!! I(‚HG:!x4Cð‚‘’´)5©Dq@„’ UЂNwª àÀ8ÀAv°ƒõ¨5ÈA ŽŠ€ ð <àPk@Õ£Õ¨4¸*€ ƒxõ:¨ b0V¯²à1€ f0¼4X ššVÄ€uA Vpøõ¯,X\ëW·¶€/`A ÛVMdW `€¥¬ $›‚Êf²•í¬ \@‚”–$(ÁH ‚˜ ¨þ-jaK‚\`¶´m v;ÞŽà·ÀÁX+‚ à @î ‚æ.7¹Ø6°HÅ•îr—KÝ x€ºà€xÅÛ]P×¼Ýí®4°õf`/6@ü#½Èoº{ \à¿0.` ØÀ°$ 3øÁp\4Àpð6Ìá xà ˆÀ†EwxÄ€À<@XÒT@à x€À€ôx r€Üã,  P@°d  KN@P€)?öåÈ?@Œc0àË^³“ÅÌ ™È>öñ ¿Ìã/+ ;fai-3.4.8ubuntu5/man/0000775000000000000000000000000011562212376011265 5ustar fai-3.4.8ubuntu5/man/fai-statoverride.80000664000000000000000000000101611562212376014624 0ustar .\" Hey, EMACS: -*- nroff -*- .TH fai-statoverride 8 "3 Sep 2008" "FAI 3.2" .SH NAME fai-statoverride \- dpkg-statoverride for multiple files .SH SYNOPSIS .B fai-statoverride FILE ... .SH DESCRIPTION Override owner and mode of a file or directory. Calls dpkg-statoverride with multiple files. This command is idempotent. .SH SEE ALSO .TP \fIdpkg-statoverride\fP(8) .P .br This program is part of FAI (Fully Automatic Installation). .SH AUTHOR Thomas Lange fai-3.4.8ubuntu5/man/fai-debconf.10000664000000000000000000000332111562212376013503 0ustar .\" Hey, EMACS: -*- nroff -*- .\" Please adjust this date whenever revising the manpage. .\" .\" Some roff macros, for reference: .\" .nh disable hyphenation .\" .hy enable hyphenation .\" .ad l left justify .\" .ad b justify to both left and right margins .\" .nf disable filling .\" .fi enable filling .\" .br insert line break .\" .sp insert n+1 empty lines .\" for manpage-specific macros, see man(7) .TH "fai-debconf" "1" "23 September 2008" "FAI 3" "" .SH "NAME" fai\-debconf \- set debconf values using classes .SH "SYNOPSIS" .B fai\-debconf .RI [OPTION] " DIRECTORY" .SH "DESCRIPTION" fai\-debconf reads files in DIRECTORY which are also a defined class. If the name of the class is a directory, all files in this directory are read. The files must have the format of debconf\-get\-selections(1). All this input is used to call debconf\-set\-selections(1). This is done in the chroot environment, if the variable $ROOTCMD is set. After setting the debconf values, dpkg\-reconfigure(8) is called for every package which is installed and for which some debconf data was set. .SH "OPTIONS" .TP .B \-h Show help, version and summary of options. .TP .B \-s Skip reconfiguration of packages. Only set values in debconf database. .TP .B \-v Create verbose output. .TP .B \-f Run dpkg\-reconfigure for all packages FAI has information on, not only for those whose database entries were modified. .SH "SEE ALSO" .BR debconf\-get\-selections (1), .BR debconf\-set\-selections (1), .BR dpkg\-reconfigure (8) .br This program is part of FAI (Fully Automatic Installation). The FAI homepage is http://fai\-project.org. .SH "AUTHOR" Written by Thomas Lange fai-3.4.8ubuntu5/man/setup-storage.80000664000000000000000000004141711562212376014167 0ustar .TH setup-storage 8 "June 29, 2010" "Debian/GNU Linux" .SH NAME \fBsetup-storage\fP \- automatically prepare storage devices .SH SYNOPSIS .br \fBsetup-storage\fP [\fB\-X\fP] [\fB\-f\fP \fIfilename\fP] [\fB\-d\fP] [\fB\-h\fP] .SH DESCRIPTION Using FAI disk_config files, \fBsetup-storage\fP computes effective partition and volume sizes and executes the necessary commands to configure storage devices. It manages disk drives as well as RAID and LVM volumes. It handles all file systems supported by \fBparted\fP(8) as well as ntfs but is flexible enough to be extended to further types as well. Once the storage devices are prepared, an appropriate \fBfstab\fP(5) file is generated. Without the \fB\-X\fP parameter \fBsetup-storage\fP runs in test-only mode and does not execute commands other than writing disk labels to a blank disk. The exit code of \fBsetup-storage\fP is 0 if all operations were performed successfully and non-zero if an error occurs. .SH USAGE To enable the use of the new partioning tool setup-storage you have to set .IR USE_SETUP_STORAGE =1 in the according class file in configspace (like /srv/fai/config/class/FAIBASE.var for example). .SH OPTIONS .TP \fB\-X\fP Really write the configuration to disk. Otherwise \fBsetup-storage\fP runs in test-only mode. .TP \fB\-f\fP \fIfilename\fP Normally \fBsetup-storage\fP selects an appropriate configuration from $FAI/disk_config/ by picking the first class from .IR classes that has an existing file. If however \fB\-f\fP is given the configuration in \fIfilename\fP is used. .TP \fB\-d\fP Enable debugging output. .TP \fB\-h\fP Display the synopsis and version info and exit. .SH ENVIRONMENT \fBsetup-storage\fP will use the following environment variables: .TP .B disklist The .IR disklist variable must contain a newline separated list of disk drives available in the system. Their order matters as they may be referred to as disk1, etc. in disk_config. .TP .B debug If .IR debug is set to a non-zero value all actions and details to track the operation of \fBsetup-storage\fP are printed to stderr. .TP .B FAI The location of the config space to find the disk_config directory. .TP .B classes The list of FAI classes to determine the appropriate configuration to choose. .TP .B LOGDIR \fBsetup-storage\fP generates disk_var.sh and fstab (see below) in this directory. .TP .B flag_initial This variable determines if partitions should be preserved when they are tagged as to be preserved. Normally set by the list of FAI flags (FAI_FLAGS). .SH FILES If \fBsetup-storage\fP executes successfully, an \fBfstab\fP(5) file matching the specified configuration is generated as $LOGDIR/fstab. Furthermore the file $LOGDIR/disk_var.sh is generated. This file defines the following variables, if not yet set: .IR SWAPLIST , .IR ROOT_PARTITION , .IR BOOT_PARTITION (which is only set in case this resides on a disk drive), and .IR BOOT_DEVICE . The latter two describe the partition and disk/RAID/LVM device hosting the mount point for /boot. If /boot has no extra mount point, / is used instead. You may source $LOGDIR/disk_var.sh to get the variables set. .SH SYNTAX This section describes the syntax of disk_config files file ::= EOF .br lines ::= EOL .br /* empty lines or whitespace only */ .br | EOL .br | EOL .br comment ::= #.* .br config ::= disk_config lvm( )* .br | disk_config raid( )* .br | disk_config cryptsetup( )* .br | disk_config tmpfs .br | disk_config end .br | disk_config disk[[:digit:]]+(