One issue I had to deal with recently when trying to get the Distributed.net client to work well on the empeg was the disk access. The client requires read/write access to it's buffer files all the time. My solution was to add the following to my init script:
echo "*** Creating Ramdisk ***" /sbin/mke2fs -m 0 -b 1024 -v /dev/ram1 echo "*** Mounting Ramdisk ***" /sbin/mount -t ext2 /dev/ram1 /usr/dnetc/buffers echo "*** Copying D.Net buffers to RAM ***" cp /usr/dnetc/empeg* /usr/dnetc/buffers cp /usr/dnetc/checkpoint /usr/dnetc/buffers
From there, the D.net client is set to read it's buffers off the ram drive, and it works fine. But the main problem is power loss. My solution to that is going to be a timed program the copies the files back to the disk, taking precautions to ensure a power loss during the short copy time doesn't corrupt the buffers. My questions on this whole thing are:
1. Whats an easy way to time things on the empeg via a script file? Best way I can think of is a simple loop script with a pause, but I can't figure out a pause function.
2. Is there a way that I can shrink the ramdrive? It's much bigger then I need it to be for the buffers, but the only way I have found is to recompile the kernel. Not fun if you plan on releasing something that depends on a modification to the kernel.
Thanks, Tom