I did it.
It worked. At least… command run during 22/06 and until now no users complained. I had my nice dose of config and data backup, but anyway @Andy_Wismer @mark_nl i’ll keep telling to my customers “backup, backup often, backup now”. And i apprecieate who does that.
Moreover an important hint: is your system a “specialty”? I mean, single board computers, pre-cooked (installed) branded servers, custom build and install from other people?
Consider safer to not do yum autoremove on your system.
OEM, you, who installed the server could have used rpm instead a repository to enable something of your hardware: storage controllers, LCD displays, diagnostic boards, fibre channel and/or not-common network cards. Therefore, yum and RPMDB could not know that the small package you carry into the server is there for allowing it to use something critical.
So reviewing every single package before allowing yum autoremove to delete them from your install, for avoiding for instance:
- missing data on the LCD Display of a firewall box
- missing network/fibre/storage network card from the newer kernel which will be delivered to your sistem
- missing custom-installed wireless network adapters for your favourite
hostapdAP
Cheers
