From owner-freebsd-current@freebsd.org  Mon Aug 27 18:50:43 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 E4CA61093394
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon, 27 Aug 2018 18:50:42 +0000 (UTC)
 (envelope-from pete@nomadlogic.org)
Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org
 [IPv6:2607:f2f8:a098::2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6CA597E674
 for <freebsd-current@freebsd.org>; Mon, 27 Aug 2018 18:50:41 +0000 (UTC)
 (envelope-from pete@nomadlogic.org)
Received: from [192.168.1.106] (cpe-76-175-75-27.socal.res.rr.com
 [76.175.75.27])
 by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 30213ff6
 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO
 for <freebsd-current@freebsd.org>;
 Mon, 27 Aug 2018 11:50:39 -0700 (PDT)
To: FreeBSD Current <freebsd-current@freebsd.org>
From: Pete Wright <pete@nomadlogic.org>
Subject: beadm vs bectl
Message-ID: <1c247846-cdd1-fa49-9033-95b7ff660a60@nomadlogic.org>
Date: Mon, 27 Aug 2018 11:50:35 -0700
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101
 Thunderbird/60.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.27
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: Mon, 27 Aug 2018 18:50:43 -0000

hi there - i have a zfs based system where /boot is on its own pool.  
beadm seems happy enough with this setup but bectl errors out like so:

$ sudo bectl list
/ and /boot not on same device, quitting
$

$ beadm list
BE                 Active Mountpoint  Space Created
default            NR     /           47.6G 2018-03-02 20:30
snapshot_02262018  -      -            1.5G 2018-03-03 14:38
badresume_05122018 -      -            4.4G 2018-05-12 19:45
11_2_beta          -      -            2.6G 2018-05-13 18:26
resume_works       -      -           12.6G 2018-06-01 16:45
$

reading the manpage for bectl it doesn't mention this being an issue.  
so i guess i have two questions:
1) is it a bad thing(tm) to have /boot on its own pool?
2) assuming that having /boot on its  own pool, why does bectl not work 
with this configuration?

thanks!
-pete

-- 
Pete Wright
pete@nomadlogic.org
@nomadlogicLA