installer: Remove the long-time broken package handling code.

installer(8): Fix building with -fno-common.

-fno-common will be default in future compilers (GCC 10, for example).

installer - Default to HAMMER2 (2)

* Fix comments.

Reported-by: noob237

installer - Default to HAMMER2

* Change the installer default from HAMMER1 to HAMMER2.

* Adjust the nrelease build to print the location of the image files
when it finishes.

disklabel64 - Make disktype optional, fix alignment bug

* Make the disktype optional, use 'auto' automatically

* Fix a bug in the kernel's l64_makevirginlabel() calculation.
It was not properly c

disklabel64 - Make disktype optional, fix alignment bug

* Make the disktype optional, use 'auto' automatically

* Fix a bug in the kernel's l64_makevirginlabel() calculation.
It was not properly calculating the alignment relative to
the physical disk.

* Refactor some of the documentation

* Refactor examples

Submitted-by: Aaron LI <aly@aaronly.me>

show more ...

installer - Avoid endless loop for UEFI installations

- While doing an UEFI installation after selecting the disk if the dialog
to write changes to the disk is cancelled there was no way to get ba

installer - Avoid endless loop for UEFI installations

- While doing an UEFI installation after selecting the disk if the dialog
to write changes to the disk is cancelled there was no way to get back
to the previous screen.
- Fix it by going to the select disk state.

show more ...

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 ...

install - Fix a few issues

* sleep 1 second before [re]surveying drives to give devfs time to
[re]probe the drive.

* fn_subpart_hammer was apparently trying to check the capacity of the
current

install - Fix a few issues

* sleep 1 second before [re]surveying drives to give devfs time to
[re]probe the drive.

* fn_subpart_hammer was apparently trying to check the capacity of the
current slice when there is no current slice. Check the disk capacity
instead.

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 ...

installer - Allow to specify cmdnames file path

installer - Use bit 'flags' for additional options

- Use a flags field to i_fn_args struct instead of single
int fields to specify different options.
- No functional change

installer: Remove pnpinfo configuration option.

pnpinfo(8) is i386 only. Also, it's easy enough to review it by logging
in as root.

Suggested-by: ftigeot

installer: Always take the root directory's /dev.

Taking /dev relative to the directory we want to copy from was fine
until we got devfs, because we shipped actual device nodes in /dev
until then.

installer: Always take the root directory's /dev.

Taking /dev relative to the directory we want to copy from was fine
until we got devfs, because we shipped actual device nodes in /dev
until then.

It only continued working because the directory we copy from is always
the distribution media's root directory currently.

show more ...

Remove some unneeded semicolons across the tree.

installer: Remove some unused variables.

Found-by: gcc47

installer: Don't say the installer is experimental.

Noticed-by: vsrinivas

Fix various whitespace and indent issues (no functional change).

Initial import of binutils 2.22 on the new vendor branch

Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.

installer: Add serial number and /etc/devtab support.

If a disk has a corresponding entry in /dev/serno with identical
major/minor, use that for all further references of the disk in the
installatio

installer: Add serial number and /etc/devtab support.

If a disk has a corresponding entry in /dev/serno with identical
major/minor, use that for all further references of the disk in the
installation process.

In the installed system, set up a /etc/devtab entry (with the labels
named disk0, disk1 etc. using the order of the disks appearing in
'sysctl kern.disks' output) and use this label for the system's
/etc/fstab entries.

/boot/loader.conf still has to use /dev/serno for its vfs.root.mountfrom
entry.

The dumpdev entry in /etc/rc.conf could use the devtab label but (as
of this commit) doesn't do so yet. This will be fixed at a later point.

If no /dev/serno is found, or if no corresponding entry in /dev/serno
is found for a specific disk, we use the traditional scheme.

While I'm here, perform some cleanup, namely remove some duplicate
functions.

Requested-by-and-in-discussion-with: dillon

show more ...

installer: Enable writing to the disk label area prior to wiping it.

While here, move the few lines of fn_create_subpartitions() to flow.c.

Suggested-by: dillon
Reported-by: <elekktretterr@exema

installer: Enable writing to the disk label area prior to wiping it.

While here, move the few lines of fn_create_subpartitions() to flow.c.

Suggested-by: dillon
Reported-by: <elekktretterr@exemail.com.au>
Dragonfly-bug: <http://bugs.dragonflybsd.org/issue1461>

show more ...

installer: Move the installer from contrib/ to usr.sbin/.

Fix trailing whitespace while I'm doing it.

installer: For bootblocks, only offer the disk that was installed to.

In the "Disk Utilities" menu, we still offer all disks.

Requested-by: dillon

installer: Remove /dev/mapper/* mappings where necessary.

installer: Slightly change the item order in the configure menu.

Move the "Set keyboard map" item before the "Set root password" item
in order to prevent accidental foot-shooting.

Submitted-by: mat

installer: Slightly change the item order in the configure menu.

Move the "Set keyboard map" item before the "Set root password" item
in order to prevent accidental foot-shooting.

Submitted-by: matthias

show more ...

installer: Utilize dumpon(8) and swapoff(8) to turn off dump and swap.

Previously, the installer would block further installation attempts
once a swap was mounted. This was very inconvenient, e.g. w

installer: Utilize dumpon(8) and swapoff(8) to turn off dump and swap.

Previously, the installer would block further installation attempts
once a swap was mounted. This was very inconvenient, e.g. when trying
to do multiple installs in one session.

It also never issued a 'dumpon off' causing dumping to be enabled
until rebooting. This caused issues upon reboot when a removable disk
(eSATA, for example) was unplugged before the reboot.

Now that we have swapoff(8), fix all these issues by turning off
dumping and swapping once the installation is completed (after
unmounting). Also, do this in a number of other places (where we
previously warned) to make sure it all gets deactivated again should
the user have cancelled a previous installation.

show more ...