head	1.4;
access;
symbols
	RELENG_4_11_0_RELEASE:1.2.2.1
	RELENG_4_11:1.2.2.1.0.10
	RELENG_4_11_BP:1.2.2.1
	RELENG_4_10_0_RELEASE:1.2.2.1
	RELENG_4_10:1.2.2.1.0.8
	RELENG_4_10_BP:1.2.2.1
	RELENG_4_9_0_RELEASE:1.2.2.1
	RELENG_4_9:1.2.2.1.0.6
	RELENG_4_9_BP:1.2.2.1
	RELENG_4_8_0_RELEASE:1.2.2.1
	RELENG_4_8:1.2.2.1.0.4
	RELENG_4_8_BP:1.2.2.1
	RELENG_5_0_0_RELEASE:1.3
	RELENG_5_0:1.3.0.2
	RELENG_5_0_BP:1.3
	RELENG_4_7_0_RELEASE:1.2.2.1
	RELENG_4_7:1.2.2.1.0.2
	RELENG_4_7_BP:1.2.2.1
	RELENG_4_6_2_RELEASE:1.2
	RELENG_4_6_1_RELEASE:1.2
	RELENG_4_6_0_RELEASE:1.2
	RELENG_4_6:1.2.0.10
	RELENG_4_6_BP:1.2
	RELENG_4_5_0_RELEASE:1.2
	RELENG_4_5:1.2.0.8
	RELENG_4_5_BP:1.2
	RELENG_4_4_0_RELEASE:1.2
	RELENG_4_4:1.2.0.6
	RELENG_4_4_BP:1.2
	RELENG_4_3_0_RELEASE:1.2
	RELENG_4_3:1.2.0.4
	RELENG_4_3_BP:1.2
	RELENG_4_2_0_RELEASE:1.2
	RELENG_4_1_1_RELEASE:1.2
	PRE_SMPNG:1.2
	RELENG_4_1_0_RELEASE:1.2
	RELENG_3_5_0_RELEASE:1.1
	RELENG_4_0_0_RELEASE:1.2
	RELENG_4:1.2.0.2
	RELENG_4_BP:1.2
	RELENG_3_4_0_RELEASE:1.1
	RELENG_3_3_0_RELEASE:1.1
	RELENG_3_2_PAO:1.1.0.4
	RELENG_3_2_PAO_BP:1.1
	RELENG_3_2_0_RELEASE:1.1
	RELENG_3_1_0_RELEASE:1.1
	RELENG_3:1.1.0.2
	RELENG_3_BP:1.1
	RELENG_3_0_0_RELEASE:1.1;
locks; strict;
comment	@# @;


1.4
date	2003.04.03.05.44.08;	author imp;	state dead;
branches;
next	1.3;

1.3
date	2002.06.06.14.08.04;	author ru;	state Exp;
branches;
next	1.2;

1.2
date	99.02.07.20.30.56;	author joerg;	state Exp;
branches
	1.2.2.1;
next	1.1;

1.1
date	97.01.02.11.54.58;	author joerg;	state Exp;
branches;
next	;

1.2.2.1
date	2002.08.08.10.05.55;	author ru;	state Exp;
branches;
next	1.2.2.2;

1.2.2.2
date	2012.11.17.07.27.16;	author svnexp;	state Exp;
branches;
next	;


desc
@@


1.4
log
@2.x->3.0 upgrade tools are no longer needed.  5.x is unlikely to fit
on a 2.1/2.2 root disk anyway.

OK'd by: peter
@
text
@$FreeBSD: src/tools/3.0-upgrade/README,v 1.3 2002/06/06 14:08:04 ru Exp $

By 1996/12/04, the utmp element size has been changed, in order to
allow for longer usernames.  This change renders all existing wtmp
files unusable.  The cvt-wtmp utility is provided as an aid to convert
your old wtmp files into the new format, so you don't lose the
existing track record.

The tool cannot handle gzip'ed wtmp backups, so unzip them first if
you need.  Then simply call it as:

	./cvt-wtmp /var/log/wtmp*

The old wtmp files are being renamed to <file>.bak, so nothing will be
lost even in case of a failure.  If you are only about to test whether
the tool will grok your files correctly, you can run it as:

	./cvt-wtmp -n /var/log/wtmp*

The tool tries an ``educated guess'', based on the reasonability of
the timestamp values in the wtmp file.  If it fails to recognize the
format of your wtmp, it normally bails out, or at least ignores
garbage records.  In this case, rename the .bak files to the original
name, and try to force the conversion:

	./cvt-wtmp -f /var/log/wtmp.xxx

Make sure to verify the result however!


Dresden, Jan 2, 1996			Joerg  <joerg@@FreeBSD.org>
@


1.3
log
@Fixed typos.
@
text
@d1 1
a1 1
$FreeBSD$
@


1.2
log
@Fix a typo describing the filename of cvt-wtmp.

Submitted by:	Ruslan Ermilov <ru@@ucb.crimea.ua>
@
text
@d1 2
d18 1
a18 1
	./cvs-wtmp -n /var/log/wtmp*
d26 1
a26 1
	./cvs-tmp -f /var/log/wtmp.xxx
d31 1
a31 1
Dresden, Jan 2, 1996			Joerg  <joerg@@freebsd.org>
@


1.2.2.1
log
@MFC: tidying.
@
text
@a0 2
$FreeBSD$

d16 1
a16 1
	./cvt-wtmp -n /var/log/wtmp*
d24 1
a24 1
	./cvt-wtmp -f /var/log/wtmp.xxx
d29 1
a29 1
Dresden, Jan 2, 1996			Joerg  <joerg@@FreeBSD.org>
@


1.2.2.2
log
@Switch importer
@
text
@d1 1
a1 1
$FreeBSD: stable/4/tools/3.0-upgrade/README 101516 2002-08-08 10:05:55Z ru $
@


1.1
log
@Add a -f (`force') option to cvt-wtmp.  This might help people with
slightly bogus wtmp files (it definately helps in Jordan's case).

Also add a README explaining what all this is for.
@
text
@d10 1
a10 1
	./cvt-tmp /var/log/wtmp*
d16 1
a16 1
	./cvs-tmp -n /var/log/wtmp*
@

