Pxe boot installation for Ubuntu

On many blogs on internet it says
"If you have the cd or cd image mounted in /var/www/ubuntu, then you will have material for netboot here: /var/www/ubuntu/install/netboot/"

but that is not the case
That is exactly where the problem is the instead it has a directory named casper where it has initrd and vmlinuz some where I read for this I need a Live CD of Ubuntu
in the install directory I have following only
root@tapas-laptop:/mnt/install# ls
mt86plus README.sbm sbm.bin

Just check the following link I downloaded netboot from Ubuntu Jaunty repositories from here
http://archive.ubuntu.com/ubuntu/dists/jaunty/main/installer-i386/current/images/netboot/
they have an image named mini.iso

Finally I found a solution the CDs named alternate have the netboot folder this is what is needed.



TFTp settings on Ubuntu I forgot but had discussed some thing here
http://ubuntuforums.org/showthread.php?t=1331410

I kept in /var/lib/tftpboot the files related to installtion
the TFTP settings for booting via network
Following changes were made to config files


First file
/etc/inted.conf
tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tftpd -s /var/lib/tftpboot
## netbios-ssn stream tcp nowait root /usr/sbin/tcpd /usr/sbin/smbd


Second file
/etc/default/atftp
USE_INETD=true
OPTIONS="--tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=5 /var/lib/tftpboot"


Third file
/etc/default/tftp-hpa

#Defaults for tftpd-hpa
RUN_DAEMON="yes"
OPTIONS="-l -s /var/lib/tftpboot"

Fourth file I touched was
/etc/default/xinetd

# Default settings for xinetd. This file is sourced by /bin/sh from
# /etc/init.d/xinetd

# enable xinetd Inetd compat mode
INETD_COMPAT=Yes

# Options to pass to xinetd
#
# -stayalive comes by default : it can be removed if xinetd is expected
# not to start when no service is configured
#
XINETD_OPTS="-stayalive"




Then 5th file
/etc/dhcp3/dhcpd.conf
/etc/dhcpd.conf
ddns-update-style none;
allow booting;
allow bootp;

option domain-name "www.yourdomainhere.com";
#option domain-name-servers ns1.example.org, ns2.example.org;

option domain-name-servers 4.2.2.6;

default-lease-time 600;
max-lease-time 7200;
log-facility local7;


# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.

subnet 192.168.1.0 netmask 255.255.255.0 {
}

# A slightly different configuration for an internal subnet.
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.4 192.168.1.250;

option domain-name-servers 4.2.2.6;
option domain-name "internal.example.org";
option routers 192.168.1.250;
option broadcast-address 192.168.1.255;
default-lease-time 600;
max-lease-time 7200;
}
next-server 192.168.1.45;
filename "pxelinux.0";
option domain-name-servers 4.2.2.6;
option domain-name "internal.example.org";
option routers 192.168.1.250;
option broadcast-address 192.168.1.255;
default-lease-time 600;
max-lease-time 7200;
}
next-server 192.168.1.45;
filename "pxelinux.0";


A good article explaining what DHCP entries are
http://www.informit.com/articles/article.aspx?p=370627&seqNum=2