From owner-freebsd-arch@FreeBSD.ORG Mon Nov 11 20:57:08 2013 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8B7A91F3; Mon, 11 Nov 2013 20:57:08 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4FF5226D4; Mon, 11 Nov 2013 20:57:08 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id rABKv6H0026518 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 11 Nov 2013 14:57:07 -0600 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.152]) by LTCFISWMSGHT06.FNFIS.com ([10.132.206.17]) with mapi id 14.03.0158.001; Mon, 11 Nov 2013 14:57:05 -0600 From: "Teske, Devin" To: Nathan Whitehorn Subject: Re: [CFT] bsdinstall and zfsboot enhancements Thread-Topic: [CFT] bsdinstall and zfsboot enhancements Thread-Index: AQHO1/VTfN3AabWEO0qqCcwz4iQiNg== Date: Mon, 11 Nov 2013 20:57:04 +0000 Message-ID: References: <5275C597.6070702@freebsd.org> <97944047-D575-4E2E-B687-9871DFE058E3@fisglobal.com> <52769CFE.5080707@freebsd.org> <5281340E.8080009@callfortesting.org> <52813E53.20403@freebsd.org> <5281441E.7060806@freebsd.org> In-Reply-To: <5281441E.7060806@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.120] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <487C3101B60CC24E98DABF63D8F8D01A@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-11-11_03:2013-11-11,2013-11-11,1970-01-01 signatures=0 Cc: "Teske, Devin" , Current Current , "freebsd-arch@freebsd.org" , Devin Teske , Peter Grehan , Michael Dexter X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Nov 2013 20:57:08 -0000 On Nov 11, 2013, at 12:54 PM, Nathan Whitehorn wrote: > On 11/11/13 14:30, Nathan Whitehorn wrote: >> On 11/11/13 14:18, Teske, Devin wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA512 >>>=20 >>>=20 >>> On Nov 11, 2013, at 11:46 AM, Michael Dexter wrote: >>>=20 >>>=20 >>> Hello all, >>>=20 >>> I have been experimenting with various BSD and GNU/Linux boot media >>> under bhyve and noticed that we may want to accommodate the "LiveCD" >>> mode of the installer, which in turn requires the correct console. >>>=20 >>> Currently, one is prompted for VT100 for installation but this does not >>> appear to work/stick for LiveCD mode. >>>=20 >>> Can anyone verify this? >>>=20 >>>=20 >>> While I developed this patch... >>> https://urldefense.proofpoint.com/v1/url?u=3Dhttp://druidbsd.cvs.sf.net= /viewvc/druidbsd/bsdinstall_zfs/usr.sbin%253A%253Absdinstall%253A%253Ascrip= ts%253A%253Aconfig.patch?revision%3D1.10%26view%3Dmarkup&k=3D%2FbkpAUdJWZui= TILCq%2FFnQg%3D%3D%0A&r=3DMrjs6vR4%2Faj2Ns9%2FssHJjg%3D%3D%0A&m=3DaZg%2Bxwq= LTX6Zcpf3Rc44iPtAQhFrpqoS4FC5B8ykxJQ%3D%0A&s=3D6d54d337ea5472f5713ddbe7788d= 3248c45feefd4b291eab0a976c39e9d40428=20 >>>=20 >>> Reasons exist to search for a better solution, see here: >>> https://urldefense.proofpoint.com/v1/url?u=3Dhttp://lists.freebsd.org/p= ipermail/freebsd-current/2013-November/046148.html&k=3D%2FbkpAUdJWZuiTILCq%= 2FFnQg%3D%3D%0A&r=3DMrjs6vR4%2Faj2Ns9%2FssHJjg%3D%3D%0A&m=3DaZg%2BxwqLTX6Zc= pf3Rc44iPtAQhFrpqoS4FC5B8ykxJQ%3D%0A&s=3D5f8128901747346f937ffc4478eadb4bc3= 9059504258dfb9b36f0fb9e7a61b79=20 >>> (and messages that follow it) >>>=20 >>> Is modifying init(8) still the way to go? What modification do we want = to make? >>> I'll do the work if we can come to consensus. >>>=20 >>> Or should we touch up the patch in some way to address the original con= cerns? >>>=20 >>=20 >> I think modifying init is the way to go -- it keeps the install system f= rom interfering with the installed one, as well as fixing this kind of issu= e with moved hard drives or PXE booting or what have you. If we can provide= a guarantee that any system that displays text has a working console (unle= ss explicitly configured not to), useability is improved. >>=20 >> I would propose one of the following (and volunteer to write the code): >>=20 >> Option A >> ------------ >>=20 >> 1. init checks if there is an entry in /etc/ttys for the terminal[s] cor= responding to the value[s] in kern.console >> 2. If an entry for each console terminal exists in /etc/ttys, enable it >> 3. If not, invent one with a terminal type of "ansi" >>=20 >> The one issue here is that someone may want to force a particular entry = to off and still have it be the kernel console. This is tricky. We could in= vent a new "status" field that is not "on" or "off" ("auto", maybe, or "ifc= onsole"?). Which brings us to: >=20 > One easy way to accomplish this is just to only implement (1) and (3), th= en comment out the ttyu0 entry in /etc/ttys on x86 instead of marking it "o= ff". Then the behavior is just that a tty marked "off" stays off, one marke= d "on" stays on, and one not present spawns login with a terminal type corr= esponding to "console" (by default "unknown") if it happens to be the conso= le. I will implement this over the next few days and then send patches unle= ss anyone has an objection. I love it. (smiles) Excellent idea and that's the winner I think. +1 --=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.