From nobody Thu Dec 21 15:35:54 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SwvfJ3fc4z54w59 for ; Thu, 21 Dec 2023 15:36:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SwvfJ1wNpz3FhG for ; Thu, 21 Dec 2023 15:36:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-a22deb95d21so112212366b.3 for ; Thu, 21 Dec 2023 07:36:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1703172965; x=1703777765; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=YzGgmbbBCYy0B5pz7Bk5ilFj6uFQqD3M5gyAPfE2uvs=; b=xgcIi3CqYK1Cj65N71KwmSjJrZDWczbfYHLXUWjkxvtFFCekiLnjQgQ8wJt5W+3cGh uv2zz4m2rWrAouWPIXP4wROwYNO8mljhrBe9EFT4z7fdUCL/oR/2+Af6JGQVcLgHcSWo wbCPfNv4eMcC1BzgSagmDm9jceChsTi0RKeiScpfehS7BB5HtJEXJPsjQAK1FY5jp/4e Ph++XUV3d2YVrfVpIQffPcENE2uFHHUtb35jjUA8yqydd9oyfS/v11aMlDs25VUQbU4h ItFISuAJocnWqxYXzHXkOffPNTCeTtCaZFy9bU6gV78Lro6hKAN8l1Ts0HeTYgfvGNXr Cuow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703172965; x=1703777765; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=YzGgmbbBCYy0B5pz7Bk5ilFj6uFQqD3M5gyAPfE2uvs=; b=VBTDJtGqXC2NfceKvM4Ki2dQpwniuunjt6eri74iXeXUvpgUNhovDthVPk8/hcdodZ ZQF8xAj1aCKfTH1BBM1VMEMpSwczU6E9zUQV8bDoF0WXz/W7IemtLEH/yeZ22A3MuIqP Cx27V8t9gh1cpuh6Xmz+U+kqdTYcc9vEZ1Fq5q3S+6fvtfQs472BoaPYWxn7uTmcaJ3Q qfOJGOX9WONhfSjyswD/5OCmN5ODN7GqPUjh1z8Lj0knHbDerSM/8mb188n3h1UlrD0F XxG7+8zTAmnBTUkeICaN7y4F0eIDRmBKgjhIcgQZf0QbMhcSG5zmOPlzmV/MfI4TBkIB y/sg== X-Gm-Message-State: AOJu0YxfuFGQaff5n9w+NzeZraS8wWvVQcVIOByF0hYK5jftgN42bEFR kjfxvvYEhbkb+a8LjztySE3ZwZo+mLUydvgT6cP2ojdQWNSzJl0RsNw= X-Google-Smtp-Source: AGHT+IGl8pp8s5CkOKWBocu4iX76nbaCzmr5bPCGHlHQH2zwvKfeWKu/Av2+KBb1poEJRid0gbcY/owdMjeE1ZHB5Ms= X-Received: by 2002:a17:907:6096:b0:a26:8f29:f7d7 with SMTP id ht22-20020a170907609600b00a268f29f7d7mr2088492ejc.88.1703172965410; Thu, 21 Dec 2023 07:36:05 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Thu, 21 Dec 2023 08:35:54 -0700 Message-ID: Subject: Re: symlink to /boot/loader.efi To: Jeffrey Bouquet Cc: Nuno Teixeira , Dimitry Andric , FreeBSD CURRENT Content-Type: multipart/alternative; boundary="000000000000983806060d06db28" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4SwvfJ1wNpz3FhG --000000000000983806060d06db28 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Dec 21, 2023, 8:18=E2=80=AFAM Jeffrey Bouquet wrote: > I am wondering if all the information in this thread present and future > should be included in > the scenarios at the bottom of /usr/ports/UPDATING with technical > explanations about > how and why? AFAIK the file was created before UEFI and thus in that > regard obsolete. There is more info on updating noe on the man pages, but we likely aren't there yet. A note in UPDATING sounds like a great idea. Warner On Thu, 21 Dec 2023 12:59:54 +0000, Nuno Teixeira > wrote: > > > Hello Dimitry, > > > > For a moment I forgot that efiboot is a fat system... > > I am inspired on what installworld does to kernel and kernel.old. > > I was thinking in something like it but with efi boot, something > automatic. > > > > Thanks! > > > > Dimitry Andric escreveu no dia quinta, 21/12/2023 =C3= =A0(s) > > 12:48: > > > > > On 21 Dec 2023, at 13:22, Nuno Teixeira wrote: > > > > > > > > On every current upgrade I update efi/freebsd/loader.efi (amd64) an= d > > > efi/boot/boota64 (aarch64) with new copies on /boot/loader.efi. > > > > For safety reasons I always have a copy of last running loader by > > > appending "-old.efi" to loader or boota64 and use beinstall to get BE= s > if > > > needed. > > > > > > > > Is that possible to link, e.g., /boot/efi/efi/freebsd/loader.efi -> > > > /boot/loader.efi ? > > > > > > Symlinks do not work on FAT file systems, so I assume you mean a > symlink > > > placed in /boot (assuming that is UFS or ZFS), which points to > > > /boot/efi/efi/freebsd? > > > > > > At the moment I think installworld would not write 'through' such a > > > symlink. In fact, it makes a hard link from /boot/loader_lua.efi to > > > /boot/loader.efi, unlinking any previous /boot/loader.efi. > > > > > > That said, it would be nice to have some sort of semi-official way of > > > upgrading the real EFI loader through installworld. It would probably > > > require some top-level Makefile magic. > > > > > > -Dimitry > > > > > > > > > > -- > > Nuno Teixeira > > FreeBSD Committer (ports) > > > > --000000000000983806060d06db28 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable



On Thu, 21 Dec 2023 12:59:54 +0000, Nuno Teixeira <eduardo@freebsd.org<= /a>> wrote:

> Hello Dimitry,
>
> For a moment I forgot that efiboot is a fat system...
> I am inspired on what installworld does to kernel and kernel.old.
> I was thinking in something like it but with efi boot, something autom= atic.
>
> Thanks!
>
> Dimitry Andric <dim@freebsd.org> escreveu no dia quinta, 21/12/= 2023 =C3=A0(s)
> 12:48:
>
> > On 21 Dec 2023, at 13:22, Nuno Teixeira <eduardo@freebsd.org<= /a>> wrote:
> > >
> > > On every current upgrade I update efi/freebsd/loader.efi (am= d64) and
> > efi/boot/boota64 (aarch64) with new copies on /boot/loader.efi. > > > For safety reasons I always have a copy of last running load= er by
> > appending "-old.efi" to loader or boota64 and use beins= tall to get BEs if
> > needed.
> > >
> > > Is that possible to link, e.g., /boot/efi/efi/freebsd/loader= .efi ->
> > /boot/loader.efi ?
> >
> > Symlinks do not work on FAT file systems, so I assume you mean a = symlink
> > placed in /boot (assuming that is UFS or ZFS), which points to > > /boot/efi/efi/freebsd?
> >
> > At the moment I think installworld would not write 'through&#= 39; such a
> > symlink. In fact, it makes a hard link from /boot/loader_lua.efi = to
> > /boot/loader.efi, unlinking any previous /boot/loader.efi.
> >
> > That said, it would be nice to have some sort of semi-official wa= y of
> > upgrading the real EFI loader through installworld. It would prob= ably
> > require some top-level Makefile magic.
> >
> > -Dimitry
> >
> >
>
> --
> Nuno Teixeira
> FreeBSD Committer (ports)



--000000000000983806060d06db28--