bsdconfig can take a very long time on systems with a large number of disks. I've seen it take 30 minutes at "Probing devices". top shows that the slowdown is entirely due to CPU usage of sh, not subprocesses. Inspection shows that the `f_device_get_all` function calls `f_device_probe_geom` for every geom, which then calls `f_geom_find`, which again loops over every geom. It's a classic O(n^2) problem. We need to refactor that code to remove the extra loops.