installer - Add hammer2 support to the installer

* hammer2 can now be selected as a filesystem in the installer.

* Note that we still for /boot to use UFS. The boot loader *CAN*
access a hammer2

installer - Add hammer2 support to the installer

* hammer2 can now be selected as a filesystem in the installer.

* Note that we still for /boot to use UFS. The boot loader *CAN*
access a hammer2 /boot, but the small size of the filesystem makes
it too easy to fill up when doing installkernel or installworld.

* Also fix a minor bug in the installer. when issuing a 'dumpon device'
be sure to first issue a 'dumpon off' to avoid dumpon complaints about
a dump device already being specified.

show more ...

installer: Fix the "missing /var/run/sem" issues better.

* Add -C to the tmpfs mount of /var/run on the USB image. This
ensures that the USB image itself keeps the ppp/, sem/, and
wpa_supplicant

installer: Fix the "missing /var/run/sem" issues better.

* Add -C to the tmpfs mount of /var/run on the USB image. This
ensures that the USB image itself keeps the ppp/, sem/, and
wpa_supplicant/ dirs under /var/run.

* Since we do not cpdup /var/run explicitly during installation
it ends up empty on the installed system. Ensure that it has
the subdirectories it needs by running mtree on /var.

* It looks like the 1e5a476188185cf1161f4fe3ffc060465562ef0d
change could be reverted because the issue never was that
/var/run/sem wasn't existing _after_ make upgrade. The mtree
in the preceding installworld takes care of it. It doesn't
hurt either, so just shuffle the commands a bit downwards.

show more ...

installer: Add basic UEFI system setup.

GPT partition 0 is a 128MB FAT32 EFI system partition. Microsoft
recommends at least 100MB and FAT32 in [1]. Partition 1 is a
"DragonFly Label64" (aka "dragon

installer: Add basic UEFI system setup.

GPT partition 0 is a 128MB FAT32 EFI system partition. Microsoft
recommends at least 100MB and FAT32 in [1]. Partition 1 is a
"DragonFly Label64" (aka "dragonfly" in gpt(8)) for the rest of
the disk. It is analogous to slice 1 in our MBR setup, and has the
same name, e.g. /dev/da0s1. The rest of the UEFI setup is identical
to an MBR setup. disklabel64, newfs*, and so forth.

We currently only support installing DragonFly to the whole disk
in UEFI mode, and we don't set any NVRAM EFI variables during
installation, so for now we are copying our stage 1 loader to
\EFI\BOOT\BOOTX64.EFI on the EFI system partition.

Also, there isn't any support for Secure Boot.

[1] https://technet.microsoft.com/en-us/library/hh824839.aspx#DiskPartitionRules

show more ...