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.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
I have two computers, one with AMD Athlon 64 3800(single core) and one with Athlon XP 2400+(also single core). One use Slackware 11 (server) and the other use Slackware current.
Never had any problems with them.
I have an Athlon64 dual core and single core and one AthlonXP. They run Slack quite well. Where did you hear that? The only thing I could see someone having an issue with would be a driver issue for a chipset, but usually a recompile will take care of that. Happy Slacking!
You shouldn't believe everything that you hear ...
Slackware will run fine ... and for better performance you may want to consider slamd64 (unofficial 64-bit Slackware), although it may be difficult to get some things like 32-bit flash player working in it.
Are there any significant problems I could encounter?
As stated by others, you should not have a problem with AMD processors.
Since AMD is fully compatible with Intel Architecture therefore you can use any Linux that supports that family. BTW, Slackware Linux supports the Intel family among others.
As for the dual core, you should read PV's 12 RC1 UPGRADE.TXT
It is recommended that you use one of the generic kernels (either the plain
kernel-generic or kernel-generic-smp) for daily use. For most systems,
you should use the generic SMP kernel if it will run, even if your system
is not SMP-capable. Some newer hardware needs the local APIC enabled in
the SMP kernel, and theoretically there should not be a performance penalty
with using the SMP-capable kernel on a uniprocessor machine, as the SMP
kernel tests for this and makes necessary adjustments. Furthermore, the
kernel sources shipped with Slackware 12.0 are configured for SMP usage,
so you won't have to modify those to build external out-of-tree modules
(such as NVidia or ATI proprietary drivers) if you use the SMP kernel.