LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

View Poll Results: Do you require 32bit compatibility in Slackware64-current?
Yes 55 46.61%
No 63 53.39%
Voters: 118. You may not vote on this poll

Reply
 
Search this Thread
Old 05-23-2009, 04:12 PM   #16
joutlancpa
Member
 
Registered: Apr 2009
Location: Orlando, FL
Distribution: Scientific Linux 6 x64
Posts: 211
Blog Entries: 1

Rep: Reputation: 31

I don't think so re: 32 bit...voted no....I tend to run Virtual Machines, actually, VB PUEL edition keeps me from booting into windows!
 
Old 05-23-2009, 04:13 PM   #17
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.1 (multi-lib) KDE 4.11.4
Posts: 1,422

Original Poster
Rep: Reputation: 137Reputation: 137
It would be nice if all programs played well with 64bits, however some just don't. If you have one or two of these programs that you have to use, and you do not wish to have to run two different systems, then you should probably answer yes.

If not then no would be a good choice.

Nobody is forcing the developers of our favourite system to do anything that they don't want to, I am sure that they look in from time to time and can make educated guesses as to what the system and it's users needs.

Please try to keep speculation and personal politics to a minimum, after all it is just a yes/no question

samac
 
Old 05-23-2009, 06:26 PM   #18
SqdnGuns
Member
 
Registered: Aug 2005
Location: Fountain Valley, CA / Thailand
Distribution: Slackware64 14.0
Posts: 981

Rep: Reputation: 88
Quote:
Originally Posted by samac View Post
Please try to keep speculation and personal politics to a minimum, after all it is just a yes/no question

samac
no.
 
Old 05-23-2009, 07:17 PM   #19
C-Sniper
Member
 
Registered: Dec 2006
Distribution: Slackware
Posts: 507

Rep: Reputation: 33
no.
 
Old 05-26-2009, 01:37 AM   #20
Skaperen
Senior Member
 
Registered: May 2009
Location: WV, USA
Distribution: Slackware, CentOS, Ubuntu, Fedora, Timesys, Linux From Scratch
Posts: 1,777
Blog Entries: 20

Rep: Reputation: 115Reputation: 115
Compatibility for migration

32-bit compatibility would make migration easier. However, I think I can swing it with with a separate 32-bit root, as opposed to a multilib setup in a common root. So I'd just need to have 32-bit compatibility turned on in the kernel (I build my own anyway). I'd just do a full install of 32-bit slackware in one directory tree, and 64-bit slackware in another directory tree, and pick which one to be root at boot time. This could be done via initramfs, initrd, or a patch I wrote for the kernel to allow choosing a subdirectory to be root on the parameter line.
 
Old 05-26-2009, 04:49 AM   #21
vinegaroon
Member
 
Registered: Sep 2008
Posts: 99

Rep: Reputation: 21
By the looks of today's changelog, multilib will at least be possible in Slackware64. I don't expect the Slackware team to have to maintain the extra packages required for multilib, however I think it's nice that it will at least be possible.
 
Old 05-26-2009, 02:49 PM   #22
Skaperen
Senior Member
 
Registered: May 2009
Location: WV, USA
Distribution: Slackware, CentOS, Ubuntu, Fedora, Timesys, Linux From Scratch
Posts: 1,777
Blog Entries: 20

Rep: Reputation: 115Reputation: 115
Quote:
Originally Posted by vinegaroon View Post
By the looks of today's changelog, multilib will at least be possible in Slackware64. I don't expect the Slackware team to have to maintain the extra packages required for multilib, however I think it's nice that it will at least be possible.
Would be nice if one could just install (some) Slackware32 libraries into a Slackware64 system and end up with a multilib system (maybe with an optional multilib support package to set up for it). But I haven't used multilib, yet, so I don't know exactly what that requires.
 
Old 05-26-2009, 06:01 PM   #23
rvdboom
Member
 
Registered: Jul 2007
Distribution: Slackware
Posts: 183

Rep: Reputation: 23
I'd appreciate a multilib system but can live without, especially if going multilib makes everything (maintainance for the Slack team, compiling) much more complicated and if it brings weird behaviour.
 
Old 05-26-2009, 06:15 PM   #24
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
From the Slackware64 -current ChangeLog.txt:
Code:
Mon May 25 17:52:56 CDT 2009
d/binutils-2.18.50.0.9-x86_64-2.txz:  Changes to enable multilib support.
  Thanks to Fred Emmott.
d/gcc-4.3.3-x86_64-4.txz:  Changes in specs file to enable multilib support.
  Thanks to Fred Emmott.
