Install-dev-tools doesn’t work without manual steps in a cloned boot pool (arguably the place you would want to do anything with dev-tools and then throw away).
is this a known issue?
I have found a bit of a workaround, but still having issues with certain things so not sure if there is more that needs to be done. I will test this in the normal pool if i have too…
to get install-dev-tools working i have to:
sudo zfs set readonly=off boot-pool/ROOT/clone-pool-name
sudo zfs set readonly=off boot-pool/ROOT/clone-pool-name/conf
sudo zfs set readonly=off boot-pool/ROOT/clone-pool-name/opt
sudo zfs set readonly=off boot-pool/ROOT/clone-pool-name/usr
but i continue to have weird issues after that - is this expected, is dev-tools only supported in the default original boot pool?
(and yes i know all about not running a production system with dev tools, so any of the usual folks who kneejerk that response, please move along, nothing here that will interest you)