LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
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 05-22-2009, 08:06 AM   #181
gargamel
Senior Member
 
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,594

Rep: Reputation: 142Reputation: 142

I just solved one little snag, apart from which this is the smoothest desktop I have ever used, and so far it seems to be very stable. KDE 3.5.x sent me often mysterious messages when I shut down my computer (which was only cosmetic, and not *very* annoying, though), KDE4 goes down silently. And while KDE 3.5.x already was a very productive environment, KDE4 is incredibly intuitive. Many things are different, but I have no problems to navigate and find what I need.
And what is more: I have no hickups and don't miss anything from 32-bit world, at the moment. Especially multimedia applications run so well, now.

I bet, that Slackware64 will be released in less than six weeks. It's mature enough.

gargamel
 
Old 05-22-2009, 08:06 AM   #182
Crashbox
Member
 
Registered: Jun 2004
Location: USA
Distribution: Slackware
Posts: 136

Rep: Reputation: 21
Quote:
Originally Posted by Franklin View Post

If you get confused, listen to the music play.
Damn right! Excellent advice for any situation. Thanks, Franklin.


[Sorry to go off-topic]
 
Old 05-22-2009, 08:16 AM   #183
Crashbox
Member
 
Registered: Jun 2004
Location: USA
Distribution: Slackware
Posts: 136

Rep: Reputation: 21
Quote:
Originally Posted by Shingoshi View Post
2.) Download and have ready all of the packages in Slamd64/c
For those of us unfamiliar with Slamd64, the 'c' series is what, 32bit compatibility packages?
 
Old 05-22-2009, 08:21 AM   #184
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
Quote:
Originally Posted by Crashbox View Post
For those of us unfamiliar with Slamd64, the 'c' series is what, 32bit compatibility packages?
Yeah, slamd64 added a new directory called 'c' for compatibility.
 
Old 05-22-2009, 08:22 AM   #185
Anonymo
Member
 
Registered: Dec 2004
Location: The Woodlands, Texas
Distribution: Slackware, Archlinux, CentOS
Posts: 183

Rep: Reputation: 27
Quote:
Originally Posted by Crashbox View Post
For those of us unfamiliar with Slamd64, the 'c' series is what, 32bit compatibility packages?
Yes

http://mirror1.slackadelic.com/slamd...t/slackware/c/
 
Old 05-22-2009, 09:41 AM   #186
rvdboom
Member
 
Registered: Jul 2007
Distribution: Slackware
Posts: 183

Rep: Reputation: 23
Quote:
Originally Posted by Nylex View Post
Do you use RPMs much then? I'm just curious, as I've never really found a need for them, personally.
Well, I essentially use rpm2tgz to convert some RPM binaries, for instance for OpenOffice. It works well and it's much faster than compiling every new release.

As for my upgrade woes, I just probably didn't use the proper methodology : I upgraded the glibc, pkgtools then the kernel, rebooted to be able to run 64bits binaries but then I was in a deadlock as after the reboot, tools like ls and cut would not work anymore.
In the end, I created the DVD on another system, booted and installed everything. I then removed all the *i486|i586|i686* packages and things seems to work mostly fine now.

I'm currently rebuilting every 32-bits packages I made myself and should be full 64-bits tonight.
 
Old 05-22-2009, 10:04 AM   #187
piete
Member
 
Registered: Apr 2005
Location: Havant, Hampshire, UK
Distribution: Slamd64, Slackware, PS2Linux
Posts: 465

Rep: Reputation: 44
Quote:
I upgraded the glibc, pkgtools then the kernel, rebooted
(emphasis mine)

You pulled the carpet out from under your dynamically linked binaries I think in this case, I would avoid "upgrading" glibc, because really what you want to do is to add in the 64-bit stuff first, then whip out the 32-bit stuff when you've put all of the fine china ... I mean ... 32-bit dynamically linked binaries away. I'm getting carried away with my analogies today.
 
Old 05-22-2009, 10:56 AM   #188
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,122
Blog Entries: 3

Rep: Reputation: 1404Reputation: 1404Reputation: 1404Reputation: 1404Reputation: 1404Reputation: 1404Reputation: 1404Reputation: 1404Reputation: 1404Reputation: 1404
Hi,
Quote:
Originally Posted by Shingoshi View Post
Slackware64 will not run 32-bit applications. Wine or anything else for that matter.
You will have to either load Slamd64 compatibility libraries, or build them yourself. Which would you like to do?

Shingoshi
Your presentations for your argument(s) are not complete. An alternative would be to use a VM. I prefer VirtualBox. You could have your M$ or whatever running on that new Slackware64® -current installed host.

Please remember that this is 'Slackware64® -current' not Slamd64.

Sorry Fred no harm intended!
 
Old 05-22-2009, 12:20 PM   #189
rvdboom
Member
 
Registered: Jul 2007
Distribution: Slackware
Posts: 183

Rep: Reputation: 23
Quote:
Originally Posted by piete View Post
(emphasis mine)

You pulled the carpet out from under your dynamically linked binaries
Exactly.
When I finally understood it, it was already too late. :-D
 
Old 05-22-2009, 01:17 PM   #190
kornerr
Member
 
