Date: Tue, 8 Oct 2013 09:21:13 +0000 From: "Teske, Devin" <Devin.Teske@fisglobal.com> To: Allan Jude <freebsd@allanjude.com> Cc: "<freebsd-current@freebsd.org>" <freebsd-current@freebsd.org>, "Teske, Devin" <Devin.Teske@fisglobal.com> Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Message-ID: <13CA24D6AB415D428143D44749F57D720FC4243D@LTCFISWMSGMB21.FNFIS.com> In-Reply-To: <52539C9F.9000400@allanjude.com> References: <52531295.7090700@allanjude.com> <52539300.50305@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC415EA@LTCFISWMSGMB21.FNFIS.com> <52539C9F.9000400@allanjude.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 7, 2013, at 10:48 PM, Allan Jude wrote: > On 2013-10-08 01:11, Teske, Devin wrote: >> On Oct 7, 2013, at 10:07 PM, Allan Jude wrote: >>=20 >>> On 2013-10-07 15:59, Allan Jude wrote: >>>> Devin Teske and I have been working on a big patch to bsdinstall to >>>> implement installing on a ZFS pool. It supports both GPT and MBR, the = 4k >>>> sector gnop trick, and optional GELI encryption. We would like to comm= it >>>> this in time for 10.0-BETA1 so it needs some testing to work out any >>>> obvious bugs before we send it off to re@ to get it committed. >>>>=20 >>>> It includes a single configuration menu that allows you to select all = of >>>> the required details, including which drives to use (gets details from >>>> camcontrol, also includes an inspection utility that presents the >>>> detailed output of camcontrol inquiry/identify, and gpart show), what >>>> ZFS RAID level to use (taking in to consideration the selected number = of >>>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>>>=20 >>>>=20 >>>> Additional, it includes some other changes to bsdinstall: >>>> 1. Change the default to the 'non-standard keyboard mapping' prompt to= no >>>> 2. Replace the 3 separate dialogs to configure an ipv4 address with ju= st 1 >>>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>>> feature has been combined into the regular 'services to enable' dialog >>>> and enabled by default >>>>=20 >>>>=20 >>>> You can browse the patches here: >>>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>>>=20 >>>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>>> available compressed (48 MB) or uncompressed (211 MB): >>>>=20 >>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>>>=20 >>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>>>=20 >>>>=20 >>>> We look forward to your feedback >>>>=20 >>> I've generated a new version of the ISO incorporating all of todays >>> changes and moving up to 10.0-ALPHA5 >>> It includes 2 patches from Warren Block, improving the keymap menu and >>> indicating which network interfaces are wireless >>>=20 >> Excellent. >>=20 >> However, I have to say... you opened a can of worms by touching keymap. >>=20 >> Eventually I plan to rewrite all of the scripts to the same format that = zfsboot >> is using. I've already started rewriting keymap to the new format. Of co= urse, >> this opened up another can of worms... the simple things like: >>=20 >> DIALOG_OK >> DIALOG_CANCEL >> DIALOG_ESC >=20 > Yeah, after having them, I felt a bit naked not having all of those > 'constants' defined. >=20 The constants are now where they belong... `dialog.subr' I also went through bsdconfig(8) with a fine-tooth comb and made use of the new "constants" everywhere. I think it's a definite improvement. > Originally, all I had done was add --defaultno to the dialog command, > but Warren's patch makes a lot of sense, allow the user to 'try' the new > keymap before trying to do the rest of the install based on it. >=20 I rewrote warren's code into the stateful design and cleaned it up. >> I feel would be much better off in the `dialog.subr' module. So,... I've= started >> peppering their usage everywhere in bsdconfig to make them "proper". >>=20 >> That means they will just be transparent from including `dialog.subr'. >>=20 >=20 > This is definately something that I think is a good idea, but my focus > is on improving the usability and functionality of the installer in time > for 10.0. Unifying everything to the bsdconfig style is slightly lower > priority. Admittedly, the `bsdconfig networking` stuff is quite nice >=20 *nods* I took a look at the bsdinstall networking stuff, and I wanted to run away. Let's push that into the future. It wasn't too hard to get those global exit codes deployed, so I did that, but like you say... I agree we should minimize "extra work" that will be eventually slated for a future release. --=20 Devin >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>>=20 >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>>=20 >> Excellent, thanks! >=20 >=20 > --=20 > Allan Jude >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" _____________ 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?13CA24D6AB415D428143D44749F57D720FC4243D>