Ubuntu instruction

[kmanley57]

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.

[Duke of Buckingham]

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.

[Mumps]

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

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+

[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?

[Mumps]

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

[Duke of Buckingham]

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.

[kmanley57]

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.

[Fire$torm]

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

@Duke: Roger and Thx.

[Fire$torm]

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

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

[Fire$torm]

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

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