gjb d772346661 When building VM disk images, vm_copy_base() uses tar(1) to ... copy the userland from one md(4)-mounted filesystem to a clean filesystem to prevent remnants of files that were added and removed from resulting in an unclean filesystem. When newfs(8) creates the first filesystem with journaled soft-updates enabled, the /.sujournal file in the new filesystem cannot be overwritten by the /.sujournal in the original filesystem. To avoid this particular error case, do not enable journaled soft-updates when creating the md(4)-backed filesystems, and instead use tunefs(8) to enable journaled soft-updates after the new filesystem is populated in vm_copy_base(). While here, fix a long standing bug where the build environment /boot files were used by mkimg(1) when creating the VM disk images by using the files in .OBJDIR. MFC after: 3 days Sponsored by: The FreeBSD Foundation		2015-04-20 19:54:54 +00:00
..
arm	Sigh. s/AutoSize/Growfs/ following upstream commit r761.	2015-03-30 19:08:37 +00:00
azure.conf	Remove vm_extra_install_base() for the Azure image, now	2015-01-16 15:37:07 +00:00
ec2.conf	It would help if I committed the right patch...	2015-03-31 04:35:35 +00:00
gce-package.sh	Add a CLOUDPACKAGE variable to contain a list of targets for	2015-02-24 22:27:02 +00:00
gce.conf	Partially revert r278118 now that the required logic for deciding whether	2015-03-31 01:44:29 +00:00
openstack.conf	Merge the following revisions from ^/projects/release-vmimage:	2015-01-20 23:56:04 +00:00
vmimage.subr	When building VM disk images, vm_copy_base() uses tar(1) to	2015-04-20 19:54:54 +00:00