It's mostly the same and the indirection through custom
is annoying to work with. Since it is just a helper for
the VM image type don't document it further.
Only VM images really handle ZFS. While here move the handling
to the core repository so rc.loader knows what to do.
We only need a 10 second boot relay on installer vga/serial/dvd/nano.
Also go back to setting the pool name using PRODUCT_ZFS which is
now safeguarded through ALLOWED/REQUESTED.
Also renames PRODUCT_SERVER to shorter SERVER because it's not really
part of the product. ;)
Allow the REMOTEDIR to be empty so we can automatically select a matching
directory in download/upload cases.
Meant as a means to boost cooperation they basically led nowhere
and sometimes refuse to build cleanly after a base build. Let's
go with the sign of the times here and expose them less which also
doesn't change the default behaviour.
This simply scans ${PORTSDIR}/MOVED file for the port at hand.
Our skim doesn't delete used but removed ports but thus we also
fail to see if FreeBSD ports (re)moved it until it breaks for good.
rebuilding tests after a full base build may fail which prevents
building a kernel without clean-obj. To sidestep require the tests
before base and see if this needs further cleaning/fixing then or
if it's fine there.
This is probably the fifth iteration of "how to approach testing"
which seems trivial but for a surprising number of reasons this
is really not tailored for casual testing in user systems.
This is a bit tedious otherwise as seen over the years but
not a lot needed to make it happen. Complaints are still
being issued on (forced) mismatch or when no configuration
was found.
We might want to change it, but more like "openssl-devel" to try version
3 at some later point in time. The FLAVOUR magic can go gradually, see
next commit.
We only support OpenSSL now and the base build is also not fully
hooked up. Perhaps we can improve the situation later on but for
now just remove the spurious bits leading to errors.
Flip the order of root and swap to allow VM image to grow.
Hook this up in extras.conf and also retrofit a serial console
for being able to test and debug in bhyve (build/boot).
Omit the use of a GPT root label in the ZFS case to deal with
devices names in the way that bsdinstall sets it up. It is
not all that important for ZFS anyway.
The setup likely needs further testing and tweaking to make
sure we emulate bsdinstall zfsboot script properly to avoid
future problems.
The solution on mismatch is rarely providing the override so
try to hint at the user using that another configuration might
be needed to match the build environment.
... and set up a chroot environment to run the proper kldxref in the
isolated environment. It turns out that building kldxref manually
in the host builds one for the host likely with the help of /usr/include
and this fails again for the forward build.
It's the facepalm of the week.
According to e0e08e9a5b this was asked about in the forum back
then, but the plugin hasn't gotten much improvement over the years
and to use it you need an Internet connection which you can also
use to install the plugin.
On a restore you can already sync all missing plugins now which is
also helping in this case.
