Memory on Scyld systems
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Sean Dilda agrajag at scyld.comTue Nov 6 08:16:36 PST 2001
- Previous message: Memory on Scyld systems
- Next message: Problems with Scyld
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 05 Nov 2001, Art Edwards wrote: > I have a question about memory on AMD-based clusters. I am now running > a homogeneous Scyld cluster with 768MB on each node. I have modified the > config file with a mem= command and have had no problems. Now I am augmenting > the cluster with new nodes that have 1.5 GB of memory on each node (single > processor nodes). Is there a way to use a different config file for the new > nodes? The kernel commandline is stored in the bootfile /var/beowulf/boot.img By default, this image is sent to all nodes, but if the file /var/beowulf/boot.img.<nodenumber> (ie boot.img.0) exists, it will use that image for the given node. You can create this image by modifying /etc/beowulf/config.boot, then running beoboot -2 -n -o /var/beowulf/boot.img.<nodenumber> Once you've created one copy of the new bootfile, you should be able to symlink or hardlink the other filenames to it so that boot.img.<nodenumber> for all your new nodes points to it. Just remember, whenever you change anything with your bootfiles in the future, you're going to have to remake both files. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available Url : http://www.scyld.com/pipermail/beowulf/attachments/20011106/88b9c747/attachment.bin
- Previous message: Memory on Scyld systems
- Next message: Problems with Scyld
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
