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.
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
/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
./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?
Reply With Quote