installer(8): Move the contents of sysids.h into <sys/diskmbr.h>.

It is needed by both fdisk(8) and the installer.

<sys/diskmbr.h> seems reasonable because it already has defines for
various partit

installer(8): Move the contents of sysids.h into <sys/diskmbr.h>.

It is needed by both fdisk(8) and the installer.

<sys/diskmbr.h> seems reasonable because it already has defines for
various partition types. Use them in the struct. Adjust the naming of
the structure and the array to match the rest of <sys/diskmbr.h>.

Based on a patch by Alexander Kuleshov <kuleshovmail@gmail.com>.

Dragonfly-bug: <https://bugs.dragonflybsd.org/issues/2875>

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: Change fn_mapper_name() to subpartition_get_mapper_name().

Similar to subpartition_get_device_name(). It also helps cleaning up
long lines.

installer - use a more modern mount setup for UFS and HAMMER.

* Rewrite a large chunk of the disklabeling and mount point code.
UFS now gains a separate /boot partition, avoiding issues with
the

installer - use a more modern mount setup for UFS and HAMMER.

* Rewrite a large chunk of the disklabeling and mount point code.
UFS now gains a separate /boot partition, avoiding issues with
the boot loader if the user desires to install a large UFS root on
a drive.

* Normalize the mount mechanics for both UFS and HAMMER. Instead of
using PFSs on HAMMER, we create two large partitions by default:
One is the root partition, the other is /build.

The /build partition holds major elements of the system which would
normally not have to be backed up:

/var/tmp (from /build/var.tmp)
/var/cache (from /build/var.cache)
/var/crash (from /build/var.crash)
/var/spool (from /build/var.spool)
/var/log (from /build/var.log)
/usr/obj (from /build/usr.obj)

The root partition holds all remaining major directories, including the
base /var.

There are several reasons for this. Generally speaking, stuff in /home,
/usr and most of the stuff in /var is critical to system operation and
user happiness, and it makes little sense to separate it out from the root
mount.

We pick-out the less critical directories and place them on /build,
using NULL mounts to mount them in their expected locations.

* Users can easily make adjustments post-install without having to mess
around with PFSs, and can make simple adjustments pre-install.

* Drives smaller than around 40GB will not create a separate /build
partition by default, but will still create a /build directory in the
root partition and generate the same nullfs mounts. This makes it easier
for the user to adjust to a larger configuration later on if desired.

* This also improves crash recovery mechanics, increasing the chance that
the root partition will be able to mount with minimal recovery work.

* We now use a tmpfs filesystem for /tmp by default. /var/tmp is mounted
from storage. Again, the user can change this easily post-install.

* Calculate better values for swap, root, and /build, based on the size
of the slice being installed to. The /build directory will cap-out
at around 20GB leaving. Swap will be made smaller if the root partition
seems to small, and so forth.

Some swap is always configured. Swap is a very useful thing to have,
even if you have tons of memory, because there will always be a certain
number of always-idle pages from idle services laying around.

* Remove /dev from sources.conf, it is no longer appropriate to try to
cpdup /dev. Fixes a cpdup error.

* UFS root can now be encrypted (it couldn't before), because the UFS
install now splits out a separate /boot partition.

* Tested w/non-crypto UFS and HAMMER install, crypto UFS and HAMMER install,
and with small and large drives.

show more ...

installer: Fix disk_find() on systems that have both da1 and da10.

In addition to comparing names (up to the length of the disk which
was found previously), also compare name lengths.

While here, r

installer: Fix disk_find() on systems that have both da1 and da10.

In addition to comparing names (up to the length of the disk which
was found previously), also compare name lengths.

While here, remove the disk_find() check in disk_new(). disk_new()
didn't deal with it returning NULL. But because the list of disks
we offer as targets for installing is taken from sysctl kern.disks'
output, it will not have duplicates (else it would likely be a bug
in the kernel).

Reported-by: BSDUX on IRC

show more ...

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

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: More /dev/serno work.

Take back the devtab(5) support in the installer.

mountroot didn't work for the UFS with serial numbers case since the
data for '/' is taken from fstab and that wou

installer: More /dev/serno work.

Take back the devtab(5) support in the installer.

mountroot didn't work for the UFS with serial numbers case since the
data for '/' is taken from fstab and that would have a devtab label
in it and we're not setting vfs.root.mountfrom explicitly for UFS.
We don't want to, either.

So just use /dev/serno/* nodes (which will work everywhere) always.

Suggested-by: dillon

show more ...

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: Move the installer from contrib/ to usr.sbin/.

Fix trailing whitespace while I'm doing it.

installer: Fix a bug when /boot (HAMMER) or / (UFS) is are to be encrypted.

The installer will warn that this is not possible, but previously left the
encryption flag set. Clear it.

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

installer: Add support for creating encrypted partitions.

With the exception of /boot for the HAMMER install and / for the UFS
install, allow the configuration of encryption of partitions via
checkb

installer: Add support for creating encrypted partitions.

With the exception of /boot for the HAMMER install and / for the UFS
install, allow the configuration of encryption of partitions via
checkboxes in the partition creation stage.

show more ...

installer: Raise WARNS to 6 and fix resulting warnings.

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

installer: Allow for tmpfs (instead of mfs) partition creation.

The installer allowed (though only in UFS "expert mode") to add mfs-backed
partitions. Change all this to tmpfs as well.