mandriva install, im lost

Mmmm... I can see this is quickly getting confused...

Firstly, focus on just getting the one instance of Boinc running.

To make yourself root on a commandline, you just give the two letter command "su". Nothing else. So, all on a line by itself, it is just:

su

Enter the root password when prompted and that's it, you're in a root shell.

To use "sudo", you need to add yourself to the sudoers list.

I've not used the packaged version of Boinc but I'm sure it works and that there'll be comments somewhere on the web for what you have to do to use it.

Alternatively, uninstall the packaged version of Boinc and instead use the xxxx.sh 'installer' version from the Boinc downloads page. For example, on the commandline in whatever directory you wish it to run from:

(For example, from your home user directory all as a normal user, no root!)
(And no need to type the "#" comments)

cd ~

# Check where you are!
pwd

# Get 64bit Boinc
wget http://boincdl3.ssl.berkeley.edu/mirror/boinc_6.10.17_x86_64-pc-linux-gnu.sh

# Make it executable
chmod +x

# Execute it (note the "dot - forward-slash" trick to execute from your current directory)
./boinc_6.10.17_x86_64-pc-linux-gnu.sh

# Voila, you now have a directory "BOINC"
# Follow the displayed instructions to use it

Good luck!

Cheers,
Martin

(Note the link to the Boinc wiki help in my sig...)

On my SuSE Linux I have always used the xxx.sh method in my home directory. It creates a BOINC directory. Then I launch the run_manager script. When, in some BOINC versions, this does nor start the client. I start first the client then the manager. Using the manager, i connect to my 6 BOINC projects.
Tullio

Hi Paul,

for easy working with the shell install(if not already installed) Midnight Commander. That program looks like the old DOS Norton Commander and is started via
mc
It has a build in viewer(F3), a build in editor(F4) and alot of other thing e.g. change file permissions.

If the boinc client is automatically started from your system, your only problem is to use the manager. This will not work with your current installation.

To do it the easy way I'd do the following:
Add yourself to the group boinc(should be possible through some desktop program).
Open terminal and cd to your boinc directory.
su
enter password
You are root now, so beware what you are doing! E.g. never start boinc as root!
Allwys start and stop the client through your init script, which will change the user to boinc.
mc
Make the gui_rpc_auth.cfg readable for the group boinc(F9 for menue, then look for File - extended chown).
Make boinccmd and boincmgr executable and readable for group boinc(use mc as described above)
Add a link to your desktop for the program boincmgr and be shure the working directory is your boinc folder.

Start the manager and connect to the projects of your choice.

Hth,
Michael

Good stuff. Something new is always a good exploration until it all becomes 'obvious'.

For the nVidia drivers, the safest route is to stay with the packaged drivers from the standard Mandriva repositories. The nVidia install script from the nVidia website works fine but it does the same job in a different way.

Best route is:

Ensure that you have all the default repositories available:

"Configure your computer" -> software management -> configure media sources for install and update

And then click on the "add" button to add all the default sources from the mirrors (if you've not already done so).

"Configure your computer" -> hardware -> set up the graphical server

And make sure that you've got the 'proprietary' nVidia driver selected for your graphics card.

Then:

"Configure your computer" -> software management -> install & remove software

Select "All" and "All" in the two selection boxes on the top left.

Type "nvidia" (no quotes!) into the find bar, hit enter, and then make sure you have selected:

dkms-nvidia-current v190.42
nvidia-current-devel v190.42
x11-driver-video-nvidia-current v190.42
nvidia-cuda-toolkit v2.3
nvidia-cuda-toolkit-devel v2.3

Good luck!

Happy crunchin',
Martin

I have in my temporary possession a laptop that has Mandriva 2010 installed on it... I wanted to run BOINC thru one WU or something for grins.

I've only worked on Debian based distros before, mostly Ubuntu.

I went to Mandriva's package manager (noticing they've got a newer version than Debian does in the repositories)... installed it. Found boinc manager in Applications-->Tools-->System Tools--> BOINC Manager.

I opened a terminal and did su.
did /etc/init.d/boinc-client status and found the client wasn't running. Started it with "service boinc-client start"... worked, says it's running now.

Used the GUI and opened BOINC Manager... It will not connect to the running client. In user/bin the boinc* executables are owned by root. From a Debian perspective this is as it should be. In /var/lib/boinc everything is owned by boinc, again as it should be from a Debian perspective.

So why will the installed manager not connect to the installed and running client?
..................................
EDIT:
OK, here's the fix...

I opened a terminal, did su.

cd /var/lib/boinc
cp -vp gui_rpc_auth.cfg gui_rpc_auth.bkp
gedit gui_rpc_auth.cfg
deleted the key in that file and save the file
service boinc-client restart
then from the GUI started the manager up again... woohoo... it connects.

Hope this helps some other Mandriva 1st timer. BTW, in Ubunt/Xubuntu/Mint this is not required but I don't know how it's install of the meta package allows them to talk with the key in place... unless... just maybe... it installs with an empty key file (gui_rpc_auth.cfg)... hmmm In my dirty sordid past (Windoze)
I always deleted the key anyway so I didn't have to enter it when remote accessing other boinc daemon instances on other machines on my LAN anyway.
....................................
EDIT:
Crap, new problem...
Message from server "platform 'i586-mandriva-linux-gnu' not found.

Why is this thing asking for that APP name?