Making Seti@Home work on a RAM disk, do I need to move the binary?

[michaelsanford]

I've been having trouble figuring out how to make Seti@Home work on a RAM disk (I'm using RamBunctious2 at the moment, other suggestions, like a command-line utility, are welcome).

I have a feeling the only way to get SaH to work on the RAM disk is to mount a disk and then move the entire ./setiathome-3.03.powerpc-apple-darwin1.2 folder to the ram disk? I don't see any run-time flags to move the work_unit.sah files to another location.

I don't think creating symlinks would work either, because work_unit.sah only exists if there is a work unit; once the WU is completed it renames the file to something else and sends it.

Any clever solutions?

EDIT: Does anyone know the exact size the ram disk has to be, anyway? I'm guessing 1 meg would be more than enough, since WUs are only 250k, no?

 

[michaelsanford]

Figured it out, writing a how-to now if anyone needs one (the solutions kind of simple )

 

[Lycander]

This is the command line client you are using right? In that case yes you would need to move the binary itself onto the RAM disk because the input/output files are written to the same directory as the seti client executable.

And to answer your last question:

"640K should be enough for anyone" :-D

 

[michaelsanford]

Hehe thanks Bill

And yeah I moved the entire seti-at-home..... folder to the RAM disk.

I'm not aware of any other clients for SaH other than the command-line client. There's an X11 wrapper, but that's just a wrapper...

 

[Lycander]

There's a GUI one for OS9.

 

[michaelsanford]

Ooh yeah youRe right I remember that. But yeah, it's the OS X commandline one