Set bootme GPT flag to mark "active" partition on a GPT-labelled image

[sobomax]

Summary

mkimg(1) is a fantastic tool to build all sorts of partitioned disk images, however it lacks the ability to mark GPT boot partition "active".

[marius]

usr.bin/mkimg/mkimg.1

163

It would be nice to have this list sorted alphabetically. Apart from that, this change looks good to me. Don't forget to bump .Dd when commtting, though.

[sobomax]

o sorted alphabetically;
o updated .Dd.

[marius]

usr.bin/mkimg/mkimg.1

160

Uhm, the "and" should go onto a separate line so it's not an argument to the .Ar macro and not rendered specially as expected.

[imp]

usr.bin/mkimg/gpt.c

211

One final nit... For GPT this is FreeBSD specific. The GPT standard just sets these bits aside for the OS to do what it wants... Linux, windows and MacOS all ignore it.
A small comment to this effect would be good.

[sobomax]

looks unnecessary.

usr.bin/mkimg/gpt.c

211

Hmm, yet Windows at least sets those bits when installing itself:

$ sudo parted /dev/nvme0n1 print
Model: INTEL SSDPEKNW512G8 (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 525MB 524MB fat32 EFI system partition boot, esp, no_automount
2 525MB 660MB 134MB Microsoft reserved partition msftres, no_automount
3 660MB 151GB 150GB ntfs Basic data partition msftdata

[imp]

usr.bin/mkimg/gpt.c

211

Are you sure? They aren't in the GPT/UEFI standard.

'boot' flag for parted has the value of '1' and is generated within parted. while the bootme flag for FreeBSD has a value of (1ULL << 59) and is definitely outside of the standard flags.