I just switched OSes from Windows to Linux, and set up my new Linux install to use BOINC. I've still got a decent number (more than I want to just let "time out" and let expire) of packets on my system. Is there any good way to take the packets for SetiBoinc from the Windows install of it, and migrate 'em to the Linux client? I poked around in the files, and it looks like maybe copying the packets over and then moving the appropriate sections in client_state.xml over might do it, but has anybody done it and care to tell me if it will or won't possibly work? (And yeah, before anybody gets mad for me packet whoring the servers, I also recently dropped my days-to-precache number now that I don't need to ride out weeks of server downtime. I'm silly like that.)

> I just switched OSes from Windows to Linux, and set up my new Linux install to
> use BOINC. I've still got a decent number (more than I want to just let "time
> out" and let expire) of packets on my system. Is there any good way to take
> the packets for SetiBoinc from the Windows install of it, and migrate 'em to
> the Linux client? I poked around in the files, and it looks like maybe copying
> the packets over and then moving the appropriate sections in client_state.xml
> over might do it, but has anybody done it and care to tell me if it will or
> won't possibly work? (And yeah, before anybody gets mad for me packet whoring
> the servers, I also recently dropped my days-to-precache number now that I
> don't need to ride out weeks of server downtime. I'm silly like that.)

Hi,

As far as I know the machine and os that was allocated and received the workunits must process them, I believe this done to reduce the possibility of people cheating on the credits.
If the windoze install is still functional, you could reduce the cache size to zero by setting the number of days in your prefs to zero, manually update to download the new prefs, crunch the units that you have cached, then fire up the linux install, remember to set your prefs back to whatever they were, and update again.

Ta Ta

---

Ken Phillips

BOINC question? Look here



"The beginning is the most important part of the work." - Plato

Yep, my Windows install's still bootable, woot for QTPartEd's NTFS resizing :) - Thanks, I'll do it.

---

> I just switched OSes from Windows to Linux, and set up my new Linux install to
> use BOINC. I've still got a decent number (more than I want to just let "time
> out" and let expire) of packets on my system. Is there any good way to take
> the packets for SetiBoinc from the Windows install of it, and migrate 'em to
> the Linux client? I poked around in the files, and it looks like maybe copying
> the packets over and then moving the appropriate sections in client_state.xml
> over might do it, but has anybody done it and care to tell me if it will or
> won't possibly work? (And yeah, before anybody gets mad for me packet whoring
> the servers, I also recently dropped my days-to-precache number now that I
> don't need to ride out weeks of server downtime. I'm silly like that.)
>

I've never tried this, so use at you own risk, but see
http://setiweb.ssl.berkeley.edu/forum_thread.php?id=2653

---

Another possibility.

Boot up windows and use "boincview" program to "error out" each of the WUs.

If you run boincview, you can see a list of all WUs on the machine(s) you connect to. There are command buttons to pause, resume and cancel individual WUs.
When you cancel, it creates a pseudo-error that is reported to the server, (as if it were a download error for example), and then the server can mark that WU to be sent to someone else.