From owner-freebsd-current Wed Aug 16 11:39:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id LAA20756 for current-outgoing; Wed, 16 Aug 1995 11:39:08 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id LAA20730 for ; Wed, 16 Aug 1995 11:38:59 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id UAA18769; Wed, 16 Aug 1995 20:38:46 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id UAA06744; Wed, 16 Aug 1995 20:38:45 +0200 Message-Id: <199508161838.UAA06744@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: Gary Palmer cc: current@freebsd.org Subject: Re: syscons Date: Wed, 16 Aug 1995 20:38:45 +0200 From: Mark Murray Sender: current-owner@freebsd.org Precedence: bulk > I've noticed some annoying behaviour form syscons. It seems to happen > when switching VTY's when there is output on the one you are switching > from happening around the same time. > > Effects have varied from the cursor being in the wrong place to parts > of the screen not being updated (i.e. bits of the old VTY are still > visable). I have this too. Bits of the previous screen overwriting the screen you have just moved to. It is a little difficult, but possible to repeat. You need rapid and copious output... > Maybe this only happens on my old, slow, 486DX33, but I've noticed it > a couple of times in the last few days/weeks and it's annoying. I'm > running a recent kernel from the 2.1-STABLE branch. I have it on a 486DX50 with a -current last compiled about 10 days ago... > Is this behaviour known about? Is there a cure? Yehbo. Dunno. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grumble.grondar.za for PGP key