redhat and version switch with yum update

[Adam Garsha]

I am not new to IT, not new to linux, not new to UNIX in general and I am just getting my feet wet with RHEL in a server environment.

When I "yum update" a RHEL 5.3 box (a fresh build) it takes me to 5.4. Most of my drivers and third-party support statements say "5.3". I've adopted some yum.conf exclude statements to keep my kernel were I need it and also block the /etc/issue*, etc/release stuff from flipping since it is required for support and also makes most installers break.

My questions are this:

1. What do RHEL folks usually do to stay at a version? Is there a flag somewhere where I can say "hey, update for security and errata, but don't flip 'versions', etc."?

2. Would yum-excluding "el5_4" stuff be ok and do the trick, is there another way?

3. Or... should I not care? updateing a fresh 5.3 and blocking kernel and release flip, still dumps a bunch of libvirt stuff, etc, that I don't want.

4. Basically, what do you do to keep minimal change when doing updates or if just starting a fresh and working to arrive at a new standard build for a given version?

[Ivan Ferreira · Accepted solution]

You can install security only packages by installing the yum-security plugin:

yum install yum-security

Then you can use:

yum list-security
yum info-sec
yum update --security

>>> Or... should I not care? updateing a fresh 5.3 and blocking kernel and release flip, still dumps a bunch of libvirt stuff, etc, that I don't want.

Normaly the kernel is the major issue with platform certifications, but there are some libraries that may change and create problems with your certified software. Is hard to say without knowing the "dependencies" of your software.

[Nuwan Alwis]

Hi Adam,
This is a common issue linux and win, when you do a automated update it applies all the newer patches and drivers to the system. these new patchese or dirvers might not certified with your apps.

So best is to manualy apply updates as the above post given you how get it done with yum.

Think twise before you add a kernel update or patch because the end result would be exact same like you faceing now.

Good Luck ...!
NJ

[Steven E. Protter]

Shalom,

1. What do RHEL folks usually do to stay at a version? Is there a flag somewhere where I can say "hey, update for security and errata, but don't flip 'versions', etc."?

I would not update a production server to update 4 until I've tested it in a sandbox. There were 12 or 13 kernel updates after update 3 was released. I think the update 3 cycle was stable, but that is in hindsight.

2. Would yum-excluding "el5_4" stuff be ok and do the trick, is there another way?

I would simply only do security only updates individually. You can usually except on an Internet exposed system afford to wait before touching a system.

3. Or... should I not care? updateing a fresh 5.3 and blocking kernel and release flip, still dumps a bunch of libvirt stuff, etc, that I don't want.

Ivan's commands are good for that.


4. Basically, what do you do to keep minimal change when doing updates or if just starting a fresh and working to arrive at a new standard build for a given version?

I generally do nothing until I am certain that the update is stable and has a few kernel patches under its belt.

Again, unless you are exposed to and serving the public Internet, you can afford to wait a few weeks on updating at all.

SEP