From owner-freebsd-current@FreeBSD.ORG Sat Oct 16 22:00:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BA5416A4D4 for ; Sat, 16 Oct 2004 22:00:51 +0000 (GMT) Received: from lakermmtao09.cox.net (lakermmtao09.cox.net [68.230.240.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D01C43D54 for ; Sat, 16 Oct 2004 22:00:23 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.30.24]) by lakermmtao09.cox.net (InterMail vM.6.01.03.04 201-2131-111-106-20040729) with ESMTP id <20041016215906.VTVK16785.lakermmtao09.cox.net@dolphin.local.net> for ; Sat, 16 Oct 2004 17:59:06 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with SMTP id i9GLx53K001862 for ; Sat, 16 Oct 2004 16:59:05 -0500 (CDT) (envelope-from conrads@cox.net) Date: Sat, 16 Oct 2004 16:59:00 -0500 From: "Conrad J. Sabatier" To: freebsd-current@freebsd.org Message-ID: <20041016165900.4a0446b0@dolphin.local.net> In-Reply-To: <41717BC8.3070205@gamersimpact.com> References: <16753.26886.433270.800049@ran.psg.com> <20041016142741.32cd5ae8@dolphin.local.net> <41717BC8.3070205@gamersimpact.com> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: no echo console X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Oct 2004 22:00:51 -0000 On Sat, 16 Oct 2004 14:51:36 -0500, Ryan Sommers wrote: > Conrad J. Sabatier wrote: > > >On Sat, 16 Oct 2004 11:31:34 -0700, Randy Bush wrote: > > > > > > > >>on -current as of an hour ago (and the last few days too), running > >>many progs leaves the console, whether serial or xterm from another > >>host, not echoing. a `reset` fixes it. shell is bash2. > >> > >>randy > >> > >> > > > >Yes, I'm still noticing this, too. The last commits from yesterday > >seem to have improved the situation somewhat, but it's still not > >100%. Echo will just randomly become disabled after certain commands. > > > >Wish I could provide more specifics. Sorry. > > > > > > > Are you both using the syscons "device sc" console driver or are you > using the pcvt "device vt" console driver? "device sc" It's very odd, and hard to tell what's causing this or when it's likely to occur. I've noticed it a few times after running portupgrade. -- Conrad J. Sabatier -- "In Unix veritas"