Does new nanobsd.sh works with non-MBR partition schemes?

[Lev Serebryakov]

 I see this in current tools/tools/nanobsd/embedded/common (lines 300
and up):

=====================
std-uefi)
	# s1 is boot, s2 is cfg, s3 is /, not sure how to make that
	# boot (marked as active) with mkimg yet
	mkimg -a 2 ${fmtarg} ${bootmbr} -s mbr \
		-p efi:=${NANO_WORLDDIR}/boot/boot1.efifat \
		-p ${s2}:=${NANO_LOG}/_.s2 \
		-p ${s3}:=${NANO_LOG}/_.s3 \
		-o ${out}
	;;
std-uefi-bios)
	# p1 is boot for uefi, p2 is boot for gpt, p3 is cfg, p4 is /
	# and p5 is alt-root (after resize)
	mkimg -a 2 ${fmtarg} ${bootmbr} -s gpt \
		-p efi:=${NANO_WORLDDIR}/boot/boot1.efifat \
		-p freebsd-boot:=${NAANO_WORLDDIR}/boot/gptboot \
		-p ${p3}:=${NANO_LOG}/_.p3 \
		-p ${p4}:=${NANO_LOG}/_.p4 \
		-o ${out}
	;;
=====================

 I don't see second root and data partitions / slices here. Also, all
these "_.{p|s}{2|3|4}" are mentioned at the end of file, but after that,
these variables (NANO_SLICE_XXX) are not used anywhere but "legacy.sh"
which contains all old code, with `newfs' & `mount', without `mkimg'

 Should it work at all? Or is it unfinished, unusable code?

-- 
// Lev Serebryakov