Ubuntu instruction

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.

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....

Quote:

---

Originally Posted by Mumps

Mumps: So yes, download that package from the berkeley site and drop it in your home directory.
Mumps: Personally, I create that BOINC folder in my home dir myself and drop all the stuff in it ahead of time.
Mumps: Then I have a script that I run.
Mumps: From within that BOINC directory:
Mumps: chmod 750 boinc_7*
Mumps: sudo apt-get -y update
Mumps: sudo apt-get -y install openssh-server+
Mumps: sudo apt-get -y install gdebi+
Mumps: sudo apt-get -y install libwxgtk2.8-0+
Mumps: sudo apt-get -y install libXss1+
Mumps: sudo apt-get -y install freeglut3+
Mumps: sudo apt-get -y install cpufrequtils+
Mumps: sudo mv boinc /etc/init.d/
Mumps: sudo update-rc.d boinc defaults 90 01
Mumps: sudo usermod -G `id -nG | sed 's/ /,/g'`,sudo boinc
Mumps: echo "%sudo ALL=NOPASSWD: ALL"
Mumps: read ans
Mumps: sudo visudo
Mumps: I've got a copy of some SSH keys from the systems I normally remote from, so I copy that into place
Mumps: /usr/bin/ssh-keygen -t dsa
Mumps: to set up a public/private key on the new host...
Mumps: cd ..
Mumps: v64bit=`egrep "flags(.*) lm " /proc/cpuinfo`
Mumps: [ -n "$v64bit" ] &&{
Mumps: sudo apt-get -y install ia32-libs+
Mumps: BOINC/boinc_7*x86_64-pc*; }
Mumps: [ -n "$v64bit" ] || BOINC/boinc_7*i686-pc*
Mumps: So the 32-bit libs get installed on a 64bit build. Some projects need 'em...
Mumps: And that last line installs the boinc package you had downloaded.
Mumps: Presuming you grabbed a 7.anything version for 64bit...

Mumps: sudo mv boinc /etc/init.d/
Mumps: sudo update-rc.d boinc defaults 90 01
Mumps: Yeah, init.d is where most start-up/shut-down scripts get placed.
Mumps: That update-rc.d command sets it to run the boinc script at the right times for starting and just as importantly cleanly stopping boinc as part off a reboot process.
Mumps: mv = Move
Mumps: So I've got a copy in my pile I always start out with.
Mumps: My normal setup goes something like this.
Mumps: Install Ubuntu.
Mumps: Log in and launch the terminal (command) prompt.
Mumps: # mkdir BOINC
Mumps: # cd BOINC
Mumps: # ftp ftp-host
Mumps: # prompt; cd setup; mget *; quit
Mumps: chmod *sh
Mumps: ./lnx.sh
Mumps: and it pretty much does the rest.

---

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. =P~

But depending on which you use, the steps are different in some ways.

Quote:

---

Originally Posted by Fire$torm

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....

---

Quote:

---

Originally Posted by kmanley57

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. =P~

But depending on which you use, the steps are different in some ways.

---

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.

Well I remembered now the instruction:

sudo aptitude install boinc-client boinc-manager

Nice, it is written here for me to not forget.

I recommend *never* installing the BOINC package.

Better to D/L it from Berkeley and run it from a personal folder or desktop.

Quote:

---

Originally Posted by Fire$torm

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....

---

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.

Quote:

---

Originally Posted by zombie67

I recommend *never* installing the BOINC package.

Better to D/L it from Berkeley and run it from a personal folder or desktop.

---

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.

Quote:

---

Originally Posted by Duke of Buckingham

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.

---

But it is not the projects that keep putting distance, in this case. The problem here is purely BOINC/DA, with a touch of linux complexity, to blame. BOINC works just fine, and simply, if not installed via pkg.

@Mumps: Can't all of that be done with a script? Including DL'ing?

I have to agree with zombie67, that most of the installable packages are 'broken' in some manner. But I think the tarball from Boinc will run with little console work on your part.

I will say I have never gone to the lengths Mumps has to make it work, but he has more Linux machines to deal with, while ! have only a couple. :cool:

Quote:

---

Originally Posted by zombie67

