Date: Mon, 11 Nov 2013 20:40:53 +0000 From: "Teske, Devin" <Devin.Teske@fisglobal.com> To: Nathan Whitehorn <nwhitehorn@freebsd.org> Cc: Current Current <freebsd-current@freebsd.org>, Devin Teske <dteske@freebsd.org>, "Teske, Devin" <Devin.Teske@fisglobal.com>, Peter Grehan <grehan@freebsd.org>, Michael Dexter <editor@callfortesting.org> Subject: Re: [CFT] bsdinstall and zfsboot enhancements Message-ID: <4E00C3CC-75EA-4249-8D9F-42F37988F4CE@fisglobal.com> In-Reply-To: <52813F9E.8080304@freebsd.org> References: <C9783B1F-20EA-4C08-9947-70DF363E8B6A@fisglobal.com> <5275C597.6070702@freebsd.org> <97944047-D575-4E2E-B687-9871DFE058E3@fisglobal.com> <ABD90FE2-1540-410A-959E-D91D0BE811E3@freebsd.org> <52769CFE.5080707@freebsd.org> <5281340E.8080009@callfortesting.org> <BFE265FC-849A-4381-8DF7-216AD5584253@fisglobal.com> <52813F9E.8080304@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 11, 2013, at 12:35 PM, Nathan Whitehorn wrote: > On 11/11/13 14:30, Teske, Devin wrote: >> (disabling default gpg-signing until they fix a bug with the quoting) >>=20 >> On Nov 11, 2013, at 11:46 AM, Michael Dexter wrote: >>=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 >> Sorry, I mistook your issue in the previous e-mail to be on-going with t= he >> thread it was inline with. >>=20 >> "LiveCD" changes things a bit. >>=20 >> (thinks) >>=20 >> I would expect that a prompt could do: >>=20 >> 1. modify /etc/ttys on the boot media >> 2. run "init q" >>=20 >> But there's a couple of assumptions... >>=20 >> 3. Can we even write to /etc/ttys? >> NB: We can write to /tmp because it's an md0 swap device >>=20 >> So do we have to get fancy with slipping a unionfs layer backed by anoth= er >> md swap device above the root? >>=20 >> That would make every file on the boot media writable (writes would go to >> the swap-backed md device and if you execute "rm -fW file" you can get b= ack >> files that have been previously unlinked -- unlinks are stored as whiteo= uts in >> the swap backed md device). For all intents and purposes, the read-only = file- >> system becomes writable and we could then munge /etc/ttys to enable seri= al >> only when a menu item is chosen. >>=20 >> If I'm off-base, let me know... sounds like a lot of trouble. >>=20 >> The alternative being that you enable serial by default but then I have = to tell >> field engineers to unplug barcode readers before they do an install??? (= that's >> a question, it may be entirely safe, but I've never tried, seems unsafe) >>=20 >> Question is, how would you disable it? Goes back to writable filesystem. >=20 > This is why I don't think we want to modify /etc/ttys. Instead we want to= have init do the right thing (follow the boot console) with a single uncha= nged /etc/ttys. Let me see if I've got it right... Already-knowns: + The boot variables are influenced by loader.conf which is read-only media. + But Michael is loading the media from bhyve. Question: Does bhyve set kern.console irrespective of loader.conf values? If so, then yeah... I'm all for supporting your stated Option-A in the othe= r thread. --=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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E00C3CC-75EA-4249-8D9F-42F37988F4CE>