Registered: Dec 2004
Location: Russia, Siberia, Kemerovo
Distribution: Slackware
Posts: 893

Rep: Reputation: 35
Hello.

I use Slamd64 to build both 64-bit and 32-bit applications (developed by me). I tested 32-bit build on 32-bit Ubuntu, it worked just fine.
So I would really appreciate to have a guide to run 32-bit apps under Slackware64, and to be able to build 32-bit apps under Slackware64 (So I would like it to be multilib in some way or another).

I want to note about WINE vs VM. VM is not WINE.
Running VM each time I need to run one little Windows application is wrong (I frequently run local GIS application in WINE to quickly look up a necessary address, just for a minute or so).
One disadvantage I can remember now for VM (VirtualBox only, because I didn't use other alternatives after I discovered VirtualBox for myself) over WINE is lack of full OpenGL support.
To ensure this you may run qtdemo.exe (shipped with Qt-4.5 SDK) in both WINE and VirtualBox and have a look at OpenGL samples.
The OpenGL sample in WINE-1.1.15 (built for Slackware) under Slamd64-12.2 (the app runs fine)
The same sample under VirtualBox-2.2.0 (the app doesn't work)

Last edited by kornerr; 05-22-2009 at 01:18 PM.
 
Old 05-22-2009, 01:37 PM   #191
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.1 (multi-lib) KDE 4.11.4
Posts: 1,422

Rep: Reputation: 137Reputation: 137
This thread will get you running wine http://www.linuxquestions.org/questi...442/page2.html. However please remember that Slackware64-current is a testing system and the packages that are added are from another similar testing OS.

samac
 
Old 05-22-2009, 01:55 PM   #192
Slacker Prime
LQ Newbie
 
Registered: May 2009
Posts: 3

Rep: Reputation: 0
I signed up just to thank the Slackware team. Thank all of you for your hard work. I appreciate it. I haven't been this excited about a distro since Fedora Core 5 came out. I'm downloading the current iso build from the ftp.
 
Old 05-22-2009, 02:02 PM   #193
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.1 (multi-lib) KDE 4.11.4
Posts: 1,422

Rep: Reputation: 137Reputation: 137
Welcome Slacker Prime I hope you like it, remember to read all the docs and visit the forum with any problems you may have.

samac
 
Old 05-22-2009, 03:41 PM   #194
Shingoshi
Member
 
Registered: Oct 2006
Location: Cochise County, Arizona
Distribution: Gentoo-AMD64 / Slackware64-Current
Posts: 474
Blog Entries: 28

Rep: Reputation: 34
If this has already been answered, all the better...

Quote:
Originally Posted by H_TeXMeX_H View Post
So I have a question, what's the difference between installing the slamd64 compatibility libs and just using the slackware libs in slackware64 ? I heard that slamd64 used many of the slackware packages to make the compatibility libs ... so what exactly is the difference if anyone knows.
The packages in Slamd64 are named differently. Each of the packages are named as $PKG32-$VERSION. This allows you to install them without interfering with the standard Slackware64 packages you will have installed. I am checking now as I write this, to make sure where they will actually be located on the system. It seems upon further examination, that the Slamd64 32-bit compat packages can be installed to replace your existing Slackware packages before any other steps are taken. Because the only thing that changes here, are the names of the packages. The filesystem locations are the same.

I have also reordered one of the steps for upgrading from a running Slackware system. I had previously written to install the Slackware64 glibc immediately after rebooting into the 64-bit kernel. That may lead to problems. I believe the kernel should still be installed and booted FIRST. However, because of the likely need for a 32-bit glibc even during the upgrade of the Slackware64 glibc, I am recommending now that the Slamd64 glibc32 be installed BEFORE the Slackware64 glibc is installed.

Other than that, the remaining steps should remain the same.

Shingoshi
>=(o_O)=>
 
Old 05-22-2009, 04:52 PM   #195
Shingoshi
Member
 
Registered: Oct 2006
Location: Cochise County, Arizona
Distribution: Gentoo-AMD64 / Slackware64-Current
Posts: 474
Blog Entries: 28

Rep: Reputation: 34
I've just been advised by Fred Emmott (the Slamd64 creator), that there will likely be issues of incompatibility with the Slamd64 32-bit packages. That seems to increase the need for having packages built exclusively for Slackware64, and not depend on any other packages from other distributions.

Slackware64 will need it's own 32-bit compatibility layer.

Shingoshi
>=(o_O)=>

Last edited by Shingoshi; 05-22-2009 at 05:59 PM.
 
  


Reply

Tags
slackware, torrent


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
LXer: Common Public Licence superseded by Eclipse Public Licence LXer Syndicated Linux News 0 04-18-2009 03:10 AM
slackware current question on the current kernels davimint Slackware 3 06-03-2007 07:39 AM
LXer: A Public Market for Public Music LXer Syndicated Linux News 0 03-30-2007 07:16 AM
LXer: Public Venture, Public Content LXer Syndicated Linux News 0 06-22-2006 08:54 PM
To anyone=(To go public or not to go public that is the question...) hotrodowner Linux - General 10 06-25-2002 09:19 AM


All times are GMT -5. The time now is 08:23 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