On Sun, Oct 23, 2022 at 7:24 PM American Citizen <[email protected]> wrote:
> I was able to use cpio to unpack the good working copy of the ps binary > executable, and manually placed it into the proper location on my hard > drive, to restore ps command functionality. > > Lo and behold, about 37 minutes later, my openSuse autoupdate program > comes along and says "You have 1 new update" "Recommended update for > procps" > > maybe someone else experienced the same situation as you, and filed a bug report? which was then fixed and released in an update? Over my dead body will I allow this software to do this update! > this would be a good opportunity to make a backup. then, there's no harm in trying the update to see what it does. > How did openSuse determine that I changed the ps command and restored it? > it is unlikely that they detected the restoration. it is more likely that whatever the underlying cause of the disappearance in the first place was, has been fixed. > How did openSuse determine that my system need to be hit with a > recommended mandatory update that won't go away until I actually give in > and accede to this disabling update which destroys ps functionality? > that was clearly not the intention. > > This whole thing has become obvious now, and I might write Novell and > let them know what I really think > > just keep in mind that this is not unique to suse. this sort of thing is ridiculously common among all flavors of linux, and all operating systems. it's not possible for anyone to take into account every possible situation. that's a bit of a lame excuse, since most of them can barely keep up with the stuff they actually officially support, but it's important to keep our expectations realistic. speaking of which, you went way past my expectations by figuring out how to download and extract an rpm. kudos to you. also, novell and suse have (separately) been bought out multiple times. -wes
