From owner-freebsd-questions Sun Sep 29 18:43:15 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA13141 for questions-outgoing; Sun, 29 Sep 1996 18:43:15 -0700 (PDT) Received: from sdev.blaze.net.au (sdev.blaze.net.au [203.17.53.11]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA12424 for ; Sun, 29 Sep 1996 18:42:02 -0700 (PDT) Received: from localhost (davidn@localhost) by sdev.blaze.net.au (8.7.6/8.6.9) with SMTP id LAA03750 for ; Mon, 30 Sep 1996 11:41:25 GMT Date: Mon, 30 Sep 1996 11:41:23 +0000 () From: David Nugent To: FreeBSD-questions Mailing List Subject: Timezone Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Here's a curley one. Currently, my FreeBSD system runs without timezones, since the CMOS clock is local time. This seems to work fine in most respects (internally) until we start interacting with the outside world. For example, the timezone on this email is probably +0000, which is incorrect. And another effect is that a network date/time ntp corrector I went to install today is also the expected 10 hours wrong. Yes, I know how to install the correct timzone (just create the link). But the problem is that since FreeBSD isn't the only OS I run, I don't really want to have to change the CMOS time every time I change operating systems where the CMOS is expected to be local time. Is there a happy medium? Linux, for example, had no problem with this. I'm running FreeBSD-(almost)-current, if that helps. Regards, David David Nugent, Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-791-9547 Data/BBS +61-3-792-3507 3:632/348@fidonet davidn@blaze.net.au http://www.blaze.net.au/~davidn