SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So nvidia linux users will no longer be able to use multilib programs like steam or wine in the future?
they will only be able to use multilib to run steam/wine/others 32bit, but have no 32 bit distro anymore.
that's why I have put this thread up, and that's why I think multilib as part of Slackware needs to be re-evaluated
I have a huge appreciation for the Eric's Multilib, and I consider it a brilliant piece of engineering. After all, he managed somehow to put a 32 bit Slackware in another, x86_64.
BUT, I believe that if one go 64, should go 64 all the way, not mixing things. You cannot leave 32 all way? Stay on 32, for gods sake! No excuses could be taken!
PS .My computers ecosystem is a mixed one. I have 32 bits installations, and PURE x86_64 installations. BUT out of 8, no one is multilib.
PS2. I specially avoid to think/realize that someone dare to propose to put down The Slackware! Until now, x86_64 is just a port, even it is a blessed one, in my humble opinion.
Last edited by Darth Vader; 12-22-2017 at 11:59 AM.
I have a huge appreciation for the Eric's Multilib, and I consider it a brilliant piece of engineering. After all, he managed somehow to put a 32 bit Slackware in another, x86_64.
BUT, I believe that if one go 64, should go 64 all the way, not mixing things. You cannot leave 32 all way? Stay on 32, for gods sake! No excuses could be taken!
PS .My computers ecosystem is a mixed one. I have 32 bits installations, and PURE x86_64 installations. BUT out of 8, no one is multilib.
PS2. I specially avoid to think/realize that someone dare to propose to put down The Slackware! Until now, x86_64 is just a port, even it is a blessed one, in my humble opinion.
wow, what a bubble, no content, ignoring all facts, just phrases, total meaningless, but an excellent pathetic text. respect :-)
Patrick Volkerding already made public his POV about multilib in the official distribution: nope.
Eric Hameleers already said that they consider the systematic put down of 32 bits by the other distributions as an excellent opportunity to gain new followers and they intend to speculate that.
Are other facts there?
BTW, please ignore a fact: I have two boxes and two netbooks, all of them 32 bits.
Last edited by LuckyCyborg; 12-22-2017 at 01:07 PM.
If 32-bit is dying, why have it in 64-bit? Multilib has always been a horrible hack.
Quite. I'm glad Slackware doesn't include multilib by default and look forward to the day we can go back to using /lib and get rid of this ugly /lib64 stuff.
wow, what a bubble, no content, ignoring all facts, just phrases, total meaningless, but an excellent pathetic text. respect :-)
Thanks you!
And, IF you talk about fundamentalism, in this note be kind to note that I am a proud 32 bits Mujaheddin.
Your talk about putting down the 32 bits is not what I want to think about, specially right now, before Christmas. You can leave it for the summer of 2027, please?
Or for when Linus Torvalds remove the 32 bits support from the Linux Kernel, which one come first.
Last edited by Darth Vader; 12-22-2017 at 03:08 PM.
Quite. I'm glad Slackware doesn't include multilib by default and look forward to the day we can go back to using /lib and get rid of this ugly /lib64 stuff.
horrible hack? well, I agree that I find the arch solution more elegant than what many other do, but calling a widely well working solution horrible hack shows some kind of ignorance.
well, thanks all for your contribution, also those who just have some opinion without any evidence of knowledge that they know what they are talking about
And, IF you talk about fundamentalism, in this note be kind to note that I am a proud 32 bits Mujaheddin.
Your talk about putting down the 32 bits is not what I want to think about, specially right now, before Christmas. You can leave it for the summer of 2027, please?
actually, if you go back and read carefully, it was nvidia talking about putting down the 32 bits
and I was thankful for Erics explanation why some might want to have it.
so don't spread any rumors,
and, it has of course nothing to do with the inability of 64 bit Slackware to run 32bit applications what will soon be the only way to run fully supported 32 bit apps on an actual system, and that's not because I take 32 bit down, but the world does it
I know well about what you talk about: you declare all my computers obsolete and good for the recycle bin.
Because you live in a rich country where you buy a new car every month. If you are so rich, why you do not outsource also your own work and be happy? And you make an Indian or Chinese happy too.
Thanks you!
Last edited by LuckyCyborg; 12-22-2017 at 01:25 PM.
actually, if you go back and read carefully, it was nvidia talking about putting down the 32 bits
and I was thankful for Erics explanation why some might want to have it.
so don't spread any rumors,
and, it has of course nothing to do with the inability of 64 bit Slackware to run 32bit applications what will soon be the only way to run fully supported 32 bit apps on an actual system, and that's not because I take 32 bit down, but the world does it
You really believe that NVIDIA ending support for 32 bits in 2019 will be an End of World for Slackware?
You seen the Patrick's take on AMD/ATI proprietary drivers? Go the open-source way and be happy.
I believe this way will be treated also the NVIDIA proprietary drivers: go the open-source (Nouveau) way and be happy.
Last edited by Darth Vader; 12-22-2017 at 01:50 PM.
'Tis just early symptoms of pre-release fever, an infectious contagion that overwhelms the Slackware community on an approximately biannual basis. It appears to start with lightheadedness in a frivolous thread, progresses through mild delirium, often associated with incantations of "Are we there yet?" and other wild imaginings, that can last for many months. The only known cure for pre-release fever is an actual Slackware release, when pent up tensions are spent in adoring congratulations to the Slackware BDFL and crew. No casualties have been recorded for those affected by pre-release fever.
Heh! Dr. Allend was right...
We need an Emergency Thread where someone qualified to offer support and to ask "Tell me, since when you see things?"
Last edited by Darth Vader; 12-23-2017 at 09:34 AM.
PS2. I specially avoid to think/realize that someone dare to propose to put down The Slackware! Until now, x86_64 is just a port, even it is a blessed one, in my humble opinion.
Actually, the 32-bit one is the port. All original development in Slackware starts in the x86_64 tree, and has since it was introduced for slackware64-13.0.
Quite. I'm glad Slackware doesn't include multilib by default and look forward to the day we can go back to using /lib and get rid of this ugly /lib64 stuff.
Even if we dropped 32-bit support entirely, for reasons of compatibility we would probably continue forward with --libdir=/usr/lib64.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.