Date: Sat, 19 Jan 2019 08:13:58 +0100 From: "O. Hartmann" <ohartmann@walstatt.org> To: Warner Losh <imp@bsdimp.com> Cc: Emmanuel Vadot <manu@bidouilliste.com>, Lev Serebryakov <lev@freebsd.org>, "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config) Message-ID: <20190119081425.64fa2d99@thor.intern.walstatt.dynvpn.de> In-Reply-To: <CANCZdfpMWuBZGJ_KjDm8EOqG7CG815aLRgRx-2RPZ1yrQPgkKg@mail.gmail.com> References: <201901181935.x0IJZ4tX057034@pdx.rh.CN85.dnsmgr.net> <49056065-1e62-f0dc-c7a4-8c358de4266e@FreeBSD.org> <20190118221013.81c8729c7bf17038e1823b52@bidouilliste.com> <CANCZdfpMWuBZGJ_KjDm8EOqG7CG815aLRgRx-2RPZ1yrQPgkKg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Am Fri, 18 Jan 2019 14:17:29 -0700 Warner Losh <imp@bsdimp.com> schrieb: > On Fri, Jan 18, 2019 at 2:11 PM Emmanuel Vadot <manu@bidouilliste.com> > wrote: > > > On Fri, 18 Jan 2019 22:50:31 +0300 > > Lev Serebryakov <lev@FreeBSD.org> wrote: > > > > > On 18.01.2019 22:35, Rodney W. Grimes wrote: > > > > > > >>> errm.. you press a key and enter device and or loader path. if it is > > not working - the code is there to be fixed. > > > >> And loader looks to "bootme" attribute and try to boot from partition > > > >> which has one, even if it is loaded from other partition itself. > > > >> > > > >>> GPT does not have the concept of active partition. > > > >> It has "bootme" / "bootonce" attributes. And [zfs]gptboot doesn't > > have > > > >> any tools to set these attributes, AFAIK. Same for UEFI boot code. > > > > > > > > The gpart(8) command is used to set/unset these. > > > gpart need booted system. NanoBSD typically have two "system" > > > partitions, "old" (previous) and "new" (current). After upgrade they > > > switched (new code is written to "previos" partition and bootable > > > atteibute is set to it, "active" in case of MBR and "bootme" in case of > > > GPT). > > > > > > If this new partition has problems and could not be booted, it is hard > > > to boot from "old" (previous) one. MBR + boot0 could (interactively) > > > change active partition before system is booted, and this problem could > > > be solved with one keypress: you select old partition on boot. > > > > > > -- > > > // Lev Serebryakov > > > > > > > With UEFI Boot* variable you could do : > > > > - Update previous partition and set BootNext to it > > - If it fail next boot will be on current partition due to BootOrder > > - If it succeed, change the BootOrder to have the new partition first. > > > > Also most UEFI BIOSes I've used (which isn't a lot) allow one to choose > which BootXXXX variable to use to boot. Some will even create new BootXXXX > variables that they use when you choose a raw device to boot from. > > There's other people that have efi programs that will pop up a menu for you > to select a particular BootXXXX to use. They then set BootNext and exit. > I've not used any of these personally. > > But this whole thread tells me we need to rewrite the boot section of our > handbook. Oh, yes, please, please! Thanks in advance! oh > > Warner > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXELOUgAKCRA4N1ZZPba5 R7PWAP9zDKuReIghEeO3UNUOPLldsjH0Zr8Ez0DVtaRt0F2WrwD/cWXjOOu5SLD2 NxHq0pKZ5oH0K7NC/4lA45j0Ir9C3wo= =Y3j1 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190119081425.64fa2d99>