From owner-freebsd-stable@FreeBSD.ORG Wed Oct 1 16:54:54 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 41E893D2; Wed, 1 Oct 2014 16:54:54 +0000 (UTC) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 08EF83D1; Wed, 1 Oct 2014 16:54:53 +0000 (UTC) Received: by mail-ig0-f178.google.com with SMTP id l13so730042iga.11 for ; Wed, 01 Oct 2014 09:54:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=bZK25mc7NtSICfnfzG7rk6ZHmr4D5XM+X9Oh67xJnHg=; b=FB78DrXPz6tnkHse1RkUDAO9n4i//g0QxJZWOTpBq8rX94+vjTFK0ut6knYwqCAXWe ZJ0dntnpepaljF/fQxFrSayO9wuXiS3WYMk9cnZ8k0tWCTEmMO0PRTfmndjnvsLXXKKR gbSWYco3YvmQtw9qXdffFhMr/STnor+YpcHj+8t2I2g2aBgneTI4sPjJuM4vNTKD2KC7 QVyOJUV2GUoi4mw+n5W27/FMpGv+tzC9v1AzQB8tZDWhuI2HoE5BG79nn37KNRFlRR4Y wnkFFGDQpb4Pk6mbEVBoBwYkZT7MrF343JlwS2XlxxvjQH9BHXrwybdgSlAtV9r/oL0u SD/A== X-Received: by 10.50.41.8 with SMTP id b8mr21739268igl.11.1412182493531; Wed, 01 Oct 2014 09:54:53 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.44.196 with HTTP; Wed, 1 Oct 2014 09:54:33 -0700 (PDT) In-Reply-To: <20141001143754.GF1275@hub.FreeBSD.org> References: <201410011358.s91DwOXJ033137@fire.js.berklix.net> <20141001143754.GF1275@hub.FreeBSD.org> From: Ed Maste Date: Wed, 1 Oct 2014 12:54:33 -0400 X-Google-Sender-Auth: viU_Mq3QpJOIrhC1NQbky59YZA8 Message-ID: Subject: Re: Media image names - Document & rationalise. To: Glen Barber Content-Type: text/plain; charset=UTF-8 Cc: "Julian H. Stacey" , freebsd-stable stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2014 16:54:54 -0000 On 1 October 2014 10:37, Glen Barber wrote: > On Wed, Oct 01, 2014 at 03:58:24PM +0200, Julian H. Stacey wrote: >> Maybe there was an explanation of -uefi- on a mail list. One can >> guess: for [some?] newer machines try uefi. But could we put a more >> exact purpose of uefi images in a README ? >> > > The UEFI images will be documented in the release announcement email, > because they are specific to the 10.1-RELEASE cycle. 11.0-RELEASE will > have the functionality in the default installation medium. To be clear, the existing, legacy-only images are built the same way as they always have been. The reason there are separate -uefi- images is to avoid accidental regression in legacy-only boot support. The 10.1 -uefi- images (as well as the 11.0 images) are actually dual-mode, and should boot in both UEFI and legacy configurations. I'm interested in receiving test reports of installations using the -uefi- images, in both UEFI and legacy boot configurations. (Technical detail: The image contains legacy MBR boot code, and is partitioned using the MBR scheme. One of the MBR partitions is an EFI system partition of type 0xEF. Legacy boot uses the MBR, while UEFI loads the first-stage loader /EFI/BOOT/BOOTX64.EFI. Both cases use the same root file system and boot the same kernel.)