Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
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.
DO NOT just install some random rpm's " found on the net"
that is the FASTEST WAY to FUBAR your system ! ( google it if you do not know what "fubar" is )
doing that might also cause your computer to NEVER EVER boot ever again
how would I add these new rpm's to my repository for distribution to my network?
as per above
this is the fastest way to KILL every RHEL6 install on the network , not fun or easy to fix .
do not put random rpms in your local repo
contact red hat support
you are paying for the Required support contract(s)
and for a good sized " networked" set up -- like say an office
that is NOT cheep..
you are paying out a lot of cash , you might as well use the tech support you are paying for .
3rd. The purpose of the question is to learn how to
add *ANY* rpm, that I deem appropriate, into a repository that I manage such
that I can use yum to install that rpm on another machine from my repository.
example: I just created an rpm for creating a user.
I wish to deploy this user to multiple machines.
How would I put that user.rpm into the local repository?
Yes, there are other ways of doing this, however I'm
attempting to do this via an rpm.
How are you serving the repo? Via nfs, web server, or do you use spacewalk( the free alternative to rhn satellite )? Have you already created a repo, ie by running the createrepo command? If you did or if you have an existing repo just copy the rpms to your repo directory and run createrepo --update and the path to your repo.
on my machine yum --help does not show localinstall as an option/cmd.
re: installing rpm's not from the official repository.
you gave this error: will toss an "this system is not registered with redhat" and a
RHN not supported error
my response: so ... when I installed the rpm's not from redhat, I did not get that
error. in fact, they installed fine.
1st. Thanks for responding.
2nd. I did the following:
1. copied the media to /var/www/html/inst/R* [ rhel 6.3.blah ]
2. added new rpm's into R*/Packages
3. rn your command: createrepo --update . in /var/www/html/inst/R*/Packages.
- it didn't work. I suspect that the path is incorrect.
So, I did the following.
cp /var/www/html/inst/R*/P* /var/ftp
cp new rpm's into /var/ftp
createrepo -d /var/ftp
that final cmd actually worked and the new rpm's showed up.
I read this pretty often here in this forum, that whoever uses RHEL needs to have a licence or will suffer pain, death and unhappiness.
Actually: That's crap.
The system itself doesn't care if you have a licence or not. I know many systems running RHEL 5 and 6, which have all the licence fees paid for, but are not configured with the licence. They work flawless for years. It all depends on the actual setup and use case of the system, but unfortunately there are many people out ther, who can only think the same distance they can see, as usual...
Yes, legally you are required to have a licence for production RHEL systems, but for test systems I'd never consider to buy one (use CentOS instead).
No, for the system itself, it doesn't really matter (if you can ignore the screen message about the missing licence file (which could be faked anyway...)).