Fix immutable flag handling in our mtree(8) invocations.

All of this only affects /var/empty so far.

* If NOSCHG isn't set (which is the default), pass -i to mtree(8) when
installing the system o

Fix immutable flag handling in our mtree(8) invocations.

All of this only affects /var/empty so far.

* If NOSCHG isn't set (which is the default), pass -i to mtree(8) when
installing the system or building an installer img.

* Pass -i always when we install a system from the installer. This
installer usage of mtree(8) should not be needed. Expand the comment
a bit.

Reported-by: zrj

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

installer: Change fn_mapper_name() to subpartition_get_mapper_name().

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

installer: Don't add an entry for 'root' to /etc/crypttab.

It is not necessary and will in fact generate a 'Device root already
exists.' warning because root has already been configured and mounted

installer: Don't add an entry for 'root' to /etc/crypttab.

It is not necessary and will in fact generate a 'Device root already
exists.' warning because root has already been configured and mounted
at this point.

show more ...

installer: Fix mapper name generation for encrypted installation.

fn_mapper_name() is supposed to take the mountpoint name, not the
device name.

This actually broke the install in environments wher

installer: Fix mapper name generation for encrypted installation.

fn_mapper_name() is supposed to take the mountpoint name, not the
device name.

This actually broke the install in environments where no /dev/serno/...
device was available and both root and /build were selected for
encrypting because the device name would never contain a '/' and so
the mapper name 'root' was returned for both.

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: Fix typo in handling null mounts array.

This could have prevented to install on certain custom system layouts.

installer: Fix comment typo.

installer - use a more modern mount setup for UFS and HAMMER (2)

* Fix bugs last commit. Muffed up fstab generation and forgot to
remove an if (hammer) from the loader.conf crypto setup. Also

installer - use a more modern mount setup for UFS and HAMMER (2)

* Fix bugs last commit. Muffed up fstab generation and forgot to
remove an if (hammer) from the loader.conf crypto setup. Also
had to mkdir /dev on the target.

* Fixes boot tested w/fresh installs.

show more ...

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: Remove some more initrd creation code.

After my revert, this original mkinitrd code (for encrypted setup
originally) came back. Since we can now rely on the ISO having an
initrd to be ins

installer: Remove some more initrd creation code.

After my revert, this original mkinitrd code (for encrypted setup
originally) came back. Since we can now rely on the ISO having an
initrd to be installed already, we can remove this too.

show more ...

Revert "installer: Create an initial initrd unconditionally."

This reverts commit 0c69777ed12f9dff4a80f46f9ef730837791cf33.

Due to shortcomings of the CD9660 filesystems, hardlinks end up
having di

Revert "installer: Create an initial initrd unconditionally."

This reverts commit 0c69777ed12f9dff4a80f46f9ef730837791cf33.

Due to shortcomings of the CD9660 filesystems, hardlinks end up
having different inode numbers on it, which leads to them being
treated like separate files when copying etc.

As a result, the initrd put together by mkinitrd from a CD9660
would end up being around 230MB large where it actually has to
be below 15MB.

We will solve this in nrelease instead, putting together the
initrd from the building machine.

show more ...

installer: Don't create a separate /usr pfs

* /usr as a separate filesystem from / doesn't really make sense
anymore in this day and age. Both / and /usr binaries are dynamically
linked and belo

installer: Don't create a separate /usr pfs

* /usr as a separate filesystem from / doesn't really make sense
anymore in this day and age. Both / and /usr binaries are dynamically
linked and belong to the same DragonFly base system.

* What's more, it's dangerous. With a separate /usr filesystem, the
rescue static binaries in /usr/share/initrd can't be accessed without
/usr mounted and in some situations /usr can't be mounted anymore with
the regular mount* binaries...

show more ...

installer: Create an initial initrd unconditionally.

Now that the mkinitrd has been detached from installworld, the rescue
image is no longer part of the ISOs/IMGs, so we have to always create
one d

installer: Create an initial initrd unconditionally.

Now that the mkinitrd has been detached from installworld, the rescue
image is no longer part of the ISOs/IMGs, so we have to always create
one during installation, not just for encrypted setup.

show more ...

installer: Save the installation log as the last step.

installer: Remove a more or less arbitrary check of the swap size.

Except for boxes which have lots of memory combined with a very very
small disk, the installer gives a sane default for swap size b

installer: Remove a more or less arbitrary check of the swap size.

Except for boxes which have lots of memory combined with a very very
small disk, the installer gives a sane default for swap size by itself
and if the user doesn't change it, all will be good.

However, if the user did choose to adjust the swap size and if it was
to below the main memory size, this check caused it not to be activated
and no dumpdev was written to the rc.conf of the installed system.

Instead of guessing around how much swap is needed to hold a dump,
adding warnings and whatnot, just assume that anyone who tinkers with
the offered defaults is intelligent enough to know possible
consequences and accept their choice in any case.

show more ...

Revert "installer: Export /boot device name in loader.conf"

This reverts commit 8a01d9f7000ef8c274b595edf681b3ff0b17591e.

It turns out putting the boot device name in a sysctl variable for its
use

Revert "installer: Export /boot device name in loader.conf"

This reverts commit 8a01d9f7000ef8c274b595edf681b3ff0b17591e.

It turns out putting the boot device name in a sysctl variable for its
use by a rescue system is not such a good idea.

show more ...

installer: Export /boot device name in loader.conf

This will eventually allow the kernel to mount /boot directly

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.

nrelease/installer: No longer build and offer separate UP and SMP kernels.

Due to sephe's recent work, SMP kernels should boot on UP machines as
well. This is to give his work more exposure.

Also r

nrelease/installer: No longer build and offer separate UP and SMP kernels.

Due to sephe's recent work, SMP kernels should boot on UP machines as
well. This is to give his work more exposure.

Also remove the (now redundant) *_SMP configs.

In-discussion-with: sephe

show more ...

installer: Move the remaining installer related files out of /usr/local.

Reported-by: y0netan1

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: Add dumpdev support.

* Use the configured swap with dumpon for the installation.

* Automatically add a dumpdev entry in the installed system's /etc/rc.conf.