Bootp/TFTP Questions

[stramiello <stramiello@whiterabbit.resnet.gatech.edu>]

Ok, this is the first diskless beowulf cluster that we're attempting here
at work, and I was wondering if anyone could either tell me what I'm doing
wrong, or point me to some good documentation I could read.

I've got a main node running bootp/tftpd. Both seem to be running fine.

<bootptab>
global.prof:\
	:sm=255.255.255.0:\
	:ds=130.207.197.112:\
	:gw=130.207.197.1:\
	:ht=ethernet:\
	:bf=linux:
williwaw:hd=/tftpboot/130.207.197.150/boot:tc=global.prof:ha=00D0B7681CD4:ip=130.207.197.50:

<file structure>
/tftpdboot/130.207.197.150/boot
- contains linux (a kernel of size ~1mb)
- contains vmlinuz (a copy of the same kernel)

Whenever the node boots from a floppy that is set up to bootstrap it to
bootp, I get:

<output>
Loading ROM image....
ROM segment 0x8000 lenght 0x4000 reloc 0x9800
Etherboot/32 version 4.7.6 [GPL] for [EEPRO1000]
Found Intel EtherExpressPro100...
eeprom[6]=4701
Searching for server (DHCP)
Me: 130.207.197.150 Server: 130.207.197.105 Gateway: 130.207.197.1
Loading /tftpboot/130.207.197.150/boot/linux <sleep>
<sleep>
...

And so on with the sleeps.

Suggestions for what I'm doing wrong?


--  
To UNSUBSCRIBE, email to debian-beowulf-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org