Installing the BOINC client and manager

michaelrowe

I'm trying to install the BOINC client (and hopefully also the BOINC manager) on Solus.

I followed these instructions for the Berkeley Installer and get to the point where the archive is unpacked and the BOINC folder created, with the relevant files in it. I try running ./run_manager and get this error message:

./boincmgr: error while loading shared libraries: libwebkitgtk-1.0.so.0: cannot open shared object file: No such file or directory

libwebkit-gtk is installed.

Ksysguard shows the BOINC process running but I'm not sure what it's doing. I think that BOINC can run in an anonymous mode but if this is the case I'd prefer to log in and have the work associated with my account.

Any thoughts on 1) what's actually happening, and 2) how can I get the BOINC manager running so that I can see what I'm doing?

brent

I'm extremely unqualified for this so just going off minimal compiling (I have 2 under my belt) experience.

"To start the client manually enter the following terminal commands:
$ cd ~/BOINC
$ ./run_client --daemon
$ ./run_manager"
OF COURSE you are thwarted at the last step. linux is lucy, charlie brown, and the football sometimes.
Is the file libwebkitgtk-1.0.so.0 inside the repo libwebkit-gtk package? Or the devel package? If all answers are yes I wonder if this 'Berkeley Method' had a permissions snag somewhere?

Their 'Building from Source' looked more familiar to the methods of outside-repo packages in these threads. That method, seems to omit 'sudo' from some of the commands so which ones? (This from compiling a couple packages similarly from memory). Seems to tie in nicely to my permissions theory.

As to what is happening exactly when you execute the /run command? It's running in b/g but no GUI?

Also saw a boinc package in Snap.

michaelrowe

Thanks for getting back to me. I appreciate your time. It seems like I'll need to set aside some time to look at this in some detail. I'll respond here if I can figure it out after going through your suggestions.

Also, the BOINC package in Snap (assuming you mean this one: https://snapcraft.io/boinctasks-js) looks like a viewer/manager, rather than getting the client installed. So it seems like it'll be really useful when I get the client up and running.

davidjharder

@michaelrowe Would you be comfortable running a docker container?
Personally, I use https://docs.linuxserver.io/images/docker-boinc becasue Solus does not have boinc packaged and this docker container bundles an interface you can access over LAN

EDIT: Actually, you can get boinc as a flatpak now: https://flathub.org/apps/details/edu.berkeley.BOINC probably easier than docker

michaelrowe

Thank you so much for that suggestion. I didn't even think to look for a flatpak. It's installed and downloading projects as I type.

davidjharder

michaelrowe You're welcome! The flatpak option is very new; I was surprised when I found it.

seasoned_geek

davidjharder The problem with this option is

This is a common problem. Far too few packagers actually test LHC or the VirtualBox projects. Ubuntu has a special VirtualBox package just for BOINC projects needing virtualbox.

davidjharder

seasoned_geek Interesting. I run World Community Grid, so have never encountered this complication with VirtualBox.