There are two ways a client can boot.
1) bootp – Bootp is used when the ethernet card has a programmed boot rom onboard. You can emulate an ethernet bootrom by booting from a floppy disk created from the http://www.Rom-O-Matic.net site. We’ve done much of this for you and have included floppy boot images in a folder of your installed K12LTSP server.
Take a look in /tftpboot/lts/boot/bootroms . You’ll find disk images there for many popular cards. If you don’t see your ethernet card head for the Rom-O-Matic site and download the righ image. It’s easy to move the image to a floppy. Just type
cat eepro100.lzdsk > /dev/fd0 to send the boot image to a floppy disk. (The example uses eepro100 card. replace this with the right image for your card). You can buy ethernet cards with boot roms all ready for K12LTSP from http://www.disklessworkstations.com/ .
2) PXE booting – PXE is an Intel boot protocol often called Wired for Management (WfM). All you really need to know is that there is one file to edit when selecting boot kernels. The kernels are in /tftpboot/lts/pxe and the file that determines which one is used is in /tftpboot/lts/pxe/pxelinux.cfg in a file called default .
The NIC from http://www.thinknic.com and the Intel D810emo Flex motherboard are good examples of products that support the PXE boot protocol. You can make PXE floppy bootdisks from the Rom-O-Matic site too.
With the old version of K12LTSP you had to edit the /etc/dhcpd.conf file to list PXE or BOOTP as the default boot type. You don’t have to do this anymore! DHCPD 3.0 will answer both types of boot requests.
To watch your terminals logging in you can run the tail command on your server:
tail -f /var/log/messages – This will let you watch the log file scroll by as terminals acquire ip numbers and login.
Filed under: Networking