From owner-freebsd-stable Wed Mar 20 17: 3:26 2002 Delivered-To: freebsd-stable@freebsd.org Received: from hilfy.ece.cmu.edu (HILFY.ECE.CMU.EDU [128.2.136.133]) by hub.freebsd.org (Postfix) with ESMTP id E9E9837B400 for ; Wed, 20 Mar 2002 17:03:18 -0800 (PST) Received: from rushlight.kf8nh.apk.net (root@VPN46.ECE.CMU.EDU [128.2.138.46]) by hilfy.ece.cmu.edu (8.11.0/8.8.8) with ESMTP id g2L138U08902 for ; Wed, 20 Mar 2002 20:03:08 -0500 (EST) Received: (from allbery@localhost) by rushlight.kf8nh.apk.net (8.11.6/8.11.6) id g2L138154061; Wed, 20 Mar 2002 20:03:08 -0500 (EST) (envelope-from allbery@ece.cmu.edu) X-Authentication-Warning: rushlight.kf8nh.apk.net: allbery set sender to allbery@ece.cmu.edu using -f Subject: Re: portupgrade insists on tty output From: "Brandon S. Allbery " KF8NH To: freebsd-stable@FreeBSD.ORG In-Reply-To: <5.1.0.14.2.20020320175430.00aa0e08@vivaldi.pn.sinp.msu.ru> References: <5.1.0.14.2.20020320175430.00aa0e08@vivaldi.pn.sinp.msu.ru> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 20 Mar 2002 20:03:08 -0500 Message-Id: <1016672588.52619.3.camel@rushlight.kf8nh.apk.net> Mime-Version: 1.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 2002-03-20 at 10:09, Sergei Vyshenski wrote: > Bringing the job to foreground with fg produces NO output > on the screen, and calmly proceeds with portupgrade. > > What does portupgrade want to say to tty? The latest portupgrade wants to be able to ask questions, so it apparently opens /dev/tty. > How I can run it in batch mode? Possibly "portupgrade -y". -- brandon s. allbery [linux][solaris][japh][freebsd] allbery@kf8nh.apk.net system administrator [openafs][heimdal][too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university ["better check the oblivious first" -ke6sls] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message