From owner-freebsd-current@FreeBSD.ORG Wed Nov 3 11:26:16 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 DE07916A4CE for ; Wed, 3 Nov 2004 11:26:16 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3850543D5A for ; Wed, 3 Nov 2004 11:26:16 +0000 (GMT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id iA3BQFH3013366; Wed, 3 Nov 2004 14:26:15 +0300 (MSK) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.13.1/8.13.1/Submit) id iA3BQF6S013365; Wed, 3 Nov 2004 14:26:15 +0300 (MSK) (envelope-from ache) Date: Wed, 3 Nov 2004 14:26:15 +0300 From: Andrey Chernov To: Poul-Henning Kamp Message-ID: <20041103112615.GA13218@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Poul-Henning Kamp , current@freebsd.org References: <20041103111813.GB13047@nagual.pp.ru> <16246.1099480832@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16246.1099480832@critter.freebsd.dk> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1; AVE: 6.28.0.12; VDF: 6.28.0.50; host: pobrecita.freebsd.ru) cc: current@freebsd.org Subject: Re: Recent TTYDEF_LFLAG default change 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: Wed, 03 Nov 2004 11:26:17 -0000 On Wed, Nov 03, 2004 at 12:20:32PM +0100, Poul-Henning Kamp wrote: > >Well, use TTYDEF_LFLAG_NOECHO I suggest for that case and leave > >user-visible default untouched to not break userland programs. > > How many pieces of software know about TTYDEF_* outside our sourcecode ? > > Most of it would be bogus I think, software should record the current > state and restore that, not mangle it with defaults. Some tty/pty-emulators can (in spirit of screen). It is not ours, it is common BSD thing. Better to not make surprises and harden porter's job here, really, without a reason. Inside kernel you can do anything you want using TTYDEF_LFLAG_NOECHO. -- http://ache.pp.ru/