From owner-freebsd-current@FreeBSD.ORG Sat Oct 16 22:19:41 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 1B0F816A4CE for ; Sat, 16 Oct 2004 22:19:41 +0000 (GMT) Received: from pozo.com (pozo.com [216.101.162.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B439B43D1F for ; Sat, 16 Oct 2004 22:19:40 +0000 (GMT) (envelope-from null@pozo.com) Received: from sunpci.pozo.com (sunpci.pozo.com [192.168.0.29]) (authenticated bits=0) by pozo.com (8.13.1/8.13.1) with ESMTP id i9GMJVq7064611 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT); Sat, 16 Oct 2004 15:19:31 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <6.1.2.0.2.20041016151749.03b6ede8@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Sat, 16 Oct 2004 15:19:31 -0700 To: "Conrad J. Sabatier" , freebsd-current@freebsd.org From: Manfred Antar In-Reply-To: <20041016165900.4a0446b0@dolphin.local.net> References: <16753.26886.433270.800049@ran.psg.com> <20041016142741.32cd5ae8@dolphin.local.net> <41717BC8.3070205@gamersimpact.com> <20041016165900.4a0446b0@dolphin.local.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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:19:41 -0000 At 02:59 PM 10/16/2004, Conrad J. Sabatier wrote: >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. Same thing here with portupgrade and a statically compiled bash (version 3) ================================== || null@pozo.com || || Ph. (415) 681-6235 || ==================================