From owner-freebsd-current@FreeBSD.ORG Sat Jul 14 21:07:23 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A437106566C; Sat, 14 Jul 2012 21:07:23 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id E16A88FC0A; Sat, 14 Jul 2012 21:07:22 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa02.fnfis.com (8.14.4/8.14.4) with ESMTP id q6EL7IVk011089 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 14 Jul 2012 16:07:19 -0500 Received: from [10.0.0.101] (10.14.152.61) by smtp.fisglobal.com (10.132.206.31) with Microsoft SMTP Server (TLS) id 14.2.283.3; Sat, 14 Jul 2012 16:07:17 -0500 MIME-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset="windows-1252" From: Devin Teske In-Reply-To: <5001DC03.6010705@cran.org.uk> Date: Sat, 14 Jul 2012 14:07:21 -0700 Content-Transfer-Encoding: quoted-printable Message-ID: References: <50013D3B.90206@cran.org.uk> <04E88813-2416-4B60-93D3-D620DBE5A8AF@fisglobal.com> <5001D152.2050007@cran.org.uk> <5001DC03.6010705@cran.org.uk> To: Bruce Cran X-Mailer: Apple Mail (2.1257) X-Originating-IP: [10.14.152.61] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855, 1.0.260, 0.0.0000 definitions=2012-07-14_05:2012-07-13, 2012-07-14, 1970-01-01 signatures=0 Cc: Ron@FreeBSD.ORG, Devin Teske , McDowell , freebsd-current@freebsd.org Subject: Re: [IMPORT] bsdconfig(8) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Devin Teske List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jul 2012 21:07:23 -0000 On Jul 14, 2012, at 1:52 PM, Bruce Cran wrote: > On 14/07/2012 21:17, Devin Teske wrote: >> The implication is that bsdconfig and bsdinstall will forever live side-= by-side once linked together. That includes having bsdconfig live on the in= stallation media so that bsdinstall can utilize it during the installation = to (among other things) set the root password. >=20 > Doesn't that mean that bsdconfig would be invoked as "bsdconfig password"= which would bypass the welcome screen and so by the time the user does see= it the root password (and timezone) will have been set? >=20 No. In 8.x, when you're performing the guided install, will prompt you to set t= he root password among many other things. At the very end, it prompts you a= s to whether you'd like to visit the configuration menu one more time. In 9.x and higher, bsdinstall (taking the place of sysinstall) in a similar= manner asks you to set the root password among many other things, but does= not ask you if you'd like to visit the configuration menu one more time (b= ecause there isn't one). So think of it this way=85 bsdinstall has these functionalities but no menu= to invoke them. By removing these functionalities from bsdinstall and instead using bsdconf= ig for these functionalities, the scenario now becomes=85 bsdinstall asks to set the root password (by either executing "bsdconfig pa= ssword" -- in which a transition is only noticeable because the --backtitle= changes from "FreeBSD Installer" to "bsdconfig" -- or bsdinstall could ins= tead include /usr/libexec/bsdconfig/040.password/include/password.subr and = call the f_dialog_input_password() function where it can control --backtitl= e to make the usage even more seemless; making bsdconfig's functionality lo= ok like bsdinstall's). After asking to set the root password, bsdinstall ca= n now (like sysinstall) ask the user if they'd like to visit the configurat= ion menu one last time to make any additional changes (and bsdconfig -- no = arguments -- would provide that menu). --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.