From owner-freebsd-current@freebsd.org  Thu Sep 19 17:15:36 2019
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id 07D89129112
 for <freebsd-current@mailman.nyi.freebsd.org>;
 Thu, 19 Sep 2019 17:15:36 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 46Z3QH6LRFz41lQ;
 Thu, 19 Sep 2019 17:15:35 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.92.2 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1iB01h-000FXP-17; Thu, 19 Sep 2019 19:15:29 +0200
Date: Thu, 19 Sep 2019 19:15:29 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: Michael Gmelin <grembo@freebsd.org>
Cc: freebsd-current@freebsd.org
Subject: Re: Lockdown adaX numbers to allow booting ?
Message-ID: <20190919171529.GH2863@home.opsec.eu>
References: <20190919140219.GE2863@home.opsec.eu>
 <7E0AE025-596C-457E-BC40-41217857A3CD@me.com>
 <20190919155713.GG2863@home.opsec.eu>
 <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org>
X-Rspamd-Queue-Id: 46Z3QH6LRFz41lQ
X-Spamd-Bar: -----
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [-5.99 / 15.00];
 NEURAL_HAM_MEDIUM(-0.99)[-0.991,0];
 NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.29
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, 19 Sep 2019 17:15:36 -0000

> > I've made a few more details available here:

> > https://people.freebsd.org/~pi/host/gpart.txt

> What about gpart output of the pool drives?

No gpart on the bck pool, raw drives.

> In general you would create zpools using gptids or gpt labels, not the devices, so you???re independent of device numbering. The boot loader should only be installed on drives that contain the boot pool (maybe you have old boot loaders on data drives?).

I think not, because they are used as raw drives.

Maybe that decision was an error in hindsight.

-- 
pi@opsec.eu            +49 171 3101372                    One year to go !