From owner-freebsd-hackers  Tue Jun  6 09:21:18 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id JAA25466
          for hackers-outgoing; Tue, 6 Jun 1995 09:21:18 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA25460
          for <freebsd-hackers@freebsd.org>; Tue, 6 Jun 1995 09:21:13 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id CAA17195; Wed, 7 Jun 1995 02:17:19 +1000
Date: Wed, 7 Jun 1995 02:17:19 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199506061617.CAA17195@godzilla.zeta.org.au>
To: freebsd-hackers@freebsd.org, jan@bagend.atl.ga.us
Subject: Re: june 5 14:39 boot.flp
Sender: hackers-owner@freebsd.org
Precedence: bulk

>However, this is the first time that I have had a problem with
>setting the timezone.  I have my cmos clock set for local time.
>I told sysinstall this but it comes back with universal time...
>regardless of what I tell it in the menu.  Now, it only asks once
>for what I think the time is... even after rebooting and running
>sysinstall over ... and over.

There are several bugs:

(1) /etc/wall_cmos_clock isn't removed when the state is switched
    to CMOS_UTC.
(2) if /etc/wall_cmos_clock exists, or if there is already a timezone
    file installed, then tzsetup never asks you for the time so you
    can't set the time or switch the state to or from CMOS_UTC :-).

tzsetup should have a separate option to switch the state.  sysinstall
could handle the problem by (optionally?) removing /etc/localtime and
/etc/wall_cmos_clock.

Bruce