Dear Fred (and List), On Thu, 2019-12-12 at 14:02 -0500, Fred Gleason wrote: > On Dec 9, 2019, at 18:42, David Klann <[email protected]> wrote: > > > More details: you *could* do: > > > > sudo rpm --erase --no-deps hpklinux > > > > I'm not completely sure how CentOS will behave when you next do a "yum > > upgrade" and there is also a Rivendell upgrade. I believe yum will simply > > re- > > install the hpklinux package, and you'll have to remove it again. Or the > > alsa- > > firmware package will conflict with the upgrade and you'll have to do > > something like "yum upgrade --skip-broken" to get it to install. Either > > way, > > it will probably require on-going attention over the life of the system... > > You do *not* want to do this! In addition to being just a Really Bad Idea in > general, it will break Rivendell. This is because the ‘hpklinux’ package > provides user-space library components in addition to the kernel driver; > removing those will mean that caed(8) will have unsatisfied link > dependencies and hence be unable to run. This true whether there is an ASI > card actually installed or not. > > The package dependency system is there for a reason. You should never bypass > it on a production system. Even in an ‘experimental’ setup, you have to very > careful. It’s easy to remove something essential inadvertently and wind up > with a completely non-functional system! It can be near-impossible to > recover from such a situation short of completely reinstalling the OS. > > Cheers! >
Yikes! I now see what you mean. /lib64/libhpi.so.10 is a dynamically loaded library on which caed and ripcd depend. Thank you for correcting me! I'll refrain from such "shortcut" suggestions in the future! Best regards, ~David Klann _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
