SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
What is the difference between BW64 and Slamd64, which is another x64 port of Slackware?
Bluewhite64 is the second unofficial port of Slackware and the differences are many. I'm not using Slamd64 anymore, it is not up to date and I need supported software for my servers. I recommend you to try Bluewhite64, here works great .
You are perfectly right MS3FGX. Well, actually, I would be curious to know how this kind of port is working. Is it just recompile the package for an x64 architecture or does it need more in depht modifications? What about the 32 bits retrocompatibility then?
I even want to ask why they did not seem to have capitalised the efforts made by Slamd64 to continue it if Slamd64 is discontinued. Which brings me to the fact that an official support of x64 architecture would be a great thing to bring for the next Slackware major release as these CPU will become more and more common and we will soon hit the 4 GB memory limit of the 32 bit architecture.
Last edited by Mark Havel; 08-07-2007 at 08:35 AM.
I think it is generally just a matter of recompiling everything for 64 bit, which is not much of a task in reality since the official Slackware build scripts for all of the packages already include a x86_64 bit option, you simply need to enable it and rebuild the package. Not that it is a walk in the park to recompile every single package in Slackware, but it isn't exactly rocket science either.
The presence of the x86_64 option in the build scripts may indicate that an eventual move to 64 bit is in the cards. Of course, on the other hand, there is also an option for s390 in the build scripts, so it could be that Pat just tries to make things a little easier for those doing the porting.
Well another thread about 64 bits Slackware have just bumped today and now, I can tell that this "arny" is the BlueWhite64 maintainer and also accused of having derivated its work from Slamd64 without crediting it nor telling it clearly.