In D60455#1387237, @imp wrote:

We should make *ALL* images that we produce 1M or 2M aligned.
With the exception of some fussy SoCs that boot from fixed locations at the start of the disk that we put GPT partitions to cover, there's no good reason for images the project produces to have less alignment.

[143/228] Upgrading FreeBSD-caroot from 15.1 to 16.snap20260720181726...
[143/228] Extracting FreeBSD-caroot-16.snap20260720181726: 100%
ld-elf.so.1: /usr/sbin/certctl: Undefined symbol "fts_open@FBSD_1.9"
pkg: POST-INSTALL script failed
[144/228] Upgrading FreeBSD-clibs from 15.1p4 to 16.snap20261007175931...
[144/228] Extracting FreeBSD-clibs-16.snap20261007175931: 100%

In D60450#1387239, @imp wrote:

Any reason not to add -A alignment to set this globally?

In D60450#1387074, @markj wrote:

Shouldn't this also get a man page update?

In D60451#1386952, @ziaee wrote:

So what is an optional alignment? Is that like, "make sure it begins and ends on an address which is a multiple of $1" or something else?

Sort local variables

In D60455#1386806, @jlduran wrote:

Thank you!
I remember mentioning this to the GSoC 2026 participant.

@kevans You've touched the bootstrap tools code in Makefile.inc1 recently; am I doing this right?

Alex, please tell me all the things I (and Claude) got wrong in the man page formatting. :-)

This is an extract from Christos Komis's GSoC work, with a very minor change from me (the image_file_unmap API changed to fix a bug, see D60148).

@sjg: Adding you since the commit I'm fixing is one of yours.

When you get to cloudware, my sense is that it's more likely someone will run e.g. make ec2ami-desktop-ufs rather than make cloudware-release.

Use backticks around ebsnvme

LGTM! I'm not entirely sure why I didn't do this a couple years ago. Maybe I was leaving bits in the tree so they would be visible in case of MFCs?

Not much here, just the "we shipped a release and another one is coming soon" which appears in every quarterly report. releng Let me know if anyone has anything else to add.