Date: Fri, 25 Nov 2016 22:55:23 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-sysinstall@FreeBSD.org Subject: [Bug 202058] bsdinstall - Disable dialog(3) for distfetch/checksum/distextract targets Message-ID: <bug-202058-2920-SwFSSOwF1h@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-202058-2920@https.bugs.freebsd.org/bugzilla/> References: <bug-202058-2920@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202058 --- Comment #8 from Devin Teske <dteske@FreeBSD.org> --- I still need to make sure that we build upon bapt, emaste, and my own work thus far with respect to the following (previously mentioned) work: https://svnweb.freebsd.org/base?view=revision&revision=307802 [bapt+emaste] https://svnweb.freebsd.org/base?view=revision&revision=306648 [emaste] https://svnweb.freebsd.org/base?view=revision&revision=306375 [emaste+dteske] I had previously suggested that a good solid approach would be to first and foremost follow the approach of bapt with respect to tzsetup, and then optionally add a command-line flag to each of the applications to enable runtime disabling of dialog(1). I do like to think of iterative approaches that build upon and reinforce prior works. The shortcomings of distfetch, distextract, and cksum are also solved by way of fixing the other issue of them not being able to run in a dialog(1,3)-less environment -- regardless of that being a decision that is made at compile-time or runtime. I think the best approach would be to use isatty(3)/stty(1) at runtime to invoke the same code-path as WITHOUT_DIALOG. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202058-2920-SwFSSOwF1h>