Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site ttrdc.UUCP Path: utzoo!watmath!clyde!cbosgd!ihnp4!cuae2!ltuxa!ttrdc!levy From: levy@ttrdc.UUCP (Daniel R. Levy) Newsgroups: net.bugs,net.unix-wizards Subject: Re: Daylight Saving Time Message-ID: <830@ttrdc.UUCP> Date: Thu, 10-Apr-86 14:09:45 EST Article-I.D.: ttrdc.830 Posted: Thu Apr 10 14:09:45 1986 Date-Received: Sat, 19-Apr-86 03:40:17 EST References: <234@sysdes.UUCP> <204@Unison6.OZ> Organization: AT&T, Computer Systems Division, Skokie, IL Lines: 24 Xref: watmath net.bugs:779 net.unix-wizards:17666 In article <204@Unison6.OZ>, rcodi@Unison6.UUCP writes: >I rekon that the BSD way of keeping the timezone info in the kernel is more >sensible, as it guarantees uniformity for all processes in the system. Perhaps >a cron script particular to each machines' timezone can be used to alter >DST at appropriate times of the year for those countries that seem >to keep changing DST (by adb'ing the kernel? - Yuk!) > Ian Donaldson Why adb the kernel? A privileged system call would do. Of course a program which used the system call to set the time zone details would have to be invoked every time the machine was rebooted, but that's easy. And why use a cron script? Deep internally the machine would know GMT (say), but would actually perform transactions in terms of the local time as figured by a table implanted in the kernel via the aforementioned system call. The default (prior to system call) could be something reasonable based on data furnished when the kernel was made. Surely this has been suggested before? -- ------------------------------- Disclaimer: The views contained herein are | dan levy | yvel nad | my own and are not at all those of my em- | an engihacker @ | ployer or the administrator of any computer | at&t computer systems division | upon which I may hack. | skokie, illinois | -------------------------------- Path: ..!{akgua,homxb,ihnp4,ltuxa,mvuxa, vax135}!ttrdc!levy