Page MenuHomeFreeBSD

release: Prepare EC2 cloudware images to be buildable as non-root
ClosedPublic

Authored by markj on Sep 9 2025, 2:54 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Oct 14, 6:30 AM
Unknown Object (File)
Fri, Oct 10, 3:47 AM
Unknown Object (File)
Fri, Oct 10, 3:47 AM
Unknown Object (File)
Thu, Oct 9, 10:39 PM
Unknown Object (File)
Thu, Oct 9, 10:39 PM
Unknown Object (File)
Thu, Oct 9, 7:12 PM
Unknown Object (File)
Fri, Oct 3, 9:58 AM
Unknown Object (File)
Fri, Oct 3, 5:00 AM
Subscribers

Details

Summary
  • Avoid chrooting to uninstall pkg, as it will not be installed in the first place.
  • Add metalog entries.

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
release/tools/ec2-builder.conf
59

Do we have cases where we'd add ./boot/loader.conf twice? (E.g., here and in ec2.conf)

release/tools/ec2-builder.conf
59

Yes. It can happen even more than that, e.g., vmimage.subr will add loader.conf entries if the root file system is on ZFS.

It's harmless to have duplicate entries. I suspect the right solution is to have each cloudware variant specify its modifications declaratively rather than having code which hacks up the image in various ad-hoc ways.

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