src/release/tools/basic-cloudinit.conf, branch main

release: Add /boot/loader.conf to some cloudware

2025-11-18T02:18:27Z

These were forgotten during the METALOGization process earlier. Reviewed by: markj MFC after: immediately (for 15.0-RC2) Differential Revision: https://reviews.freebsd.org/D53795

release: Create /firstboot in common VM image creation code

2025-09-11T13:05:31Z

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 be responsible for creating it. Do so in a centralized place. Aside from simplifying things, this ensures that we create a metalog entry for the firstboot file. Reviewed by: cperciva, emaste MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D52450

basic-cloudinit: remove duplicated rc.conf entry

2024-11-20T08:48:57Z

release: basic-cloudinit disable rsa key

2024-10-09T13:50:25Z

release: basic-cloudinit improve default image

2024-09-26T11:01:03Z

- Add the firstboot-freebsd-update package, as long as we do not have pkgbase, this is needed - Support SLAAC by default to complement DHCPv4 (use SYNCDHP instead) Signed-off-by: Jose Luis Duran

release: add basic cloudinit images

2024-03-18T09:58:50Z

Provide both zfs and ufs images which a 1MB partition reserved for the config drive wearing a GPT Label "config-drive" to allow consumer to know where they should push the config drive on the provided image. 2 formats available: qcow2 and raw This has been tested on OVHCloud baremetal via "bring your own image" Also tested on openstack Reviewed by: emaste Sponsored by: OVHCloud Differential Revision: https://reviews.freebsd.org/D44369