SlackwareThis Forum is for the discussion of Slackware 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.
There is less than 2 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
You do NOT want to "pick one closest to your physical location". You DO want to use a pool server. The problem stems from the fact that tons of people link to specific time servers, causing a SERIOUS bandwidth problem and in some cases has resulted in restrictions being placed on specific timeservers. Anybody running a computer for personal use has absolutely no need to link to a specific server, pool servers will work quite nicely and spread the load around.
The link you gave does mention using pool servers, and if you need more information check out http://pool.ntp.org
There's nothing wrong with NTP, I'm sure, but if you're not always connected to the Internet, then how can this update? That's why I was wondering if there were something within Slackware itself that would be able to automatically adjust the time, similar to how Windows does. With Windows 95/98, when Daylight Savings Time came around, when I would initially power up my computer, I would be prompted to accept the new time settings (something that appears to have been removed from later versions of Windows). I was not connected to the Internet, and the time was adjusted accordingly. I was just wondering if there were a way to enable something similar to this in Slackware, not necessarily the prompt, but to take place behind the scenes. Perhaps there is some sort of program available that would do this?
I still think Pat should come out with a patch for Slack 10.2 and older! What gives, Pat?
Does anyone bother keeping up with patches after installing?
(see http://slackware.osuosl.org/slackwar...ches/packages/ for the updates)
Tue Aug 22 15:20:32 CDT 2006
patches/packages/glibc-2.3.5-i486-6_slack10.2.tgz: Patched an issue with
kernel version parsing in ld-2.3.5.so that was leading glibc to treat 2.4
kernels with 4 version parts (such as 220.127.116.11) as if they supported NPTL,
leading to a crash at boot.
Added ru_RU.CP1251 locale support.
Updated timezone information from tzdata2006j.
Updated timezone utilities from tzcode2006j.
Added ru_RU.CP1251 locale support.
patches/packages/glibc-solibs-2.3.5-i486-6_slack10.2.tgz: Patched an issue
with kernel version parsing in ld-2.3.5.so that was leading glibc to treat
2.4 kernels with 4 version parts (such as 18.104.22.168) as if they supported
NPTL, leading to a crash at boot.
Updated timezone information from tzdata2006j.
To answer that question, yes. But not by looking at the changelogs. I subscribe to the slackware-security list.
A lot of IT staff in the industry has been scrambling for OS fixes to the government's DST announcement late fall. I was expecting Linux to be no different. From looking at the date in the changelog, I'm surprised that the DST fix was incorporated in August.
I was expecting some sort of message to be sent to the list since December. But it seems it's really a non-issue. Besides, not sure about you, but "Updated timezone information from tzdata2006j" doesn't jump out to me as "Fixed changes to DST start/end dates for 2007".
It worked on my menagerie of Slack boxen including one as old as SlackWare 7.1
I only wish Windows was this easy.
Did you follow the above steps exactly? I'm not having any luck on Slack 8.1 installs, and in order to have the updates work on a 10.2 box, I needed to install the latest glibc-zoneinfo package... unfortunately, I'm running the most current glibc-zoneinfo for the 8.1 installs. Any ideas? Thanks.
EDIT: Answered my own question. The zic... northamerica command wasn't generating a new "Central" timezone file, to which my /etc/localtime symlink was pointing. Scrolling farther down the list of timeconfig timezones, I was able to choose "Chicago". That file had been updated by the zic command.
/usr/sbin/netdate time.nrc.ca time-nw.nist.gov (from my main server located in Canada)
/usr/sbin/netdate tcp xxx.xxx.xxx.xxx (from my secondary server, where the xxx.xxx.xxx.xxx is the IP of my main server)
Hope this help,
Welcome to LQ!
Now to ask you a favor..... You link directly to a couple of time servers, and unless you have some acute and pressing need to do so, you should be using pool servers. I've got a post earlier in this thread explaining why. Please be a good netizen and change your netdate command.
There's nothing wrong with NTP, I'm sure, but if you're not always connected to the Internet, then how can this update? That's why I was wondering if there were something within Slackware itself that would be able to automatically adjust the time Perhaps there is some sort of program available that would do this?
I created the file /etc/ppp/ip-up , as I'm on dial-up and not connected alll the time, and in it I put:
/usr/sbin/ntpdate ca.pool.ntp.org; /sbin/hwclock -w
You have a couple of options:
1) Upgrade to Slack 11.0
2) Use the "zic" command to generate new timezone files (see the man page for zic).
If you are going to use zic, you'll need the latest timezone rules, which you can get from the latest source code tarball for the glibc library (search the www.gnu.org site). The rules will be in timezone subdirectory.
Or you can get the latest rules from this website http://www.twinsun.com/tz/tz-link.htm . The FTP link will list a file called something like "tzdata2006p.tar.gz", which also contains the complete rules.
Then to generate the latest timezone files for North America you would do something like this:
# zic -d /tmp/zoneinfo northamerica
After this is done, copy the generated files from "/tmp/zoneinfo" to the "usr/share/zoneinfo" directory, and then run "timeconfig" to select your timezone.
This didn't work for me. Obtained tzdata2007c.tar.gz from elsie.
Followed instructions exactly. After compiling with zic the DST start date for my time zone still showed April 1. Solved the problem for my Vector Linux 5.0 SOHO box by getting a Slackware 10.2 package 'glibc-zoneinfo-2.3.4-noarch-1.tgz and installing that. Ran "timeconfig" and now zdump -v /etc/localtime | grep 2007 shows the correct March 11 start date for DST.
Would someone in this forum get "tzdata2007c.tar.gz" from elsie and see if it works for you?
running Slackware 11.0, Slackware 10.2, Vector Linux 5.0 SOHO,
and SuSE 9.3 (don't ask why)
Thanks for the info. Worked like a charm on my Slack 10.2 boxes. I wrote a fully automated script that downloads the timezone data, updates the system, and launches the timeconfig program. I figured it may help some users that need to get it done quickly. I recommend reading thru this short script to understand what it's doing.