From owner-freebsd-stable@freebsd.org Wed Jan 25 09:52:22 2017 Return-Path: <owner-freebsd-stable@freebsd.org> Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F6F4CB5057 for <freebsd-stable@mailman.ysv.freebsd.org>; Wed, 25 Jan 2017 09:52:22 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C79E9CB4 for <freebsd-stable@freebsd.org>; Wed, 25 Jan 2017 09:52:21 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from bsdrookie.norma.com. ([IPv6:fd00::7af]) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPS id v0P9qF8l065946 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <freebsd-stable@freebsd.org>; Wed, 25 Jan 2017 14:52:16 +0500 (YEKT) (envelope-from emz@norma.perm.ru) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=norma.perm.ru; s=key; t=1485337936; bh=wcesSxf6tMaBFN0429Qwkcp/UvZ4estdZBGCsdS9opA=; h=To:From:Subject:Date; b=rEewuL+RfQKOth/Gx4uQ+PlNN+Wls5QqnBAkemULOscN75AhVtb2ZHG5RdAygKu1V qiiG/1abhnm3LU19Z6TknsWt1iSUdn/gkHn0vBeptCtnWI4SXWNlUvW658rMrrxyVv ED3e0NHOARLbFp5shhn6C0W7GcZn7jOd1Cg/IGtw= To: freebsd-stable@freebsd.org From: "Eugene M. Zheganin" <emz@norma.perm.ru> Subject: reset not working like 70% of the time Message-ID: <5888754F.2040901@norma.perm.ru> Date: Wed, 25 Jan 2017 14:52:15 +0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 25 Jan 2017 09:52:22 -0000 Hi, does anyone suffer from this too ? Right now (and for several last years) a 100% decent way to reset a terminal session (for instance, after a connection reset, after acidentally displaying a binary file with symbols that are treated as terminal control sequence, after breaking a cu session, etc) is to launch midnight commander and then quit from it. And the reset is working like in 30% of cases only. Unlike in Linux, where it's 100% functional. Am I the only person seeing this ? Eugene.