But it is not the projects that keep putting distance, in this case. The problem here is purely BOINC/DA, with a touch of linux complexity, to blame. BOINC works just fine, and simply, if not installed via pkg.

---

I can't comply with that Z. To join to the complexity of Linux, there is my state of mind, however Ubuntu is much more friendly than other Linux systems much more complex. It was good however that more limited people will start with Ubuntu and go step by step learning the system, that takes so less memory and is faster on a general way.

I am not ready to give up fighting, I will keep stubborn as I am, my dear friend.

@Kmanley and F$ it is always good to listen to all experts, on computation and on Linux or any other system. Till tomorrow is the day for getting ready for RL, not that being here is not very real ... IS ONLY ANOTHER REALITY.

Quote:

---

Originally Posted by Fire$torm

@Mumps: Can't all of that be done with a script? Including DL'ing?

---

Yes. That's what it says in what you transcribed there...

Quote:

---

Originally Posted by Fire$torm

Mumps: Then I have a script that I run.
...
Mumps: My normal setup goes something like this.
Mumps: Install Ubuntu.
Mumps: Log in and launch the terminal (command) prompt.
Mumps: # mkdir BOINC
Mumps: # cd BOINC
Mumps: # ftp ftp-host
Mumps: # prompt; cd setup; mget *; quit
Mumps: chmod *sh
Mumps: ./lnx.sh

---

The rest of what you posted was a copy of a portion of that "./lnx.sh" script. :) That's the "bootstrap load" kind of process I go through for now, because I'm still installing Ubuntu from the standard Desktop ISO Distro. If I ever bother to get PXE booting under control, I'll be able to have the setup folder replicated automatically as part of the build and have the script run automatically as well.

On my "ftp-host" I have a folder named "setup" that includes the following:

• my standard boinc installer
• my standard install package for virtualbox (which is what uses gdebi)
• some default local preferences, cc_config and gui_rpc password and hosts files
• default settings for X-Windows
• the public keys for my normal management machines for remote controlling
• scripts to take care of setting the cpu-freq to perfomance
• the script (I lifted from Dotsch-UX) for auto-starting boinc on reboot

Also in my script, I include attaching to my (currently) favorite projects. (Which includes checking if the script is running in a VM and attaching to a different list of projects if so.) So by the time the script is done running, boinc is downloading and running work.

A pared down version to just install boinc (without the autostart feature) would go something like this:

