Skip to main content

yum update but exclude multiple packages


I have up2date setup for my servers to update most packages but ignore kernel updates as well as oracleasm-related updates. Kernel updates break things and must be done manually, when needed. However, I prefer using yum over up2date. But until now I did not find an easy way to tell yum to ignore updates on some packages. An old Duke mailing list had an improved man yum text that eluded to add multiple exclude=package* statements to the repos in /etc/yum.repos.d/. Thanks Duke!
Here is my example yum repo configuration with the excluded packages:
[el4_patch]name=Oracle Enterprise Linux - $releasever - $basearch - patchbaseurl=http://uln.example.com/yum/EL4/$releasever/patch/$basearch/exclude=kernel*exclude=oracleasm*gpgcheck=1enabled=1

Update: something is still not right for it just upgraded the kernel anyway.
Update2: When I moved the 'exclude' lines before the 'enabled' line, the yum update process does indeed ignore kernel updates, as expected. Before, I had the exclude lines after the line to enable that repo.
Update3: You can exclude at the main yum level (/etc/yum.conf) and on a per-repository basis. Using the command line switch disableexcludes=all you can then manually install the otherwise packages anyway. [Source]

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Preventing PuTTY timeouts

Just found a great tip to prevent timeouts of PuTTY sessions. I'm fine with timeouts by the host, but in our case the firewall kills sessions after 30 minutes of inactivity... When using PuTTY to ssh to your Linux/Unix servers, be sure to use the feature to send NULL packets to prevent a timeout. I've set it to once every 900 seconds, i.e. 15 minutes... See screenshot on the right.
1 comment
Read more

Removing VGs or LVs from LVM

While are many excellent tutorials about creating and using LVM on Linux, not may show you how you can remove disks from LVM Volume Groups (VG) and reclaim storage or how to remove a Logical Volume (LV) from your LVM set-up. Here is what I did: Use -t to TEST ANY LVM action first! We are going to release 1 TB from LVM. The Volume group was extended with 1 TB storage to serve as a cheap NFS/CIFS file server when setting up our data center. It is now deprecated and replaced by a NAS so it's no longer needed. 1) check LVM; note the four 256 GB LUNs [root@server ~]# pvscan -v Wiping cache of LVM-capable devices Wiping internal VG cache Walking through all physical volumes PV /dev/sdb1 VG vgdata lvm2 [50.00 GB / 0 free] PV /dev/sdc1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdd1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sde1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdf1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdg ...
Post a Comment
Read more

Dell Linux - OMSA Hardware Monitoring

Just getting started using Dell's OpenManage Server Administrator (OMSA) on our Oracle Linux platform. There are some confusing instructions going around so it's not immediately clear what to do, hence my blogging here. :) There is a site on Dell - Hardware Monitoring , as well as a wiki with instruction on how to setup their OMSA tooling using yum or up2date. [update]My first update for their instructions: be sure your server has Internet access, as most servers will use a proxy or so. use export http_proxy=http://yourproxy.example.com:port to configure it just for the session, and setup up2date to use an HTTP proxy by editing the settings in /etc/sysconfig/rhn/up2date .
2 comments
Read more