For those of you who are used to working with NotFred, I came up with a series of changes that allows NotFred to run -bigadv work units. I'm putting this up as an alternative to the virtual appliances mentioned here. Like a regular NotFred, FredNotFred is very lightweight - it can be run from a USB drive, a CD, or even a TFTP network boot - but unlike regular NotFred, FNF can run -bigadv units. Here are the changes I made from regular NotFred:
- Updated the client install to 6.24beta.
- Added in the drop-in client binary necessary to run -bigadv units.
- Added additional configuration options to the web interface:
- Additional parameters (to pass to the client)
- Hostname (the name of the VM on the network)
- Using the remote reboot script now backs up the WU data files before shutting down.
I'm looking for a few people willing to help me test this VM. You can find the *.vmx and *.vmdk files here:
Give it a shot - try to break it. If you manage to get it to break, post about it here.
A few things to keep in mind:
- To run bigadv work units, put -bigadv in the additional parameters box. Also, make sure that the checkbox for advmethods units is turned OFF.
- The VM is configured to use 5GB of memory. If you have more memory to dedicate to folding, feel free to increase this number; likewise, if you don't plan on running -bigadv work units (for whatever reason), you can turn that value back down.
- You will need VMWare Player 3 to run this. DO NOT use VMWare Workstation - it chokes on anything above 4 processors. I haven't tried it in Server, but I imagine the results may be similar.
- As always when running -bigadv, keep an eye on your temperatures.
I'll keep this thread updated as I make updates to the VM. Let me know about any issues you encounter - be as specific as you can.
Update 2010/01/20: The VM has been updated. New features include a handful of bugfixes, removal of the quote requirement in the "additional parameters" box, and a working updater script. To update, wait for your current WU to finish, then shut down the VM, replace the .vmhd file with the replacement from the link, restart the VM, and rerun configuration. Future updates should be able to use the now-working updater client built into the VM.
Update 2010/01/21: Version 20100121 is now available. Please update your machines. I may post a manual-update script you can download and run with wget at some point later today. For now, please use the automatic updater (which is in an unknown working state) at http://YOUR.FNF.VM.IP/cgi-bin/update.cgi .
Thanks for taking part in my beta! Happy folding!