From owner-freebsd-arch@freebsd.org Tue Feb 6 00:39:38 2018 Return-Path: Delivered-To: freebsd-arch@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 136ECEDC9C4 for ; Tue, 6 Feb 2018 00:39:38 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B61A86A144; Tue, 6 Feb 2018 00:39:37 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id AE9F110A8BA; Mon, 5 Feb 2018 19:39:31 -0500 (EST) From: John Baldwin To: freebsd-arch@freebsd.org Cc: Warner Losh , Devin Teske , Poul-Henning Kamp , Devin Teske Subject: Re: Feedback on proposed loader changes Date: Mon, 05 Feb 2018 16:38:31 -0800 Message-ID: <11401110.65I9PsZnfs@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Mon, 05 Feb 2018 19:39:31 -0500 (EST) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Feb 2018 00:39:38 -0000 On Thursday, February 01, 2018 10:59:14 AM Warner Losh wrote: > On Thu, Feb 1, 2018 at 9:58 AM, Devin Teske wrote: > > And as the principal author of the Forth menu since 9.0: > > > > 3. Please give me a way to run my code (at the very least until I c= an > > bring the Lua up to snuff; and if I can=E2=80=99t just let me run F= orth > > in-perpetuity). > > > > Interrupting boot1 so I can drive the system in the pre-boot Execut= ion env > > is very important to me. >=20 >=20 > For !EFI, this is relatively easy. boot1 you can type /boot/loader_fo= rth > instead of the default /boot/loader if the symlink changes and you wa= nt to > go back. >=20 > For EFI the answer is more complicated. boot1.efi is going away, so > loader.efi will move to the ESP in \efi\freebsd\loader.efi, but it's = easy > enough to have multiple versions there (loader_lua.efi and > loader_forth.efi) and select via EFI Shell or EFI Env variables which= one > you want should you need to fall back. >=20 > Does that answer your concerns? I think there is an even easier route for doing scripted loader develop= ment now: Use bhyve with bhyveload. You get to run the loader as a plain us= erland program (so you can use normal debuggers on it while it is running) whi= le being able to test all the menu features. You can even make it use the= builtin host: filesystem without requiring a disk image so you can modi= fy the lua files directly on the host that are getting pulled in for a fast edit-debug cycle. --=20 John Baldwin