Multilib Slackware - disadvantages?
I am aware of the advantages of a multilib Slackware system.
Are there any disadvantages, other than having to take more care of updates and suchlike? |
Can't say I have noticed any, If you run a stable release and add a couple of lines to /etc/slackpkg/blacklist like this
Quote:
I always wait until the release stabilizes before downloading and adding the multi-lib additions. samac |
None that I'm aware of, but I'm just an end user.
:) |
I would have asked the question the other way around: "Pure 64-bit Slackware - disadvantages?"
and the answer to that one is simply one: skype. You can get around that one by using the "static" skype package for 64 bits (it is not really static as it includes a few 32-bit libraries to make it work, however these are only available to skype, they don't "pulute" the rest of the system) there is a good reason why Pat only makes a pure 64-bit build. (BTW, I remember running 64-bit machines back in 1996...) |
Quote:
EDIT: Also - Android SDK. I'll think of more. later probably. As far as I am aware, you might be using more space for both libs, and your system is a tad more complex as a result. I prefer to run pure 64 bit if I have no need for 32 bit libs. But I generally do need them. |
Quote:
|
There are no real advantages or disadvantages to running multilib, other than the ability not to run some 32-bit software. That's why multilib is offered as optional to Slackware.
|
Quote:
|
I did not manage to compile the WRF weather model on multilib Slackware. But on stock 64-bit it compiles without problems.
So the next Slackware installation on both my machines will be pure 64 bit Slackware 14. Skype can be installed neatly using the package with bundled 32-bit libraries, provided in a thread in this forum. I just wish such a package existed also for acroread (Adobe Acrobat Reader). |
Quote:
|
Quote:
I mean the "all distributions AMD64 link here: https://www.virtualbox.org/wiki/Linux_Downloads Markus |
All times are GMT -5. The time now is 09:25 PM. |