FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=main 2025-07-16T15:04:03Z 2025-07-16T15:04:03Z Bojan Novković bnovkov@FreeBSD.org 2025-06-24T15:17:36Z urn:sha1:483ef23ebb7235059c30db86588e178cdeb80097 This change cleans up the inconsistent ways of invoking makefs and mkimg by making sure that these tools are invoked through their corresponding variables. This was previously only used in a few amd64 and arm64 release scripts. Sponsored by: Klara, Inc. Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D51039 Reviewed by: emaste, markj 2023-08-16T17:55:03Z Warner Losh imp@FreeBSD.org 2023-08-16T17:55:03Z urn:sha1:d0b2dbfa0ecf2bbc9709efc5e20baf8e4b44bbbf Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/ 2022-02-28T22:37:37Z Jessica Clarke jrtc27@FreeBSD.org 2022-02-28T22:37:37Z urn:sha1:1a9b1c367fa606c7850cfc876bf73a1e1129279a This requires two sets of changes. Firstly, for non-FreeBSD, we do not know where tools are in PATH (and it is likely that some are not in system directories and have been built as bootstrap tools during the build), so we should leave PATH alone and trust the user. Secondly, makefs needs a master.passwd for building images from a METALOG file, so pass the directory in the image tree to makefs's -N option in order to pick up a valid FreeBSD master.passwd; this is unnecessary on FreeBSD (except in the edge case of building an image that refers to users or groups not present in the host's database, which is unlikely but technically possible) but harmless so can be done unconditionally. Reviewed by: brooks, emaste, gjb Differential Revision: https://reviews.freebsd.org/D34001 2022-02-28T22:37:03Z Jessica Clarke jrtc27@FreeBSD.org 2022-02-28T22:37:03Z urn:sha1:13cb004130d2b62f79fe421eaf4a7973efd6a505 This requires a bunch of METALOG mangling to include the files we inject into the tree. The mkisoimages.sh and make-memstick.sh scripts are now called with the current directory inside the tree so that the relative paths in the METALOG match up with the current directory. The scripts do not require this when not using a METALOG, but for simplicity we always do so. The Makefile mangles the real METALOG created from the install, as those files are shared across all uses of the tree, but the shell scripts create a temporary copy of the METALOG that they mangle as their tree modifications are specific to that image. We also need to pass -D to makefs to turn any duplicate METALOG entry errors into warnings, as we have many (harmless) instances of those. Whilst dvd1.iso should work, the !NOPKG code will need more work to support this. All media will also lack mergemaster and etcupdate trees, since more work is needed to add -DNO_ROOT modes to them. Users of install media built this way will have to manually bootstrap them. Reviewed by: brooks, gjb Differential Revision: https://reviews.freebsd.org/D33999 2020-05-24T18:25:49Z Ed Maste emaste@FreeBSD.org 2020-05-24T18:25:49Z urn:sha1:05f2347421781b4a9ca5de94c3dc9ada70bb6e84 This reverts the i386 part of r342283, "Rework UEFI ESP generation", and the followup commit in r342690. r342283 added an ESP to the i386 memstick image, and as a side effect made the ESP the active partition, not the bootcode-containing UFS partition. As a result the i386 memstick images would not boot in either UEFI or legacy mode - UEFI failed because we do not support i386 UEFI booting, and legacy mode failed because the partition with legacy bootcode was not active. The bootcode-containing UFS partition is again the only, and active, partition. PR: 246494 Reported by: Jorge Maidana Differential Revision: The FreeBSD Foundation 2019-01-02T16:22:33Z Glen Barber gjb@FreeBSD.org 2019-01-02T16:22:33Z urn:sha1:252373ac4c91c26829c0c0e8505ea1c8b63047c1 Sponsored by: The FreeBSD Foundation 2018-12-20T19:39:37Z Rebecca Cran bcran@FreeBSD.org 2018-12-20T19:39:37Z urn:sha1:db8b56134506840832bec2d1ce07b9e00d4d6d71 Currently, the installer uses pre-created 800KB FAT12 filesystems that it dd's onto the ESP partition. This changeset improves that by having the installer generate a FAT32 filesystem directly onto the ESP using newfs_msdos and then copying loader.efi into /EFI/freebsd. For live installs it then runs efibootmgr to add a FreeBSD boot entry in the BIOS. Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D17947 2018-10-22T19:39:20Z Ed Maste emaste@FreeBSD.org 2018-10-22T19:39:20Z urn:sha1:a7d9306a40a7cfd6f82191559b99731cf3dc7f1a Reviewed by: gjb Differential Revision: https://reviews.freebsd.org/D17651 2018-04-12T19:00:22Z Ed Maste emaste@FreeBSD.org 2018-04-12T19:00:22Z urn:sha1:bf249c5a0a273663367995eb70b0fea4f464f21c Some BIOSes have trouble booting from GPT in non-UEFI mode. This is commonly reported with Lenovo laptops, including my x220. As we do not currently support booting FreeBSD/i386 via UEFI there's no reason to prefer GPT. The "vestigial swap partition" was added in r265017 to work around an issue with loader's GPT support, so we should not need it when using MBR. We may want to make the same change to amd64, although the issue there is mitigated by such systems booting via UEFI in the common case. PR: 227422 Reviewed by: gjb MFC after: 3 weeks Relnotes: Yes Sponsored by: The FreeBSD Foundation 2018-04-10T19:49:04Z Ed Maste emaste@FreeBSD.org 2018-04-10T19:49:04Z urn:sha1:8ea90e075c2d9467dc4f294cc69eba7acdf98cf8 This makes it easier to identify the individual partition types and facilitates comparisons across architectures. Reviewed by: gjb MFC after: 1 week Sponsored by: The FreeBSD Foundation