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.
All details are logged in the file /var/log/yum.log.
If a package needs supportive packages, they all will be listed in yum.log.
You can not expect that only main package should be listed.
May be supportive packages are not important for you but they are important in every manner.
Sorry didn't get you actually. I need to know the command which would fetch all packages which were installed by a user (Not default packages) on Centos. I was using rpm -qa but that doesn't help as it lists all packages.
I also tried "yum list installed" but that too lists all packages.
I would need to know the list of packages which are only manually installed on the centos box.
By knowing what was originally installed one can get the difference. In any case, I replied thinking you were simply trying to inventory. It seems you want to build other systems based on your current package selections. What is your end goal? Your question does not have a clear goal in mind. By providing what you're attempting to do as a whole you potentially let yourself receive a better process than what you're attempting step by step in your questions.
and again, all the packages are installed by root. There is no such thing "manually" installed packages. All the packages are installed by invoking a package management tool (yum or rpm), but noone knows how (by script or by human beeing) were they invoked. It is not logged.
I checked that log "/var/log/yum.log" but I believe it also lists all linux packages. I need the ones which are installed by a user on Centos and not a list of all packages installed. Would you be aware how can I fetch that?
The script which would give me a list of all installed packages on linux (installed by root), I need to run it on another number of servers provided by client in my environment. The output report needs to list all packages which were installed on the linux host i.e. centos and I don't want to report the packages which are default in linux.
Hence, my goal is to obtain a list of installed packages on linux (application packages) which were installed so that I can get the similar report for all other servers.
If that's what you're trying to do then it is better to install a configuration management solution to manage the packages across your systems. Some configuration management solutions include:
By using configuration management you can standardize on a base set of installed packages and then customize what gets installed after that. It would also serve as documentation for which systems have what packages installed. I'm more inclined to promote the right tool for the job.