FreeBSD on AWS Graviton (t4g)
Colin Percival
cperciva at tarsnap.com
Sun Jan 3 20:42:44 UTC 2021
On 1/3/21 10:49 AM, Rafal Lukawiecki wrote:
> I wonder if I am replicating what your AMI maker does anyway by building
> things using make, or is this still the right way to go around.
This is the right approach. The AMI Builder extracts a disk image of the
release -- it doesn't do any building itself.
> I’ve one more question: where can find out the currently *available* level of
> the patches, ie. the “-p2” in "12.2-RELEASE-p2”? There is nowhere I could see
> on freebsd.org <http://freebsd.org> that publishes that, and I assume it has
> to be somewhere in the svn trees but I cannot find it. I would like a way of
> being able to check if I am current.
src/sys/conf/newvers.sh has the value you're looking for.
> My user data script, perhaps I should post it somewhere…:
> [...]
> sleep 10
> sync; sync; sync;
> umount /bits/usr/obj
> umount /mnt/src
> umount -f /mnt/dev
> sync; sync; sync;
> sleep 10
> sync; sync; sync;
> sleep 10
> umount -f /mnt
> sleep 10
> mkami "FreeBSD 12.2 PB 3.16" "Project Botticelli Ltd Customised FreeBSD 12.2"
All of the sync and sleep is unnecessary here; for that matter, the `umount
/mnt` is also unnecessary. The mkami script takes care of that. (But you do
still need to unmount anything you mounted *under* /mnt/.)
--
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
More information about the freebsd-cloud
mailing list