svn commit: r264907 - in head/release: amd64 i386
gjb at FreeBSD.org
Fri Apr 25 02:26:32 UTC 2014
On Thu, Apr 24, 2014 at 07:12:10PM -0700, Nathan Whitehorn wrote:
> On 04/24/14 18:38, Glen Barber wrote:
> >Author: gjb
> >Date: Fri Apr 25 01:38:57 2014
> >New Revision: 264907
> >URL: http://svnweb.freebsd.org/changeset/base/264907
> > Refactor make-memstick.sh to avoid creating the 'dangerously
> > dedicated' partition scheme, reported to cause the memstick.img
> > to fail to boot.
> > Similar to how make-memstick.sh worked on stable/8, use makefs(8)
> > to create the actual filesystem. Then calculate the size of the
> > resulting image file, create the GPT partition scheme, then dd(1)
> > the filesystem created with makefs(8) to the freebsd-ufs GPT
> > partition.
> > This was tested on a known-working machine for regression, and
> > a known-not-working machine to ensure the boot issue has been
> > resolved.
> GPT may not be the best choice here. On a number of, in particular, Lenovo
> hardware, the BIOS will unconditionally boot with EFI from GPT media. I'm
> not sure we want to just swap the set of machines on which this will not
> boot. It probably needs to be nested MBR (or straight MBR -- I forget if
> that works) until the boot media work with EFI (which should be soon on
Noted. The thing here is that I want to get an EFI GPT partition on the
image eventually, which unless I'm missing something obvious, we cannot
mix GPT and MBR.
I don't particularly like swapping which machines boot with this hack.
Maybe it's time to do a MBR stick for "legacy" boot, and the GPT stick
for UEFI and/or "fails-to-boot-DD" case?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 834 bytes
Desc: not available
More information about the svn-src-head