> From Nick Holland <n...@holland-consulting.net> > Date Thu, 25 Dec 2014 22:52:15 -0500
>> My system won't run like 90% of the binaries on it. > such as...? > I'm assuming you mean "add-on packages", not base utilities like > "tar" > or "more". If "more" is screwed up, you didn't unpack in the right > directory. My apologies for my lack of specific information. I was a wee bit flustered when this first happened. :) Your assumption is correct; base utilities were working correctly; I didn't notice any problems with anything in /bin or /sbin, but when I ventured outside of there I started finding more problems. > This is user error. This upgrade *IS* trickier than most, but that's > why we carefully document things -- if you follow the process, it > works fine. I'm well aware of that. I've been using OpenBSD since 4.x, and a few times before that for brief stretches. After another response to my initial post I ended up tracing the problem down to /etc/pkg.conf and $PKG_PATH, both set for the entire system, pointing at irrelevant versions. One was pointing at a 5.4 repository and another was pointing at a 5.3 repository. That seems like a rather strange portion not to automate in the upgrade process, but I've hardly ever rolled a distribution of an OS before. > Well, you didn't provide many details of what you actually did, but > it is pretty obvious you did not uninstall all packages BEFORE you did the > upgrade. Sucks to be you, but I bet you read the instructions more > carefully next time. :) Good news, should be recoverable. > The fact that you have binaries that don't run proves you didn't > remove the packages before upgrade. The other options are your kernel and > userland are out of sync (i.e., forgot to upgrade kernel or userland) > or you unpacked your userland to a different location, but either of > those would probably be far worse situations. Well I got a little slightly more detailed information on recovering from foolishness that I caused like this, and have implemented a recovery strategy to the best of my limited mindset. ;) Unfortunately, things are still out of sync a bit; everything, again, out of the primary /bin and /sbin directories, seems to pretty much be crashing on attempts to load invalid libraries. I'll consolidate the actual debugging output and facts of the matter into my reply to that message; if you're still willing to help, I certainly do appreciate your input on the problem. Should be posted within a relatively short amount of time here. Thank you for your time & help on this matter. -Damon
