I have a many systems which use up2date to install new kernels when they
become available. The machines then will do a reboot at the next
appropriate time.
But on a few of them, I have custom NIC drivers installed as modules.
If the machines are left to their own the new kernel would not load the
old kernel modules (they might not be compatible too).
The modules are delivered as an RPM with requires kernel = matching-version
but since up2date does an 'pkgsToInstallNotUp' on the kernel RPMs, we can
have a new kernel installed without the requires dependency being broken
on the module RPM.
My first thought was to add a conflicts kernel > matching-version to
prevent the new kernel from installing without a matching upgrade on the
module RPM. This has two drawbacks. One, it would uninstall the old
module RPM. Two, requires a new RPM to be built and installed for the
old kernel version.
So in summary the tasks are:
1) prevent new kernel from being installed by up2date until
matching-version module RPM is available.
2) install (not upgrade) new kernel and kernel-module-nic by up2date, when
both are available.
2) allow rpm -e kernel-version-old kernel-module-nic-old
3) allow rpm -e kernel-version-new kernel-module-nic-new
Any suggestions?
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Partner & Sr. Manager 7 West 24th Street #100 -
- +1 (443) 921-0381 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you
have received it in error, purge the message from your system and
notify the sender immediately. Any other use of the email by you
is prohibited.
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
