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.
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free.
Way to much software breaks in 64 bit compilation for now.
It's going to be interesting in the next few months to see how much software (mainly Windows I suspect) is not thread safe on SMP machines, as the Pentium D dual cores become cheap. These are about to be updated with the two AMD64 instructions Intel initially omitted.
AMD64 instruction capability is going to be the default on new machines next year, but Slackware 386 is running on a lot of legacy boxes and will be for some time. I don't think that there will be many left less than PII (ie 686) by then though.
I don't think PK is the maintainer of the 390 port.