RPM Locked???

Ok tell me is there supposed to be a hyphen between the su and rpm ?

I tried the kdesu mcc , I get prompted for a password not in the command line, it was a popup, which I entered the root and just goes back to the command line.

This is hard ...

EDIT: I assure you I didnt forget the root password.

OK we getting somewhere.

After typing su-- for more help it prompted me for the root password which i gave.

Now the command line is on root. So i guess i jsut have to get the command right.

the su - rpm -Uvh pa.rpm doesnt work. It says -- U is an invalid option

Yes, kdesu is the command for opening a graphical root window application, so it should not drop to console--that is odd

See my edit in previous post if root is not working

OK - thank you for the help.

Anyway I double click on the file on the desktop and it prompted me for root password.

I out it in, said something but gave me the option to install anyway which I did.

Then said succesfully installed, the rpm.

Um , where is it, how do I get the the program.

Rofl sorry im so used to windows, what normally happens here.

ok, just drag the rpm icon into your root shell and press enter

edit: ok i see you got it working--ignore this sentence ^^^^^

what is the exact name of the application?

Did so

Permission denied.

are you using kde?

if you are try the search bar at the top of your kickoff menu and type panda or any relevant search--if that doesn't work try going into /usr/bin and search for the shell script

open your mandriva control center, (if you haven't found the script)

go to the package manager

search for the package you just installed--highlight it and look for the option files

paste the list of files here so i can tell you how to get to the shell script

OK Cider , I'm a little hung over and have never used that distro ( at least since Mandrake ) but some explanations for you:

I apologize if it is too basic.

If sudo is set up on the system, and your user is a sudo user, you would not use a - after sudo and before the command. sudo is used for a one-time run ( like run as )

Open a terminal.
You would normally get a prompt like below ( can be changed or differ depending on distro ) where user would be your user name, computer would be the name of the host.

to change the root password
user@computer: sudo passwd root

it may or may not ask you to put in a password, depending on how sudo was set up, then it will ask you for a new password, and then to confirm it. ( an example when to use this would be when running Ubuntu LiveCD and you want to login as root: Ubuntu will not recognize a root password unless you change it to your own. )

OK, now I have set ( or changed ) a root password, now I want to perform a lot of tasks as root.
Instead of constantly typing sudo before every command I will su to root, which means my terminal will be running under the root user.

user@computer: su -

it will now ask you for the root password. If all went well, your prompt will change to

root@computer:

Now every command you type will be run as the root user. BE CAREFUL !
Also note the - after su
All that does it tell the su command to use the root user's paths. Some distros set up different paths for non-root users. If your user has the same path statements as root it is not necessary.

Ctl-d
to go back to normal user, a second time will close the terminal window, or log you out if you are at run level 3 ( no GUI such as Gnome or KDE running under Xwindows, which is run level 5)


Why did you rename the app ???????
RPM ( RedHat Package Manager ) is very powerful and has been adopted by may distros, but apps packaged for a one distro probably will not work on another ( there are exceptions ) because of the programs installed on the build system may vary to those on another. Also distros don't always use the same set-up of the file systems, so you may be putting something in, for example, /bin that your distro would put in /sbin or /usr/sbin
RPM also can verify the checksum and/or signature of the file(s) before it installs it.
Mucking with the file before you try to install it is not a good idea.
man rpm
man is your friend!

Some useful rpm commands for what you are doing:

rpm -qi -p <rpm file>
will give you info on the package, including if it is installed.

rpm -q –filesbypkg -p <rpmfile>
gives a listing of the files to be installed, and where

rpm -q -p <rpmfile> –dump -l
gives a lot more information on files to be installed, just in case interested!

If all else fails and your GUI did not create an icon somewhere for you to run a program , ( you may have to look in a couple of places as C:\Saw said ) you can use the second command above to look for the file to run the program ( will usually be in one of the /bin or /sbin directories. )

Remember, RPM is a package manager! Unless is specifies that it is source ( usually with a .src extension ) it is pre-compiled. As said by C:\Saw " ... tar.gz or tar.bz, deb, bin, and more... gunzipped files (.gz) are usually source packages that require being compiled manually. " They can not be installed with RPM .

Also, there are update managers that use RPM such as yum and yast
You probably have yum on that system, which can also be used to install packages and keep them up-to-date.

Wow , thank you for that info. Really what I needed.

C:\saw I was post what yuou requested tomorrow, quite tired now.

Thanks very much for all your help.

Enjoying it already, challenging but cool.

Thanks :)

OK well couldnt find it anywhere so double clicked on it again.

It reads.

Cannot install the selected package (unsatisfied ed)

Suggestions?