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!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Where exactly did you get these rpms? Why aren't you using a yum and getting what you need from CentOS repositories? It is important make sure the rpms you get are for the Linux distribution and version of same you're using. You can't just install any rpm on CentOS. (e.g. If you found Fedora 20 rpms they would almost certainly not work on CentOS 5.) Generally speaking rpms are designed for a specific distribution and version. (On the flip side most of what is designed for CentOS will work on RHEL of the same version and vice-versa because CentOS is designed to be a binary compile from RHEL source.)
Yum will address dependencies automatically so long as it can find them in the repositories you're using. This is the main point in yum - it prevents the "dependency hell" people used to get when trying to install packages with rpm.
You can actually install multiple rpms at the same time with "rpm -ivh *rpm" if they're all in the same directory but I don't know if it would build a long enough command to contain 1500 of them before it puked on you. If it will and the dependencies are satisfied it will see that it is in the list and won't complain about it. (That is if you install 2 or more rpms with the same command line that command line will see the dependency if it is one of the rpms in the command line.)
However, as noted you really ought to be doing this using yum. 1500 is one heck of a lot of rpms and it sounds almost as if you're trying to change the entire system.
If the dependencies for the packages are in the repository, yum should be able to install the packages with their dependencies.
Step 1. Make a short list of rpms installed on your system. The sole purpose of the list is to get an idea of the format of the list that yum needs.
So: in a console, run,
yum list installed > installed.txt
then interrupt the listing with a ctrl-c. You just need an idea of how to format your list of 1500 rpms.
Step 2. To install the rpms from the list of 1500, using yum, edit the list so that it matches the format of the list you produced with yum in step one above. Once the list is ready, install the entire list, using yum:
yum -y install $(cat installed.txt)
As to the dependencies, you may be able to determine whether or not you will have dependency problems by running something like:
thanks guys, we are duplicating an offsite server. but ... our OS is newer
As was asked above, where did you get these rpms? If you're running a different OS, then you cannot install the same RPMs that are on the offsite server, you need to install versions of those programs for your OS. The best place to get them would be through the standard repository for your OS - yum.
Also, why are you trying to duplicate an offsite server to a machine running a newer OS? The idea is fundamentally flawed...if it's a different OS, then it's running different packages of different versions, often with incompatible config files, locations, etc. If you want to use the offsite server as a reference for setting up a new machine with similar functionality, that's a very different topic, and you would not be asking how to install a block of 1500 unknown RPMs.
we have just the list of the name of the rpms. not the actual rpm packages. the actual rpm packages will be grabbed from the installation CD. we are actually aiming to duplicate the functionality of the offsite server. but our offsite team is not being very helpful in terms of giving us the requirements.
we have just the list of the name of the rpms. not the actual rpm packages. the actual rpm packages will be grabbed from the installation CD.
That won't work. Different OS means different package versions, which means a different RPM name. If it was just a few you could peel off the version information and extract the actual package name, and then use yum to install it, but for 1500 of them that's going to be a royal pain.