From owner-freebsd-stable@freebsd.org Tue Apr 5 22:44:05 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 58D48B03A44 for ; Tue, 5 Apr 2016 22:44:05 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 175F31A97 for ; Tue, 5 Apr 2016 22:44:04 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x22d.google.com with SMTP id v188so4097819wme.1 for ; Tue, 05 Apr 2016 15:44:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=aw/dmbLg93mvrZUBPeSXkeqfmvtoouPh3sZZlHPRKPs=; b=KOS7bP6g+OCd0+vYeb9qFadc2GhmSAhbM2/iU15BqWJ1sQLU+eLTpFAC2Fi+HA2Sj7 Ao8qZhQ+ZSU1E55IuqA8uF6T3JtNPCZGQNy9TQAkFKebV9x4Ca3z9gcrCE4rvk44F5JD CdApCv5e7z6Ltg5gF05Mmf3WV5GESOiawtk5rSZ802zrbCVdVO2NQp2/4mMhmXA0bXys VUMSCpFVTMAH9wOmp8u6XMf5EzDBql9iueaBH3FM0PF7DeHj0RzrJQHhVAcBGbC1X20l Zmn9F1I3uCgwY61j9Z1H6YaNSoUjY75rg1mRy5we9VeFuntfg3pduIIX8U28fyPDKRJL 0hIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=aw/dmbLg93mvrZUBPeSXkeqfmvtoouPh3sZZlHPRKPs=; b=LzMKuvneY2y/+5Q+Xr9MFUCqEg0TX3B7SKBc3gAIM5LJtm7iNqZqItTzKHjKRLya8j tPHgw8+uoJUVwjHYIDvc0XseDRKVvGjkkpWLwrTW8krIpIHkbVviwh3Xs6juBBT5Ewak hLPWGCfYy+fe/iUprepvkewffv1umgc5QmfDM9vB1DVjmBSW94YluNjHvRitjWDfV70Q dtPpuJVMN6+wBddeAVTAYy+S25jDh1t6M94zuR1XJG7wT6gOnMUqu53y+VyDb/NrEYJs ny8Z/NjVKHLcK/PDvOnSc1bRCXqW3Wt8u3ESy/sKxqf38NqMAlat7DYgh3Y9l2vKFZqF fEKQ== X-Gm-Message-State: AD7BkJJ/WO0ti4XZVGO4SygKlExM2b+QZ4tS4WegQo24jZEE1/M+SSrG0Q2CO9HUXaChD8vA X-Received: by 10.28.46.193 with SMTP id u184mr20746307wmu.95.1459896243104; Tue, 05 Apr 2016 15:44:03 -0700 (PDT) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id c125sm351472wme.6.2016.04.05.15.44.01 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 05 Apr 2016 15:44:02 -0700 (PDT) Subject: Re: A gpart(8) mystery on 10.3-RELEASE To: Warren Block References: <5703B0D5.5060701@passap.ru> <57042EE2.9030304@multiplay.co.uk> Cc: freebsd-stable@freebsd.org From: Steven Hartland Message-ID: <57043FB5.7020505@multiplay.co.uk> Date: Tue, 5 Apr 2016 23:44:05 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 22:44:05 -0000 On 05/04/2016 23:09, Warren Block wrote: > On Tue, 5 Apr 2016, Steven Hartland wrote: >> On 05/04/2016 20:48, Warren Block wrote: > >>> Actually, the more I think about it, using bootcode -p to write the >>> entire EFI partition seems dangerous. Unless it is surprisingly >>> smart, it will wipe out any existing stuff on that EFI partition, >>> which could be any number of important things put there by other >>> utilities or operating systems, including device drivers. >>> >>> The safer way is to mount that partition and copy the boot1.efi file >>> to it. > >> Pretty sure that's not done as you cant guarantee fat support is >> available. > > In the kernel, you mean? True. But odds are good that someone with a > custom kernel without msdosfs will understand the implications of > overwriting the EFI partition. > > And of course it is safe to create an EFI partition, it would only be > a problem if one already existed with some extra files on it. Yes, we remove msdosfs here and it would be PITA to have to add it back in just to support writing EFI boot fs. So personally I much prefer the current method. For those that want to play with the EFI partition then they can do the manual update step instead easily enough. Regards Steve