From owner-freebsd-current@freebsd.org Fri Jan 18 19:42:22 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83C8D14A9040 for ; Fri, 18 Jan 2019 19:42:22 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-zteg10011401.me.com (pv50p00im-zteg10011401.me.com [17.58.6.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 963E07054A for ; Fri, 18 Jan 2019 19:42:21 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-zteg10011401.me.com (Postfix) with ESMTPSA id A22B3900130 for ; Fri, 18 Jan 2019 19:42:19 +0000 (UTC) From: Toomas Soome Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config) Date: Fri, 18 Jan 2019 21:42:17 +0200 References: <201901181933.x0IJXfdT057018@pdx.rh.CN85.dnsmgr.net> To: FreeBSD Current In-Reply-To: <201901181933.x0IJXfdT057018@pdx.rh.CN85.dnsmgr.net> Message-Id: <96BDA1B2-32FA-4FA1-AAD1-612BC3324373@me.com> X-Mailer: Apple Mail (2.3445.102.3) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-01-18_11:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1901180142 X-Rspamd-Queue-Id: 963E07054A X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.66 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RBL_COMPOSITE_RCVD_IN_DNSWL_MED_DWL_DNSWL_LOW(0.00)[]; FREEMAIL_FROM(0.00)[me.com]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; MV_CASE(0.50)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[me.com:+]; RCVD_IN_DNSWL_MED(-0.20)[41.6.58.17.list.dnswl.org : 127.0.5.2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; MX_GOOD(-0.01)[cached: mx1.mail.icloud.com]; NEURAL_HAM_SHORT(-0.98)[-0.983,0]; RECEIVED_SPAMHAUS_PBL(0.00)[148.52.235.80.zen.spamhaus.org : 127.0.0.10]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[me.com]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[me.com:s=04042017]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_LOW(0.00)[me.com.dwl.dnswl.org : 127.0.5.1]; IP_SCORE(-1.47)[ip: (-4.40), ipnet: 17.58.0.0/20(-1.52), asn: 714(-1.36), country: US(-0.08)]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Fri, 18 Jan 2019 19:42:22 -0000 > On 18 Jan 2019, at 21:33, Rodney W. Grimes = wrote: >=20 >>=20 >>=20 >>> On 18 Jan 2019, at 19:57, Lev Serebryakov wrote: >>>=20 >>> On 18.01.2019 20:13, Warner Losh wrote: >>>=20 >>>>> Also, there are same problems with GPT/BIOS setup (which uses GPT = but >>>>> legacy boot) :-( >>>>>=20 >>>>=20 >>>> What same problems? I don't think we've touched how gptboot has = handed off >>>> to /boot/loader in a long, long time. It there's an issue here, = it's a >>>> different issue. >>> Ok, strictly speaking it is different issue with same "high-level" >>> description: pmbr/gptboot has less features than simplest oldest = boot0. >>>=20 >>> pmbr/gptbood doesn't have any way to select partition to boot from, = as >>> "boot0" has. No, setting "nextboot" from live system is not a = solution. >>> I speak about NanoBSD situation when there is tow partitions, both >>> bootable, one marked as "active" ("bootme" on GPT parlance) but it = is >>> completely broken and user need to boot from other one form very >>> beginning. This task is trivially solved by "boot0" in pure-MBR = case. >>> What about GPT/Legacy and GPT/UEFI? >>>=20 >>> --=20 >>> // Lev Serebryakov >>>=20 >>=20 >> errm.. you press a key and enter device and or loader path. if it is = not working - the code is there to be fixed. >> GPT does not have the concept of active partition. >=20 > It certainly does, it is called the attribute bootme, > and the above correctly states that. >=20 Shall you give the reference to specification?:)=20 I am very well aware about the =E2=80=9Cvendor=E2=80=9D attributes, and = I guess You can make a difference about vendor extensions and = specification=E2=80=A6 =20 And regarding to GPT attributes, I personally would avoid writing = partition table from the boot loader=E2=80=A6 rgds, toomas