From owner-freebsd-questions Mon Sep 30 04:26:30 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA17163 for questions-outgoing; Mon, 30 Sep 1996 03:48:32 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA17023 for ; Mon, 30 Sep 1996 03:48:22 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id XAA19296 for ; Sun, 29 Sep 1996 23:27:01 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id XAA00508; Sun, 29 Sep 1996 23:24:37 -0700 (PDT) Date: Sun, 29 Sep 1996 23:24:37 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: David Nugent cc: FreeBSD-questions Mailing List Subject: Re: Timezone In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 30 Sep 1996, David Nugent wrote: > 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. FreeBSD should handle this fine. I'm doing that on this box. You should have had the option to set the timezone in sysinstall post-install; it asks if your cmos clock is local time. This drops the empty file /etc/wall_cmos_clock. This informs adjkerntz to do the necessary corrections for local time clocks. But your timezone has to work first. Try running the 'tzsetup' utility to properly set your time zone. Then reboot. (see tzsetup(8)). Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major