LinuxQuestions.org
Help answer threads with 0 replies.
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 05-14-2018, 10:27 AM   #16
55020
Senior Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 1,307
Blog Entries: 4

Rep: Reputation: Disabled

This isn't the first time that the labelling on the 14.2 DVD has led somebody to install 32 bit instead of 64 bit

It would be good if we could suggest something constructive to help the OP. Probably like Patrick's two posts here?

https://www.linuxquestions.org/quest...4/#post5846674
 
Old 05-14-2018, 10:37 AM   #17
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231
Considering that the OP's system is (supposedly) brand new, I believe that the easiest way is to do a fresh install.

After all, it is about re-installing all packages from a Slackware64 DVD, then the process duration will be the same.

With the kind note: the OP to look three times on the boot screen for the "Slackware64" thing.

Last edited by Darth Vader; 05-14-2018 at 11:04 AM.
 
Old 05-14-2018, 12:25 PM   #18
Paulo2
Member
 
Registered: Aug 2012
Distribution: Slackware64 -current (started with 13.37(32))
Posts: 412

Rep: Reputation: 126Reputation: 126
Quote:
Originally Posted by Darth Vader View Post
Oh, now I am The Villain?
YES!, Darth Vader.


I have a dual-disc, audio CD in one side and DVD videos on the other side.

There is a label printed CD on the side that is in fact the DVD side,
and a label printed DVD on the side that is in fact the CD side.

The side that I want to play must be with it's label up. easy,
but I always put the wrong side to play.
 
1 members found this post helpful.
Old 05-14-2018, 12:49 PM   #19
ZhaoLin1457
Member
 
Registered: Jan 2018
Posts: 155

Rep: Reputation: 140Reputation: 140
Excuse me, but where is very possible for someone to mistakelly boot the wrong installer or even to inardventenly install the wrong architecture, I dissagree with idea that he would not notice that runs a 32-bit operating system until final, when he successfully configured everything and he arrived in a desktop and starts to browse the on-line docs for adding additional features.

There are lots of bells ringing about architecture, from the dialogs saying that are installed i586 packages, the kernel, the "uname", the lack of "lib64" folders and many other signs that you are in a 32-bit system.

And according with his own words, he's a Slackware noob, but not a Linux begginer; then he should have been noticed at least that the libraries are in "lib" folders, instead of expected "lib64" folders, used by any distribution for x86_64 architecture (Ubuntu, Fedora, Arch)

Even the thread title "Adding multilib to Slack 14.2 broke all /bin commands?" talks about the pure Slackware 32-bit.

That's why I doubt that OP wasn't aware that he runs a 32-bit Slackware before trying to install multilib.

Last edited by ZhaoLin1457; 05-14-2018 at 01:07 PM.
 
Old 05-14-2018, 01:22 PM   #20
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 880

Rep: Reputation: 332Reputation: 332Reputation: 332Reputation: 332
This is a revised and hopefully better version of my initial post. It was morning, my thinking cap was missing and only one cup of coffee and I had to leave for work. All work no pay.

Okay I attempted to to do a recovery with Slackware 14.2 in a virtual machine. This was a fully updated install via slackpkg before starting. I reproduced the problem created by the OP. This is what happened.

The OP properly followed the directions for installing multilib, with one major problem, the installed system was Slackware (x86) not Slackware64 (x86_64). The first part of the install takes care of the compat32-tools, gcc and glibc. Glibc was the failure point.

The compat32-tools and gcc* packages were all installed without issues. The problem was at the installation of glibc. The doinst.sh install script is what caused the problem. Quoting from doinst.sh
Quote:
# Swap glibc on the fly.
#
# If we're on a running system we have to handle this _very_ carefully. :-)
# The tricks involved here get trickier every time...
Well it's expecting to do this on a x86_64 install not a x86 install Installing on a x86 system is an unanticipated and not designed for "trick". After all the purpose of multilib is to add 32-bit capability to a Slackware64 install.

The install was left totally unusable. Nothing worked, as the OP pointed out, basic commands no longer worked. The system could find anything due to the library changes not meant for an x86 install. The machine had to be turned off or reset. Rebooting resulted in: "Kernel panic - not syncing" No working init found." Attempting to boot from the DVD and passing parameters to boot: results in the same. After booting to the DVD you can mount and navigate the install, but you cannot chroot to the mounted drive to do anything useful.

In my original post, I stated the OP could recover by doing an install from the DVD and skip the formatting part. As Didier Spaier pointed out, this "would leave all broken software in the system alongside the good one and result in a broken packages database". Here is why:

Take the x86 install, that I am fairly certain that OP meant to install as a x86_64 system. Here we have a system full of x86 packages. If Slackware64 is installed on top of Slackware we will end up with two sets of packages installed one x86 and one x86_64. If Slackware is installed on top of Slackware, it won't be as bad, but you will end up with two sets of packages for all those patched (_slack14.2 tag) packages. Bottom line, There is only one fix option and that is to format and install. If you need to recover to access data to save I will describe that later.

