Gary Heston wrote:

In article <rMzyf.35779$W4.10501@newsfe4-gui.ntli.net>,
Martin 53N 1W  <ml_news@ddnospamddml1dd.co.uk.dd> wrote:
  [ ... ]

And you can set up remote mounts for the Linux filesystem. This is often done for systems that have just a few MB of RAM. You just need to get a kernel (1 MB or so) image in there to boot, and then mount the filesystem off your central server HDD.

I prefer the ramdrive root approach as it allows rebooting the NFS server
without affecting the diskless nodes operation.

Very good point.

Depending on what you find or how much hacking you want to do, you could squeeze it all in 64MB but considering the cost of RAM and likely future Boinc projects, putting in 128MB looks to be a /lot/ easier!

It's looking like 128MB is a minimum. Depending upon the difference in
price, I may just go with 256MB and make sure I don't run into problems.

I was looking to put together a minimal system. The extra small cost of putting in ooodles (lots) of RAM was very worthwhile instead of wasting my time for working around too little RAM.

Let us know how you get on. I'm sure there's some Linux hackers over in Ars Technica (sp?) that could help.

I don't anticipate any real problems; there are several descriptions on
the web about how to set it up with various distributions; I should have
all the hardware I need (other than memory). Just a matter of getting it
all put together and upgrading the connection. As that involves a hefty
increase in the monthly cost ($57 more) it'll be the last thing I do.

Does the link speed matter much?

You can have it maxed out for a while without problems so long as the data gets through eventually.

The linux kernel comes with powerful traffic management controls that can prioritise what data gets out at what rate over a limited link. Look up "wondershaper". I've done a good few tweaks myself to be able to surf uninterrupted despite multiple concurrent uploads and downloads.


Good luck,
Martin