| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix an error where vfs.root.mountfrom was not always set as required
when creating a bootpool. After the recent geliboot changes, it was only
set if the main pool was encrypted.
Also resolve an error where the bootpool was unmounted twice causing
bsdinstall to stop with an error message about the failed command.
Approved by: re (gjb)
Sponsored by: BSDCan Hacker Lounge
|
|
|
|
|
|
|
|
|
| |
Allow to setup country and/or regulatory domain before scanning
(since channel list is affected by regulatory restrictions this may
impact scan results).
PR: 182600 (originally)
Differential Revision: https://reviews.freebsd.org/D6325
|
|
|
|
|
|
|
| |
This fixes regression introduced in r298946 (fixes static address
assignment for wireless networks).
Reported & submitted by: allanjude
|
|
|
|
| |
Sponsored by: ScaleEngine Inc.
|
|
|
|
| |
Sponsored by: ScaleEngine Inc.
|
|
|
|
|
|
| |
This step is required in order to dd the boot2 bits into the ZFS partition
Sponsored by: ScaleEngine Inc.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Do not set canmount=noauto on the boot environment at create time, because
this causes / to not be mounted, and since the chroot is read only, new
mountpoints cannot be created.
The property is set later, when other properties are adjusted
Reported by: HardenedBSD
Sponsored by: ScaleEngine Inc.
|
|
|
|
|
|
|
|
|
|
|
|
| |
In this configuration, a separate bootpool is not required.
This allows ZFS Boot Environments to be used with GELI encrypted ZFS pools.
Support for GPT+EFI+GELI is planned for the future.
Tested by: Joseph Mingrone, HardenedBSD
Relnotes: yes
Sponsored by: ScaleEngine Inc.
Differential Revision: https://reviews.freebsd.org/D5869
|
|
|
|
|
|
|
|
|
| |
The root file system is mounted early via vfs.root.mountfrom.
The canmount=noauto property only affects the zfs rc.d script.
This ensures that the 'default' BE is not mounted overtop of another BE when
one is selected from the beastie menu
Sponsored by: ScaleEngine Inc.
|
|
|
|
| |
Submitted by: Colby Swandale <colby@taplaboratories.com.au> (via github)
|
|
|
|
|
|
| |
PR: 209415
Submitted by: Ganael LAPLANCHE <ganael.laplanche@corp.ovh.com>
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
Filter out IFCONFIG_PREFIX variable (which may contain WPA keyword)
from ifconfig parameters.
PR: 169199
|
|
|
|
| |
No functional change.
|
|
|
|
|
|
|
|
|
|
|
| |
Installs both pmbr+gptzfsboot as well as boot1.efifat in separate partitions
The resulting system can be booted with either UEFI or BIOS/CSM.
Preference is controlled by the user's firmware boot settings.
This is now the default for zfsboot installs
PR: 208629
Submitted by: Galael LAPLANCHE <ganael.laplanche@corp.ovh.com> (original version)
|
|
|
|
|
|
|
| |
PR: 208629
PR: 208568
Submitted by: Galael LAPLANCHE <ganael.laplanche@corp.ovh.com>
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
If a user requested encrypted swap, but 0 sized, it would still be added to fstab
PR: 208630
Submitted by: Ganael LAPLANCHE <ganael.laplanche@corp.ovh.com>
MFC after: 2 weeks
Sponsored by: ScaleEngine Inc.
|
|
|
|
|
|
|
|
| |
Remove the requirement that the resulting partition table be atleast 50% ZFS
PR: 208094
Requested by: brooks
Sponsored by: ScaleEngine Inc.
|
|
|
|
|
|
| |
MFC after: 3 days
Sponsored by: ScaleEngine Inc.
Differential Revision: https://reviews.freebsd.org/D4960
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the bootpool does not start at the first sector of the BSD partition
then zfsldr seeks to the wrong offset inside the ZFS vdev label, and is
unable to find zfsboot, so the system does not boot
If 4k alignment is requested, align the BSD partition in the MBR table,
and align the swap and data pool, but the bootpool must start at sector 1
While here, if 4k alignment is requested, disable MBR CHS alignment, as
this results in not-4k aligned partitions.
Reported by: Alex Wilkinson
MFC after: 5 days
Sponsored by: ScaleEngine Inc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Dell Precision Tower 5810 fails to boot from GPT in Legacy/BIOS mode
without the Active flag in the Protective MBR. Suggest the workaround
during installation.
Since an increasing number of Dell systems exhibit this behavior,
I imagine all Dells past a certain date will do so. I would like
to suggest the workaround for all Dells with a BIOS date of, say,
2014 or later, but I would need to test a variety of systems before
committing such a change.
Reviewed by: allanjude, dteske
MFC after: 5 days
Relnotes: We should probably suggest using GPT+Active on "recent" Dells.
Sponsored by: Dell Inc.
Differential Revision: https://reviews.freebsd.org/D4075
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Rework MANIFEST generation and parsing via bsdinstall(8).
- Allow selecting debugging distribution sets during install.
- Rework bsdinstall(8) to fetch remote debug distribution sets
when they are not available on the local install medium.
- Allow selecting additional non-GENERIC kernels during install.
At present, GENERIC is still required, and installed by default.
Tested with: head@r293203
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
|
|
|
| |
Differential Revision: https://reviews.freebsd.org/D3933
Submitted by: jmg
Reviewed by: delphij, markm
Approved by: secteam (delphij)
MFC after: 3 days
X-MFC-to: stable/10 stable/9
|
|
|
|
| |
ifconfig anymore.
|
|
|
|
|
| |
MFC after: 1 week
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
|
|
| |
PR: 194359
Approved by: bapt (mentor)
MFC after: 2 weeks
Sponsored by: ScaleEngine Inc.
Differential Revision: https://reviews.freebsd.org/D3525
|
|
|
|
|
|
| |
MFC after: 3 days
X-MFC-to: stable/10
Pointy hat to: me
|
|
|
|
|
| |
MFC after: 3 days
X-MFC-to: stable/10
|
|
|
|
|
| |
MFC after: 3 days
X-MFC-to: stable/10
|
|
|
|
|
| |
MFC after: 3 days
X-MFC-to: stable/10
|
|
|
|
|
| |
MFC after: 3 days
X-MFC-to: stable/10
|
|
|
|
|
| |
MFC after: 3 days
X-MFC-to: stable/10
|
|
|
|
|
| |
MFC after: 3 days
X-MFC-to: stable/10
|
|
|
|
|
| |
MFC after: 3 days
X-MFC-to: stable/10
|
|
|
|
|
| |
MFC after: 3 days
X-MFC-to: stable/10
|
|
|
|
|
| |
MFC after: 3 days
X-MFC-to: stable/10
|
|
|
|
|
| |
MFC after: 3 days
X-MFC-to: stable/10
|
|
|
|
|
| |
MFC after: 3 days
X-MFC-to: stable/10
|
|
|
|
|
|
|
| |
distribution sets.
MFC after: immediately
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
|
|
|
|
|
|
| |
GPT active workaround
PR: 194359
Requested by: sbruno, hiren
Approved by: marcel
MFC after: 3 days
Relnotes: yes
Sponsored by: ScaleEngine Inc.
Differential Revision: https://reviews.freebsd.org/D3139
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
on some hardware
For Lenovo laptops with buggy bios (x220, t420, t520):
Write the 0xee entry into the second slot in the pmbr instead of the first
For some Dell and HP models:
The BIOS gives a warning message when booting in legacy mode from a GPT partitioned disk where the 0xee partition in the pmbr is not flagged active
For models known to have this problem, mark the pmbr active during installation
Use smbios data to identify machines known to be affected by any of the above, and offer the user the option to apply the workaround
In bsdinstall's ufs auto mode (autopart partition wizard):
Allow users to select which type of partition table to use
Keep current defaults: MBR for BIOS, GPT for UEFI
This allows users to choose GPT for legacy boot if they wish
PR: 184910
PR: 194359
Reviewed by: Michael Dexter
Approved by: marcel
MFC after: 3 days
X-MFC-With: r285594
Relnotes: yes
Sponsored by: ScaleEngine Inc.
Differential Revision: https://reviews.freebsd.org/D3091
|
|
|
|
|
|
|
|
|
|
|
|
| |
requests it
PR: 195174
Reviewed by: darius
Approved by: brueffer
MFC after: 3 days
Relnotes: yes
Sponsored by: ScaleEngine Inc.
Differential Revision: https://reviews.freebsd.org/D3062
|
|
|
|
|
|
|
|
|
|
|
| |
mountpoint to inherit
Reviewed by: darius
Approved by: brueffer
MFC after: 3 days
Relnotes: yes
Sponsored by: ScaleEngine Inc.
Differential Revision: https://reviews.freebsd.org/D3063
|
|
|
|
|
|
|
|
|
|
|
| |
not part of the OS boot environment
PR: 199864
Submitted by: Jason Unovitch
Approved by: brueffer
MFC after: 3 days
Relnotes: yes
Differential Revision: https://reviews.freebsd.org/D2861
|
|
|
|
|
|
|
|
|
|
|
| |
A variable was misspelled resulting in chmod executing on the installer instead of on the target chroot
PR: 191402
Submitted by: Martin Simmons <martin@lispworks.com>
Approved by: brueffer
MFC after: 3 days
Sponsored by: ScaleEngine Inc.
Differential Revision: https://reviews.freebsd.org/D3061
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Off by default, build behaves normally.
WITH_META_MODE we get auto objdir creation, the ability to
start build from anywhere in the tree.
Still need to add real targets under targets/ to build packages.
Differential Revision: D2796
Reviewed by: brooks imp
|
| | |
|
| |\
| |/
|/| |
|