NetBSD-10_BETA gpt sysinst experience

[David Brownlee <abs%absd.org@localhost>]

This is from the Jan 7 amd64 image from nyftp, trying to install onto
a ThinkPad T430 with an existing GPT Windows 10 install, with ~165GB
of unused space

Issues marked with **

      start       size  index  contents
          0          1         PMBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34       2014         Unused
       2048     204800      1  GPT part - EFI System
     206848      32768      2  GPT part - Windows reserved
     239616  565872240      3  GPT part - Windows basic data
  566111856        400         Unused
  566112256    1058816      4  GPT part - de94bba4-06d1-4d40-a16a-bfd50179d6ac
  567171072  409602063         Unused
  976773135         32         Sec GPT table
  976773167          1         Sec GPT header

1) Selecting install > wd0 > set sizes gives a list with

a: = (Other: EFI system partition <Boo
b: + /
c: <swap>
d: /tmp (tmpfs)
...
g: = (Other: Microsoft reserved partit
h: = (Other Basic data partition)
i: = (Other: d1...

** The EFI should probably not be "a"
** Likewise having "/" as "b"
** "c" and "d" should probably be reserved and not showing up as <swap> and /tmp
** Filesystem details column is truncated with around 20 spare chars
on right (minor)

2) Selecting install > wd0 > Preconfigured wedges

Gives a fine display of the existing wedges (no way to proceed)

2) Selecting install > wd0 > Extended

** Runs into output from the system redetecting dk5 on the install
sd0, requiring a ^L to avoid a confused display. I assume the disks
are being rescanned explicitly here? maybe a "one moment..." delay
could help here? (Longer term wscons with console output elsewhere?)

after ^L display includes wd0 with
dk2 on NO NAME (MSDOS) unused 100M
dk3 (FFSv2) 16M
dk4 (MSDOS) 270G

** dk3 is definitely not FFSv2

Select wd0 and Edit partitions > Add a partition and marking is as
mount point /, install & newfs.

** Filesystem does not appear to new newfsed, or mounted, and install
attempts to write to USB image and fails

** Viewing "existing wedges" shows the new wedge with an uuid of all zeros

going back into the Extended partitioning menu shows wd0 with
dk3 on NO NAME (MSDOS) unused 100M
dk4 (FFSv2) 16M
dk5 (MSDOS) 270G
dk2 on / (FFSv2) (unused)

** Note existing ids have all switched and new dk2 is marked as "unused)

The extended partitioning menu feels a great addition since I last
used sysinst, and its close to being really nice, but .... :/

Thanks

David