From owner-freebsd-arch@freebsd.org Wed Feb 7 16:22:36 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 C2992F125A2 for ; Wed, 7 Feb 2018 16:22:36 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6AFB170BD3; Wed, 7 Feb 2018 16:22:36 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (220-253-149-130.dyn.iinet.net.au [220.253.149.130]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id w17GMTMd070380 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 7 Feb 2018 08:22:32 -0800 (PST) (envelope-from julian@freebsd.org) Subject: Re: Feedback on proposed loader changes To: Warner Losh , Devin Teske Cc: Poul-Henning Kamp , Devin Teske , "freebsd-arch@freebsd.org" References: <5015.1517478674@critter.freebsd.dk> From: Julian Elischer Message-ID: <2f744512-6ed1-eebf-7dba-ddba2786d4de@freebsd.org> Date: Thu, 8 Feb 2018 00:22:23 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US 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: Wed, 07 Feb 2018 16:22:37 -0000 On 2/2/18 1:59 am, Warner Losh wrote: > On Thu, Feb 1, 2018 at 9:58 AM, Devin Teske wrote: > >> >>> On Feb 1, 2018, at 1:51 AM, Poul-Henning Kamp >> wrote: >>> -------- >>> In message > n3ESiUw@mail.gmail.com>, Warner Losh writes: >>>> So I'd like feedback on two questions: Should I kill the forth features >> I >>>> oulined above? And should I make the build system build multiple loaders >>>> with a link controlling the default? >>> I think you should just move forward and go for the end-stage >>> without too many temporary bandaids. >>> >>> The loader is pretty decoupled from everything, so in case anybody >>> needs any of these Forth cornercases, they can use 11.X loader with >>> very little, if any, trouble. >>> >> As a person that both reviewed the GSoC code you are working with >> (in-depth; including a list of short-comings) and the most likely person to >> bring it up-to-par after it is committed, I have 2 opinions: >> >> 1. Please allow both boot systems for a while so that the lua-based menu >> can be made as feature full as the Forth menu. Example: submenus were added >> in Forth long after the GSoC lua project had ended >> > OK. The plan outlined does that. The lua code will be installed into /boot. > But it will be .lua, so no conflicts with .4th. And we start from > loader.lua not loader.rc. > > >> 2. Please don’t force us to run Lua until I can code the new features >> > OK > > >> 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 can >> bring the Lua up to snuff; and if I can’t just let me run Forth >> in-perpetuity). >> >> Interrupting boot1 so I can drive the system in the pre-boot Execution env >> is very important to me. > > For !EFI, this is relatively easy. boot1 you can type /boot/loader_forth > instead of the default /boot/loader if the symlink changes and you want to > go back. > > 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. so, there are multiple loaders.   zfsloader and loader for example. how does this fit into the picture you are drawing? a symlink for each? > > Does that answer your concerns? > > Warner > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > >