On Mon, Aug 29, 2022 at 07:51:24PM +0000, Miod Vallat wrote:
> > What's the status on this diff?
>
> I'm waiting for review from at least one of the softraid suspects prior
> to putting this in, in case there are further cinematics to address.
Sounds like a good idea.
In the meantime, while converting remaining/forgotten architectures
from the manual disklabel/newfs dance to 'installboot -p', I also tested
this diff wrt. fresh installations on softraid and found no behaviour
change.
When installing to a fresh softraid volume, the disklabel UID is all
zeroes.
On macppc for example, the installer still does
disklabel $_disk 2>/dev/null | grep -q "^ i:" || disklabel -w -d $_disk
newfs -t msdos ${_disk}i
which can be replaced with
installboot -p $_disk
as for example arm64 already does.
I only have access to macppc via multi-user SSH, so I can't step through
the installer myself.
However, reconstructing the installer on softraid on vnd works with
manual disklabel/newfs as well as with installboot -p, with and without
miod's kernel race fix.
With zeroed images/disks, these tests always start out with an
all-zeroed disklabel UID on the softraid volume at the time fdisk and
newfs (directly or through installboot -p) are run.
Again, installation works on softraid with zeroed-DUIDs, with and
without miod's diff.
