Thanks Brian, Matt, and rgb,<br> <br> The floppy idea is great (I think I remember now reading about it in rgb's book, but had forgotten), and I certainly will look into that. The motherboards are in some cases years and years old; one computer I'm deciding whether I'll use or not does have a 400mhz processor in it, so their age is sufficient to make me worry.<br> <br> In response to how I'm handling "DHCP/TFTP management", I am ridiculously interested in knowing how everything works, so I install each computer using a method that follows the guidelines similar to Linux From Scratch. I'll likely be using dhcpcd for DHCP and I'm currently looking into TFTP options. If there is a suggested program of choice among you all, please feel free to let me know. I opt for the Linux from Scratch route, one, because I hate going to class and thereby have plenty of time on my hands (hah), and two because the majority of computers I deal with are old and need all
the free resources they can get.<br> <br> Again, much thanks to those who helped.<br> <br> Ellis<br><br><b><i>Brian Dobbins <firstname.lastname@example.org></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> <br>Hi Ellis,<br><br> I wasn't sure from your post whether you meant the nodes had /no/ <br>network whatsoever, or simply no capabilities for network booting from <br>the NICs in the system. If it's the latter, and assuming these systems <br>have a floppy drive, I'd suggest looking into using the Etherboot <br>software to handle network booting. No need to spend extra money. :)<br><br> The webpages will explain more, but essentially (from memory - it's <br>been a while!), if you set up a DHCP / TFTP server for the images <br>somewhere on the network, just create a boot floppy with the correct <br>network drivers for the node, stick it in, power on, and provided the <br>DHCP/TFTP servers are
correctly configured, the node should boot up, <br>initialize the network, send out a request to the DHCP server, and then <br>(from the information handed back), request a boot image from the TFTP <br>server. To create this boot floppy, you can probably just visit the <br>Rom-O-Matic page ( http://rom-o-matic.net/ ) and select the type of card <br>you have, but definitely read over the Etherboot documentation, too ( <br>http://www.etherboot.org/ ). If you're not certain what type of card is <br>in the nodes, I'd suggest putting a Knoppix CD in, booting up, starting <br>the network, and then listing the modules that are loaded - the network <br>drivers should be in that list.<br><br> If you get stuck, drop me a note and I'll be glad to try to walk you <br>through it - I'm a pack rat, and probably still have all the old <br>configuration files from when I last did this, too. Finally, in terms <br>of the DHCP/TFTP management, are you handling that by yourself, or using
<br>some already-written package? The initial cluster that I used Etherboot <br>on used the Warewulf package - I'd recommend you take a look at it, <br>too. The webpage is ( http://www.warewulf-cluster.org/ ). The guy <br>developing it, Greg Kurtzer, is really helpful, too, so if you get stuck <br>in that stage of things, you won't pull out all your hair in frustration.<br><br> Good luck!<br> - Brian<br><br>(Naturally, RGB also helped me out in the past -- anyone know if there <br>is some analogue in the Beowulf realm to the Erdos number for RGB? I <br>can't imagine there's anyone he /hasn't/ helped!)<br><br>Brian Dobbins<br>Yale Engineering HPC<br></blockquote><br><p>
<hr size=1>Fussy? Opinionated? Impossible to please? Perfect. <a href="http://us.rd.yahoo.com/evt=48516/*http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 ">Join Yahoo!'s user panel</a> and lay it on us.