From owner-freebsd-current  Mon Jan 20 18:07:25 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id SAA19911
          for current-outgoing; Mon, 20 Jan 1997 18:07:25 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA19905;
          Mon, 20 Jan 1997 18:07:18 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id TAA17661; Mon, 20 Jan 1997 19:06:57 -0700 (MST)
Date: Mon, 20 Jan 1997 19:06:57 -0700 (MST)
Message-Id: <199701210206.TAA17661@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
Cc: freebsd-current@freebsd.org (FreeBSD-current users), sos@freebsd.org
Subject: Re: 2.2 syscons breakage!
In-Reply-To: <Mutt.19970121004909.j@uriah.heep.sax.de>
References: <Mutt.19970121003709.j@uriah.heep.sax.de>
	<Mutt.19970121004909.j@uriah.heep.sax.de>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

J. Wunsch writes:
> As I wrote:
> 
> > Please fix ASAP (or back the changes out of 2.2 until the bugs have
> > been shaken out in -current).
> 
> Just to prove: reverting syscons.c to 1.182.2.7 and syscons.h to
> 1.23.2.1 fixes the problem.

Forgive me for losing track, but what exactly was the bug that you
reported?


Nate