Date: Mon, 11 Nov 2013 16:41:29 -0500 From: Allan Jude <freebsd@allanjude.com> To: freebsd-current@freebsd.org Subject: Re: Default MBR boot "manager" Message-ID: <52814F09.5090000@allanjude.com> In-Reply-To: <236424BC-EC62-4FDC-B9F6-E08653FF2F4B@fisglobal.com> References: <33391A36-2E7A-473B-87E0-88BDE1AC97D1@fisglobal.com> <52814CD8.5020708@freebsd.org> <236424BC-EC62-4FDC-B9F6-E08653FF2F4B@fisglobal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On 2013-11-11 16:39, Teske, Devin wrote:
> On Nov 11, 2013, at 1:32 PM, 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.
> Well, I'm sensitive to the fact that sysinstall offered "none" and
> even explained why in an F1 dialog that brought up "drives.hlp"
> to explain that you might want to keep whatever (alternate) boot
> manager you may be using already.
>
> In a proposed selector, the full breadth of options that I was
> envisioning was:
>
> GPT + gptboot
> GPT + none (use your existing boot manager... syslinux?)
> MBR + mbr
> MBR + boot0
> MBR + none (again, BYOBM)
>
> Hadn't got around to zfsboot yet. Where would that go? at the top?
>
> GPT + zfsboot ?
>
> (and of course, this is x86 specific... I was gleaning from sysinstall
> that for systems like pc98, they call it an IPL and there's only two
> options... a standard IPL or bring your own boot manager, aka "none").
>
> I imagine that there would be architectures that are like the ol' pc98,
> wherein they don't have all these options (is, for example? sparc64
> GPT only?)
for ZFS on GPT It would be /boot/gptzfsboot
/boot/zfsboot is the bits for MBR that get's DDd into the ZFS partition
--
Allan Jude
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSgU8JAAoJEJrBFpNRJZKfmWoP/jJ+YrM40E6Hq+U4I7dsbc2X
FikSxy04cS6sCAAGsoR4ceo4iiMMKsfmpEia7Q15u3dToMH8ZzpIStw4Yt1TbBb4
zQLK5qRGI+afhq2norfnMpp27Jx1sDh7ee9nngAYtt0v2aA0DkC8qexQHQeiPISi
t03Lmcl1kBJxfnaYpjjZsxGs0NifNQLBW8jCobnsudbYUxZ+4cVy3eJmKBfiLK+e
yxA2uQxH+bWLlRhglKqkmKc/HeqtrF+UpbZN0f1h0kgGnGqzJ8NAwRMBMXWJKtb0
zIssTQXg6SgCAKJ7apY3bB8T7KfcWktuCKLO0b9CmAtLoE6fcnp09Spwpw+Yqtci
RRHO4RwTFnqRHXHTsHbLZfTeGF7yFCnpJLF3zT0GW6GpZNXqMgxYlwDGcgd7elhz
pRG1UA29CQmXAVWUde/Jp4U08tprVQRfAfQTbQX42IIjOKLXg3BVl/wyGN+WMaUE
vKSyDF2FKX/akcsDiMN3ITqQ22TIlX1/O7XILu+n5ntZmlpcC3nBifAYojezWCcM
BDfEUTVXvAx8SmhX2AxiwVOVvNmpDsqcK17Fqb09iqZefu4GzQ4DEmc+/mRijaUE
iaZyxhleyZDY08DByLWXuUOGsmAVxq2TFmcBYjVOdJMD+aQvzDKwAGLGrrvKAGkA
DQl0gvLm1MTa1YvS41un
=YMzQ
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52814F09.5090000>