LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-15-2014, 08:34 AM   #1
ga_flyer
LQ Newbie
 
Registered: Apr 2014
Location: Atlanta, GA
Distribution: Slackware
Posts: 4

Rep: Reputation: Disabled
Thumbs up Patching SW14.1 breaks it completely (/bin/login won't execute)


After patching SW14.1 two days ago (04/13/2014) with all available patches applied to an unpatched SW14.1 install, it no longer works.

The system logs suggest some executables (such as /bin/login -- kinda important -- and /lib/udev/udisks-part-id no longer execute even though the files are there mode 755. This suggests that after patching they are incompatible with dynamic libraries).

Logs now include the following (the binaries exist and perms include executable):

Apr 14 14:05:02 flash agetty[765]: tty1: can't exec /bin/login: No such file or directory

Apr 14 21:19:14 flash udevd[479]: failed to execute '/lib/udev/udisks-part-id' 'udisks-part-id /dev/loop2': No such file or directory

Apr 14 20:33:14 flash udevd[502]: failed to execute '/lib/udev/udisks-probe-ata-smart' 'udisks-probe-ata-smart /dev/sda': No such file

The hardware is a lenovo T61 Thinkpad laptop. I still can boot SW13.37 for analysis and repair.

I'm puzzled that nobody else has experienced this but I don't see what I might have done wrong. I've been using SW for 19 years! THANKS!

Last edited by ga_flyer; 04-15-2014 at 09:14 AM. Reason: Correct typos.
 
Old 04-15-2014, 08:48 AM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106
My first guess is that your patches were meant for a different architecture than the originally installed OS - for instance, you have upgraded a 32-bits Slackware OS using 64-bit packages or vice-versa.

Eric
 
1 members found this post helpful.
Old 04-15-2014, 08:56 AM   #3
Mark Pettit
Member
 
Registered: Dec 2008
Location: Cape Town, South Africa
Distribution: Slackware 15.0
Posts: 619

Rep: Reputation: 299Reputation: 299Reputation: 299
Only 19 years ! Well there's your problem. You need 20 years experience to be a slacker :-)

Good luck !
 
1 members found this post helpful.
Old 04-15-2014, 09:30 AM   #4
ga_flyer
LQ Newbie
 
Registered: Apr 2014
Location: Atlanta, GA
Distribution: Slackware
Posts: 4

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Alien Bob View Post
My first guess is that your patches were meant for a different architecture than the originally installed OS - for instance, you have upgraded a 32-bits Slackware OS using 64-bit packages or vice-versa.

Eric
Yup, that appears to be it. THANKS for your LIGHTNING-FAST HELPFUL solution!

I did install the 64-bit SW14.1, my first 64-bit SW install. For patching, I cloned my 32-bit patch download scripts to FTP patches from:

ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages

Clearly, the right location is:

ftp.slackware.com/pub/slackware/slackware64-14.1/patches/packages

I assume that I'll need to do:

upgradepkg --reinstall oldpackagename%newpackagename [old2%new2] ...

including any packages where there was a patch only in the 32-bit version by specifing the original 64-bit package.

Again, THANKS!

Last edited by ga_flyer; 04-15-2014 at 09:33 AM.
 
Old 04-15-2014, 06:18 PM   #5
ga_flyer
LQ Newbie
 
Registered: Apr 2014
Location: Atlanta, GA
Distribution: Slackware
Posts: 4

Original Poster
Rep: Reputation: Disabled
Smile Yup, that worked!

Yup, that worked!
 
Old 04-17-2014, 11:52 PM   #6
bormant
Member
 
Registered: Jan 2008
Posts: 426

Rep: Reputation: 240Reputation: 240Reputation: 240
upgradepkg --reinstall *txz does the task, old%new syntax is a bit redundant here.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Trouble with .bin file execution. Completely, utterly new to Linux. Cantankerous Linux - Newbie 6 05-03-2013 09:09 PM
could not execute bin folder of a package from cgi bin script using python ashish hasani Linux - Server 1 04-05-2012 12:18 AM
How do I execute a .bin file? andi_kan Linux - Newbie 3 11-16-2005 08:15 AM
openoffice won't start. cannot execute bin. y? dark_prancer Linux - Software 3 10-15-2005 06:55 AM
Execute .bin fiies nodnarb Linux - Software 3 07-19-2004 05:27 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:06 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration