From owner-freebsd-current@FreeBSD.ORG  Tue Nov  4 02:56:22 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id A8214106567F
	for <freebsd-current@freebsd.org>; Tue,  4 Nov 2008 02:56:22 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	by mx1.freebsd.org (Postfix) with ESMTP id 528A68FC14
	for <freebsd-current@freebsd.org>; Tue,  4 Nov 2008 02:56:22 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost [127.0.0.1])
	by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id mA42tuYa064707;
	Mon, 3 Nov 2008 19:55:56 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Mon, 03 Nov 2008 19:57:09 -0700 (MST)
Message-Id: <20081103.195709.-1674606699.imp@bsdimp.com>
To: sgk@troutmask.apl.washington.edu
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20081103232009.GA3161@troutmask.apl.washington.edu>
References: <20081103232009.GA3161@troutmask.apl.washington.edu>
X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org
Subject: Re: TTY or SSH character echoing issue
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2008 02:56:22 -0000

In message: <20081103232009.GA3161@troutmask.apl.washington.edu>
            Steve Kargl <sgk@troutmask.apl.washington.edu> writes:
: With current source of 16 Oct 08, I'm seeing a seemly
: strange echoing problem when I use ssh to connect from
: one node in my cluster to another.  At the (t)csh command
: line prompt, I want to execute ~/trunk/cmd.  So, I have
: 
: % ~/trunk/cmd
: 
: The strange behavior is that the ~ character does not
: appear on the terminal until after I enter the / character.
: 
: Any advice at determining whether this a tty or ssh or
: some other problem would be appreciated.

Are you using tip?

Warner