src/usr.sbin/bsdinstall/scripts/auto, branch main

bsdinstall: Drop "Technology preview" from package sets

2026-01-12T18:47:38+00:00

And refer to dist sets as "legacy."  This matches our expectation for
FreeBSD 16.0.

Reviewed by:	cperciva
Sponsored by:	The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D54156

bsdinstall: Mount /dev and /packages after using the shell to partition disks

2025-12-08T21:33:30+00:00

Normally after partitions are created by the installer, the 'mount'
script is used to mount the target disk partitions under /mnt.  The
tail end of this script also mounts a couple of additional filesystems
under /mnt so that chrooted programs can work such as devfs and
/packages.

When the "Shell" option is used to permit the user to manually mount
the destination filesystem, the "mount" script is not used as the user
is instructed to mount the target filesystems and construct
/mnt/etc/fstab, etc.  However, this means that the user is responsible
for mounting devfs (which is not included in /etc/fstab) and /packages
as well.  The help message for the "Shell" option doesn't mention
these requirements, so users may not know to do so.  This can lead to
confusing errors as chrooted commands can fail to find needed /dev
entries.  For example, running fwget to fetch wireless firmware fails
because /dev/pci doesn't exist.

To make this less painful for users using this option, split out the
bottom half of the 'mount' script that mounts these non-fstab-related
filesystems into a separate 'mount_aux' script.  Invoke 'mount_aux'
after using "Shell" to create the filesystem to ensure that these
filesystems are always present.

PR:		290901
Reported by:	Peter 
Tested by:	Peter 
Differential Revision:	https://reviews.freebsd.org/D53770

bsdinstall: Fix typos

2025-10-18T17:13:16+00:00

Reviewed by:	emaste
MFC after:	2 days
Differential Revision:	https://reviews.freebsd.org/D53170

bsdinstall: Tweak pkgbase/dist set labels

2025-10-11T17:22:19+00:00

Have the button labels refer to the artifact type directly (distribution
sets / packages), and use "Tech Preview" as packaged base is no longer
experimental.

Reviewed by:	ivy, cperciva
Sponsored by:	The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D52999

bsdinstall: Add loader.efi to all ESPs we create

2025-09-30T02:55:46+00:00

For proper redundancy, add copies of loader.efi to each of the ESPs we
create when we create multi-volume ZFS datasets. zfsboot creates a list
of secondary ESPs, while bootpart doesn't create any (it's the UFS
partitioning tool) because we don't supporg UFS over gmirror. The
primary ESP is mounted and is what we use efibootmgr to boot from. The
redundant copies allow the system to boot if the primary disks fails.

Sponsored by:		Netflix
MFC After:		2 days
PR:			208802
Reviewed by:		cperciva
Differential Revision:	https://reviews.freebsd.org/D52780

bsdinstall: Skip pkgbase question if no legacy dist sets

2025-06-23T14:44:14+00:00

If the install media was built without dist sets (and so has no MANIFEST
file) we do not need to prompt the user, and only pkgbase is in use.

Reviewed by:	Isaac Freund 
Event:		Kitchener-Waterloo Hackathon 202506
Sponsored by:	The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D50918

bsdinstall: Emit a warning if the system has too little memory

2025-06-20T19:22:18+00:00

PR:		251993
Reviewed by:	adrian
Event:		Kitchener-Waterloo Hackathon 202506
Sponsored by:	The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D50944

bsdinstall: Default to pkgbase if media contains base packages

2025-06-16T22:44:57+00:00

As of commit 62d18f8c4c10 ("release: Add -DPKGBASE option to include
pkgbase packages") we can include base system packages on the install
media instead of dist tarballs.

Set the default for the traditional/pkgbase question to match the
artifact type included in the install image.

Reviewed by:	jrm
Event:		Kitchener-Waterloo Hackathon 202506
Sponsored by:	The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D50467

bsdinstall: restore the environment when restarting

2025-06-01T12:53:16+00:00

It is possible to restart the installation process upon errors, when
installing normally through the `auto` script, or when installing a jail
with the `jail` script. However, some values obtained interactively from
the user or guessed by some scripts were kept in the environment when
restarting the process; this made it impossible to re-run some steps as
expected after the restart.

For instance, if a bad choice of mirror was made in the `mirrorselect`
phase, restarting the installer remembered the choice made, and would
never prompt for a different one again. Rebooting was then the only easy
way out of this situation.

This change restores a pre-defined list of environment variables when
restarting the installation process.

PR:		266987
Reviewed by:	emaste
Approved by:	philip (mentor)
Sponsored by:	The FreeBSD Foundation
Differential revision:	https://reviews.freebsd.org/D42281

bsdinstall: support offline pkgbase installation

2025-05-23T13:41:49+00:00

Reviewed by:	bapt, emaste
Sponsored by:	The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D50347