Page MenuHomeFreeBSD

nanobsd: Use NANO_NAME
Needs ReviewPublic

Authored by senguptaangshuman17_gmail.com on Aug 19 2026, 10:25 AM.
Tags
None
Referenced Files
F173805347: D58972.id184338.diff
Mon, Sep 28, 1:56 PM
F173797137: D58972.id185115.diff
Mon, Sep 28, 12:23 PM
F173769803: D58972.id184952.diff
Mon, Sep 28, 6:45 AM
F173760949: D58972.diff
Mon, Sep 28, 5:11 AM
F173757991: D58972.id184568.diff
Mon, Sep 28, 4:37 AM
F173737866: D58972.id185115.diff
Mon, Sep 28, 1:20 AM
F173724545: D58972.id184846.diff
Sun, Sep 27, 11:25 PM
F173722695: D58972.id184472.diff
Sun, Sep 27, 11:09 PM
Subscribers

Details

Reviewers
jlduran
jrm
ashish
Summary

Interpolate NANO_NAME into NANO_IMGNAME instead of hard coding the
full tag into the image name.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 76310
Build 73193: arc lint + arc unit

Event Timeline

tools/tools/nanobsd/defaults.sh
63

This will force several changes in our internal tooling...

tools/tools/nanobsd/defaults.sh
63

This will force several changes in our internal tooling...

Default NANO_NAME is still full, so NANO_IMGNAME still resolves to _.disk.full by default. Only configs that override NANO_NAME to a non-default value would see the image name and NANO_OBJ dir change, and for those the old hardcoded _.disk.full was arguably already wrong (image name not reflecting the actual variant built).