aboutsummaryrefslogtreecommitdiff
path: root/usr.sbin/bsdinstall/scripts
Commit message (Collapse)AuthorAgeFilesLines
...
* bsdinstall: add pkgbase prompt to auto scriptIsaac Freund2025-04-291-34/+52
| | | | | Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D49824
* bsdinstall: add pkgbase prompt to jail scriptIsaac Freund2025-04-291-50/+68
| | | | | Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D49823
* bsdinstall: add pkgbase targetIsaac Freund2025-04-282-0/+178
| | | | | | | Reviewed by: ziaee (manpages), kevans (lua), emaste Relnotes: Yes Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D49822
* bsdinstall: Switched back to amended single-button finalconfigJessica Clarke2025-02-041-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Commit ac78e3e9c581 ("bsdinstall: Add "Finish" button to finalconfig") removed the Exit entry from the menu, renamed OK to Select and added a Finish in place of the old Exit entry. On the surface this seemed like a good idea, as at a glance OK wasn't clear that it was selecting an entry rather than just closing the box, Exit isn't the most obvious term to use for proceeding through the installer without doing anything, and it separated out the different cases of "do something extra" and "continue". However, because bsddialog (and dialog) keep a menu entry highlighted even when the Cancel (in this case, Finish) button is selected, this now looks even more confusing, with users easily believing that they are about to select the Add User option (being either surprised when it doesn't actually do that, or being confused about how to not select it). Instead, go back to the old scheme that fits more with bsddialog's supported functionality but tweak it to try and improve on the confusing UI/UX from the past. Specifically, the UI changes compared with the original version are as follows: 1. The OK button is renamed to Select, as in the current UI 2. The Exit entry is renamed to Finish, mirroring the label of the button in the current UI that it replaces This partially reverts commit ac78e3e9c581ac3b695adeec1ae312d619a1402b. Reviewed by: khorben_defora.org Differential Revision: https://reviews.freebsd.org/D47229
* bsdinstall: hook up help line and prompt for ZFS disk selectionFranco Fichtner2025-01-241-4/+4
| | | | | | | | | | Previously we were passing the wrong variable names for the prompt and help line, so the intended action wasn't clear to the user. Reviewed by: jhb, markj MFC after: 3 days See also: https://github.com/opnsense/installer/issues/22 Pull Request: https://github.com/freebsd/freebsd-src/pull/1579
* bsdinstall/zfsboot: Remove unused global variableAlexander Ziaee2025-01-211-1/+0
| | | | | | | | | | | | | | | In an AMA session on the FreeBSD Discord, it was revealed that no logic remains calling GPART_BOOTCODE_PARTONLY. It was removed in aa2a0e0fc311 for FreeBSD 12. git grep shows no other references. No functional change intended. MFC after: 2 weeks Fixes: aa2a0e0fc311 (Enable new UEFI+GELI support) Reported by: Antranig Vartanian <antranigv@freebsd.am> Reviewed by: emaste, mhorne Approved by: emaste, mhorne (src) Approved by: mhorne, carlavilla (mentors) Differential Revision: https://reviews.freebsd.org/D48086
* bsdinstall: Fix a typo in a commentMark Johnston2025-01-061-1/+1
| | | | | PR: 283507 MFC after: 1 week
* bsdinstall zfsboot: Add an option to edit the ZFS pool creation optionsCraig Leres2024-12-261-0/+12
| | | | | | | | | | This allows the default options (-O compress=lz4 -O atime=off) to be overridden, before the ZFS boot pool is created. For example, to set the compression algorithm to something different. Reviewed by: jhb, dim MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D47478
* bsdinstall: add menu to install firmwareBjoern A. Zeeb2024-11-204-0/+131
| | | | | | | | | | | | | | | | Add a menu to the installer to run fwget(8) inside the newly installed system to install firmware known to be needed. This requires working netowrking. This is needed at least for wireless currently for when we entirely stop shipping new firmware in src.git to have working networking on the installed system (we already do need this for at least rtw89). Sponsored by: The FreeBSD Foundation Tested with: 4 different iwlwifi chipsets in a system (earlier version) Suggested improvments by: jrtc27 MFC after: 8 hours Differential Revision: https://reviews.freebsd.org/D47491
* bsdinstall: wlanconfig: fix interface UP on (re-)starting wpa_supplicantBjoern A. Zeeb2024-11-191-1/+2
| | | | | | | | | | | Make sure an interface is back up before (re-)starting wpa_supplicant in wlanconfig not relying on wpa to UP the interface (though we fixed that). Sponsored by: The FreeBSD Foundation Reviewed by: emaste (in D47491) MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D47491
* bsdinstall: skip tzsetup UTC questionEd Maste2024-11-121-1/+1
| | | | | | | | | | | | | | | | | | | | | During installation bsdinstall asks (via tzsetup): > Is this machine's CMOS clock set to UTC? If it is set to local time, > or you don't know, please choose NO here! Most operating systems, except for Windows, use UTC in the hardware real-time clock by default. This question from tzsetup is presumably intended to aid in dual-boot-with-Windows configurations, but these represent a fraction of all FreeBSD installs. Rather than asking this question on every install just default to UTC. Users who want to dual-boot Windows can create /etc/wall_cmos_clock. We can look at making this smarter in the future. Reviewed by: bapt, brooks, brd, cy, 0mp, ngie Relnotes: yes Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D45569
* Copy the new ia32 loaderAhmad Khalifa2024-09-201-14/+22
| | | | | | | | | | | | | | | | This handles copying in install-boot.sh and bsdinstall's bootconfig. install-boot.sh: make_esp_file now optionally takes extra arguments so it can copy multiple files. This is used by the amd64 release scripts. make_esp_device also takes an extra optional argument for efibootname. This is currently unused, but it can be used in the future to do something like: make_esp_device loader.efi bootx64 make_esp_device loader_ia32.efi bootia32 Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/1098
* Remove residual blank line at start of MakefileWarner Losh2024-07-151-1/+0
| | | | | | | This is a residual of the $FreeBSD$ removal. MFC After: 3 days (though I'll just run the command on the branches) Sponsored by: Netflix
* bsdinstall: Fix wifi network selection sizeRenato Botelho2024-05-201-1/+1
| | | | | | | | | Use correct variable while creating dialog used to select among available wireless networks Approved by: asiciliano Sponsored by: Rubicon Communications, LLC ("Netgate") Differential Revision: https://reviews.freebsd.org/D45271
* bsdinstall: Remove unused variables in fetchmissingdistsFernando Apesteguía2024-05-121-3/+0
| | | | | | | | | | ALL_DISTRIBUTIONS and VERIFY_MANIFEST_SIG They are neither used in the script nor exported. Not referenced anywhere in bsdinstall/* Approved by: imp@ Differential Revision: https://reviews.freebsd.org/D42369
* bsdinstall: Stop loading cryptodev for ZFS installationsMark Johnston2024-05-081-3/+0
| | | | | | | | | | | | | | | - zfs depends on the crypto module, not cryptodev, and most arm64 kernel configs include std.dev, which includes "device crypto" anyway. - This config works around a problem with kldxref lacking cross-target support, but that has since been fixed. - Loading cryptodev creates /dev/crypto, which gives unprivileged users access to the kernel's opencrypto framework. Very few applications need it, so we're needlessly increasing the kernel's surface area. Thus, stop auto-loading cryptodev. Reviewed by: kevans, allanjude, des Differential Revision: https://reviews.freebsd.org/D45127
* bsdinstall: update comment related to pkgBjoern A. Zeeb2024-04-251-1/+1
| | | | | | | | | pkg_add has been gone since 2013(?). Refer to pkg(8) instead. Sponsored by: The FreeBSD Foundation MFC after: 3 days Reviewed by: jrtc27 Differential Revision: https://reviews.freebsd.org/D44946
* bsdinstall: draw attention to new network config optionsMike Karels2024-03-271-1/+1
| | | | | | | | | | | | The network configuration options have changed in bsdinstall, with an Auto option to proceed directly to DHCP and IPv6 autoconfig (which is the default) as well as Manual (the old mode). For users like me that were used to hitting return automatically to select an interface, but want manual configuration, attempt to call out the difference: Change the menu caption to say "Please select a network interface and configuration mode:" and not just an interface. Reviewed by: jrtc27
* bsdinstall: remove two dead mirrorsPhilip Paeps2024-02-151-2/+0
|
* bsdinstall: prefer HTTPPhilip Paeps2024-02-151-1/+2
| | | | | | | | In 2024, users are more likely to have working HTTP than working FTP. Present http://ftp.FreeBSD.org as the first option in the installer. Keep ftp://ftp.FreeBSD.org as the second option. MFC after: 3 weeks
* bsdinstall: Add new Auto option to netconfig interface selection dialogJessica Clarke2024-02-093-24/+109
| | | | | | | | | | | | | | | | | | This changes the OK / Cancel buttons into Auto / Manual / Cancel, with Auto being the default. Manual behaves like OK used to, i.e. presents a series of dialogs asking exactly how to configure the interface, and Cancel is unchanged, exiting with exit code 1. Auto will attempt to configure IPv4+DHCP and IPv6+SLAAC with no interaction, failing only if neither can be configured, thereby supporting all of IPv4-only, IPv6-only and dual-stack environments. If at least one DNS server is provided, it will also skip asking for DNS settings, otherwise it will act like Manual mode for the purposes of DNS settings and prompt. For a standard dual-stack environment this cuts down the number of netconfig dialogs from 6 (interface, IPv4, DHCP, IPv6, SLAAC, DNS) to just the first one. Reviewed by: brooks Differential Revision: https://reviews.freebsd.org/D43731
* bsdinstall: Fix broken netconfig persistence for installed systemJessica Clarke2024-02-033-4/+4
| | | | | | | | | | The replacement of echo >> with sysrc -f used sysrc key value, which means "read variables key and value" and thus did nothing useful (and in fact emitted errors to the log about neither existing). Instead use the correct sysrc key=value form so the installed system comes back up with working networking. Fixes: 60b37735f305 ("bsdinstall netconfig: avoid duplicate entries in rc.conf")
* bsdinstall: Drop Error from title in netconfig no interfaces dialogJessica Clarke2024-02-031-1/+1
| | | | | | | | | | | | This isn't inherently an error. It is if you're attempting to download dist tarballs or later install packages, but a FreeBSD system with no NIC is a reasonable setup to have, especially in a throwaway VM setting, so we shouldn't say it is one. Leaving the exit code as 1 is still fine, since auto will ignore it, and avoids breaking other uses. MFC after: 1 week
* bsdinstall: Fix netconfig script when no interfaces are presentJessica Clarke2024-02-031-1/+2
| | | | | | | | | | | | | The script uses [ -z "$INTERFACES" ] to check if the list of interfaces is empty and will exit early if so, but INTERFACES always contains at least a space due to the way it appends the list of wireless devices. Fix this by only adding the space when there are devices to append, mirroring the behaviour for non-wireless devices above (both will result in a redundant leading space when the list is non-empty, but that one is harmless). Fixes: 159ca5c844cd ("Adapt to new wireless scheme where base wlan interfaces do not show up in ifconfig anymore.") MFC after: 1 week
* Revert "bsdinstall: separate out dist selection in prep for pkgbase support"Jessica Clarke2024-02-032-81/+32
| | | | | | | | | | | Firstly, my review comments were not addressed and instead totally ignored. Secondly, and a more valid justification for the revert, this completely breaks the installer, since selectdists isn't installed. Given the blatant lack of testing, back out this commit until it has actually been tested and review comments taken on board so that the installer actually works. This reverts commit 009d3f66cb5f0cf3f1d353f311d3a6878b2a534e.
* bsdinstall: separate out dist selection in prep for pkgbase supportBrad Davis2024-01-312-32/+81
| | | | | | | | No functional change intended. Approved by: asiciliano Sponsored by: Rubicon Communications, LLC ("Netgate") Differential Revision: https://reviews.freebsd.org/D43621
* bsdinstall: Fix installation script splittingMichael Gmelin2024-01-092-10/+22
| | | | | | | | | | | | | | | | | | This allows writing setup scripts that contain lines starting with "#!", e.g., a shebang when creating a shell script using cat: #!/bin/sh echo "Populate rc.local" cat >/etc/rc.local<<EOF #!/bin/sh echo booted | logger -s -t 'example' EOF Prevent accidentally running a setup script left behind by a previous invocation of bsdinstall. Reviewed by: imp, jrtc27 Differential Revision: https://reviews.freebsd.org/D43350
* bsdinstall: Encode dists to valid variable names in checksum scriptJessica Clarke2023-12-061-6/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently we just strip the .txz of the dist name (and add a status_ prefix) to get the shell variable name for its status, but this doesn't give a valid result for dists like base-dbg, kernel-dbg and lib32-dbg, or even kernel.KERNCONF (or, combining the two, kernel.KERNCONF-dbg). As a result, four things go wrong for such dists: 1. If there is a dot and/or a dash in the name, writing to the variable fails and spits an error out on stderr to the log 3. If there is a dot in the name before any dash, the syntax is always invalid, reading the variable fails, spits an error out on stderr to the log, the result is the empty string and that is interpreted as being 0% 2. If there is a dash in the name before any dot, and there is a dist whose name is the substring up to that first dash, and it has already had its status written to, reading the variable instead reads that dist's variable and so the status of that dist is displayed instead 3. If there is a dash in the name before any dot, and either there is not a dist whose name is the substring up to that first dash or there is such a dist but it has not already had its status written to, reading the varaible instead results in the substring after the first dash, including any additional string expansion syntax that follows (i.e. ${status_kernel-dbg:--11}, the expression used to read the variable, is interpreted as reading status_kernel with a default value of "dbg:--11") For example, in a default install with base, kernel, kernel-dbg and lib32, the following sequence of displays happens: 1. base is In Progress, kernel is Pending, kernel-dbg is 0% (what shows for the garbage input "dbg:--11") and lib32 is Pending 2. base is Passed, kernel is In Progress, kernel-dbg is In Progress (since kernel has now had its status written to) and lib32 is Pending 3. base is Passed, kernel is Passed, kernel-dbg is Passed (again, since that is the status of kernel, despite that kernel-dbg is being verified at this point) and lib32 is Pending 4. base is Passed, kernel is Passed, kernel-dbg is Passed and lib32 is In Progress Fix this with a crude encoding scheme. More special characters can easily be added if needed in future. Note that, prior to bsddialog being used (and thus for branches this is MFC'ed to where dialog is still used), the same problem existed but displayed slightly differently due to a combination of different default values and different behaviour for unintended inputs. Fixes: b70047d41362 ("Add generation of an installation manifest containing SHA256 checksums as ...") MFC after: 1 week
* bsdinstall zfsboot: Don't override ZFSBOOT_FORCE_4K_SECTORS if it is null.John Baldwin2023-11-181-1/+1
| | | | | | | | | Only set a default value of 1 if the shell variable is unset. This allows installer scripts to disable the variable. PR: 274513 Reported by: Albin "a12l" Otterhäll <bugs.freebsd.org@a12l.xyz> Differential Revision: https://reviews.freebsd.org/D42319
* bsdinstall hostname: Restore bsdconfig APIAlfonso S. Siciliano2023-10-191-5/+7
| | | | | | | | | | | | | | | Restore bsdconfig API to handle hostname dialog because bsddialog 1.0 matches all features required by bsdconfig(1). Implicitly this commit restores also Xdialog(1) for this script. This commit reverts: - "bsdinstall hostname: Replace dialog with bsddialog" 6368dcb29228dd8e18d50c54c3ca1596262d4676 - "bsdinstall(8) hostname: Update for bsddialog 0.3" 5f3ec44e7e9c11f90ad1128db1116925b493fad0. The script continues to use bsddialog(1) by default via $DIALOG in bsdconfig(1).
* bsdinstall: Fail nicely in jail targetFernando Apesteguía2023-10-181-1/+5
| | | | | | | | | | If the directory is empty we fail with a message regarding mkdir in which the empty directory can't be seen because it is not quoted. Show a nice message so the user knows what is going on. Reviewed by: bapt@ Differential Revision: https://reviews.freebsd.org/D42252
* bsdinstall netconfig: avoid duplicate entries in rc.confPierre Pronchery2023-10-133-4/+4
| | | | | | | | | | | | This uses sysrc to write and update configuration variables in the temporary configuration file for network access, ._rc.conf.net. This replaces the previous mechanism, which was simply appending new values as they were updated. PR: 212396 Reviewed by: emaste Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D42194
* bsdinstall: reset the mirror when restartingPierre Pronchery2023-10-131-0/+1
| | | | | | | | | | | | | | | | | | | | | | It is possible to restart the installation process upon errors, when installing normally through the `auto` script, or when setting up a jail with the `jail` script. However, some values obtained interactively from the user or guessed by some scripts are kept in the environment when restarting the process; this makes it impossible to 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 remembers the choice made, and will never prompt for a different one. Rebooting is then the only easy way out of this situation. This change only affects the `jail` script for now, as otherwise there is no way to tell if the value had been specifically set by the user before starting bsdinstall. Reviewed by: bapt Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D42183
* bsdinstall: Add "Finish" button to finalconfigPierre Pronchery2023-10-131-5/+6
| | | | | | | | | | | | | | This adds a "Finish" button to the finalconfig step, replacing the previous first choice, which was to "apply configuration and exit". The new button is the default action, while the "OK" button is renamed to "Select". Also, if an unknown option is chosen, the code flow prompts the user again instead of exiting. Reviewed by: bapt Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D42047
* bsdinstall: revisit the finalconfig stepPierre Pronchery2023-10-133-53/+83
| | | | | | | | | This moves the "finalconfig" step into a dedicated script, where it uses a loop instead of recursing into itself. Reviewed by: bapt Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D42046
* bsdinstall auto: replace dialog with bsddialogAlfonso S. Siciliano2023-10-111-7/+7
| | | | bsdinstall/scripts/auto: Replace dialog(1) with bsddialog(1).
* bsdinstall: restore --calendarAlfonso S. Siciliano2023-10-111-1/+1
| | | | | Restore --calendar to select a date because bsddialog(1) >= 0.4 provides a calendar dialog.
* bsdinstall: Fix command line argument list parsingAlfonso S. Siciliano2023-10-112-2/+2
| | | | | | | bsddialog(1) uses getopt_long(3) to parse command line argument list. Add '--' to avoid errors caused by arguments (menu items) begin with '-'. The change is compatible with dialog(1) and Xdialog(1).
* bsdinstall: avoid conflicts with fd 3Lars Kellogg-Stedman2023-09-2111-59/+58
| | | | | | | | | | | | | | | | | | | | | | | | | Throughout the bsdinstall script fd 3 is used by f_dprintf (set through $TERMINAL_STDOUT_PASSTHRU). In several places in the bsdinstalls scripts, we use fd 3 to juggle stdout when calling out to other tools, which can cause the installer to fail with a "Bad file descriptor" error when f_dprintf attempts to use it. This commit replaces all constructs like this: exec 3>&1 SOME_VARIABLE=$(some command 2>&1 1>&3) exec 3>&- With: exec 5>&1 SOME_VARIABLE=$(some command 2>&1 1>&5) exec 5>&- PR: 273148 Reviewed by: corvink Fixes: 1f7746d81f53447ac15cc99395bb714d4dd0a4da ("bsdinstall: stop messing with file descriptors") MFC after: 1 week
* Remove $FreeBSD$: one-line sh patternWarner Losh2023-08-1626-26/+0
| | | | Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
* bsdinstall: remove sendmail hardening optionBaptiste Daroussin2023-06-011-6/+2
| | | | | | | sendmail is fully disabled in 14.0 by default Reviewed by: imp, emaste Differential Revision: https://reviews.freebsd.org/D40367
* bsdinstall on zfs: create dataset for /home rather than /usr/homeMike Karels2023-05-231-3/+3
| | | | | | | | | Now that pw (hence adduser and the initial install) use /home for user home directories rather than /usr/home, create a dataset for /home rather than /usr/home. Update the man page to match. Reviewed by: rgrimes, markj Differential Revision: https://reviews.freebsd.org/D40086
* bsdconfig, bsdinstall: Refresh mirrors listDanilo G. Baio2023-01-161-83/+31
| | | | | | | | | | | | | The mirrors list is in sync with the Handbook / Mirrors section [1], which was refreshed a few months ago. Mirrors removed were not responding or had duplicated addresses (aliases) with another mirror. 1 - https://docs.freebsd.org/en/books/handbook/mirrors/ Reviewed by: philip (clusteradm) Approved by: philip MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D38014
* bsdinstall: s/to small/too small/Mateusz Guzik2022-12-221-1/+1
| | | | Reported by: Sulev-Madis Silber <ketas@si.pri.ee>
* bsdinstall: Fix local_unbound option default on revisitJessica Clarke2022-11-291-1/+2
| | | | | | | | | The variable used for the checklist's default value needs to correspond to the rc.conf variable as that's what's being parsed to determine them. In the case of local_unbound it's missing the _enable suffix and thus always defaults to off on revisit. Fixes: 58eb9abb3157 ("Add a line to the post-installation configuration dialog to enable the local_unbound service.")
* bsdinstall: Fix issues parsing rc.conf.services on revisitJessica Clarke2022-11-291-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | There are a few issues here, some of which are hiding others. The first is that we don't use double quotes around the command substitution so every word in the conf file is treated as a separate argument to eval, resulting in spaces being used in place of newlines and thus comments in the file commenting out the rest of the file, not just to the end of their line. In particular, we insert one comment just before the dumpdev entry (the final one in the file) and so we never see dumpdev as set, and thus set a default value of on for the menu. The second issue is that, for dumpdev, it takes a value of AUTO not YES when set, but we don't replace this with on when eval'ing, so then end up giving AUTO to bsddialog which is interpreted the same as off (which seems to match GPL dialog). Thus handle AUTO like YES otherwise it will always appear as unchecked on revisit. The final issue is that our case-insensitive YES/NO (and now AUTO) replacements have no word boundaries around them so match the middle of words too. As it happens this doesn't matter in practice at the moment, but it could in future; currently the only effect is that it rewrites moused_nondefault_enable to moused_offndefault_enable, but since this variable is never read, only written based on moused(_enable) this is harmless, but we should fix it in case a service comes along in future that does get affected by it.
* bsdinstall: Fix ntpd_sync_on_start service optionJessica Clarke2022-11-291-1/+6
| | | | | | | | | | | | | | | | | | | | | | This installer option is currently totally useless, as it ends up creating an ntpd_sync_on_start_enable="YES" entry in rc.conf, not an ntpd_sync_on_start="YES" entry, as is the correct name. This can also be noticed by revisiting the services menu, which parses the previously written rc.conf.services file to set variables governing the default menu entry values so that selecting OK regenerates the same file, as the menu entry will use the correct variable name and thus think the entry was not selected last time, defaulting back to off and losing the setting. Thus, add a special case in the loop for this option. The only other entry that doesn't follow the *_enable pattern is dumpdev (even moused does, it just also sets a second variable), but that also deviates in terms of being explicitly set either way and using AUTO rather than YES, hence why ntpd_sync_on_start follows a different pattern here and is special-cased rather than introducing a whole new variable that governs behaviour outside the loop. Fixes: c153a35bfd71 ("bsdinstall: replace ntpdate by ntpd_sync_on_start")
* bsdinstall: use the correct DISTDIR for fetching local distfilesKyle Evans2022-10-141-1/+1
| | | | | | | | | | | | | | | | | fetchmissingdists naturally sets BSDINSTALL_DISTDIR to a directory in the new filesystem that it can write fetched distfiles to. As a result, BSDINSTALL_DISTSITE was incorrectly set to the scratch space on /mnt for the call to distfetch when grabbing local distfiles, and it would subsequently fail. Switch to using the copy of BSDINSTALL_DISTDIR that we stashed off coming into fetchmissingdists; this one is in-fact set to the path where the local distfiles are stored. Patch suggested by jrtc27. Reported and tested by: Daniel O'Connor <darius dons net au> MFC after: 1 week
* bsdinstall: add hooks to allow for easier customizing the installBrad Davis2022-10-031-0/+10
| | | | | | Approved by: allanjude Sponsored by: Rubicon Communications, LLC ("Netgate") Differential Revision: https://reviews.freebsd.org/D36459
* bsdinstall: replace ntpdate by ntpd_sync_on_startVinícius Zavam2022-09-271-2/+2
| | | | | | | | | | | | | | | | * change current NTP services offered by the FreeBSD Installer; * no longer offer ntpdate to be enabled and started on boot; * start offering the option to make ntpd set the date and time on boot itself. The motivation for this change comes from the ntpdate(8) manpage: Note: The functionality of this program is now available in the ntpd(8) program. See the -q command line option in the ntpd(8) page. After a suitable period of mourning, the ntpdate utility is to be retired from this distribution. Approved by: cy (src), dteske (src) Differential Revision: https://reviews.freebsd.org/D36206
generated by cgit v1.3 (git 2.53.0) at 2026-05-30 02:26:32 +0000