So it appears Fred is helping them out, and Slackware64 will have 32-bit support.
Maybe we can install 32-bit packages with some care, and they'll run, but perhaps
not be *officially supported* by Slackware.

Last edited by Bruce Hill; 05-26-2009 at 06:26 PM.
 
Old 05-27-2009, 02:58 AM   #25
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.1 (multi-lib) KDE 4.11.4
Posts: 1,422

Original Poster
Rep: Reputation: 137Reputation: 137
Beowulf999 posted this in another thread.
Quote:
Re: Building wine on Slackware64
You may need a few extra items. Run over to http://www.slamd64.com/download and in particular check out the slamd64/slackware64-current directory. There are a number of packages for the a, d, l, n, x series. From the readme:

Quote:
This directory contains the start of 32-bit compatibility packages for
Slackware64-current.

Tested with:
- Skype (dynamic build)
- RTCW: ET
- Wine (built withs script from builds.slamd64.com)

Slamd64's c/ set isn't quite right for this purpose; my goal with these
packages is to add 32-bit compatibility as unobtrusively as possible.
...
Enjoy.
samac
 
Old 06-01-2009, 08:15 AM   #26
Agon
EZIM Maintainer
 
Registered: Jul 2007
Distribution: Slackware64 14.0
Posts: 10

Rep: Reputation: 0
I don't know if I'm the only one, but I think a pure 64bit OS would be most desirable. It also fits our KISS principle.
 
Old 06-01-2009, 08:40 AM   #27
Martinezio
Member
 
Registered: May 2009
Location: Warsaw, Poland
Distribution: Slackware64-current
Posts: 191

Rep: Reputation: 32
I vote for Yes.

Primo: easier and quicker distro-upgrade from previous version of Slack.
Secundo: there are to many software not ready for 64-bit (ie. Wine, Skype, Sane)...

 
Old 06-01-2009, 09:36 AM   #28
Lufbery
Senior Member
 
Registered: Aug 2006
Location: Harrisburg, PA
Distribution: Slackware 64 14.0
Posts: 1,142
Blog Entries: 29

Rep: Reputation: 119Reputation: 119
Hi all,

Transitions in the computer world are a pain in the butt. I personally dislike setting up a new operating system, personalizing my settings, personalizing my wife's settings, etc. One of the things that I really like about Slackware is that, after I set it up, it basically runs unattended without problems -- except for applying the occasional security patch.

The important things for me are the applications. I need stuff to work and to work well. Slackware is an excellent distribution for adding lots of esoteric libraries to get even more esoteric programs to run (e.g. QGIS, GRASS, Wine, Scribus, Inkscape). If 32-bit compatibility is necessary for some of those programs, then I'm all for it.

I'm not saying that the full Slackware installation needs to have everything pre-installed, but I'd like to be able to use 32-bit libraries if I need them.

However, this may be a moot point. The above-quoted section from the --current changelog shows that 32-bit compatibility will be enabled.

Regards,

-Drew
 
Old 06-02-2009, 09:30 AM   #29
Linux.tar.gz
Senior Member
 
Registered: Dec 2003
Location: Paris
Distribution: Slackware forever.
Posts: 2,227

Rep: Reputation: 86
I didn't voted because i wait to see if pure 64 is possible with all the stuff i use @home and @work...

In order to chroot and execute programs in a single script :

##########################
#!/bin/sh

cd /home/me/my_slack32_environment

chroot ./ <<EndChroot

/usr/bin/run_my_32bit_app

EndChroot
##########################
 
Old 06-02-2009, 09:45 AM   #30
ROXR
Member
 
Registered: Jan 2009
Location: Spain
Posts: 107
Blog Entries: 1

Rep: Reputation: 20
I vote Yes

certainly at least 5 years more

An operating system is to serve applications, not applications to serve operating system.

Last edited by ROXR; 06-02-2009 at 09:47 AM.
 
  


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
Slackware64 -current made public! bsdunix Slackware 289 06-19-2009 12:15 AM
Slackware64-Current / slackpkg slackass Slackware 31 06-06-2009 10:51 PM
Slackware64 and 32-bit compatibility mattydee Slackware 24 05-23-2009 02:01 PM
Slackware64-current ATI, and few more proprietary questions dolphin77 Linux - Newbie 1 05-22-2009 06:57 PM
LXer: Slackware64 -current made public! LXer Syndicated Linux News 3 05-21-2009 12:02 PM


All times are GMT -5. The time now is 11:39 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration