Date: Mon, 11 Nov 2013 15:36:30 -0600 From: Nathan Whitehorn <nwhitehorn@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: Default MBR boot "manager" Message-ID: <52814DDE.6040109@freebsd.org> In-Reply-To: <52814D98.9050404@allanjude.com> References: <33391A36-2E7A-473B-87E0-88BDE1AC97D1@fisglobal.com> <52814CD8.5020708@freebsd.org> <52814D98.9050404@allanjude.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
>>> ===================================================================
>>> --- 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.
>
We could just decide we won't support booting from ZFS on MBR. For GPT,
there is no size limit, which simplifies everything.
-Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52814DDE.6040109>