This breaks the new feature in the interim since the router file
read is not yet supposed to read :slaac counterpart since the router
file is still read manually. Refactor to follow.
We do want to eventually lean on exclusive ifctl use in order to
be able to improve logic in ifctl or make adjustments really easy in
the future without missing a spot (e.g. adding scope to link-local
routers).
Was in need of something like this to gain access to a ZFS pool without
having to run a command sequence from the top of my head.
Comes in pretty handy when being included from a recovery install stick.
An idea from the last refactoring: create a database directory
that holds the defaults as portable files with the ability to
invoke other user-created melodies as well as override the default
using ".local" suffix.
We already have "kernel" and "base" and plugins also follow this
pattern by only registering its name once per devel or release
version. This kills ambiguity for "opnsense" vs. "opnsense-version"
and makes it more branding friendly. Suffice to say "core", "kernel"
and "base" are reserved names and also align with tools.git.
product_flavour is embedded in the release package but the
package itself does not insist on a particular flavour other
than having knowledge about the flavour the package was
built for originally. This is ok and direct crypto deps
seem to have failed to produce reliable upgrade / sidegrade
results in recent tests anyway.
Long story short: find out the real crypto flavour installed
from the OpenSSL binary or fall back to the metadata if said
binary cannot be found.
Document the shell invoke in the importer for 18.7 and the people
who will want the installer to run early. This is really not what
we want to do ever since we moved to a `installer' user and try to
enforce a live environment to help people test the look and feel,
either by first impression for new users or for previewing the new
version prior to installation.