Mumps: Install Ubuntu.
Mumps: Log in and launch the terminal (command) prompt.
Mumps: # firefox "http://boinc.berkeley.edu/dl/?C=M;O=D"
Download the most recent version of the x86_64-pc-linux (for 64 bit) or i686-pc-linux (for 32 bit) package that you can stomach. (I'm currently using 7.0.42.) By default it should land in your "Desktop" folder.
Mumps: # bash Desktop/boinc_7.*
Mumps: # BOINC/run_manager

You should now have boinc installed and running, ready for you to attach to any projects via the GUI. If you have problems running some of the projects later on, one of the first troubleshooting steps would be to install the 32-bit libraries if you installed a 64-bit O/S. Some people don't like having the 32-bit libraries installed because they can cause some confusion with some 64-bit apps that may make them run slower, but because I'm only running Linux to boinc, it's fine for me.

# sudo apt-get -y install ia32-libs+

@Mumps: Going through your commands on a VM. Goes well until...

root@Osiris:/home/chani/BOINC# sudo usermod -G `id -nG | sed 's/ /,/g'`,sudo boinc
usermod: user 'boinc' does not exist

What is needed here?

Quote:

---

Originally Posted by Fire$torm

@Mumps: Going through your commands on a VM. Goes well until...

root@Osiris:/home/chani/BOINC# sudo usermod -G `id -nG | sed 's/ /,/g'`,sudo boinc
usermod: user 'boinc' does not exist

What is needed here?

---

When I build my hosts, I always use the username of "boinc" So just replace that with whatever username you created and will be running boinc with.

All that command is for is to give that user the ability to use the sudo command for running things as the Super-User. Running locally, that won't be required. But if you want to use another Linux machine to ssh commands on this one with sudo, you'll need it.

Try boinc-client on that line or boinc-manager or even both F$

The system assumes one of the both or both for a GPU-Linux.

Sorry if I didn't understood the question.

Quote:

---

Originally Posted by Mumps

When I build my hosts, I always use the username of "boinc" So just replace that with whatever username you created and will be running boinc with.

All that command is for is to give that user the ability to use the sudo command for running things as the Super-User. Running locally, that won't be required. But if you want to use another Linux machine to ssh commands on this one with sudo, you'll need it.

---

Looking at his prompt line he is running as the SuperUser already. :p

Quote:

---

Originally Posted by Mumps

When I build my hosts, I always use the username of "boinc" So just replace that with whatever username you created and will be running boinc with.

All that command is for is to give that user the ability to use the sudo command for running things as the Super-User. Running locally, that won't be required. But if you want to use another Linux machine to ssh commands on this one with sudo, you'll need it.

---

OK thx Mumps. Obviously I'm still fumbling my way around Linux..... :P

@Duke: Roger and Thx.

Quote:

---

Originally Posted by kmanley57

Looking at his prompt line he is running as the SuperUser already. :p

---

Yep, I set up most of my important icons with gksudo in the command line.

@Mumps: In a bash script can I use $USER ?

Example: sudo usermod -G `id -nG | sed 's/ /,/g'`,sudo "$USER"

Quote:

---

Originally Posted by kmanley57

Looking at his prompt line he is running as the SuperUser already. :p

---

Not really. It's just shorter to type that than the full prompt I normally see. :) Sorry to confuse those that are knowledgeable. :rolleyes:

Quote:

---

Originally Posted by Mumps

Not really. It's just shorter to type that than the full prompt I normally see. :) Sorry to confuse those that are knowledgeable. :rolleyes:

---

I was commenting on Fire$torms 'root@' prompt. I do the same thing as you on my prompts when giving command line help.

Quote:

---

Originally Posted by kmanley57

I was commenting on Fire$torms 'root@' prompt. I do the same thing as you on my prompts when giving command line help.

---

But truthfully we should both use the "$" which is a true non-admin user prompt. It just doesn't come across quite right all the time that way. :)

Quote:

---

Originally Posted by Mumps

But truthfully we should both use the "$" which is a true non-admin user prompt. It just doesn't come across quite right all the time that way. :)

---

:p If I had a lot of $, I could use them either.$-)

In Ubuntu when admin powers are needed the system asks for a password and there is one instruction for being a super user but always with password.

OK, I think I fubar'd the install. Not sure what I did so I'm not bothering with it. I'm going to create a new VM and start from scratch. Once I learn something here then I'll go back and try to fix the old VM.

I hate Linux with a passion :p:p:p ... :D

I haven't used Linux in quit awhile but figure I'm going to have to suffer the Pain & use it if I want to get to 100 App's for the WUProp Badge. I'm in a Linux OS right now (Ubuntu 12.10) that I installed on a Bare Drive so I don't mess up a Windows Drive. Anywho I can't even find the freakin Terminal, I've been searching for it for an hour now but it's no where to be found, and I wonder why I hate Linux ... :p:p:p

EDIT: I found it by Goggling, or found how to get it to show anyway

Quote:

---

Originally Posted by STE\/E

I hate Linux with a passion :p:p:p ... :D

I haven't used Linux in quit awhile but figure I'm going to have to suffer the Pain & use it if I want to get to 100 App's for the WUProp Badge. I'm in a Linux OS right now (Ubuntu 12.10) that I installed on a Bare Drive so I don't mess up a Windows Drive. Anywho I can't even find the freakin Terminal, I've been searching for it for an hour now but it's no where to be found, and I wonder why I hate Linux ... :p:p:p

EDIT: I found it by Goggling, or found how to get it to show anyway

---

No expert either, but go to the top of the taskbar and look for the icon marked Dash Home. Open it and type Terminal in the search bar. It should magically appear. Then just drag and drop it to the taskbar and it should be there whenever you need it.

