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.
64-bit software runs faster than 32-bits and can use more than 4 GiB of RAM, also x86_64 is backwards compatible with x86, so the only reason a 32-bit program won't run on a 64-bit system is because it can't find the libraries. Slackware 13.37 has multilib packages available; this will allow installation of 32-bit libraries on a 64-bit system.
I see no reason not to use the 64-bit version.
Last edited by zwitterion-241920; 08-17-2012 at 05:15 PM.
Reason: typo
Just for completeness, as mentioned by whizje, you will need the multilib package to run those 32bit programs that you cannot live without. You will find a complete and thorough guide to install and let your system multilib-ready from AlienBob's How-to and wiki:
How much RAM do you have? I've mentioned this before elsewhere, but I'd go 64-bit if you have >= 4GB RAM (either installed or planning to install very soon,) else just stick with 32-bit.
Third-party 32-bit software can be run on Slackware64 via AlienBOB's multilib packages, but I usually prefer to keep 64-bit only and just find 64-bit versions of that software (only to install multilib when absolutely necessary, which I haven't really run into yet.)
Make it simple you want the best of both worlds dual boot them. yes a 32 and a 64. simple. I run Alien Bob's Multi Lib's on my 64. that said hey you know what on the heavy coffee days been known to upgrade things and bork my 32 bit programs not a big deal little more work..
The 2.6.36.7 kernel can be recompiled to use 64 gigs of ram ok recompile it and have fun. run Slk64-current Multi-lib then I would recommend keeping a couple mirrors of it in different stages or progression on my hard drive to back step if needed. Again it is all the same speed it just can do it in different ways. PAE been around a long time. I have a custom distro for vurtual worlds that is rebuild of Slacko Puppylinux and my wife Loves her AMD 6core 16 gigs of ram as puppy loves to run there. it fast blinding fast and runs cool. for a 32 bit O/S.
traveling twice the speed of sound it is easy to get burned
i got me a new laptop with core i7-3520m and intel hd 4000 graphics.
now i want to install slackware 13.37 on it.
i am using the 32bit on my 32bit computer and dont have any problems with it.
now i am not sure which version i should choose for my notebook.
i have seen that people have troubles with some programs because they dont run on 64bit.
what would you suggest me?
A good rule nowadays seems to be "Unless you have a serious reason to go 32bit, go 64bit".
Some cpu intensive programs like ffmpeg are quite faster due to larger (and more registers) and of course apps can access all the memory without tricks. So you gain some advantages without losing anything.
In early 64bit times, many programs were poorly coded and didn't work well in 64bit where int and pointers have different sizes but nowadays every opensource program works fine on 64bit. For the few packages that either are closed sourced like skype or need 32bit like wine, you can use AlienBOB's excellent multilib packages.
What programs have you seen not working on 64bit ?
Quote:
Originally Posted by zakame
How much RAM do you have? I've mentioned this before elsewhere, but I'd go 64-bit if you have >= 4GB RAM (either installed or planning to install very soon,) else just stick with 32-bit.
If the cpu is 64bit then there isn't much reason to go 32bit nowadays. 64bit isn't useful only with >4GB RAM. In theseposts, Linus explains the way virtual memory works and argues that 64bit is a necessity for >1GB RAM
If the cpu is 64bit then there isn't much reason to go 32bit nowadays. 64bit isn't useful only with >4GB RAM. In these posts, Linus explains the way virtual memory works and argues that 64bit is a necessity for >1GB RAM
That were really interesting topics, thanks, even if rather hard to understand ^^
In fact, a 64bits OS is not only useful for computers that have more than 1GB of RAM, but also if you have programs that may use more than 1GB of RAM. And that's not hard to reach even with Firefox (addons + plenty of open tabs).
Last edited by zithro; 08-19-2012 at 03:32 PM.
Reason: added quote's author
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.