SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This one's been bugging me since daylight savings ended on Nov. 4. Every time I start the computer the hardware clock is correct but the system clock is -5 hours (GMT -5). I can manually adjust it with the date or hwclock commands but the next time I start it the same thing happens. This machine dual boots Slackware 12 and Win2K. Win2K doesn't have the problem, the BIOS clock is correct and my laptop, running Slackware 12 only, doesn't have the problem.
I compared /etc/adjtime to the laptop and tried deleting it. Both computers use localtime and don't have anything /etc/sysconfig. I tried booting into Windows and changing the time. When daylight savings ended the clock didn't adjust itself although I have the patched glibc-zoneinfo and /etc/localtime is linked to the correct file in /usr/share/zoneinfo. The laptop did change correctly. I could probably work around it by setting the hwclock +5 but that wouldn't really solve the problem.
Or am I wrong and the hwclock should be +5 and the laptop is the one that's wrong?
Win2k requires the hardware/BIOS clock be stored in your local time, i.e., if the clock on your wall says it's 5:23pm, that's what you need to set the BIOS to.
Then you need to run timeconfig, and select "NO Hardware clock is set to local time", or just edit /etc/hardwareclock and change "UTC" to "localtime".
Vista supposedly doesn't have the "DOS Backwards Compatibility" requirement that is the reason/excuse Microsoft made everything screw up horribly if you try to tell say, XP to use UTC for the clock, but I'll believe it when I see it.
Thanks for the link, Alien_Hominid. All I needed was the --localtime switch. I know I searched here at least twice but I didn't see that thread. I'm adding this to my notebook for future reference.
evilDagmar, that's why I dusted off my Win2k and booted into it forcing it to save some changes. I'll believe Vista's "improvements" when I see them, too, which I hope isn't anytime soon.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.