Okay I'll try that later, I unhooked the Linux Drive & re-hooked up the Windows Drive because Berkley is down right now & I can't download the latest Linux BOINC Manager. I could install the one in the software package but I want to go with the latest one available if possible. When I can get it downloaded I'll run the Linux Drive again ...

Quote:

---

Originally Posted by STE\/E

I hate Linux with a passion :p:p:p ... :D

I haven't used Linux in quit awhile but figure I'm going to have to suffer the Pain & use it if I want to get to 100 App's for the WUProp Badge. I'm in a Linux OS right now (Ubuntu 12.10) that I installed on a Bare Drive so I don't mess up a Windows Drive. Anywho I can't even find the freakin Terminal, I've been searching for it for an hour now but it's no where to be found, and I wonder why I hate Linux ... :p:p:p

EDIT: I found it by Goggling, or found how to get it to show anyway

---

Yup. Unity sucks for novice users.

Ubuntu: It'll be real clean to hide *everything* and just have the user type what they want in this "Dash Home" search tool.
User: But what If I don't know what you *named* the crap??!!??!?!

Dash Home does also have a "browse" kinda mode. Just click on Dash Home and then look at the icons along the bottom. The second one from the left will show you "Recently Used" but more importantly "Installed" App lists. Just click on the "See more results" next to the "Installed" one to see everything you have installed. That at least gets you the full list, although most folks won't like that it can't be organized into folders in there.

Okay I'm back in the Linux OS, I found an alternate site for the Linux BOINC Client Download. No Dash Home to be found, I know I seen that some where but can't find it again ... :rolleyes:

It looks like BOINC 7.052 is installed in the Home poorboy Directory but I'm getting this when trying to start the Manager:

