Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello, I am a linux newby and having tasted the goodies of Fedora 9, I am now a very convinced linux wannabe.
The sense of control in the type and execute is, to tell the tale , a great ride and having found just what a chum yum could be, I yummed a lot of installs – yum presto too.
Since I found yum Presto is too pronto in its execution and does not really update effectively, to get rid of this part of the otherwise most excellent yum , as root I executed the command :-
“yum erase yum presto”
Yum erased a lot of stuff more and beyond yum presto.
Now if I execute any “yum” command such as “yum update”, the terminal returns the message:-
I'm afraid you've uninstalled yum. yum erase yum-presto would have done what you want, but with a space instead of a hyphen, yum saw two things to remove: yum itself and "presto" (which doesn't exist - the package's name is yum-presto). The power of the command line is great, as you say, but it can be dangerous!
At this point, the quickest thing to do might be to reinstall Fedora. But before you "go nuclear", we can have a go at reinstalling yum. You can download the package directly from here: http://download.fedora.redhat.com/pu...fc9.noarch.rpm
But pick the correct architecture for your system (post the output of uname -i if you're not sure) - that's the i386 version.
That file is what yum would download if it were installing the package automatically, but you can install it yourself with
Code:
rpm -ivh yum-3.2.14-10.fc9.noarch.rpm
This is an older way of installing things. The disadvantage is that rpm can't go online and find other packages that yum depends on (that's what's so great about yum and other package managers), so you may get a "failed dependency" error if yum also erased other packages on which it depended. With a bit of patience you should be able to sort it out though, all the dependencies will also be available as rpm files from the URL above. If you get a failed dependency error, just keep installing the required packages until you can install yum!
Hope that's clear, post the output of the rpm command if you can't get it to work.
PS: there are a lot of other packages whose names begin with "yum" that you'll also have erased. Once you've got yum installed, you probably want to install those too. The ones on my system (F8) are:
yum-fedorafaq
yum-metadata-parser
yum-priorities
yum-updatesd
yum-utils
and AFAICR all of those were installed by default when I installed Fedora, except possibly yum-priorities.
Just grab a yum rpm package from any of the Fedora mirrors (this one, for example) and install it with..
Code:
rpm -ivh yum-<version>.rpm
It's possible that rpm will complain about missing dependancies - if it does (I'm not sure if yum depends on any other packages apart from rpm and wget/curl which it uses for downloading and installing) you'll also have to pull those missing rpm packages from the mirror and install them via rpm -ivh just like above.
I'm afraid you've uninstalled yum. yum erase yum-presto would have done what you want, but with a space instead of a hyphen, yum saw two things to remove: yum itself and "presto" (which doesn't exist - the package's name is yum-presto). The power of the command line is great, as you say, but it can be dangerous!
At this point, the quickest thing to do might be to reinstall Fedora. But before you "go nuclear", we can have a go at reinstalling yum. You can download the package directly from here: http://download.fedora.redhat.com/pu...fc9.noarch.rpm
But pick the correct architecture for your system (post the output of uname -i if you're not sure) - that's the i386 version.
That file is what yum would download if it were installing the package automatically, but you can install it yourself with
Code:
rpm -ivh yum-3.2.14-10.fc9.noarch.rpm
This is an older way of installing things. The disadvantage is that rpm can't go online and find other packages that yum depends on (that's what's so great about yum and other package managers), so you may get a "failed dependency" error if yum also erased other packages on which it depended. With a bit of patience you should be able to sort it out though, all the dependencies will also be available as rpm files from the URL above. If you get a failed dependency error, just keep installing the required packages until you can install yum!
Hope that's clear, post the output of the rpm command if you can't get it to work.
PS: there are a lot of other packages whose names begin with "yum" that you'll also have erased. Once you've got yum installed, you probably want to install those too. The ones on my system (F8) are:
yum-fedorafaq
yum-metadata-parser
yum-priorities
yum-updatesd
yum-utils
and AFAICR all of those were installed by default when I installed Fedora, except possibly yum-priorities.
-------------------------------------------------------------------------
Many thanks for the detailed suggestion and the earnest mind behind your suggestion and thank you too "Maligree"
So I clicked on the link that you had provided and downloaded the package and then executed the suggested command.
The terminal replies as follows:-
"error: open of yum-3.2.14-10.fc9.noarch.rpm failed ; No such file or directory"
Have I indeed done precisely that you have so kindly suggested? Is there
any thing else to try, before I commit harakiri?!
1. the file was downloaded by the browser to home/downloads.
2. how do I go to that directory to run rpm from there?
cd downloads from your home directory, or cd ~/downloads from anywhere. pwd will tell you your current directory, ls will list the files in the current directory. Remember when you type the rpm command that file names are case-sensitive (don't use capitals unless they're there in the filename).
You have a knack for finding just the right way to prevent our suggestions from working . Not blaming you (or me or the others), it's just that bash (the shell program which is interpreting your commands) is complex, and when you're used to it it's hard to think of every little step to guide a newbie through it.
The ~ character expands to the home directory of the current user. So cd ~/downloads will work when you're logged in as yourself, but if you're logged in as root then ~ expands to root's home - not where you want to be. The actual path to your home dir is /home/yourusername, so you can use that instead of ~ when you're logged in as root. By the way, remember that file names are case-sensitive - are you sure it's downloads and not Downloads?
You might want to google around for a tutorial on the basics of bash - this one looks alright. If you're having trouble finding files and directories, use pwd to find out where you are and ls to see what files are in the current directory. Depending on your distro, subdirectories will hopefully come up in a different colour from regular files so you can see which ones you can cd into. If there's no colour, use ls --color=auto.
Having sought the light of TUTs as suggested so kindly by OPENSAUCE, and one what the SeniorMemeber suggested, the terminal replies:- error: can't create transaction lock on /var/lib/rpm/_db.000
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.