On Fri, 9 Mar 2001, Clay Fandre wrote:
> I found out some more details. It's a ThinkNIC that they're trying to
> network boot. What exactly is PXELinux? We created a custom kernel and
> ROOT-NFS dir structure. We're using bpbatch to load the kernel. We have
> the entire filesystem created under /tftpboot. What does the display
> option do?
pxelinux == linux program to support machines with Intel PXE network cards
(which the ThinkNIC has; that config file was actually one I use to boot a
ThinkNIC.)
You can drop the display statement; that just displays the contents of the
.txt file on the person's screen before booting.
Why are you creating the entire filesystem under /tftpboot? This is how I
have it set up:
$ ls -al /tftpboot /tftpboot/pxelinux.cfg
drwxr-xr-x 3 nobody nobody 4096 Feb 15 17:30 .
drwxr-xr-x 25 root root 4096 Jun 15 2000 ..
-rw-r--r-- 1 nobody nobody 680785 Feb 15 17:30 /tftpboot/kernel
-rw-r--r-- 1 nobody nobody 7372 Nov 22 14:20 /tftpboot/pxelinux.bin
/tftpboot/pxelinux.cfg:
-rwxr-xr-x 1 nobody nobody 201 Feb 15 14:17 C0A8FC37
-rwxr-xr-x 1 nobody nobody 662 Nov 22 14:03 message.txt
-rwxr-xr-x 1 nobody nobody 147 Nov 22 15:53 default
/etc/dhcpd.conf contains:
allow booting;
allow bootp;
filename "/tftpboot/pxelinux.bin";
option dhcp-class-identifier "PXEClient";
option vendor-encapsulated-options
09:0f:80:00:0c:4e:65:74:77:6f:72:6b:20:62:6f:
6f:74:0a:07:00:50:72:6f:6d:70:74:06:01:02:08:03:80:00:00:47:04:80:00:00:00:ff;
next-server <server_with_/tftpboot>;
host nic {
hardware ethernet 00:e0:06:e7:dc:59;
fixed-address 192.168.252.55;
}
when you power on the client, this gives it the ip 192.168.252.55, tells
it to grab /tftpboot/pxelinux.bin and execute it. pxelinux.bin looks for
the config file, downloads it, and follows it.
--
Nate Carlson <natecars at real-time.com> | Phone : (952)943-8700
http://www.real-time.com | Fax : (952)943-8500