From owner-freebsd-current@FreeBSD.ORG Tue Nov 12 01:40:26 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 ESMTPS id 28B346E9 for ; Tue, 12 Nov 2013 01:40:26 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4615926F2 for ; Tue, 12 Nov 2013 00:24:54 +0000 (UTC) Received: from julian-mbp3.pixel8networks.com (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id rAC0Or0H072218 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 11 Nov 2013 16:24:54 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <5281755A.3090301@freebsd.org> Date: Mon, 11 Nov 2013 16:24:58 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; 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> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.16 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: Tue, 12 Nov 2013 01:40:26 -0000 On 11/11/13, 1:36 PM, 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 >>>> =================================================================== >>>> --- 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. >> for mbr/zfs , just declare a zfs-boot slice type, and put it in there sure it complicates it a bit but it is basically what happens in gpt right? > > 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" >