bsdinstall: Remove unused sysctl.h header #include(cherry picked from commit 3e5bff102b4bd09962b0f735217635cb513d53a3)
Add a new mode to the scripted partition editor for variant disk names.If the disk parameter "DEFAULT" is set in place of an actual device name,or no disk is specified for the PARTITIONS parameter
Add a new mode to the scripted partition editor for variant disk names.If the disk parameter "DEFAULT" is set in place of an actual device name,or no disk is specified for the PARTITIONS parameter, the installer willfollow the logic used in the automatic-partitioning mode, in which itwill either provide a selection dialog for one of several disks ifseveral are present or automatically select it if there is only one. Thissimplifies the creation of fully-automatic installation media forhardware or VMs with varying disk names.Suggested by: Egoitz Aurrekoetxea <[email protected]>MFC after: 3 weeksRelnotes: yes(cherry picked from commit 5140034cc077c416690b4fdb79a96744fe0af0e6)
show more ...
bsdinstall: Drop vestigial bsdinstall-esps cleanupThis is not needed after 0b7472b3d8d2f1e90fade5236b44fd98d8e396c2.MFC after: 3 daysSponsored by: iXsystems, Inc.Reviewed by: impDifferential R
bsdinstall: Drop vestigial bsdinstall-esps cleanupThis is not needed after 0b7472b3d8d2f1e90fade5236b44fd98d8e396c2.MFC after: 3 daysSponsored by: iXsystems, Inc.Reviewed by: impDifferential Revision: https://reviews.freebsd.org/D29325(cherry picked from commit b07b7aec6534052d60cffe010c0426a7ab986d85)
Fix scripted installs on EFI systems after default mounting of the ESP.Because the ESP mount point (/boot/efi) is in mtree, tar will attempt toextract a directory at that point post-mount when the
Fix scripted installs on EFI systems after default mounting of the ESP.Because the ESP mount point (/boot/efi) is in mtree, tar will attempt toextract a directory at that point post-mount when the system is installed.Normally, this is fine, since tar can happily set whatever properties itwants. For FAT32 file systems, however, like the ESP, tar will attempt toset mtime on the root directory, which FAT does not support, and tar willinterpret this as a fatal error, breaking the install (seehttps://github.com/libarchive/libarchive/issues/1516). This issue wouldalso break scripted installs on bare-metal POWER8, POWER9, and PS3systems, as well as some ARM systems.This patch solves the problem in two ways:- If stdout is a TTY, use the distextract stage instead of tar, as in interactive installs. distextract solves this problem internally and provides a nicer UI to boot, but requires a TTY.- If stdout is not a TTY, use tar but, as a stopgap for 13.0, exclude boot/efi from tarball extraction and then add it by hand. This is a hack, and better solutions (as in the libarchive ticket above) will obsolete it, but it solves the most common case, leaving only unattended TTY-less installs on a few tier-2 platforms broken.In addition, fix a bug with fstab generation uncovered once the tar issueis fixed that umount(8) can depend on the ordering of lines in fstab in away that mount(8) does not. The partition editor now writes out fstab inmount order, making sure umount (run at the end of scripted, but notinteractive, installs) succeeds.PR: 254395Approved by: re (gjb)Reviewed by: gjb, impMFC after: 3 daysDifferential Revision: https://reviews.freebsd.org/D29380(cherry picked from commit c2f16c595eb51c6e0cb6ece3f6f078d738019059)
Mount the EFI system partition (ESP) on newly-installed systems and VMimages.Per hier(7), the ESP will be mounted at /boot/efi. On UFS systems,any existing ESP will be reused and mounted there; o
Mount the EFI system partition (ESP) on newly-installed systems and VMimages.Per hier(7), the ESP will be mounted at /boot/efi. On UFS systems,any existing ESP will be reused and mounted there; otherwise, a new onewill be made. On ZFS systems, space for an ESP is allocated on all disksin the root pool, but only the partition actually used to boot is set upand mounted.This makes future upgrades of the EFI loader easier (upgrade scripts canjust change /boot/efi) and also greatly simplifies the parts of theinstaller involved in initialization of the ESP. It also makes theinstaller's behavior correspond to the documentation in hier(7).Reviewed by: imp, tsoome, bdragonApproved by: re (gjb)Relnotes: yesDifferential Revision: https://reviews.freebsd.org/D28897(cherry picked from commit 0b7472b3d8d2f1e90fade5236b44fd98d8e396c2)(cherry picked from commit 2c26d77d989abe48c662eeb6f52f7e4c9b81680c)(cherry picked from commit e77cf2a4ab32a381df3c06d25b8b4f650047c3f2)(cherry picked from commit e70eb40271512dfbca7cecf823e4b445e3989c2e)
bsdinstall: riscv-specific tweaksMake the installer more useful, by allowing it to create a bootableinstallation. Also, enable the menu option for ZFS-on-root.Like arm64, RISC-V boots by UEFI on
bsdinstall: riscv-specific tweaksMake the installer more useful, by allowing it to create a bootableinstallation. Also, enable the menu option for ZFS-on-root.Like arm64, RISC-V boots by UEFI only, so arm64's parteditimplementation is renamed and shared among the two platforms.Reviewed by: gjb(cherry picked from commit 7b08a307e88bb1abe17d13d11288392a8e4739ce)
bsdinstall: remove VTOC8 partition scheme optionNow that sparc64 has been removed, there are no kernels built withsupport for the VTOC8 partitioning scheme by default. Remove the optionfrom the i
bsdinstall: remove VTOC8 partition scheme optionNow that sparc64 has been removed, there are no kernels built withsupport for the VTOC8 partitioning scheme by default. Remove the optionfrom the installer, as it is unsupported on all installer imagesproduced by re@.Reviewed by: impDifferential Revision: https://reviews.freebsd.org/D27641
- Cleanups related to sparc64 removal.- Remove remains of sparc64 files.Reviewed by: impDifferential Revision: https://reviews.freebsd.org/D25831
Fix regression in bsdinstall post r356740 - partedit errno(2) 21 EISDIRThis resulted in the partitioning step failing if either of the"Auto (UFS)" or "Manual" options were selected.Reason: parte
Fix regression in bsdinstall post r356740 - partedit errno(2) 21 EISDIRThis resulted in the partitioning step failing if either of the"Auto (UFS)" or "Manual" options were selected.Reason: partedit was attempting to open a directory (TMPDIR) read/write,which resulted in errno(2) 21 - EISDIR - Is a directory.Reported by: Clay Daniels <[email protected]>Reviewed by: Ryan Moeller <[email protected]>Approved by: emaste, bcranDifferential Revision: https://reviews.freebsd.org/D23232
bsdinstall: Use TMPDIR if setSubmitted by: Ryan Moeller <[email protected]>Reviewed by: bcran, Nick Wolff <[email protected]>Differential Revision: https://reviews.freebsd.org/D22979/
powerpc/boot: Move ubldr to /boot/uboot, and make this a separate filesystemSummary:Now that mpc85xx can boot via ubldr, move ubldr to a separatefilesystem, mounted on /boot/uboot, so that a fres
powerpc/boot: Move ubldr to /boot/uboot, and make this a separate filesystemSummary:Now that mpc85xx can boot via ubldr, move ubldr to a separatefilesystem, mounted on /boot/uboot, so that a fresh install can boot correctly.Reviewed By: nwhitehornDifferential Revision: https://reviews.freebsd.org/D18709
Rework UEFI ESP generationCurrently, the installer uses pre-created 800KB FAT12 filesystems thatit dd's onto the ESP partition.This changeset improves that by having the installer generate a FAT3
Rework UEFI ESP generationCurrently, the installer uses pre-created 800KB FAT12 filesystems thatit dd's onto the ESP partition.This changeset improves that by having the installer generate a FAT32filesystem directly onto the ESP using newfs_msdos and then copyingloader.efi into /EFI/freebsd.For live installs it then runs efibootmgr to add a FreeBSD boot entryin the BIOS.Sponsored by: NetflixDifferential Revision: https://reviews.freebsd.org/D17947
Add partition scheme for mpc85xx devicesSome mpc85xx devices with u-boot need MBR partitioning with a FAT bootpartition. Since the infrastructure is already in place to have a dedicatedboot part
Add partition scheme for mpc85xx devicesSome mpc85xx devices with u-boot need MBR partitioning with a FAT bootpartition. Since the infrastructure is already in place to have a dedicatedboot partition, this adds the necessary bits to use that infrastructure withmpc85xx boards.Reviewed By: nwhitehornDifferential Revision: https://reviews.freebsd.org/D15664
Fix math error in the computation of the free space after the last partitionon a disk. This resulted in one sector always remaining free at the end.PR: bin/228322Submitted by: Rikiya YonemotoMF
Fix math error in the computation of the free space after the last partitionon a disk. This resulted in one sector always remaining free at the end.PR: bin/228322Submitted by: Rikiya YonemotoMFC after: 2 weeks
bsdinstall: enable SUJ by default (revert r327890)fsck should be fixed as of r328092.PR: 225110Tested by: dumbbell, Arshan Khanifar <arshankhanifar gmail.com>
bsdinstall: disable SUJ by defaultSUJ + cg checksums produce spurious warnings after an unclean shutdown(e.g. a crash). For now disable SUJ for UFS installs so installing froma FreeBSD 12 snapsh
bsdinstall: disable SUJ by defaultSUJ + cg checksums produce spurious warnings after an unclean shutdown(e.g. a crash). For now disable SUJ for UFS installs so installing froma FreeBSD 12 snapshot results in a usable filesystem, until this can befixed.PR: 225110Submitted by: Arshan Khanifar <arshankhanifar gmail.com>Sponsored by: The FreeBSD FoundationDifferential Revision: https://reviews.freebsd.org/D13890
Add installer support for PS3 and PowerNV systems, also laying thefoundation for invoking efibootmgr as part of new-style EFI booting onx86. On PS3 and PowerNV, which are booted using Linux kexec f
Add installer support for PS3 and PowerNV systems, also laying thefoundation for invoking efibootmgr as part of new-style EFI booting onx86. On PS3 and PowerNV, which are booted using Linux kexec from petitbootrather than by loader(8), install the kernel and the rest of /boot to aFAT partition and set up the appropriate petitboot configuration filethere.The new bootconfig installer stage can do platform-dependent modificationsmore complex than partition layout and installation of boot blocks and canbe used to (as here) set up some special configuration files, run efibootmgr,or boot0cfg.MFC after: 1 month
Teach bsdinstall partedit/sade how to format FAT partitions on GPT, whichhave the partition type code "ms-basic-data".MFC after: 2 weeks
Fix bug introduced in r326674, in which efi boot partitions created bythe installer but not mounted (i.e. with boot1.efifat dd'ed to themrather than the forthcoming proper filesystem) would get new
Fix bug introduced in r326674, in which efi boot partitions created bythe installer but not mounted (i.e. with boot1.efifat dd'ed to themrather than the forthcoming proper filesystem) would get newfs_msdos runon them immediately after the boot code was copied. This would overwritethe bootstrap code, causing the EFI system partition to be blanked andresulting in an unbootable system.PR: 224562
Support mounted boot partitions in the installer. This allows the platformlayer, for example, to specify that the EFI boot partition should bemounted at /efi and formatted normally with newfs_msdos
Support mounted boot partitions in the installer. This allows the platformlayer, for example, to specify that the EFI boot partition should bemounted at /efi and formatted normally with newfs_msdos rather thansplatted to from /boot/boot1.efifat.This commit adds only the API for this; actual platform use will come later.
various: general adoption of SPDX licensing ID tags.Mainly focus on files that use BSD 2-Clause license, however the tool Iwas using misidentified many licenses so this was mostly a manual - error
various: general adoption of SPDX licensing ID tags.Mainly focus on files that use BSD 2-Clause license, however the tool Iwas using misidentified many licenses so this was mostly a manual - errorprone - task.The Software Package Data Exchange (SPDX) group provides a specificationto make it easier for automated tools to detect and summarize well knownopensource licenses. We are gradually adopting the specification, notingthat the tags are considered only advisory and do not, in any way,superceed or replace the license texts.No functional change intended.
DIRDEPS_BUILD: Update dependencies.Sponsored by: Dell EMC Isilon
When doing a non-interactive installation, don't display an interactivewarning about a filesystem which doesn't have a mountpoint. Presumably, theperson who wrote the install script knew what they
When doing a non-interactive installation, don't display an interactivewarning about a filesystem which doesn't have a mountpoint. Presumably, theperson who wrote the install script knew what they were doing.Submitted by: Brian Mueller <[email protected]>MFC after: 1 monthSponsored by: PanasasDifferential Revision: https://reviews.freebsd.org/D12346
bsdinstall: correct comment after r320007Submitted by: vangyzen
bsdinstall: use consistent EFI configuration across platforms- increase arm64 EFI partition to 200M, as x86- use EFI_BOOTPART_SIZE and EFI_BOOTPART_PATH macros on x86- increase ZFS EFI partition
bsdinstall: use consistent EFI configuration across platforms- increase arm64 EFI partition to 200M, as x86- use EFI_BOOTPART_SIZE and EFI_BOOTPART_PATH macros on x86- increase ZFS EFI partition to 200MPR: 201898Reviewed by: allanjude, manuMFC after: 3 daysSponsored by: The FreeBSD FoundationDifferential Revision: https://reviews.freebsd.org/D11239
1234