#
a997b777 |
| 13-Oct-2015 |
Navdeep Parhar <np@FreeBSD.org> |
Sync up with head up to r289211.
|
#
65dcb5bc |
| 01-Oct-2015 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r288197 through r288456.
|
#
5a2b666c |
| 01-Oct-2015 |
Baptiste Daroussin <bapt@FreeBSD.org> |
Merge from head
|
#
91c42fff |
| 29-Sep-2015 |
Glen Barber <gjb@FreeBSD.org> |
In vm_copy_base(), turn off SU+J on the resultant filesystem, leaving only SU enabled.
Discussed with: kib (a few weeks ago) MFC after: 3 days Sponsored by: The FreeBSD Foundation
|
Revision tags: release/10.2.0 |
|
#
416ba5c7 |
| 22-Jun-2015 |
Navdeep Parhar <np@FreeBSD.org> |
Catch up with HEAD (r280229-r284686).
|
#
37a48d40 |
| 28-May-2015 |
Glen Barber <gjb@FreeBSD.org> |
MFH: r282615-r283655
Sponsored by: The FreeBSD Foundation
|
#
98e0ffae |
| 27-May-2015 |
Simon J. Gerraty <sjg@FreeBSD.org> |
Merge sync of head
|
#
ccbf2502 |
| 11-May-2015 |
Glen Barber <gjb@FreeBSD.org> |
Fix virtual machine disk format creating by passing VMFORMAT to mkimg(1)
PR: 200068 Submitted by: Jeremy Norris MFC after: 3 days Sponsored by: The FreeBSD Foundation
|
#
7757a1b4 |
| 03-May-2015 |
Baptiste Daroussin <bapt@FreeBSD.org> |
Merge from head
|
#
de7df74b |
| 01-May-2015 |
Glen Barber <gjb@FreeBSD.org> |
MFH: r281855-r282312
Sponsored by: The FreeBSD Foundation
|
#
26e4122a |
| 27-Apr-2015 |
Glen Barber <gjb@FreeBSD.org> |
Fix a comment.
MFC after: 3 days Sponsored by: The FreeBSD Foundation
|
#
08a75d1f |
| 23-Apr-2015 |
Glen Barber <gjb@FreeBSD.org> |
Create the arm64/aarch64 VM disk image as MBR instead of GPT scheme. UEFI needs to know the unique partition GUID with GPT, which changes each time. Specifically, the QEMU EFI BIOS file has this ha
Create the arm64/aarch64 VM disk image as MBR instead of GPT scheme. UEFI needs to know the unique partition GUID with GPT, which changes each time. Specifically, the QEMU EFI BIOS file has this hard-coded.[1]
Since the GPT labels are now unavailable, unconditionally label the root filesystem as 'rootfs' with newfs(8), since it does not hurt anything anywhere else. For the arm64 case, '/' is mounted from /dev/ufs/rootfs; for all other VM images, '/' is mounted from /dev/gpt/rootfs.
Unfortunately, since the /dev/gpt/swapfs label is also lost, set NOSWAP=1 for the arm64/aarch64 images. This is temporary, until I figure out a scalable solution to this. But, a certain piece of softare was written "very fast", and ended up living for 15 years. We can deal with this for a week or so.
Information from: andrew, emaste [1] Sponsored by: The FreeBSD Foundation
show more ...
|
#
7263c8c0 |
| 22-Apr-2015 |
Glen Barber <gjb@FreeBSD.org> |
MFH: r280643-r281852
Sponsored by: The FreeBSD Foundation
|
#
bf93ac78 |
| 21-Apr-2015 |
Glen Barber <gjb@FreeBSD.org> |
Revert r281809, which did more harm than good, and apply a more proper fix when attempting to locate the /boot files.
Sponsored by: The FreeBSD Foundation
|
#
fa569615 |
| 21-Apr-2015 |
Glen Barber <gjb@FreeBSD.org> |
Simplify variable expansion in attempt to fix the vm-image build.
Sponsored by: The FreeBSD Foundation
|
#
6b1cf1b2 |
| 21-Apr-2015 |
Glen Barber <gjb@FreeBSD.org> |
Merge the following from ^/projects/release-arm64 to allow building FreeBSD/arm64 VM images and memstick.img installation medium: r281786, r281788, r281792:
r281786: Add support for building arm6
Merge the following from ^/projects/release-arm64 to allow building FreeBSD/arm64 VM images and memstick.img installation medium: r281786, r281788, r281792:
r281786: Add support for building arm64/aarch64 virtual machine images.
r281788: Copy amd64/make-memstick.sh to arm64/make-memstick.sh for aarch64 memory stick images.
Although arm64 does not yet have USB support, the memstick image should be bootable with certain virtualization tools, such as qemu.
r281792:
Add a buildenv_setup() prototype, intended to be overridden as needed.
For example, the arm64/aarch64 build needs devel/aarch64-binutils, so buildenv_setup() in the release.conf for this architecture handles the installation of the port before buildworld/buildkernel.
Sponsored by: The FreeBSD Foundation
show more ...
|
#
6a3afe69 |
| 20-Apr-2015 |
Glen Barber <gjb@FreeBSD.org> |
Add support for building arm64/aarch64 virtual machine images.
Sponsored by: The FreeBSD Foundation
|
#
7fffcb0d |
| 20-Apr-2015 |
Glen Barber <gjb@FreeBSD.org> |
MFH: r281668 through r281783
Sponsored by: The FreeBSD Foundation
|
#
4b8175ee |
| 20-Apr-2015 |
Glen Barber <gjb@FreeBSD.org> |
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 res
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
show more ...
|
#
4bf53d0b |
| 04-Apr-2015 |
Baptiste Daroussin <bapt@FreeBSD.org> |
Merge from HEAD
|
#
dcdebabd |
| 30-Mar-2015 |
Colin Percival <cperciva@FreeBSD.org> |
Improve check for whether ${DESTDIR}/dev is mounted.
Submitted by: gcooper
|
#
96341228 |
| 30-Mar-2015 |
Colin Percival <cperciva@FreeBSD.org> |
Clean up filesystem unmounting in vmimage builds: * Remove vm_umount_base function which is currently unused. * Add umount_loop function which loops attempting to unmount one filesystem. * Replace ca
Clean up filesystem unmounting in vmimage builds: * Remove vm_umount_base function which is currently unused. * Add umount_loop function which loops attempting to unmount one filesystem. * Replace calls to umount with calls to umount_loop. * Don't attempt to unmount ${DESTDIR}/dev if it isn't mounted.
The looping is necessary because sometimes umount fails due to filesystems being busy. The most common cause of such busyness is periodic(8) jobs running `find / ...`.
Reviewed by: gjb
show more ...
|
#
e6e746bf |
| 25-Mar-2015 |
Glen Barber <gjb@FreeBSD.org> |
MFH: r278968-r280640
Sponsored by: The FreeBSD Foundation
|
#
25c11557 |
| 20-Mar-2015 |
Colin Percival <cperciva@FreeBSD.org> |
When creating VM images, copy the contents of the created filesystem into a new filesystem before packaging it into a disk image. This prevents "remnants" of deleted files from showing up in the VM
When creating VM images, copy the contents of the created filesystem into a new filesystem before packaging it into a disk image. This prevents "remnants" of deleted files from showing up in the VM images, and reduces their compressed size (by about 10% for the cloudware images) as a result.
Looks good to: gjb
show more ...
|
#
9f3d45b6 |
| 08-Feb-2015 |
Baptiste Daroussin <bapt@FreeBSD.org> |
Merge from HEAD
|