From owner-freebsd-current@freebsd.org Fri Mar 11 07:52:10 2016 Return-Path: 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 63666ACB098; Fri, 11 Mar 2016 07:52:10 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 DFDFAA70; Fri, 11 Mar 2016 07:52:09 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id l68so6495234wml.1; Thu, 10 Mar 2016 23:52:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=FWdOLhjCF/oVZDYnZTJPH0R1onxzRoA9K/o1KdDp22w=; b=JxPXlpkAAYYOEeq7dQVye40Ed6V6PvqH4jQYDTnj4Cxst3MxEMu5/j+GP+X4qUKijf ngFhbj3528u76U4X63TdpfJJ6mxZKBHhHyO5he9IU7llOH3arfC4Tyn9SP2MtVH3GUZ3 q2A8BQTIAsWqqUUYRiHknL+R1bgENJQwoQQQwrGq4HzLqCGFfdn6SF0olv5uYE8ZDtzK qnG13RMyGt81Q0rb/TpMwVaG7VKbu50/N86y8A5d7OeQZ29i+haKAJ9TRuEJjLdHGwIK 9t7qVPcR28ievxG2m+Gj3OP2HP4WfBmOfTsd5JBu64LmBwIngFYmTZ0ob7MyzjH12pFp Ri1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=FWdOLhjCF/oVZDYnZTJPH0R1onxzRoA9K/o1KdDp22w=; b=S4kgp8E+aEx/lI6UItPvnoBRXk1nBStsibvMr0d+bBgh4eqj5RbNWWm5kIAV3DPBZ3 s5uEDobt2gLgcxbgVFEmHFvYPOdCYorJ1WJ/4D6w3P8CXGk+5DBiuNW7h8HONS8Ixhbd zbb3qf+EvyZaKWcQ1dVjgwbJPdLCNri27JzAIN+TC1vhsCU7wdgbOYdRXMNrTOmoFOMO Wmjn0N7EX4h+CKRHpKFgaSbrVN+FM+DRq6b7THWLGV1DLwpZx5ckiwxJPjn4br+KdPI8 iAuP05HYfdUBsjEoF1BCO4VqVNfpnnGJpXaGa0E7l/CwCD/KYt05brp5N3cFKDjD6PIL rjbA== X-Gm-Message-State: AD7BkJIp6uX5lD5+L3WHub8Mh22V/AIabnUMB9OmGr2s0hySqDBTR1w8FYZZQAiKNRtMA9GcKmRTbAIQzNDAwQ== MIME-Version: 1.0 X-Received: by 10.28.12.80 with SMTP id 77mr1251282wmm.19.1457682728173; Thu, 10 Mar 2016 23:52:08 -0800 (PST) Received: by 10.28.31.143 with HTTP; Thu, 10 Mar 2016 23:52:08 -0800 (PST) In-Reply-To: References: <56E045C8.1040000@vangyzen.net> Date: Fri, 11 Mar 2016 07:52:08 +0000 Message-ID: Subject: Re: EFI zfs loader and beadm? From: krad To: =?UTF-8?Q?Trond_Endrest=C3=B8l?= Cc: Andrey Fesenko , "freebsd-hackers@freebsd.org" , freebsd-current X-Mailman-Approved-At: Fri, 11 Mar 2016 12:29:42 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 07:52:10 -0000 Its also worth pointing that if you decouple the userland from the kernel files you no longer have a boot environment, as all the basic stuff to boot the os isn't contained within the bootfs. I'm still struggling to see why /boot needs to be on a different dataset, its just a bit of a linuxism. On 10 March 2016 at 19:23, Trond Endrest=C3=B8l < Trond.Endrestol@fagskolen.gjovik.no> wrote: > On Thu, 10 Mar 2016 18:38+0300, Andrey Fesenko wrote: > > > On Thu, Mar 10, 2016 at 6:11 PM, krad 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 wrote: > > >> > > >> On Thu, Mar 10, 2016 at 2:55 PM, krad wrote: > > >> > presumably it boots now? > > >> > > > >> > On 10 March 2016 at 11:01, Andrey Fesenko > wrote: > > >> >> > > >> >> On Thu, Mar 10, 2016 at 1:49 PM, krad 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 boo= t > > >> 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=C3=B8l, | Trond Endrest=C3=B8l, = | > | IT-ansvarlig, | System administrator, | > | Fagskolen Innlandet, | Gj=C3=B8vik Technical College, Norway, = | > | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | > | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | > +-------------------------------+------------------------------------+ > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " >