LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   slackware64 multilib pros and cons? (http://www.linuxquestions.org/questions/slackware-14/slackware64-multilib-pros-and-cons-795915/)

Pluribootent 03-16-2010 09:35 PM

slackware64 multilib pros and cons?
 
I am running slackware64 successfully, really dig it. Only problem is, Im missing sunbird and skype from time to time.

I read the howto bout building the multilib several times and I am about to go those steps.

I need to know bout the experience of other users, concerning upgrade issues.

If I build a multilib:

Can I upgrade my slackware13 to slackware14?
or would I have to change the packages back to original "non-multilib"?
could I use slackpkg to remove all multilib packages and return to a save non-multilib environment?
would there be a howto, when that happens?

thank you all for your replies.

Greetings, Pluribootent

onebuck 03-16-2010 10:09 PM

Hi,

You should look at 'Multilib SlackwareŽ for x86_64' to get some insight & information.

:hattip:
The above link and others can be found at 'Slackware-Links'.
More than just SlackwareŽ links!

slkrover 03-16-2010 10:47 PM

I am running a slackware multilib 64. I tried it with a 64b system already running so I could play games and it didn't work.I think this was just a problem with the gfx driver as wine installed with no problems. I had to do a fresh install and put the 32 libs in before doing anything other than updating the 64libs. I didn't do xorgsetup or install the gfx driver till after the 32 lib install. The 64b gfx driver from nvidia installs its 32libs for you when installing the driver, very easy. I even used wine 1.14 from winehq not Bobs, it even istalled gecko right. Everything works great, playing 32b windows games in wine and installing 32b software. My first 64b install I used sbopkg edited to SB64,master and there are very limited packages to use. With the 64b install I am using now I decided to try sbopkg without edits so I could use some of the 32b stuff also ( like daisy-applet). It works great. If there is a 64b application it will install automatically and if not it makes a 64b tgz package and if it cant it just installs the 32b package. Opera automatically installed its 64b program, Nexiuz created a 64b package and Daisy just installed the 32b package. ( I think the default ARCH setting controls all this). They all work great. In the first 64b install I could not get slackpkg to blacklist the kernel or the libs,gcc even when it says they are blacklisted so I don't even try any automated updating but this runs so well I don't think I will need to update for some time.I am very happy. I don't know if you will have a problem updating to slackware 14. I had not thought that far ahead.

P.S I have a fast hdd and the Slackware13 32b DVD so it didnt take long to do and I run KDE, wine never seems to work right for me with xfce or fluxbox. I dont know how long it takes when downloading the 32b files.

Alien Bob 03-17-2010 03:07 AM

Quote:

Originally Posted by Pluribootent (Post 3901142)
I am running slackware64 successfully, really dig it. Only problem is, Im missing sunbird and skype from time to time.

I read the howto bout building the multilib several times and I am about to go those steps.

I need to know bout the experience of other users, concerning upgrade issues.

If I build a multilib:

Can I upgrade my slackware13 to slackware14?

Yes. When Slackware 13.1 gets released, there will also be appropriate new multilib packages available so that you can upgrade those too. For Slackware -current they are here: http://connie.slackware.com/~alien/multilib/13.1/
Quote:

or would I have to change the packages back to original "non-multilib"?
This is not necessary, as long as you blacklist the gcc and glibc packages you replaced with their multilib versions.
Quote:

could I use slackpkg to remove all multilib packages and return to a save non-multilib environment?
Sure, when you remove the lines for multilib packages that you possibly added to your /etc/slackpkg/blacklist and run "slackpkg update ; slackpkg upgrade-all" any multilib package will be replaced with the original Slackware64 package.
Quote:

would there be a howto, when that happens?
Perhaps. For now, what I wrote here is sufficient.

Eric

SpelledJ 03-17-2010 10:06 AM

I'll share a note of caution. I wanted to remove Eric's KDE 4.4 packages and go back to 3.5. I had forgotten about installing the multilib packages, and did this:

Code:

*WARNING DO NOT ATTEMPT WITH MULTILIB INSTALLED*
cd /var/log/packages
removepkg *alien*

I was thinking that the only "alien" packages were from KDE4, but with mulitib, you'll notice that your gcc and glibc will now be the "alien" versions. I watched my slack box give itself a slow-motion lobotomy until it could no longer delete files. It finally dropped to a bash prompt that could no longer even do an "ls".

After I realized what I'd done I was still confused because I thought it would just go back to a pure Slackware64 without multilib. But because Eric's packages are replacements, not just additions, you can't just removepkg *alien*. You have to reinstall the original Slackware64 gcc and glibc if you want to remove multilib.

Luckily I was able to recover with my install DVD and then reinstall multilib. Lesson learned. Don't do major system changes late at night when you really should just turn the thing off and go to bed.

metageek 03-18-2010 03:23 AM

Quote:

Originally Posted by SpelledJ (Post 3901906)
Lesson learned. Don't do major system changes late at night when you really should just turn the thing off and go to bed.

I happens to us all at one point or another. I Once rm -rf * from /etc and then slowly realized what this meant. Fortunately it was not so late in the night and I could think a bit and instead of shutting down the machine I slowly recreated enough config files by hand to put it in a state that it be able to boot successfully again... (but ls and echo were still working for me)

lumak 03-18-2010 09:11 AM

If you compile a lot of software, compile all 64bit packages BEFORE going multilib. This will save you the headache of having to add extra environment variables for the packages that want to use the 32bit libs. This is especially nasty with cmake and QT.

If you are needing 3D support for 32 bit apps. You will probably need the compatibility drivers from your manufacture. Nvidia has 3 different packages. The one you need will have pkg2.run at the end.

Even with multilib, somethings will never compile... BUT! if you have binaries, they will still run. Zsnes for example.


All times are GMT -5. The time now is 08:55 PM.