Date: Mon, 16 Jul 2018 23:46:10 +0300 From: Lev Serebryakov <lev@FreeBSD.org> To: freebsd-embedded@freebsd.org Cc: imp@FreeBSD.org Subject: Does new nanobsd.sh works with non-MBR partition schemes? Message-ID: <5e73338b-4d0b-7efe-1d06-4cdcf9437ffe@FreeBSD.org>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5e73338b-4d0b-7efe-1d06-4cdcf9437ffe>