Page MenuHomeFreeBSD

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

Authored by markj on Tue, Sep 9, 2:54 PM.
Tags
None
Referenced Files
F130294344: D52452.id161791.diff
Sun, Sep 28, 3:08 AM
F130257511: D52452.diff
Sat, Sep 27, 8:04 PM
Unknown Object (File)
Wed, Sep 24, 11:04 AM
Unknown Object (File)
Tue, Sep 23, 5:38 PM
Unknown Object (File)
Wed, Sep 17, 11:31 AM
Unknown Object (File)
Wed, Sep 17, 11:05 AM
Unknown Object (File)
Wed, Sep 10, 7:47 AM
Unknown Object (File)
Tue, Sep 9, 9:10 PM
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.Tue, Sep 9, 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.Tue, Sep 9, 7:46 PM