Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
Dual OS. Windows and Linux. Linux and OS/390? MacOS and Windows?
Dissimilar operating systems won't share information about timezones.
Even with Linux and Linux unless they share the same /etc/localtime and the timezone files then changing one won't have any effect on the other. You're probably not sharing these directories.
That is to say you need to update both OSes.
Your question sounds like it is prompted by a misunderstanding of time and timezone. On UNIX/Linux time is stored as UTC (a/k/a GMT or Zulu). Timezone on the other hand is what is used to determine how the system sees the time. For example for EST5EDT timzeone there is an offset of 5 hours from UTC for EST (and 4 hours for EDT).
Translation: Changing timezone is not the same as changing time.
The operating systems are XP and Suse, what brought this question to mind was when you do a new install it picks time up from (bios I thought)and times when I go back to bios the time was changed, but that was with an Windows only install and not a dual boot. If this assumption isn't correct, when I enter bios which time would it read?
Last edited by Larry Webb; 02-17-2007 at 09:11 AM.
Very odd. I'd replied to this before but it didn't post.
Anyway: Previously I'd noted there is a difference between time zone and time. Now I'll note there is a difference between hardware clock time and "system" time. On boot your system gets it's system time from the hardware clock. As noted though in UNIX/Linux system time is actually stored as UTC rather than your local time. It is the timzeone information that determines how it is DISPLAYED.
I would recommend doing the following in Linux:
1) Use the date command to set your system time (using your current timezone time - it will be stored in UTC in the background).
2) Use the "hwclock -systohc" command to set your hardware clock to the system time.
3) Apply your DST changes (3 really has nothing to do with 1 and 2 but needs to be done before the Mar 11th time change if you're in the U.S. or one of the other countries adjusting their DST then).
4) Reboot into XP and see if the time is OK there.
The only issue could be if both Windows and Linux try to change the time, and you end up doubling it. I'd try booting into Windows first (since it will probably try to change the clock) then boot into Linux. If the time is still wrong, I'd then just go to BIOS and fix it manually