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.
I read probably a rumor that Linux/Unix will die in 2031. Because Linux use 32bits registers. Also the time represents in seconds, threrefore by 2031 the Linux will die becase of this problem, similar to 2k problem. True or Not?
well, aside from the fact that it's 29 freakin years away, linux is already beginning the transistion to 64-bit capability. the 2.5 experimental kernel is already being written to be able to use 64 bits, but the full transition probably won't be made for another versions or two.
we all know what a HUGE problem that y2k thing turned out to be ...
Moore's law was that the number of transistors that we could cram on a die doubles every 18 months. Okay, this has actually been perverted into twice the Mhz every 18; for the luddite crowd that at least can understand Megahertz. Let's run with that...
29 Years = 348 months / 18 months = 19.33 iterations of doubling, or 2^19 the clock speed (Today's ballpark 1.8Ghz [Intel can bite me]) = 943718-ish Ghz! or... (remembering to divide by 1024!) 921 Thz Processor.
Well that basically depends on how the time is stored. Our applications store the time in microseconds since EPOCH in a double. That would mean that the maximum time would be:
19th January 2038 03:14:07.999999
As far as I know the kernel stores the time in 10ms increments so it can go a lot further then that before it gets problems.
we all know what a HUGE problem that y2k thing turned out to be
Correction, we all know what a HUGE problem that y2k thing would have been had nobody done anything about it. That's one of the reasons why 2031 won't be a problem for Linux -- because somebody is doing something about it .