How to tell if the install is x86 or x64_86. Well in the root of the DVD, one side will have a /slackware directory, the other side will have a /slackware64 directory. When you boot to the DVD the first screen will also tell you what you are about to install.

Welcome to Slackware64 version 14.2 (Linux kernel 4.4.14)! = x86_64 or 64-bit

Welcome to Slackware version 14.2 (Linux kernel 4.4.14)! = x86 or 32-bit

Advanced. Not guarantee to work. It does in my test install, ran it though several times no issues.

Here is the recover option for the x86 install. I tested it, seem to be okay with no problems so far. Boot to the DVD, mount the affected partition to /mnt on the DVD. Run pkgtool and remove the following using "Remove packages that are currently installed": (Do not remove any other packages.)

compat32-tools-3.7-noarch-19alien.tgz
gcc-7.3.0_multilib-x86_64-2alien.txz
gcc-brig-7.3.0_multilib-x86_64-2alien.txz
gcc-g++-7.3.0_multilib-x86_64-2alien.txz
gcc-gfortran-7.3.0_multilib-x86_64-2alien.txz
gcc-gnat-7.3.0_multilib-x86_64-2alien.txz
gcc-go-7.3.0_multilib-x86_64-2alien.txz
gcc-objc-7.3.0_multilib-x86_64-2alien.txz
glibc-2.27_multilib-x86_64-2alien.txz <<< This package may or may not be installed.

