To include Boinc after the download the Linux - Ubuntu instruction is "sudo boinc" and what else?
Thanks in advance for the help. I only need to install Boinc to start using it on Linux.
To include Boinc after the download the Linux - Ubuntu instruction is "sudo boinc" and what else?
Thanks in advance for the help. I only need to install Boinc to start using it on Linux.
Friends are like diamonds and diamonds are forever
Hey Duke.
If you are ok woth using BOINC version 5.10.58 then you can install it from Synaptic Package Manager.
If you need a version more recent then it becomes harder. Below are instructions I got from Mumps during an IRC chat. I haven't tried it yet, I haven't had the time to play with it.
Anyhoot here they are....
Originally Posted by Mumps
Last edited by Fire$torm; 02-21-13 at 09:20 PM.
I have to ask! Are you using the package from the repository, or the 'tarball' from the Boinc site?
I use the tarball, so that I can use the latest version.
But depending on which you use, the steps are different in some ways.
BOINC Sees it - BOINC DOES it!
Oh my. I used Ubuntu 11.04 "Natty Narwhal" - Release amd64 already and had installed Boinc only with one instruction, that would be something like:
sudo apt-get install Boinc
Only one instruction and the system created the directory and make the others setups, I didn't needed all those instructions, like the mkdir to create the directory, I can understand most of them since it is very seemed with DOS and I used DOS for a lot of time. The problem was that I was writing app instead of apt, I would like to let the computer ready and in use before I go to the hospital this time.
I don't know so much about hardware to make this configuration ( I don't know my computer so well ) that is why I am using Ubuntu that is much more user friendly and capable of assuming some instructions. I didn't updated the Ubuntu also to make this (more simple installation) and would updated it later and the system has to assume the previous configuration.
Anyway I am not ready or have a good head to do this for now, in face of the complexity, I need to be much more logic that I am not this last few days but I can understand most of the instructions. I don't know much of Linux but this Install seems to be for Debian that is much more complex than this version of Ubuntu.
Thank you both for the help and the patience. I will try tomorrow with that instruction and if doesn't work, I will let it for a later time. I will be back to this problem, more rational, I am sure.
Friends are like diamonds and diamonds are forever
Well I remembered now the instruction:
sudo aptitude install boinc-client boinc-manager
Nice, it is written here for me to not forget.
Last edited by Duke of Buckingham; 02-21-13 at 11:35 PM.
Friends are like diamonds and diamonds are forever
I recommend *never* installing the BOINC package.
Better to D/L it from Berkeley and run it from a personal folder or desktop.
Those instructions are more difficult, but they include all the things I've learned as I went along. Those packages are ones I've found are required along the way, so I include them whenever I build a new host so I don't have to re-learn which packages are needed as I move around to other projects. The simplest steps would be
- download whichever version of the tarball from http://boinc.berkeley.edu/dl/ and drop it in your "home" directory. (Where you end up by default when you simply run a terminal, command-line, prompt.) Say for example the latest bleeding edge boinc_7.0.52_x86_64-pc-linux-gnu.sh for a 64 bit Ubuntu.
- run the sudo apt-get -y install ia32-libs+ if you installed a 64bit Ubuntu. Many projects require the 32bit libs to run.
- run your downloaded boinc installer using bash boinc_7.0.52_x86_64-pc-linux-gnu.sh (That way you don't have to worry about the chmod to make it executable)
- Start it by typing BOINC/run_manager
Caveats explaining some of what Fire$storm posted:
- The above set of commands won't automatically start boinc after a reboot, but the script for doing that wasn't included in what Fire$torm posted. It's a bit long to just include here. And without that, the bits about the update-rc.d won't work.
- The bits about openssh-server, gdebi, libwxgtk, ssh-keygen and libXss1 are just extra tools. If you don't use another Linux box to run the manager remotely using ssh, you wouldn't need any of those.
- freeglut3 is required by a project, but I've forgotten which one.
- cpufrequtils would be required if you have power management enabled in the BIOS. BOINC runs at low priority, so it's common for CPUs to be allowed to run at the very lowest speed when BOINC is the only thing running. With cpufrequtils you can have Ubuntu force the CPU into "Performance" mode and it will run at its full speed all the time.
- The usermod and visudo allow you to use sudo to run commands as the Super-User using your "boinc" user account without having to provide the password each time.
Last edited by Mumps; 02-22-13 at 09:23 AM.
I can understand that Z but that was I was trying to say the other day, we are not far to make a doctor degree to crunch Boinc. The projects must understand how all this started. Give your spare time from your computer for us to use. It was a sentence like that more or less.
Not everyone has the knowledge or the means to keep boincing that is another reason for people to go, if the projects keep putting distance between themselves and the users, they will be alone in a flash.
There are some that try for simple words to keep the information flowing and the users interested that is why I like so much Bok's and FreeDC work.
It is only for about a week if everything goes OK, not to lose the crunching time. And crunch some NFS with Carlos, I will let the computer running hope everything is according to plan.
Friends are like diamonds and diamonds are forever
@Mumps: Can't all of that be done with a script? Including DL'ing?