HardenedBSD/release
Glen Barber 4b8175ee8f 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
..
amd64 Merge the following revisions from ^/projects/release-vmimage: 2015-01-20 23:56:04 +00:00
arm Crochet sources moved to a new home; update accordingly. 2015-03-25 22:08:02 +00:00
doc Document r279663, qsort(3) enhancements. 2015-03-16 15:54:53 +00:00
i386
pc98
picobsd do not strip /stand 2015-01-24 08:48:05 +00:00
pkg_repos
powerpc
scripts When creating VM images, copy the contents of the created filesystem into 2015-03-20 19:40:19 +00:00
sparc64
tools When building VM disk images, vm_copy_base() uses tar(1) to 2015-04-20 19:54:54 +00:00
Makefile Add 'cloudware-install' target to handle copying cloud 2015-02-24 21:06:25 +00:00
Makefile.ec2 Add code for creating an EC2 AMI. 2015-04-01 00:00:17 +00:00
Makefile.vm Add code for creating an EC2 AMI. 2015-04-01 00:00:17 +00:00
rc.local
release.conf.sample Default XZ_THREADS=0, and add to RELEASE_RMAKEFLAGS 2015-02-20 18:51:52 +00:00
release.sh Default XZ_THREADS=0, and add to RELEASE_RMAKEFLAGS 2015-02-20 18:51:52 +00:00