After that is done, exit pkgtool, umount /mnt and run setup. Set the TARGET to the affected partition. Do not format this partition. At the PACKAGE SERIES SELECTION screen, deselect all series except for D and L. Next use menu or expert to pick which packages to install. With the D set, deselect everything except the gcc* packages. With the L set, deselect everything except for glibc (a bit tedious do this but it's needed). This will install only those packages. You can probably skip the CONFIGURE THE SYSTEM screen but it doesn't hurt. I tried it both ways.

Now reboot to the hard disk. Now you can use slackpkg to restore the correct packages. Do not run slackpkg update, you don't want to add more packages to the mix.

All of the affected gcc and glibc packages have been patched. So the will be two version of each on the system right now. The one just installed and the one already there (_slack14.2). The best way to handle this is remove the patches. One would think the opposite, but the last package install was the version from the DVD. Do the following:

# slackpkg remove gcc
Then deselect the non patched pacakges (with out the _slack14.2 tag) to remove them. Only the _slack14.2 packages should be selected for removal.

# slackpkg remove glibc
Be careful here, deselect everything except the glibc-2.23 with the _slack14.2 tag. Only one package should be selected. The glibc-2.23 with the _slack14.2 tag.

# slackpkg upgrade-all
This should show you all gcc* the packages and glibc package to upgrade.

Once this is done the system has been recovered.

Last edited by chrisretusn; 05-15-2018 at 08:13 AM.
 
7 members found this post helpful.
Old 05-14-2018, 01:47 PM   #21
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,618

Rep: Reputation: Disabled
Quote:
Originally Posted by chrisretusn View Post
If you have data on the broken Slackware install you need to keep, then skip the format part during the default full install.
This would leave all broken software in the system alongside the good one and result in a broken packages database, so don't do that, but for a separate partition (not the / partition) holding the data you want to keep, case occurring. Or just backup your data before installing anew.
 
3 members found this post helpful.
Old 05-14-2018, 11:06 PM   #22
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 880

Rep: Reputation: 332Reputation: 332Reputation: 332Reputation: 332
Didier Spaier is correct, my post has been removed.
 
Old 05-15-2018, 12:10 AM   #23
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,618

Rep: Reputation: Disabled
@chrisretusn: Actually I just corrected one statement of your globally sound post, furthermore having removed all its content makes the discussion hard to follow. May I suggest that you reinstate it?

Last edited by Didier Spaier; 05-15-2018 at 12:12 AM.
 
1 members found this post helpful.
Old 05-15-2018, 08:21 AM   #24
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 880

Rep: Reputation: 332Reputation: 332Reputation: 332Reputation: 332
Quote:
Originally Posted by Didier Spaier View Post
@chrisretusn: Actually I just corrected one statement of your globally sound post, furthermore having removed all its content makes the discussion hard to follow. May I suggest that you reinstate it?
Done, morning no coffee...
 
Old 05-16-2018, 09:28 AM   #25
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Slackware, Pop!_OS
Posts: 173

Original Poster
Blog Entries: 2

Rep: Reputation: 30
Quote:
Originally Posted by Darth Vader View Post
Oh, now I am The Villain?

OK, let's play politically correct, and blame our BDFL that he made an installer so easy to use that even someone who have no clue what installs still manage to install Slackware, also let's blame Eric Hameleers that he do not specified clear that his multilib cannot add x86_64 support in a 32-bit system.

Also, let's propose to our BDFL to literally specify the architecture within boot screen, something like: "You are about to install the Slackware for 32-bit architercture!" and just to be sure, he should add a confirmation dialog on starting the installer, with the same sense.

Oh, and probably Eric should amend the docs and to specify clear that his multilib cannot add x86_64 support in a 32-bit system. Just in case.
I'm not really sure why I'm even engaging any more, but oh well. Saying I "have no clue" because of a single post!

No need to change anything about the multilib packages - it's clear what they do. Indeed, as everyone has figured out, my mistake was installing 32-bit Slackware when I thought it was the 64-bit version. Same DVD, just flipped over.
 
Old 05-16-2018, 09:41 AM   #26
thethinker
Member
 
Registered: Jul 2006
Location: Peabody, MA, USA
Distribution: Xubuntu, Slackware, Pop!_OS
Posts: 173

Original Poster
Blog Entries: 2

Rep: Reputation: 30
Quote:
Originally Posted by chrisretusn View Post

Once this is done the system has been recovered.
I really appreciate the work done here. This is exactly why I come to LQ, and exactly why I use Slackware - knowledgeable people with a passion for finding solutions. I guess you can't get this without the occasional flaming...

...but actually I did a fresh install last night, which seemed simpler since it was a new machine anyway. So I'm going to mark this as solved, give you all the karma points in the world, and hopefully someone else who does this particular blunder will be helped by your efforts.

Thanks!
 
4 members found this post helpful.
Old 05-16-2018, 09:52 AM   #27
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231
Quote:
Originally Posted by thethinker View Post
Saying I "have no clue" because of a single post!
You are the one claiming that.

I for one, I strongly believe that you had been well aware that you installed and run Slackware 32-bit, at least after finishing the installation, specially because you are not a newbie in Linux, then you had terms of comparation with the other operating systems.

I apologize for not being politically correct, but be kind to call that as cultural difference, because I am European, not American.

Last edited by Darth Vader; 05-16-2018 at 10:36 AM.
 
Old 05-17-2018, 03:19 AM   #28
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 880

Rep: Reputation: 332Reputation: 332Reputation: 332Reputation: 332
Quote:
Originally Posted by thethinker View Post
I really appreciate the work done here. This is exactly why I come to LQ, and exactly why I use Slackware - knowledgeable people with a passion for finding solutions. I guess you can't get this without the occasional flaming...

...but actually I did a fresh install last night, which seemed simpler since it was a new machine anyway. So I'm going to mark this as solved, give you all the karma points in the world, and hopefully someone else who does this particular blunder will be helped by your efforts.

Thanks!
We have all done blunders. I have some big ones back in the day as a system administrator. I had fun testing this out and learned a few things my self. Glad I was of help. Since you were, I think... installing a x86_64 install, the easiest choice, the one you decided on was the best.

You should see the system I did a test install of a x86_64 on top of x86, what a mess. LOL.
 
2 members found this post helpful.
Old 05-18-2018, 07:46 AM   #29
coldbeer
Member
 
Registered: May 2006
Location: Orion–Cygnus Arm, MWG
Distribution: Slackware, Ubuntu
Posts: 249

Rep: Reputation: 130Reputation: 130
Quote:
Originally Posted by Darth Vader View Post
You are the one claiming that.

I for one, I strongly believe that you had been well aware that you installed and run Slackware 32-bit, at least after finishing the installation, specially because you are not a newbie in Linux, then you had terms of comparation with the other operating systems.

I apologize for not being politically correct, but be kind to call that as cultural difference, because I am European, not American.

Don't you realize, Darth, that you are NOT giving the O.P. the benefit of the doubt WHILE AT THE SAME TIME ASKING for the benefit of the doubt of your own transgressions due to "cultural differences" ? And as you put it, you are not a newbie to the english language and not a newbie to LQ.

Just saying.....

And for the record, I have also had to hesitate and figure out which way to put the DVD in every single time I use it. And I'm older than you.
 
2 members found this post helpful.
Old 05-18-2018, 07:47 PM   #30
glorsplitz
Member
 
Registered: Dec 2002
Distribution: slackware!
Posts: 655

Rep: Reputation: 130Reputation: 130
I'm with Lord Vader, RTFM and OP's not a newbie.

Last edited by glorsplitz; 05-18-2018 at 07:51 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
[SOLVED] Would System Commands be Considered Those Commands under /bin? JockVSJock Linux - Newbie 2 04-26-2016 01:40 PM
multilib slackware64 <--I broke it, need advice smitchel1099 Slackware 17 11-20-2015 10:59 AM
Help! I think I broke the Less and Man commands... Biggen Linux - Newbie 3 09-30-2004 04:34 PM
adding commands to /bin (root user) xone Linux - Software 4 03-23-2004 01:26 PM
broke /bin/hostname nitsky416 Linux - Networking 2 11-30-2003 05:45 AM

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

All times are GMT -5. The time now is 01:20 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration