[SOLVED] Fresh Install of Slackware 64 14.2, Missing Things (Mplayer & SSHD) and How Do I Kill Network Manager

tronayne · 08-16-2016, 02:27 PM

Did a clean install (of everything) on my lap top (don't want to risk the workstation yet).

Window Manager: Xfce

Mplayer does not exist (what the heck happened to it?). Now what.

Down in the corner of the task bar are what look to be Network Manager icons. I do not want Network Manager, I'm fond of Wicd. How do I get rid of Network Manager? It'd not executable in /etc/rc.d, so who started it and how do I kill it? Or convince me that I should be in love with it.

And, then, SSH seems to be kaput:

Code:

pita-root-/etc/rc.d: rc.sshd start
rc.sshd: line 19: /usr/bin/ssh-keygen: cannot execute binary file: Exec format error
rc.sshd: line 21: /usr/sbin/sshd: cannot execute binary file: Exec format error

I did install all the available patches (the Firefox and Thunderbird ones would not start, backed 'em out and reinstalled the disk packages). But no SSH seems to be a bit much.

Alien Bob · 08-16-2016, 02:36 PM

I guess you mixed a 64bit OS with 32bit patches (or vice versa) and the result is a broken system.

As for the NM control widget in the system tray, you can simply remove it if you do not use networkmanager. WICD Is not installed by default, you have to install it from Slackware's ./extra directory.

bassmadrigal · 08-16-2016, 03:56 PM

Quote:

Originally Posted by tronayne

Mplayer does not exist (what the heck happened to it?). Now what.

It's supposed to exist...

http://packages.slackware.com/?r=sla...5-x86_64-3.txz

The package's name is with a capital MP for MPlayer, but the binary is all lowercase, mplayer.

Ztcoracat · 08-16-2016, 11:13 PM

https://slackbuilds.org/mirror/slack....1/extra/wicd/

tronayne · 08-17-2016, 12:34 PM

Well, OK, I blew away root and reinstalled (I only install in root, everything else is on various partitions and they are simply added without formatting). I did check what the patches were:

Code:

pita-trona-/usr/local/patches: ls
bind-9.10.4_P2-x86_64-1_slack14.2.txt
bind-9.10.4_P2-x86_64-1_slack14.2.txz
bind-9.10.4_P2-x86_64-1_slack14.2.txz.asc
curl-7.50.1-x86_64-1_slack14.2.txt
curl-7.50.1-x86_64-1_slack14.2.txz
curl-7.50.1-x86_64-1_slack14.2.txz.asc
gimp-2.8.18-x86_64-1_slack14.2.txt
gimp-2.8.18-x86_64-1_slack14.2.txz
gimp-2.8.18-x86_64-1_slack14.2.txz.asc
glibc-zoneinfo-2016f-noarch-1_slack14.2.txt
glibc-zoneinfo-2016f-noarch-1_slack14.2.txz
glibc-zoneinfo-2016f-noarch-1_slack14.2.txz.asc
libidn-1.33-x86_64-1_slack14.2.txt
libidn-1.33-x86_64-1_slack14.2.txz
libidn-1.33-x86_64-1_slack14.2.txz.asc
mozilla-firefox-45.3.0esr-x86_64-1_slack14.2.txt
mozilla-firefox-45.3.0esr-x86_64-1_slack14.2.txz
mozilla-firefox-45.3.0esr-x86_64-1_slack14.2.txz.asc
mozilla-thunderbird-45.2.0-x86_64-1_slack14.2.txt
mozilla-thunderbird-45.2.0-x86_64-1_slack14.2.txz
mozilla-thunderbird-45.2.0-x86_64-1_slack14.2.txz.asc
openssh-7.3p1-x86_64-1_slack14.2.txt
openssh-7.3p1-x86_64-1_slack14.2.txz
openssh-7.3p1-x86_64-1_slack14.2.txz.asc
php-5.6.24-x86_64-1_slack14.2.txt
php-5.6.24-x86_64-1_slack14.2.txz
php-5.6.24-x86_64-1_slack14.2.txz.asc
samba-4.4.5-x86_64-1_slack14.2.txt
samba-4.4.5-x86_64-1_slack14.2.txz
samba-4.4.5-x86_64-1_slack14.2.txz.asc
stunnel-5.35-x86_64-1_slack14.2.txt
stunnel-5.35-x86_64-1_slack14.2.txz
stunnel-5.35-x86_64-1_slack14.2.txz.asc

Can anybody see anything wrong there? I sure can't but have not redone the patches on this install as yet.

Turns out that mplayer (the command line version) actually does exist (now) and SSH configures and attaches to one of the other computers (I only do the laptop first to make sure everything is going to work).

I use Xfce as a window manager. Existing accounts connect and work just fine; those accounts are in /home which does not get formatted during installation. Root, well, root is a different matter, Xfce is slower than a three legged dog with a busted tail and seems to have a problem logging out (like 3 or 4 minutes!).

When I do the initial install I copy things from a saved copy of /etc; e.g, passwd, shadow, profile.d/ksh.sh (sets the system to default to KornShell, works fine), fonts/local.conf (I keep non-release fonts in /usr/local/fonts) stuff like that.

Also, when I do batch updates of patches I put the system in single user and reboot when things are all done. I have not done the patches as yet and I'm hoping the thing doesn't poop its pants again.

So, anyway, onward and hopefully upward.

tronayne · 08-17-2016, 02:39 PM

Got all the way through another fresh install, configured pretty much everything, worked fine.

Did upgradepkg *.t?z in my directory /usr/local/patches which contains the above referenced list of files; e.g.,

Code:

mozilla-firefox-45.3.0esr-x86_64-1_slack14.2.txt
mozilla-firefox-45.3.0esr-x86_64-1_slack14.2.txz
mozilla-firefox-45.3.0esr-x86_64-1_slack14.2.txz.asc

and all the others.

Did it in single use, rebooted, try to start any of the patched programs and get

Code:

cannot execute binary file: Exec format error

for Firefox, Thunderbird, SSH, etc.

The downloaded patch files are from

Code:

http://ftp.osuosl.org/pub/slackware/slackware64-14.2/patches/packages/

the files are dated 2016-08-06.

The actual command to do so is

Code:

wget ftp://ftp.osuosl.org/pub/slackware/slackware64-14.2/patches/packages/*

Is there any chance that those files on that mirror are actually 32-bit in the 64-bit patches directory with 64-bit names? And, if not, what the hell is going on and what can I do to fix it?

Really don't want to try and live without security patches, methinks.

Alien Bob · 08-17-2016, 02:53 PM

Your original OS is 32bit perhaps?

What is the output of "uname -a"?

tronayne · 08-17-2016, 03:00 PM

No, there has never been a 32-bit installation on this system, always been Slackware 64-bit.

I shut the thing off because few things would work after updating and am calming down before I whack it again.

Alien Bob · 08-17-2016, 03:01 PM

I still would like to see the output of "uname -a" once you calmed down enough. Just to strike one possible cause off.

tronayne · 08-17-2016, 03:02 PM

No, there has never been a 32-bit installation on this system, always been Slackware 64-bit (and only Slackware after I blew away Windows a long, long time ago).

I shut the thing off because few things would work after updating and am calming down before I whack it again -- or just give up and live with it but it won't touch any other system till I figure out what I've done wrong.

tronayne · 08-17-2016, 03:15 PM

Gotta type this on the 14.1 box, try to get it right.

Linux pita 4.4.14-smp #2 Fri Jun 24 14:44:24 CDT 2016 i686 Pentium(R) Dual-Core CPU T4300 @ 2.10GHz GenuineIntel GNU/Linux

That's it.

tronayne · 08-17-2016, 03:18 PM

Oh, yeah, have to go away for an hour or so.

Alien Bob · 08-17-2016, 03:48 PM

Quote:

Originally Posted by tronayne

Linux pita 4.4.14-smp #2 Fri Jun 24 14:44:24 CDT 2016 i686 Pentium(R) Dual-Core CPU T4300 @ 2.10GHz GenuineIntel GNU/Linux

Yeah... you have installed a 32bit Slackware alright.

suppy · 08-17-2016, 03:51 PM

Quote:

Originally Posted by tronayne

Gotta type this on the 14.1 box, try to get it right.

Linux pita 4.4.14-smp #2 Fri Jun 24 14:44:24 CDT 2016 i686 Pentium(R) Dual-Core CPU T4300 @ 2.10GHz GenuineIntel GNU/Linux

That's it.

I gotta tell you, that's a 32bit slackware right there

Ztcoracat · 08-17-2016, 03:53 PM

Happens to the best of us. I've by accident installed the 32-bit version of Slackware in the past.

http://mirrors.slackware.com/slackwa...re64-14.2-iso/