poorboy@PBOYZTOY18L:~$ sudo
usage: sudo [-D level] -h | -K | -k | -V
usage: sudo -v [-AknS] [-D level] [-g groupname|#gid] [-p prompt] [-u user
name|#uid]
usage: sudo -l[l] [-AknS] [-D level] [-g groupname|#gid] [-p prompt] [-U user
name] [-u user name|#uid] [-g groupname|#gid] [command]
usage: sudo [-AbEHknPS] [-r role] [-t type] [-C fd] [-D level] [-g
groupname|#gid] [-p prompt] [-u user name|#uid] [-g groupname|#gid]
[VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AknS] [-r role] [-t type] [-C fd] [-D level] [-g
groupname|#gid] [-p prompt] [-u user name|#uid] file ...
poorboy@PBOYZTOY18L:~$ bash boinc_7.0.52_x86_64-pc-linux-gnu.sh
use /home/poorboy/BOINC/run_manager to start BOINC
poorboy@PBOYZTOY18L:~$ BOINC/run_manager
./boincmgr: error while loading shared libraries: libwx_gtk2u_html-2.8.so.0: cannot open shared object file: No such file or directory
poorboy@PBOYZTOY18L:~$ /home/poorboy/BOINC/run_manager
./boincmgr: error while loading shared libraries: libwx_gtk2u_html-2.8.so.0: cannot open shared object file: No such file or directory
poorboy@PBOYZTOY18L:~$ sudo /home/poorboy/BOINC/run_manager
[sudo] password for poorboy:
./boincmgr: error while loading shared libraries: libwx_gtk2u_html-2.8.so.0: cannot open shared object file: No such file or directory
poorboy@PBOYZTOY18L:~$
poorboy@PBOYZTOY18L:~$ sudo apt-get -y install ia32-libs+
Reading package lists... Done
Building dependency tree
Reading state information... Done
ia32-libs is already the newest version.
The following package was automatically installed and is no longer required:
linux-headers-3.5.0-17
Use 'apt-get autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 243 not upgraded.
poorboy@PBOYZTOY18L:~$ /home/BOINC/run_manager
bash: /home/BOINC/run_manager: No such file or directory
poorboy@PBOYZTOY18L:~$ sudo /home/BOINC/run_manager
sudo: /home/BOINC/run_manager: command not found
poorboy@PBOYZTOY18L:~$ /home/poorboy/BOINC/run_manager
bash: /home/poorboy/BOINC/run_manager: No such file or directory
poorboy@PBOYZTOY18L:~$ sudo /home/poorboy/BOINC/run_manager
sudo: /home/poorboy/BOINC/run_manager: command not found
poorboy@PBOYZTOY18L:~$

Quote:

---

Originally Posted by STE\/E

Okay I'm back in the Linux OS, I found an alternate site for the Linux BOINC Client Download. No Dash Home to be found, I know I seen that some where but can't find it again ... :rolleyes:

It looks like BOINC 7.052 is installed in the Home poorboy Directory but I'm getting this when trying to start the Manager:

poorboy@PBOYZTOY18L:~$ sudo
usage: sudo [-D level] -h | -K | -k | -V
usage: sudo -v [-AknS] [-D level] [-g groupname|#gid] [-p prompt] [-u user
name|#uid]
usage: sudo -l[l] [-AknS] [-D level] [-g groupname|#gid] [-p prompt] [-U user
name] [-u user name|#uid] [-g groupname|#gid] [command]
usage: sudo [-AbEHknPS] [-r role] [-t type] [-C fd] [-D level] [-g
groupname|#gid] [-p prompt] [-u user name|#uid] [-g groupname|#gid]
[VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AknS] [-r role] [-t type] [-C fd] [-D level] [-g
groupname|#gid] [-p prompt] [-u user name|#uid] file ...
poorboy@PBOYZTOY18L:~$ bash boinc_7.0.52_x86_64-pc-linux-gnu.sh
use /home/poorboy/BOINC/run_manager to start BOINC
poorboy@PBOYZTOY18L:~$ BOINC/run_manager
./boincmgr: error while loading shared libraries: libwx_gtk2u_html-2.8.so.0: cannot open shared object file: No such file or directory
poorboy@PBOYZTOY18L:~$ /home/poorboy/BOINC/run_manager
./boincmgr: error while loading shared libraries: libwx_gtk2u_html-2.8.so.0: cannot open shared object file: No such file or directory
poorboy@PBOYZTOY18L:~$ sudo /home/poorboy/BOINC/run_manager
[sudo] password for poorboy:
./boincmgr: error while loading shared libraries: libwx_gtk2u_html-2.8.so.0: cannot open shared object file: No such file or directory

---

looks like libwxgtk2.8-0 is not on your system or not in your library path. So you can try installing it.

sudo apt-get install libwxgtk2.8-0

Note: you probable need a couple other libraries, but I do not know off the top of my head which ones.

Still get the same crap after installing libwxgtk2.8-0:

poorboy@PBOYZTOY18L:~$ BOINC/run_manager
bash: BOINC/run_manager: No such file or directory
poorboy@PBOYZTOY18L:~$ sudo /home/poorboy/BOINC/run_manager
[sudo] password for poorboy:
sudo: /home/poorboy/BOINC/run_manager: command not found
poorboy@PBOYZTOY18L:~$

Back to windows for the night, enough Linux pain for the day ...

Quote:

---

Originally Posted by STE\/E

Still get the same crap after installing libwxgtk2.8-0:

poorboy@PBOYZTOY18L:~$ BOINC/run_manager
bash: BOINC/run_manager: No such file or directory
poorboy@PBOYZTOY18L:~$ sudo /home/poorboy/BOINC/run_manager
[sudo] password for poorboy:
sudo: /home/poorboy/BOINC/run_manager: command not found
poorboy@PBOYZTOY18L:~$

Back to windows for the night, enough Linux pain for the day ...

---

1) Assuming BOINC is in your home directory, the command is "~/BOINC/run_manager &". If BOINC is on your desktop, then the command is "~/Desktop/BOINC/run_manager&".


2) Here is the list of packages I install and remove with every new ubuntu 64 bit installation. You can just copy/paste the line, and it will install them all at once.

sudo apt-get install openssh-server+ gdebi+ libwxgtk2.8-0+ libXss1+ freeglut3+ gnome-applets+ cpufrequtils+ ia32-libs+

That includes everything you need to get BOINC to run, as well as the additional 32 bit libraries needed for the 32 bit apps.

Okay, new VM. Here is what I've done so far.

Note: All commands are run from root, ex. root@Sys1:

mkdir /home/dilbert/BOINC
cp /home/dilbert/downloads/boinc* /home/dilbert/BOINC
chmod 750 boinc_7*
bash boinc*.sh
mv /home/dilbert/BOINC/BOINC/* /home/dilbert/BOINC
rmdir /home/dilbert/BOINC/BOINC
apt-get -y update
apt-get -y install openssh-server+
apt-get -y install gdebi+
apt-get -y install libwxgtk2.8-0+
apt-get -y install libXss1+
apt-get -y install freeglut3+

Note: I did not run cpufrequtils+ as this is a VM and governor does not exist in a VM.

mv boinc /etc/init.d/
update-rc.d boinc defaults 90 01
usermod -G `id -nG | sed 's/ /,/g'`,dilbert
echo "%ALL=NOPASSWD: ALL"
read ans
visudo
cd ..

And the following lines is where I ran into a problem.....

v64bit=`egrep "flags(.*) lm " /proc/cpuinfo`
[ -n "$v64bit" ] &&{
apt-get -y install ia32-libs+
BOINC/boinc_7*x86_64-pc*; }
[ -n "$v64bit" ] || BOINC/boinc_7*i686-pc*

So after coping/pasting all to a single line and then using bash errors I played with spacing between parts....

So is the following correct? I did not get a bash error but it didn't seem to do anything

v64bit=`egrep "flags(.*) lm " /proc/cpuinfo`[ -n "$v64bit" ] &&{sudo apt-get -y install ia32-libs+BOINC/boinc_7*x86_64-pc*; }

Well I am not mumps but this seems wrong.

install ia32-libs+BOINC/boinc_7*x86_64-pc*;

maybe a space between libs+ and BOINC. Should install the lib package and the Boinc package.

Quote:

---

Originally Posted by Fire$torm

And the following lines is where I ran into a problem.....

v64bit=`egrep "flags(.*) lm " /proc/cpuinfo`
[ -n "$v64bit" ] &&{
apt-get -y install ia32-libs+
BOINC/boinc_7*x86_64-pc*; }
[ -n "$v64bit" ] || BOINC/boinc_7*i686-pc*

So after coping/pasting all to a single line and then using bash errors I played with spacing between parts....

So is the following correct? I did not get a bash error but it didn't seem to do anything

v64bit=`egrep "flags(.*) lm " /proc/cpuinfo`[ -n "$v64bit" ] &&{sudo apt-get -y install ia32-libs+BOINC/boinc_7*x86_64-pc*; }

---

Well, a little bit of explanation. The special "file" /proc/cpuinfo has all the geek speak explaining the capabilities the O/S sees the CPU supports. "lm" is actually short for "Long Mode" and means the O/S sees that the CPU supports 64bit mode. So that means both the CPU and the O/S are 64bit aware, so we need to install the 64bit version of BOINC. We also install the 32bit libraries, considering that many BOINC projects will actually send the 32bit app to run on a 64bit Linux host. So you need the 32bit libraries if they haven't compiled the program to work without them.

Not really sure what problem you ran in to. But at the very least, if you mash it all into one line, you'll need semi-colons in various places. Let's also eliminate assigning that to a variable...

[ -n "`egrep 'flags(.*) lm ' /proc/cpuinfo`" ] && { sudo apt-get -y install ia32-libs+; BOINC/boinc_7*x86_64-pc*; }

Also, to be clear, that line is expecting to find the appropriate BOINC installer in a folder named BOINC within the Current Working Directory. So, if you've simply launched terminal, and are running those commands, it would be in your home directory.

Quote:

---

Originally Posted by kmanley57

Well I am not mumps but this seems wrong.

install ia32-libs+BOINC/boinc_7*x86_64-pc*;

maybe a space between libs+ and BOINC. Should install the lib package and the Boinc package.

---

Good thought, but the BOINC package from the Berkeley dl site isn't a package. And we don't want to install the (extremely antiquated) package from the repository. It's a self-extracting sh file and you simply want to execute it. In the script Fire$torm is working from, that sh script is chmod'ed to be executable, and then it's run. But run from the home directory so it gets extracted into the BOINC subfolder.

Quote:

---

Originally Posted by Mumps

Well, a little bit of explanation. The special "file" /proc/cpuinfo has all the geek speak explaining the capabilities the O/S sees the CPU supports. "lm" is actually short for "Long Mode" and means the O/S sees that the CPU supports 64bit mode. So that means both the CPU and the O/S are 64bit aware, so we need to install the 64bit version of BOINC. We also install the 32bit libraries, considering that many BOINC projects will actually send the 32bit app to run on a 64bit Linux host. So you need the 32bit libraries if they haven't compiled the program to work without them.

Not really sure what problem you ran in to. But at the very least, if you mash it all into one line, you'll need semi-colons in various places. Let's also eliminate assigning that to a variable...

[ -n "`egrep 'flags(.*) lm ' /proc/cpuinfo`" ] && { sudo apt-get -y install ia32-libs+; BOINC/boinc_7*x86_64-pc*; }

Also, to be clear, that line is expecting to find the appropriate BOINC installer in a folder named BOINC within the Current Working Directory. So, if you've simply launched terminal, and are running those commands, it would be in your home directory.

---

Quote:

---

Originally Posted by Mumps

Good thought, but the BOINC package from the Berkeley dl site isn't a package. And we don't want to install the (extremely antiquated) package from the repository. It's a self-extracting sh file and you simply want to execute it. In the script Fire$torm is working from, that sh script is chmod'ed to be executable, and then it's run. But run from the home directory so it gets extracted into the BOINC subfolder.

---

1st, just to be clear, my bash prompt looks like this root@Betty_Boop:/home/dilbert#

Okay my mistake. I was executing bash commands from /home/dilbert/BOINC. That is why I had to use the mv command with wildcard and move everything from .../BOINC/BOINC to .../BOINC.

I had to run the BOINC .sh file early because you have the command mv boinc /etc/init.d/ before you get to the command with the v64bit... stuff.

As for your revised command string...

root@Betty_Boop:/home/dilbert#[ -n "`egrep 'flags(.*) lm ' /proc/cpuinfo`" ] && { sudo apt-get -y install ia32-libs+; BOINC/boinc_7*x86_64-pc*; }

it worked but not until I added "deb http://archive.ubuntu.com/ubuntu lucid-backports main restricted universe multiverse" to /etc/apt/sources.list.
So all kinds of files were downloaded and updated. Then after it was all over it printed the instruction "use /home/dilbert/BOINC/run_manager to start BOINC"

Of course I ignore that and in terminal try /etc/init.d/boinc start but that gave me the following error

Quote:

---

/etc/init.d/boinc: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory

---

Then I try the command I was instructed to use and got the following error

Quote:

---

./boincmgr: error while loading shared libraries: libnotify.so.4: cannot open shared object file: No such file or directory

---

Should I start over and reinstall Ubuntu so I have a clean slate to try again?

Quote:

---

Originally Posted by zombie67

1) Assuming BOINC is in your home directory, the command is "~/BOINC/run_manager &". If BOINC is on your desktop, then the command is "~/Desktop/BOINC/run_manager&".


2) Here is the list of packages I install and remove with every new ubuntu 64 bit installation. You can just copy/paste the line, and it will install them all at once.

sudo apt-get install openssh-server+ gdebi+ libwxgtk2.8-0+ libXss1+ freeglut3+ gnome-applets+ cpufrequtils+ ia32-libs+

That includes everything you need to get BOINC to run, as well as the additional 32 bit libraries needed for the 32 bit apps.

---

Thanks Z, I got BOINC to run with the ~/BOINC/run_manager command after moving the BOINC Folder out of the folder it was in & putting it directly in the Home Directory.

Anywho got some of the LINUX Only Projects & App's running now, is there any way to Minimize the BOINC Window without having to restart BOINC each time ??? Seems like if I minimize the BOINC Window it stops BOINC & I have to restart BOINC again ...

Quote:

---

Originally Posted by STE\/E

[...]is there any way to Minimize the BOINC Window without having to restart BOINC each time ??? Seems like if I minimize the BOINC Window it stops BOINC & I have to restart BOINC again ...

---

The buttons on the linux windows and the msft windows are not the same. With ubuntu, it is the down arrow button to minimize.