Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 Apr 2014 19:12:10 -0700
From:      Nathan Whitehorn <nwhitehorn@freebsd.org>
To:        Glen Barber <gjb@freebsd.org>, src-committers@freebsd.org,  svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r264907 - in head/release: amd64 i386
Message-ID:  <5359C47A.4060609@freebsd.org>
In-Reply-To: <201404250138.s3P1cvHn050580@svn.freebsd.org>
References:  <201404250138.s3P1cvHn050580@svn.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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
>
> Log:
>    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[1] for regression, and
>    a known-not-working machine[2] 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 -CURRENT).
-Nathan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5359C47A.4060609>