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> In-Reply-To: <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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 !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190919171529.GH2863>