Date: 10 Nov 2000 04:29:27 -0800 From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) To: Jordan Hubbard <jkh@winston.osd.bsdi.com> Cc: Jimmy <olgeni@uli.it>, ports@FreeBSD.ORG, pine@freebsd.ady.ro, kris@FreeBSD.ORG Subject: Re: 4.2 BETA ISO image Message-ID: <vqcy9ysko2g.fsf@silvia.hip.berkeley.edu> In-Reply-To: <23007.973846892@winston.osd.bsdi.com> (Jordan Hubbard's message of "Fri, 10 Nov 2000 01:01:32 -0800") References: <vqcpuk4eg44.fsf@silvia.hip.berkeley.edu> <23007.973846892@winston.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* From: Jordan Hubbard <jkh@winston.osd.bsdi.com> * Well, due to the well-publicized limitations in pkg_add, eliminating * them is a good thing. It basically hangs up the install pretty good * otherwise. :( That is not good. :< * > Perhaps sysinstall should be fixed? If that is not possible, we can * * It's not sysinstall - it's pkg_add taking stdin from a pipe in slave Ok, pkg_add then. Can't it be modified to take the input from a named pipe or something? * mode. Even if the I/O were to occur over on VTY1, you couldn't * provide input to the dialogs. The I/O simply needs to be suppressed, * as Steve's patch supposedly does (I haven't had the chance to really * look at what those environment variables do yet), or pkg_add needs to * reopen a controlling tty before the post-install scripts are run. The * former "solution" might happen before 4.2 if it really does the job, * but certainly not the latter. Eventually, sysinstall/pkg_add should be fixed. There is no reason why we can't let people use sysinstall where a normal pkg_add works fine. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?vqcy9ysko2g.fsf>