LinuxQuestions.org
Visit Jeremy's Blog.
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 12-22-2017, 05:29 AM   #1
a4z
Senior Member
 
Registered: Feb 2009
Posts: 1,627

Rep: Reputation: 677Reputation: 677Reputation: 677Reputation: 677Reputation: 677Reputation: 677
future of 32 bit on Slackware?


now also nvidia is stopping 32bit support
http://nvidia.custhelp.com/app/answe...ail/a_id/4604/

there are already many applications that do not run on 32bit any more
and the duple effort with 32bit becomes more and more annoying,
for example, submitting a Sackbuild to Slackbuilds.org
I need an extra VM for something I will never use and no one other should use.

Best would be Slackware would have buildin 32bit support out of the box, to be able to run 32bit applications without needing 3rd party (Eric's) stuff
and forgets about the 32bit distribution.

seriously, whatever old 32bit machine is running, replace it with a raspery or beagle bone, that's better for the environment.

But at least I wish a 32bit buldin by default at Christmas :-)
 
Old 12-22-2017, 06:02 AM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,108

Rep: Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841
You want Slackware 32bit releases to stop, so you don't have to work so hard as a SlackBuild script maintainer. But you do want that Slackware should still offer full 32bit support - as part of a multilib setup, thereby shifting the burden to Pat.
Either you want, or you don't want, 32bit support. Make up your mind.
 
15 members found this post helpful.
Old 12-22-2017, 06:57 AM   #3
solarfields
Member
 
Registered: Feb 2006
Location: Outer Shpongolia
Distribution: Slackware
Posts: 841

Rep: Reputation: 336Reputation: 336Reputation: 336Reputation: 336
I also maintain a few SlackBuilds. Of course, this thought has crossed my mind. However, it is very rare that the 32bit compilation will require specific tweaking of the SlackBuild (but it has happened). In case I cannot find a solution (most recent example is this), I just leave the 32bit architecture as UNSUPPORTED. Also, there are some 32bit programs I do use. One is Adobe Reader (I know about alternatives, but some PDF forms require it), another one is AmplifX.
 
1 members found this post helpful.
Old 12-22-2017, 06:59 AM   #4
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 4,964

Rep: Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713
Having a good time at the office Christmas party are we?
Quote:
seriously, whatever old 32bit machine is running, replace it with a raspery or beagle bone, that's better for the environment.
Not really a suitable replacement for the 32-bit netbook that I regularly use. During my daily commute there are no power points for a power supply and I like a workable keyboard and display. I also like having full-size ports, rather than carrying a myriad of adapter cables.
Sheesh, the world revolves around me attitude, it just keeps becoming more prevalent.
 
3 members found this post helpful.
Old 12-22-2017, 07:18 AM   #5
a4z
Senior Member
 
Registered: Feb 2009
Posts: 1,627

Original Poster
Rep: Reputation: 677Reputation: 677Reputation: 677Reputation: 677Reputation: 677Reputation: 677
Quote:
Originally Posted by Alien Bob View Post
You want Slackware 32bit releases to stop, so you don't have to work so hard as a SlackBuild script maintainer. But you do want that Slackware should still offer full 32bit support - as part of a multilib setup, thereby shifting the burden to Pat.
Either you want, or you don't want, 32bit support. Make up your mind.
the main point was to deliver 32 bit with the 64bit distribution out of the box, multilib per default.

but of course, you focus on the other part of what I have written, and that is clearly also a valid point.
and make so much noise that the main topic goes away.
thanks for this, Eric.
 
Old 12-22-2017, 07:20 AM   #6
a4z
Senior Member
 
Registered: Feb 2009
Posts: 1,627

Original Poster
Rep: Reputation: 677Reputation: 677Reputation: 677Reputation: 677Reputation: 677Reputation: 677
Quote:
Originally Posted by solarfields View Post
I also maintain a few SlackBuilds. Of course, this thought has crossed my mind. However, it is very rare that the 32bit compilation will require specific tweaking of the SlackBuild (but it has happened). In case I cannot find a solution (most recent example is this), I just leave the 32bit architecture as UNSUPPORTED. Also, there are some 32bit programs I do use. One is Adobe Reader (I know about alternatives, but some PDF forms require it), another one is AmplifX.
thanks, than I will in future make the same.
the 32 bit programs should be buildable per default on Slackware, without requiren an extra multilib installation from a 3rd party.
of course, after reading the first messages I do not expect that this will happen, but maybe there will be a miracle.
 
Old 12-22-2017, 07:23 AM   #7
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 4,964

Rep: Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713Reputation: 1713
Quote:
the main point was to deliver 32 bit with the 64bit distribution out of the box, multilib per default.
If 32-bit is dying, why have it in 64-bit? Multilib has always been a horrible hack.
 
3 members found this post helpful.
Old 12-22-2017, 07:27 AM   #8
a4z
Senior Member
 
Registered: Feb 2009
Posts: 1,627

Original Poster
Rep: Reputation: 677Reputation: 677Reputation: 677Reputation: 677Reputation: 677Reputation: 677
Quote:
Originally Posted by allend View Post
Having a good time at the office Christmas party are we?

Not really a suitable replacement for the 32-bit netbook that I regularly use. During my daily commute there are no power points for a power supply and I like a workable keyboard and display. I also like having full-size ports, rather than carrying a myriad of adapter cables.
Sheesh, the world revolves around me attitude, it just keeps becoming more prevalent.
sory for forgetting your 32-bit netbook

