Personal computing discussed
Moderators: renee, farmpuma, just brew it!
retro2001 wrote:If those Dells have CD-ROM drives then you can use notfred's Folding CD generator.Do you have any links / suggestions for getting LTSP setup to netboot nodes? I've got about 35ghz worth of Dell Optiplexes sitting in a corner (unused) That I would to get folding, if I can make them all netboot.
Thanks,
Will
retro2001 wrote:Do you have any links / suggestions for getting LTSP setup to netboot nodes? I've got about 35ghz worth of Dell Optiplexes sitting in a corner (unused) That I would to get folding, if I can make them all netboot.
retro2001 wrote:Do you have any links / suggestions for getting LTSP setup to netboot nodes? I've got about 35ghz worth of Dell Optiplexes sitting in a corner (unused) That I would to get folding, if I can make them all netboot.
Thanks,
Will
cheesyking wrote:Retro, any idea what version of PXE those Intel NICs have? I found I had to use V2 or later to get it to work (though they were still picking up an IP so it's probably a different problem). There is a section on etherboot in that guide I linked to, could be worth a look.
cd /fah
./FAH502-Linux.exe -forceasm
cheesyking wrote:Last time I did LTSP folding I mounted the folding directory for that client and just tacked something likeCode: Select allcd /fah
./FAH502-Linux.exe -forceasm
onto the end of LTSP's rc.init script
Real quick, but real dirty
just brew it! wrote:Yeah, I was thinking of trying something along those lines instead of the SSH/NIS approach. But you lose the ability to monitor the diskless system or do a clean shutdown of the folding client in the event that you want to power the node off.
Edit: Also, how would you handle multiple nodes? Can each node have its own rc.init?
Edit #2: I suppose you could just name the directories based on the node name and use the node name to cd to a different directory for each node.
cheesyking wrote:Loosing monitoring is a bit of a pig, though doing that does mean the client's output goes to the display on the node so you can plug a monitor in to help debugging.
multiple nodes are dealt with by mounting each clients' own folding directory on fah, does mean a little extra work on the exports file but not that much.
retro2001 wrote:I've got one of the beasts up and folding courtesy of notfred's magic boot image. Provided it holds together, I hope to get the party started this weekend...
retro2001 wrote:I've got one of the beasts up and folding courtesy of notfred's magic boot image. Provided it holds together, I hope to get the party started this weekend...
just brew it! wrote:cheesyking wrote:Loosing monitoring is a bit of a pig, though doing that does mean the client's output goes to the display on the node so you can plug a monitor in to help debugging.
I plan to stuff the crates into the crawlspace once they're working, so being able to use the console port for debugging doesn't really matter to me.multiple nodes are dealt with by mounting each clients' own folding directory on fah, does mean a little extra work on the exports file but not that much.
How would you do that? I thought it was the NFS client that determines what gets mounted where, not the server?
# specific to each node
/node1 192.168.1.1(sync,rw,no_root_squash,no_all_squash)
/fah/node1 192.168.1.1(sync,rw,no_root_squash,no_all_squash)
/node2 192.168.1.2(sync,rw,no_root_squash,no_all_squash)
/fah/node2 192.168.1.2(sync,rw,no_root_squash,no_all_squash)
# for all nodes
/home 192.168.1.0/24(sync,rw,no_root_squash,no_all_squash)