Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
x86 is a generic term for all Intel and compatible 32-bit processors, starting with the 8086. In this context, I don't know what "normal" would be.
A 32-bit processor handles data and addresses in 32-bit words A 64-bit uses 64-bit words. Unless a program is written for 64-bit, you might never see a difference in performance. One limitation of a 32-bit processor is that it can only directly address 2^32 (4.295 X 10^9) bytes of memory.
Most users do not need anything more than a 32-bit system.
Moreover, if you have a Unix system installed on a 32-bit machine, you will use it until 19 January 2038 at 04:14:07. After that date your system will not be usable anymore, due to the limitation in the representation of dates. You will not have this problem on a 64-bit machine. Anyway, I don't think your system will be supported anymore in 2038!
It's been a few years since I took a microprocessor class, but I don't think an 8086 was 32-bit (it was 16-bit if I remember correctly). As far as which is better, more bits will always be better. The reason for this is that you can address more memory locations, have a much larger instruction set, and deal with larger numbers per instruction. Of course, the applications have to be compiled to support the increased number of bits for it to really be useful.