Date: Thu, 10 Mar 2016 20:23:51 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: Andrey Fesenko <f0andrey@gmail.com> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: EFI zfs loader and beadm? Message-ID: <alpine.BSF.2.20.1603102014210.1014@mail.fig.ol.no> In-Reply-To: <CA%2BK5SrNKtqcc79ipgx7hsRvM7n5Z-WUNDAzzeugizimTTMT_=Q@mail.gmail.com> References: <CA%2BK5SrPZ-esGHU=rggSgOFiyy4NqOWhP31rfO4S=P9=m10pEbw@mail.gmail.com> <56E045C8.1040000@vangyzen.net> <CA%2BK5SrPhwH4%2BtSHs9d=xg1mzBbojtWwXhMqFeL0MdKmAJywKTg@mail.gmail.com> <CALfReydcsb-MhaTYAwMeEkJm0QGgUsgSweUC%2BObOFKSv-G4QYw@mail.gmail.com> <CA%2BK5SrOuah4j_U_qPpnfqPo5nhSF7DKwYR63wiW85Qj0bbOiHA@mail.gmail.com> <CALfReyceEMiN7czQ9wU8oBTC706jdL9JnoED6r3g%2BhaH30J%2BQw@mail.gmail.com> <CA%2BK5SrPAhtt3cao1-i54z6dDpdFh7UXLqD7WPBs2jhYxb6EAKA@mail.gmail.com> <CALfReyfoxgzTk%2Be9EMdheE=0TCP0g_eVDr_wajyrz1AiGoPWNQ@mail.gmail.com> <CA%2BK5SrNKtqcc79ipgx7hsRvM7n5Z-WUNDAzzeugizimTTMT_=Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 10 Mar 2016 18:38+0300, Andrey Fesenko wrote: > On Thu, Mar 10, 2016 at 6:11 PM, krad <kraduk@gmail.com> wrote: > > As Eric said you cant have /boot on a separate dataset as the whole loader > > bootstrap isnt designed too look for it on the dataset defined by bootfs. > > Remember no other datasets are mounted at that stage of the bootstrap. > > > > You could maybe bodge something by manually playing around with the bootfs > > property, symlinks and rootfs variables in the loader.conf. But why would > > you want to do this? It's more work and non standard, and will break a lot? > > > > > > > > On 10 March 2016 at 12:11, Andrey Fesenko <f0andrey@gmail.com> wrote: > >> > >> On Thu, Mar 10, 2016 at 2:55 PM, krad <kraduk@gmail.com> wrote: > >> > presumably it boots now? > >> > > >> > On 10 March 2016 at 11:01, Andrey Fesenko <f0andrey@gmail.com> wrote: > >> >> > >> >> On Thu, Mar 10, 2016 at 1:49 PM, krad <kraduk@gmail.com> wrote: > >> >> > Make sure you are running the latest snapshot of current or 10.3 as > >> >> > well, as > >> >> > the MFC commits were in early February for 10-stable > >> >> > > >> >> >> > >> >> >> If remove efiwpool/ROOT/init/boot and copy his content on > >> >> >> efiwpool/ROOT/init my scheme work fine too. > >> >> >> /usr /var /home and other included in BE for consistent boot system > >> >> >> (CURRENT world may not boot with kernel other rev), and old home > >> >> >> snapshot sometimes useful for backup/restore > >> >> >> _______________________________________________ > >> >> > >> >> % uname -a > >> >> FreeBSD x220.efi.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296548: > >> >> Wed Mar 9 01:16:17 MSK 2016 > >> >> root@des.local:/usr/obj/usr/src/sys/X220 amd64 > >> > > >> > > >> > >> My current working config > >> % mount > >> .... > >> > >> This work fine, booted, beadm create new env, activate them, see boot > >> menu and select BE. > >> > >> % beadm list > >> BE Active Mountpoint Space Created > >> init - - 420.7M 2016-03-09 02:57 > >> init0 NR / 35.9G 2016-03-10 05:00 > >> > >> If i'm add separate dataset for /boot (efiwpool/ROOT/init0/boot) > >> system not booted, efi loader (first stage) see only my pool, not > >> found /boot/loader.efi > > > > > > It probably does not matter, as bootfs have snapshots (BE), just > wanted to make it more clear (having taken significant mountpoint > /boot, /usr, /var... in zfs dataset) and was surprised why the system > does not boot > > It is clear that as long as the functionality is experimental and > under development, but would like to see where the full instructions > on its implementation / restrictions, at least as early as has been > described https://wiki.freebsd.org/RootOnZFS If you keep /boot as a separate dataset/filesystem, with efiwpool/ROOT/init0/boot as the given bootfs, then boot1.efi will not see a /boot directory inside that dataset. The files and directories from /boot will be presented as living in /, the local root directory of that dataset. You could create a /boot/boot symlink pointing to . (dot), but it's better to let /boot be part of the regular boot environment, pretty similar to what you would find on a UFS system using a separate root filesystem. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-current@freebsd.org Thu Mar 10 20:16:28 2016 Return-Path: <owner-freebsd-current@freebsd.org> Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EA33ACB70C for <freebsd-current@mailman.ysv.freebsd.org>; Thu, 10 Mar 2016 20:16:28 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 41392232; Thu, 10 Mar 2016 20:16:28 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [IPv6:::1]) by freefall.freebsd.org (Postfix) with ESMTP id 39ECB1B89; Thu, 10 Mar 2016 20:16:28 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 01B7A1E811; Thu, 10 Mar 2016 20:16:28 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id THfqAhWQkiXN; Thu, 10 Mar 2016 20:16:25 +0000 (UTC) Subject: Re: sparc64 linker scripts get installed and removed during upgrade DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com 12EDC1E80B To: Kurt Lidl <lidl@pix.net>, FreeBSD-Current <freebsd-current@freebsd.org> References: <56E18E59.6090207@pix.net> From: Bryan Drewery <bdrewery@FreeBSD.org> Organization: FreeBSD Message-ID: <56E1D619.6090207@FreeBSD.org> Date: Thu, 10 Mar 2016 12:16:25 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <56E18E59.6090207@pix.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 10 Mar 2016 20:16:28 -0000 On 3/10/16 7:10 AM, Kurt Lidl wrote: > I have a sparc64 host running stable/10. > > I have noticed on the last several updates that I've > done (basic list of operations below): > checkout current stable/10 sources > make buildworld > make buildkernel > make installkernel > reboot > mergemaster -p > make installworld > mergemaster > make delete-old > > I get a bunch of sparc64 linker scripts that get installed > each time, and then are removed during the 'make delete-old' > operation. > > root@gatekeeper-372: make delete-old && make delete-old-libs > >>>> Removing old files (only deletes safe to delete libs) > remove /usr/libdata/ldscripts/elf64_sparc.x? y > remove /usr/libdata/ldscripts/elf64_sparc.xbn? y > remove /usr/libdata/ldscripts/elf64_sparc.xn? y > remove /usr/libdata/ldscripts/elf64_sparc.xr? y > remove /usr/libdata/ldscripts/elf64_sparc.xs? y > remove /usr/libdata/ldscripts/elf64_sparc.xu? y > remove /usr/libdata/ldscripts/elf64_sparc.xc? y > remove /usr/libdata/ldscripts/elf64_sparc.xsc? y > remove /usr/libdata/ldscripts/elf32_sparc.x? y > remove /usr/libdata/ldscripts/elf32_sparc.xbn? y > remove /usr/libdata/ldscripts/elf32_sparc.xn? y > remove /usr/libdata/ldscripts/elf32_sparc.xr? y > remove /usr/libdata/ldscripts/elf32_sparc.xs? y > remove /usr/libdata/ldscripts/elf32_sparc.xu? y > remove /usr/libdata/ldscripts/elf32_sparc.xc? y > remove /usr/libdata/ldscripts/elf32_sparc.xsc? y > > I would think these shouldn't be installed at all, if they > are not needed or obsolete. > This should fix it once MFC'd: https://svnweb.freebsd.org/changeset/base/296623 -- Regards, Bryan Drewery
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1603102014210.1014>