DebianThis forum is for the discussion of Debian 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.
I have a debian & windows dual boot system, everything seems to be fine except the system date in both os. Each time I logout from one os and boot into another, the system date jump several hour forward.
For example, if the system date is 12:00 when I logout from Windows, it will become, say, 22:00 after I boot into Debian.
My timezone setting is the same in windows and debian, is there a way to synchronize the system date in both os?
The hw clock is assumed to be in UTC since it cannot store the offset. Windows has not concept of this, it sets the hw clock to local time. To work around this issue, make sure that the hw clock is set to local time and change UTC=yes to UTC=no in /etc/default/rcS
That same time problem started for me when I upgraded Sarge to Etch with 2.6.12 kernel. It was very frustrating because no offered solution worked. Neither Kanotix nor Mepis nor Sarge ever had problem. Then after several weeks my upgrading kernel to 2.6.14 and system to Etch/Sid resolved time errors. Cheers.