From owner-freebsd-current  Sat Dec  7 09:36:39 1996
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id JAA01780
          for current-outgoing; Sat, 7 Dec 1996 09:36:39 -0800 (PST)
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA01774
          for <freebsd-current@freebsd.org>; Sat, 7 Dec 1996 09:36:35 -0800 (PST)
Received: (from imb@localhost)
          by asstdc.scgt.oz.au (8.7.6/BSD4.4) id EAA06776
          Sun, 8 Dec 1996 04:36:26 +1100 (EST)
From: michael butler <imb@scgt.oz.au>
Message-Id: <199612071736.EAA06776@asstdc.scgt.oz.au>
Subject: Re: cvs commit: src/include utmp.h
In-Reply-To: <22065.849978642@time.cdrom.com> from "Jordan K. Hubbard" at "Dec 7, 96 09:10:42 am"
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Sun, 8 Dec 1996 04:36:26 +1100 (EST)
Cc: freebsd-current@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Jordan K. Hubbard writes:

>    One of these upgrade-time actions could, in this case, be the
>    migration of your wtmp file for instance.
 
Personally, I'm in favour of a migratory program even if only for wtmp
conversion since some of us use the accumulated data for customer
accounting,

	michael