From owner-freebsd-current Mon Jan 20 15:52:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA11213 for current-outgoing; Mon, 20 Jan 1997 15:52:54 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA11186; Mon, 20 Jan 1997 15:52:42 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA25092; Tue, 21 Jan 1997 00:52:39 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id AAA00584; Tue, 21 Jan 1997 00:49:10 +0100 (MET) Message-ID: Date: Tue, 21 Jan 1997 00:49:09 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.org (FreeBSD-current users) Cc: sos@FreeBSD.org Subject: Re: 2.2 syscons breakage! References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from J Wunsch on Jan 21, 1997 00:37:09 +0100 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk 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. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)