From owner-freebsd-current@FreeBSD.ORG Mon Nov 11 21:39:21 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B8409F6A for ; Mon, 11 Nov 2013 21:39:21 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 915B429A3 for ; Mon, 11 Nov 2013 21:39:21 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id ABD4F475A4 for ; Mon, 11 Nov 2013 21:39:20 +0000 (UTC) Message-ID: <52814E8F.5050608@allanjude.com> Date: Mon, 11 Nov 2013 16:39:27 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Default MBR boot "manager" References: <33391A36-2E7A-473B-87E0-88BDE1AC97D1@fisglobal.com> <52814CD8.5020708@freebsd.org> <52814D98.9050404@allanjude.com> <52814DDE.6040109@freebsd.org> In-Reply-To: <52814DDE.6040109@freebsd.org> X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="O1qHI4a8e0trmn8ujkII0wGqte6ob75ta" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Nov 2013 21:39:21 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --O1qHI4a8e0trmn8ujkII0wGqte6ob75ta Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2013-11-11 16:36, Nathan Whitehorn wrote: > On 11/11/13 15:35, Allan Jude wrote: >> On 2013-11-11 16:32, Nathan Whitehorn wrote: >>> On 11/11/13 15:19, Teske, Devin wrote: >>>> Topic: Lenovo Laptops and bsdinstall zfsboot with MBR layout... >>>> >>>> Should we do the quick patch to change the default >>>> from /boot/boot0 to /boot/mbr: >>>> >>>> Index: zfsboot >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>> --- zfsboot (revision 258016) >>>> +++ zfsboot (working copy) >>>> @@ -764,7 +764,7 @@ zfs_create_diskpart() >>>> # >>>> f_eval_catch $funcname gpart "$GPART_CREATE" mbr >>>> \$disk || >>>> return $FAILURE >>>> - f_eval_catch $funcname gpart "$GPART_BOOTCODE" >>>> /boot/boot0 \ >>>> + f_eval_catch $funcname gpart "$GPART_BOOTCODE" >>>> /boot/mbr \ >>>> \$disk || return $FAILURE >>>> >>>> # >>>> >>>> That would fix things for Lenovo laptops for the next >>>> release until I finish up the bootcode selection menu. >>>> I'd like to take my time in making sure Allan and I design >>>> a worthy bootcode selection menu. >>> This patch looks good (I don't remember why it was boot0 in the first= >>> place). I think gpart automatically installs something like /boot/mbr= >>> by default, so I'd be interested to know if making the diff purely >>> negative still works. >>> >>> On another note, I think we should move away from a selector. Right >>> now, we have three kinds of boot code: >>> 1. ZFS boot code >>> 2. UFS boot code >>> 3. boot0 >>> >>> Unifying 1 and 2 would help a lot -- I don't know of any reason we >>> need both except for tradition. #3 is probably best done as a >>> post-install config step ("Install FreeBSD boot manager" or >>> something), which also means it works for UFS systems. >>> -Nathan >>> _______________________________________________ >>> 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" >> You have to do down right evil things to boot ZFS on MBR. dd'ing the >> 'remainder' of the boot loader into a reserved space at the head of th= e >> ZFS partition. The GPT boot code is 14k, and the code to boot ZFS is >> 40k, whereas the UFS stuff is 512 bytes and fits in the intended slot.= >> > > We could just decide we won't support booting from ZFS on MBR. For > GPT, there is no size limit, which simplifies everything. > -Nathan > _______________________________________________ > 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" With GPT you just make a partition to put the boot code in, so, there can be a size limit, but the zfsboot script uses a generous 512kb (and aligns the first partition to 1mb) I had originally thought to just use GPT all the time, but there was significant demand for ZFS on MBR. Seems people don't want to replace their laptops just to get ZFS --=20 Allan Jude --O1qHI4a8e0trmn8ujkII0wGqte6ob75ta Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSgU6PAAoJEJrBFpNRJZKfTfAP/1nM7Ku2KtUvk9yqCxrSzZ/d 4K5WweyASDydc3RvhdDaNVxhl75sXp0NtyQTsBrlL0RGkFA0XtdEMvaJvHb/txxG f0BP5oSabatH6KNgdiNNIJaaSnXsT4zdbLiRhB+riN3TlWRJerQHr8Wyk5MTAgex AwdC8nxnABKpceIyb5LAfO9ZSGtag+QPd87UdKQ8OH9Ah7VDc9FL0nX4wOYALmYx BMOARe4xB5tEoe6uVf29E+anYrFlZTBc4yqWoRQ4Q3W9lMsJCNry//yYdSvc/DFi vBTfLHtJPMyf/oM/iLeR1l5R0MZDLq+blqnVBz6ZGvMLJXyH0pf3SCE/mMj/1OHz qC0i6RwuS8T8WmURfAccJ7iNvtBdyvo1BhkVzgYe6zXJl0tcBSfuqZubiyjV4VjL VKEXyUD9r+/MQFw/B6jc+UZm0YSHCgUVdcnQDrWXLB7gOyp9TfFDZJbqejrsc+AZ 4hce17Kry2INSG8X3/xRcmOqHJ30TWZpnoFzNDwxILhh7leFsTy/gQJTrhRg+aMb TXWF5Cq2/QUY0eADZsXesH/cb+Tnqvmmq6wgoDEwEyg3PFoV8RRXnf46xUMZJzuT JBqgxDmP/y8u09L55J9VAmAMHCeRbzIVImaCxKQkICouXveObRk+SwBVdmHDOz9X sqLvNLVJlbltkZ4e+Mjq =KeMa -----END PGP SIGNATURE----- --O1qHI4a8e0trmn8ujkII0wGqte6ob75ta--