From owner-freebsd-arch@freebsd.org Wed Feb 7 16:36:14 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 EF093F13506 for ; Wed, 7 Feb 2018 16:36:13 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id 9170A7193F; Wed, 7 Feb 2018 16:36:13 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [10.1.38.238] (mobile-107-107-63-237.mycingular.net [107.107.63.237]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 302F72855; Wed, 7 Feb 2018 16:36:11 +0000 (UTC) Date: Wed, 07 Feb 2018 11:36:10 -0500 User-Agent: K-9 Mail for Android In-Reply-To: <3ef628a0-becd-dc4c-c3d0-efd121e841da@freebsd.org> References: <2c882f57-def0-b9f1-3c62-147cbe6bec02@metricspace.net> <3ef628a0-becd-dc4c-c3d0-efd121e841da@freebsd.org> MIME-Version: 1.0 Subject: Re: Feedback on proposed loader changes To: Julian Elischer ,Warner Losh CC: "freebsd-arch@freebsd.org" From: Eric McCorkle Message-ID: <7DD29EFF-2D94-4E14-9960-4BC47E5D922D@metricspace.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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:36:14 -0000 The keybuf system also needs a man page (that's on me as it was my inventio= n)=2E On February 7, 2018 11:30:53 AM EST, Julian Elischer wrote: >On 8/2/18 12:04 am, Warner Losh wrote: >> >> As for redoing things, I've just finished redoing ~15-years of >sys/boot >> neglect for stuff that wasn't done right the first time, so please be >> patient with my pickiness=2E >> >> Warner >the boot code in all its varying forms needs a full (re) writeup=2E >the boot(8) man page and the handbook description (chapter 12 I think) >are nowhere near complete=2E >If you are doing this work I'd ask if you can spend a few hours on=20 >that too? >That way we can follow what the new code is doing better=2E >(and don't forget examples) >Especially concentrating on changes=2E=2E --=20 Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E From owner-freebsd-arch@freebsd.org Wed Feb 7 16:40:03 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 609ADF138CB for ; Wed, 7 Feb 2018 16:40:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E4BD671B0E for ; Wed, 7 Feb 2018 16:40:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x231.google.com with SMTP id n206so2955365itg.1 for ; Wed, 07 Feb 2018 08:40:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=jZBCaCCdAohYx7cLjhQRglby6O2K+HEvw/Tfg46KWCU=; b=DCWvg41zIr0QekcOG0iQiGjdCCNFgZsgwLLfVHNjyboeAzikuisUEMksBacc2auTiC 13qkBId3VhKjR/9U6Zao9THJydMNtGNNEMFcbJsJpB1y1Zo1y7t4st6Pm7DCE4cjF3k/ j96HG2INNrAVy1oq2WGnJt7A9ab4CVDqR7N7wHoZVfA/Mm1tprBWzOAwkJq+isTtF3Nv OKUB4DuDI9AQVFPCfWrUjV37jrfgyUgil2Rxhci5fTDd/j5Y/1O4j6s0FYjiVH4jeAzV Wmf/845wlQ3UhmkzBmTvwxYalEsnnCAwN9sjrO1EJ/qBXqSVS3ttpK2usgMwtCJGXLTU ajCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=jZBCaCCdAohYx7cLjhQRglby6O2K+HEvw/Tfg46KWCU=; b=l3H2YnbCM2Hk6qkbAFIIek8GpNL7++b/nIDmGWcjl5SLMllRz+7M9zCnPngFQ9Jcsl +E2RiD/7V35Hc0bv8KER9+1034nz70G+q7bqj7cYwmy4iMso14qMrw4FlhmYJzfKRqvJ j+Z2RqVSsUJHtBX+ZFGVm0PL1tI6U7ggTJzoff6nqGe7mLZL+4BPqLqUexjBzhhWtn6E 8br3HAQUInj75Obo3SKLzkX6cTYVfJaVuEr9JZpIyulOwBtGzU6+9DoNeb3B3lBxYf7y 3hoDmjOdvTyb5ydRj3n5YmtOC08+ur+9KdeptjgVSNozPMeLZXf31KsFNRx+00m8uwB3 ezzQ== X-Gm-Message-State: APf1xPD9qMbrAx5xaOSlaqRlQ3KLLTol/boI3Ir8RIvjNOnwnshOcClf vLsg6FOql8ACk1nATB5D/5f4t5XjwgGTSDIm86JWhQ== X-Google-Smtp-Source: AH8x225gmRZcOYUjk2c+IkFmtEGuSeYTd1/e8OKC29FZEs+azjq8rG7Ee/24vAIbo+4x3iwNd+I9gnEeardBTzmljDk= X-Received: by 10.36.146.196 with SMTP id l187mr9171215itd.115.1518021602219; Wed, 07 Feb 2018 08:40:02 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Wed, 7 Feb 2018 08:40:01 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <2f744512-6ed1-eebf-7dba-ddba2786d4de@freebsd.org> References: <5015.1517478674@critter.freebsd.dk> <2f744512-6ed1-eebf-7dba-ddba2786d4de@freebsd.org> From: Warner Losh Date: Wed, 7 Feb 2018 09:40:01 -0700 X-Google-Sender-Auth: DLQF66UjvWlwUQECr192VYvldN0 Message-ID: Subject: Re: Feedback on proposed loader changes To: Julian Elischer Cc: Devin Teske , Poul-Henning Kamp , Devin Teske , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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:40:03 -0000 On Wed, Feb 7, 2018 at 9:22 AM, Julian Elischer wrote: > 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 feature= s >>>>> >>>> I >>> >>>> oulined above? And should I make the build system build multiple loade= rs >>>>> 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 perso= n >>> 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 men= u >>> 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=E2=80=99t force us to run Lua until I can code the new fea= tures >>> >>> 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=E2=80=99t 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 eas= y >> enough to have multiple versions there (loader_lua.efi and >> loader_forth.efi) and select via EFI Shell or EFI Env variables which on= e >> 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? > That's my plan. Of course, we shouldn't have a separate zfsloader and loader, but due to other limitaitons we do. At least we don't have a zfsloader.efi. Warner