Page MenuHomeFreeBSD

release: Create /firstboot in common VM image code
ClosedPublic

Authored by markj on Sep 9 2025, 2:54 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Oct 15, 7:31 AM
Unknown Object (File)
Thu, Oct 9, 10:42 PM
Unknown Object (File)
Thu, Oct 9, 10:42 PM
Unknown Object (File)
Thu, Oct 9, 10:42 PM
Unknown Object (File)
Thu, Oct 9, 7:13 PM
Unknown Object (File)
Wed, Oct 8, 1:07 AM
Unknown Object (File)
Thu, Oct 2, 8:58 AM
Unknown Object (File)
Wed, Oct 1, 1:33 PM

Details

Summary

Some services, such as growfs, only run upon the first boot of an image.
The first boot is indicated by the presence of the file /firstboot,
which is unlinked after boot.

Individual cloudware types shouldn't need to create it. Do so in a
centralized place. Aside from simplifying things, this ensures that we
create a metalog entry for the firstboot file.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

markj requested review of this revision.Sep 9 2025, 2:54 PM

"which is unliked after boot." -> unlinked

LGTM modulo the typo Colin noted. It makes sense to start by centralizing this. Eventually I'd like to go even further in formalizing an image build toolkit that gets used for VM images, nanobsd, installer, etc.

This revision is now accepted and ready to land.Sep 9 2025, 4:15 PM