Re: Daylight savings time / 6.1 and 4.11

2007-01-22 Thread Damian Wiest
On Tue, Jan 16, 2007 at 01:31:22PM -0700, hal wrote: This came down from above?! Beginning in 2007, Daylight Savings Time will be lengthened one month by starting three weeks earlier (2AM on the second Sunday in March) and ending one week later (2AM on the first Sunday in November).

Re: Daylight savings time / 6.1 and 4.11

2007-01-20 Thread Matthew Seaman
hal wrote: 6.2-STABLE zdump -v -c 2008 MST7MDT MST7MDT Sun Mar 11 08:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 MST isdst=0 gmtoff=-25200 MST7MDT Sun Mar 11 09:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 MDT isdst=1 gmtoff=-21600 MST7MDT Sun Nov 4 07:59:59 2007 UTC = Sun Nov 4

Re: Daylight savings time / 6.1 and 4.11

2007-01-20 Thread Javier Henderson
Your /etc/localtime is probably a copy of the old zoneinfo data, left over from a previous incarnation. My system at home is running 6.2-RELEASE: zdump -v /etc/localtime | more (...) /etc/localtime Sun Mar 31 06:59:59 1918 UTC = Sun Mar 31 01:59:59 1918 EST isdst=0 gmtoff=-18000

Re: Daylight savings time / 6.1 and 4.11

2007-01-20 Thread Javier Henderson
On Jan 20, 2007, at 10:36 AM, Matthew Seaman wrote: Errr --- why are you looking at when daylight savings changes happened in 1918? Yeah, I noticed that after I sent the email. Duh. -jav ___ freebsd-questions@freebsd.org mailing list

Re: Daylight savings time / 6.1 and 4.11

2007-01-20 Thread Matthew Seaman
Javier Henderson wrote: Your /etc/localtime is probably a copy of the old zoneinfo data, left over from a previous incarnation. My system at home is running 6.2-RELEASE: zdump -v /etc/localtime | more (...) /etc/localtime Sun Mar 31 06:59:59 1918 UTC = Sun Mar 31 01:59:59 1918 EST

Re: Daylight savings time / 6.1 and 4.11

2007-01-20 Thread Pete Slagle
Matthew Seaman wrote: [You could make /etc/localtime a link or a symlink to the appropriate file under /usr/share/zoneinfo, but only if /etc and /usr/share/zoneinfo happen to be on the same filesystem (ie. on the root filesystem), which is not the case in the default install of FreeBSD] As

Re: Daylight savings time / 6.1 and 4.11

2007-01-19 Thread hal
On Jan 18, 2007, at Thursday, Jan18, 2007 5:36 PM, Murray Taylor wrote: This is an issue here at work. We have very many FreeBSD 4.x machines and a growing number of FreeBSD 6.x. The change when daylight saving time starts and ends is an issue for machines in the United States and, we think,

Re: Daylight savings time / 6.1 and 4.11

2007-01-18 Thread Josef Grosch
On Tue, Jan 16, 2007 at 01:31:22PM -0700, hal wrote: This came down from above?! Beginning in 2007, Daylight Savings Time will be lengthened one month by starting three weeks earlier (2AM on the second Sunday in March) and ending one week later (2AM on the first Sunday in November).

RE: Daylight savings time / 6.1 and 4.11

2007-01-18 Thread Murray Taylor
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Josef Grosch Sent: Friday, 19 January 2007 10:59 AM To: hal Cc: freebsd-questions@freebsd.org Subject: Re: Daylight savings time / 6.1 and 4.11 On Tue, Jan 16, 2007 at 01:31:22PM -0700, hal wrote

Re: Daylight savings time / 6.1 and 4.11

2007-01-16 Thread Dan Nelson
In the last episode (Jan 16), hal said: Beginning in 2007, Daylight Savings Time will be lengthened one month by starting three weeks earlier (2AM on the second Sunday in March) and ending one week later (2AM on the first Sunday in November). What patch levels do I need to be at for my 4.7

Re: Daylight savings time / 6.1 and 4.11

2007-01-16 Thread hal
On Jan 16, 2007, at Tuesday, Jan16, 2007 1:59 PM, Dan Nelson wrote: Since it's not a security issue, I doubt the new zone files will go into any -p# branch. If you were tracking the main branches (RELENG_4 or RELENG_6) instead of a -RELEASE branch (RELENG_4_11 or RELENG_6_1), you would have

Re: Daylight savings time / 6.1 and 4.11

2007-01-16 Thread Matt Emmerton
On Jan 16, 2007, at Tuesday, Jan16, 2007 1:59 PM, Dan Nelson wrote: Since it's not a security issue, I doubt the new zone files will go into any -p# branch. If you were tracking the main branches (RELENG_4 or RELENG_6) instead of a -RELEASE branch (RELENG_4_11 or RELENG_6_1), you would