Enable network booting from BIOS and move it above the rest.
Install Ubuntu Server 10.04 LTS or better on a VM (VMWare or VirtualBox works).
sudo apt-get update && apt-get dist-upgrade
sudo apt-get install tftpd-hpa dhcp3-server openbsd-inetd tftp-hpa
Backup and replace /etc/dhcpd3/dhcpd.conf with the file below the divider.
Download the correct netboot package:
etc.
mkdir -p /tftpboot/lucid-64bit
cd /tftpboot/lucid-64bit ; tar -zxf ~/netboot.tar.gz
do the same for the 32 bit packages if you have any older machines.
Boot the PC once over the network. It won't. Note down the IP address.
Edit /etc/dhcpd3/dhcpd.conf and change the following for your env:
hardware ethernet 00:1E:8C:5C:7D:42;
fixed-address 192.168.1.100;
next-server 192.168.1.64;
filename "lucid-64bit/pxelinux.0";
option routers 192.168.1.254;
option domain-name-servers 192.168.1.254;
replacing the hardware ethernet with the PC's MAC, modify fixed-address to a value you would like to hand out to the machine, next-server, option routers and domain-name servers should point to the existing ADSL router etc.
Restart the dhcpd daemon. Make sure inetd is running, if not invoke the daemon.
This step is very critical: PLUG THE FRIGGIN' CABLE TO THE EEE...
Reboot. Enjoy.
Then it's a matter of spending a couple of hours while it downloads everything over the net and installs.
# /etc/default/tftpd-hpa
TFTP_USERNAME="tftp"
TFTP_DIRECTORY="/tftpboot"
TFTP_ADDRESS="0.0.0.0:69"
TFTP_OPTIONS=""
# Sample configuration file for ISC dhcpd for Debian
#
# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
# configuration file instead of this file.
#
# $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $
#
# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;
# option definitions common to all supported networks...
#option domain-name "example.org";
#option domain-name-servers ns1.example.org, ns2.example.org;
default-lease-time 600;
max-lease-time 7200;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;
# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
#subnet 10.152.187.0 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.
#subnet 10.254.239.0 netmask 255.255.255.224 {
# range 10.254.239.10 10.254.239.20;
# option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}
# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.
#subnet 10.254.239.32 netmask 255.255.255.224 {
# range dynamic-bootp 10.254.239.40 10.254.239.60;
# option broadcast-address 10.254.239.31;
# option routers rtr-239-32-1.example.org;
#}
# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
# range 10.5.5.26 10.5.5.30;
# option domain-name-servers ns1.internal.example.org;
# option domain-name "internal.example.org";
# option routers 10.5.5.1;
# option broadcast-address 10.5.5.31;
# default-lease-time 600;
# max-lease-time 7200;
#}
# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.
#host passacaglia {
# hardware ethernet 0:0:c0:5d:bd:95;
# filename "vmunix.passacaglia";
# server-name "toccata.fugue.com";
#}
# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
# hardware ethernet 08:00:07:26:c0:a5;
# fixed-address fantasia.fugue.com;
#}
# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.
#class "foo" {
# match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}
#shared-network 224-29 {
# subnet 10.17.224.0 netmask 255.255.255.0 {
# option routers rtr-224.example.org;
# }
# subnet 10.0.29.0 netmask 255.255.255.0 {
# option routers rtr-29.example.org;
# }
# pool {
# allow members of "foo";
# range 10.17.224.10 10.17.224.250;
# }
# pool {
# deny members of "foo";
# range 10.0.29.10 10.0.29.230;
# }
#}
authoritative;
subnet 192.168.1.0 netmask 255.255.255.0 {
host terotestaa {
# 'ping target_host', 'arp' shows MAC address
# only give DHCP information to this computer:
hardware ethernet 00:0D:56:73:F0:0D;
# Basic DHCP info (see 'ifconfig', 'route', 'cat /etc/resolv.conf')
fixed-address 172.28.1.7;
option subnet-mask 255.255.0.0;
option routers 172.28.1.254;
option domain-name-servers 172.28.1.67, 172.28.1.69;
# Non-essential DHCP options
option domain-name "tielab.helia.fi";
}
host pxeinstall {
hardware ethernet 00:1E:8C:5C:7D:42;
fixed-address 192.168.1.100;
next-server 192.168.1.79;
filename "intrepid-32bit/pxelinux.0";
option routers 192.168.1.254;
option domain-name-servers 192.168.1.254;
}
host foo {
hardware ethernet 00:0C:29:61:01:A2;
fixed-address 192.168.1.101;
next-server 192.168.1.79;
filename "jaunty-64bit/pxelinux.0";
option routers 192.168.1.254;
option domain-name-servers 192.168.1.254;
}
host cthulhu {
hardware ethernet 00:11:11:8e:c6:fc;
fixed-address 192.168.1.102;
next-server 192.168.1.79;
filename "jaunty-32bit/pxelinux.0";
option routers 192.168.1.254;
option domain-name-servers 192.168.1.254;
}
host sheila {
hardware ethernet 00:a0:d1:26:2d:ce;
fixed-address 192.168.1.103;
next-server 192.168.1.79;
filename "jaunty-32bit/pxelinux.0";
option routers 192.168.1.254;
option domain-name-servers 192.168.1.254;
}
host galileo {
hardware ethernet 00:00:e2:3c:d8:5e;
fixed-address 192.168.1.109;
next-server 192.168.1.79;
filename "lucid-32bit/pxelinux.0";
option routers 192.168.1.254;
option domain-name-servers 192.168.1.254;
}
host cassini {
hardware ethernet 00:00:E2:48:07:E2;
fixed-address 192.168.1.109;
next-server 192.168.1.79;
filename "lucid-32bit/pxelinux.0";
option routers 192.168.1.254;
option domain-name-servers 192.168.1.254;
}
host acer {
hardware ethernet 00:23:8B:5A:85:60;
fixed-address 192.168.1.110;
next-server 192.168.1.79;
filename "lucid-32bit/pxelinux.0";
option routers 192.168.1.254;
option domain-name-servers 192.168.1.254;
}
host hubble {
hardware ethernet 00:1a:a0:b8:0f:7d;
fixed-address 192.168.1.111;
next-server 192.168.1.79;
filename "/tftpboot/lucid-64bit/pxelinux.0";
option routers 192.168.1.254;
option domain-name-servers 192.168.1.254;
}
host banu-laptop {
hardware ethernet 00:21:9b:cc:d5:9c;
fixed-address 192.168.1.112;
next-server 192.168.1.79;
filename "lucid-64bit/pxelinux.0";
option routers 192.168.1.254;
option domain-name-servers 192.168.1.254;
}
host minotaur {
hardware ethernet 00:1e:8c:9b:7b:8f;
fixed-address 192.168.1.113;
next-server 192.168.1.79;
filename "/tftpboot/lucid-64bit/pxelinux.0";
option routers 192.168.1.254;
option domain-name-servers 192.168.1.254;
}
host vmtest1 {
hardware ethernet 08:00:27:3f:72:da;
fixed-address 192.168.1.114;
next-server 192.168.1.79;
filename "/tftpboot/lucid-64bit/pxelinux.0";
option routers 192.168.1.254;
option domain-name-servers 192.168.1.254;
}
}
