Date: Mon, 11 Nov 2013 16:35:20 -0500 From: Allan Jude <freebsd@allanjude.com> To: freebsd-current@freebsd.org Subject: Re: Default MBR boot "manager" Message-ID: <52814D98.9050404@allanjude.com> In-Reply-To: <52814CD8.5020708@freebsd.org> References: <33391A36-2E7A-473B-87E0-88BDE1AC97D1@fisglobal.com> <52814CD8.5020708@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Jx8jksmRvPacXCT5FFoc5PP9eWtutpilG
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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 the
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.
--=20
Allan Jude
--Jx8jksmRvPacXCT5FFoc5PP9eWtutpilG
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/
iQIcBAEBAgAGBQJSgU2ZAAoJEJrBFpNRJZKfiT8QAJNCIP3lTczwVLVJ7kzUNma5
lIDYdN1AcVwr/t+gYDQ2RvCHlj8PTpOxF3eFYsm4k9MGyhLqewLnHVhmNdKvdB2X
BSKaoeXnpTEkB0iixeUPvqrTz0WtmA17z99V1zxtrDWRy915jeZWR+3XY/nMqsXX
5H7u98KGL+7DPQQAfXls84pycN4Zvc/diWtysv8bPYe6eFX/Kjj7MPkd82aZqIAA
5Q+BpvzI055V9WnbAQxYMXt9gSJi1rVDfaWZJCBPnq3jwaV6PhCuxMplzCCtpPy9
pyj/D1pyJiyA723JmKRzrR9wBFEUJi9NglBhU44VCfeMzIoytpz0JZ9gsUB589VB
/cQOly0twNOuaPPZO4bmWhfPTCzobKiQzXfXRDQQmTOsepTXOoth9slpEOwWn4a/
gOo3R77jLaJ5jEDgXM++6fyA1aFw+KajYGMPDkUohWD6HkdyzDzYGBBa1ZB5v1nV
kwqRbZkP3yA/qXfI8fOASrQtySxl0jSeAEEH755TnmmrMcAjCVth9/Q+R3wVQDYm
4VAOPNboJ0DVWd/cUZxQeoAPDbIxOVncOKSsVP0RhnSLXRsDMrDjJhVAt+mK8duL
y70IF8Wp3sGo+n1iECkzNSdIcfVW9xbPhxJFV+HwgCdKGVg1Momj+1ktJ0+naSz4
ZkY/c0j5MxPy67yd1p4Z
=iQ+L
-----END PGP SIGNATURE-----
--Jx8jksmRvPacXCT5FFoc5PP9eWtutpilG--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52814D98.9050404>