No, but there is a l337 514ck3r reading this thread.

okay, guess i'll just figure it out myself, thanks anyway.

Brian what are you insinuating?

About what? Do you mean the "1337 514ck3r" comment? Thought I saw somebody else viewing this thread, who knew more than me.

Well what would you do in this situation, no offense but a man of your years must have some insight?

Is there a possibility that the upgrade installed the wrong arch? If you are using multilib, did you point slackpkg to x86 instead of x86_64?

Fraid not. On the ladder from noob to expert, I'm still on a fairly low rung.

guess that makes two of us brian , thank you for your response mlangdn, just check my mirrors and slackpkgplus.conf all pointing to x86_64 repos. removed the compat32 openssl packages and still no go any other ideas.

Was the openssl-solibs pkg installed as well? Now I'm out of ideas.

yes it was mlangdn.

LOL! it was a special shadow package I had installed from sbo that was a fix for gksu to work that I removed during the upgrade.

DOH!

All is well after re-installing it. I was just ranting on in the Slackware vs BSD thread about how FreeBSD has no services started by default well thank god Slackware does or else I would have never been able to ssh into the box and retrace my steps as easily! Thanks to Brian and mlangdn for trying to help my noobishness :P , and I still havent been able to break this slackware yet through all my noob moves.

BEST DISTRO EVER!

Glad you've got it sorted out. Mark it as solved, from the Thread Tools.

Nice work! Just goes to show - never give up!

Yes Sir! And thanks again fellas! Hopefully I can return the favor sometime.

ehm, dunno what your problem was, but I'm pretty sure we don't have anything like that on SBo...