From owner-freebsd-current@FreeBSD.ORG Mon Oct 18 21:33:05 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 E724F16A4CE for ; Mon, 18 Oct 2004 21:33:05 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32C5E43D2F for ; Mon, 18 Oct 2004 21:33:05 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id i9ILWvju064691; Mon, 18 Oct 2004 23:33:02 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Randy Bush From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 18 Oct 2004 11:01:04 PDT." <16756.1248.574545.815252@ran.psg.com> Date: Mon, 18 Oct 2004 23:32:57 +0200 Message-ID: <64690.1098135177@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org 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: Mon, 18 Oct 2004 21:33:06 -0000 In message <16756.1248.574545.815252@ran.psg.com>, Randy Bush writes: >>>> root's shell is /usr/local/bin/bash (no comments, please:-) >>>> i am seeing the problem as root in multiluser. i don't spend >>>> much time in single abuser, so can't say. >>> Ahh, that's different then. >>> I'll hunt this one down tomorrow. >> >> Can you try this patch ? > >did, but it did not fix the problem. did a simple portupgrade. >when it finished, i typed "ls," which was not echoed, but i got >the output of the command. issued "reset" command. now it >echos again. sorry. I must be missing something, I can't reproduce it. Your tty should not be opened and/or closed after a portupgrade, so I'm not really sure I understand what's going on. If portupgrade fiddles your echo setting, it should of course reset them. [t]csh takes a very dim view of applications doing this and resets the terminal mode for each prompt (a good thing, since that also works for apps which core dump). So first I'm wondering how this can have anything to do with my changes, (not that I doubt it has, I just can't see the connection) and second I'm wondering if there is a bug in portupgrade which tcsh covers for us which we ought to look at as well. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.