for those who did not get it, the point was getting multilib into Slackware, if 32 bit exists or not ir irrelevant,
if I mark slackbuilds in future 32 bit unsupported because I can not test them, who cars

so no need for you die hard what ever change request comes freak out hard-liner to overreact, thanks.
 
Old 12-22-2017, 07:29 AM   #9
a4z
Senior Member
 
Registered: Feb 2009
Posts: 1,627

Original Poster
Rep: Reputation: 677Reputation: 677Reputation: 677Reputation: 677Reputation: 677Reputation: 677
Quote:
Originally Posted by allend View Post
If 32-bit is dying, why have it in 64-bit? Multilib has always been a horrible hack.
if you want performance you run 32bit application on 64bit machines, but you don't know about that, right?
not your 32bit netbook world, hm,
So please, if you have nothing other to add than false info, stop pollution this thread, thanks!
 
Old 12-22-2017, 07:40 AM   #10
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,537

Rep: Reputation: 598Reputation: 598Reputation: 598Reputation: 598Reputation: 598Reputation: 598
Quote:
Originally Posted by a4z View Post
the main point was to deliver 32 bit with the 64bit distribution out of the box, multilib per default.

but of course, you focus on the other part of what I have written, and that is clearly also a valid point.
and make so much noise that the main topic goes away.
thanks for this, Eric.
Yes, but you launch the 2018 troll before 2018 .....

just a joke
 
Old 12-22-2017, 07:56 AM   #11
NonNonBa
Member
 
Registered: Aug 2010
Distribution: Slackware
Posts: 90

Rep: Reputation: Disabled
Quote:
Originally Posted by a4z View Post
seriously, whatever old 32bit machine is running, replace it with a raspery or beagle bone, that's better for the environment.
It will probably consume far more power to make (and bring) a new device than the supplement the old will consume for the rest of its life.

Plus, here I have an old AMD-Duron box I use as a NAS where I plug all the IDE HDDs I can't use anywhere else. Therefore I'm happy my favorite OS has a 32bits flavor, because it makes me things very simple to configure and maintain.
 
Old 12-22-2017, 07:57 AM   #12
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,108

Rep: Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841Reputation: 4841
Quote:
Originally Posted by a4z View Post
the main point was to deliver 32 bit with the 64bit distribution out of the box, multilib per default.

but of course, you focus on the other part of what I have written, and that is clearly also a valid point.
and make so much noise that the main topic goes away.
thanks for this, Eric.
Patrick has repeatedly stated that Slackware64 will not become a multilib solution. And as long as there is a (large) part of the world where old hardware is all they have, a 32bit distro will be welcomed. So there is still an audience for 32bit Slackware, especially so because other distros are closing the door on these people.

I personally believe that 32bit software has a limited lifespan, and future Slackware releases may switch to 64bit only. When that time comes, I will also stop providing multilib packages because there are will no longer be original 32bit Slackware packages that I can convert. And I am not going to maintain a 32bit spin-off.
 
9 members found this post helpful.
Old 12-22-2017, 09:22 AM   #13
a4z
Senior Member
 
Registered: Feb 2009
Posts: 1,627

Original Poster
Rep: Reputation: 677Reputation: 677Reputation: 677Reputation: 677Reputation: 677Reputation: 677
Quote:
Originally Posted by Alien Bob View Post
Patrick has repeatedly stated that Slackware64 will not become a multilib solution.
we are living in a changing world, and from time to time it is time to reflect and check if yesterday statements need to be adjusted. If this does not happen, we have a case of fundamentalism.

There are parts that should not be 3rd party, and multilib is definitely one of them, if not the essential part.
Especially when more and more say no 32 bit anymore, if you need 32 bit software, run it on 64 bit platform.
That a hardware vendor like nvidia joins the club saying so creates definitely a new situation, so time for reflection.


Quote:
Originally Posted by Alien Bob View Post
And as long as there is a (large) part of the world where old hardware is all they have, a 32bit distro will be welcomed. So there is still an audience for 32bit Slackware, especially so because other distros are closing the door on these people.

I personally believe that 32bit software has a limited lifespan, and future Slackware releases may switch to 64bit only. When that time comes, I will also stop providing multilib packages because there are will no longer be original 32bit Slackware packages that I can convert. And I am not going to maintain a 32bit spin-off.
good point, thanks Eric, and I am fine with this. Especially when it is OK and accepted that I can use unsupported for whatever slackbuild I make. but this is up to the SBo guys to decide and I might ask on the sbo list, so no need to discuss this here.
 
Old 12-22-2017, 10:01 AM   #14
montagdude
Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 984

Rep: Reputation: 708Reputation: 708Reputation: 708Reputation: 708Reputation: 708Reputation: 708Reputation: 708
Too soon. Let's have this discussion in 10 years.
 
4 members found this post helpful.
Old 12-22-2017, 11:03 AM   #15
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,213

Rep: Reputation: Disabled
So nvidia linux users will no longer be able to use multilib programs like steam or wine in the future?
 
1 members found this post helpful.
  


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
Ubuntu 32-bit Future? wagscat123 Ubuntu 3 11-03-2016 10:18 AM
LXer: GNU/Hurd Plans For A Future With USB, SATA, 64-Bit LXer Syndicated Linux News 0 02-10-2013 04:01 AM
How important is 64-bit support in future Slackware? wheeliee Slackware 36 03-25-2009 05:34 AM
LXer: Desktop FreeBSD: 64-bit Future LXer Syndicated Linux News 1 10-06-2006 11:14 AM

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

All times are GMT -5. The time now is 06:27 PM.

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