root device is already available. This allows to avoid USB probe messages
printed over the installer menu. This is needed only in installer with
its UFS, since ZFS root of installed system implies it automatically.
Ticket: #35497
*_name has special meaning in loader.conf so is a bad variable name.
Rename ${product_name} to ${product} so it behaves like a regular
environment variable.
Ticket: #35730
This variable contains a presentable string to indicate the product name
in menu entries and wherever else it may be handy. It helps
distinguish the installer media from an installed system.
Ticket: #35730
This change cause more harm then good. Without setting boot_serial it
makes unpredictable which console become primary, and on which installer
menu will appear. We probably need some loader menu or other solution.
This reverts commit 3b05806bac.
what version to set in the FreeBSD ports we build. This is
to work around an issue with shallow checkouts (Which we should be
using everywhere) and still provide the port a numerical that
increases.
We are not using labels other then gptid and iso9660 in normal run,
and ufs during ISO updates from ancient versions. Removing them
should reduce disk tasting time by GEOM.
Initial work to start adding a SDK build of FreeNAS - Add
SDK {no|yes} option that can be set during build, turn off a bunch
of flags if this isn't set to the default "no".
a commented lin in /etc/rc to show how to use it). This will allow
it to be used in real builds. Also to see if I screwed up on my
builds. (I've been building with it for a while now, however.)
This variable really configure serial console with these parameters,
while previous ones could leave us with black screen during install.
Ticket: #23147
Move the Profile Specific Release directory data into the appropriate Profile directory. Add a build-tool that copies this release information from the appropriate Profile Release directory into the common Release directory during build as part of the make checkout: –and– update: just after the point where the data has been updated.
A checkout prior to this point will yield:
* The Common Release directory contains the release information for multiple Profiles making it non-generic
* The Release directory was laid out in Version Product Build order instead of Product Version Build order, which is more intuitive because generally a Build belongs to a Version, which belongs to a Product
