summaryrefslogtreecommitdiff
path: root/release
Commit message (Collapse)AuthorAgeFilesLines
* Switch from "quarterly" to "release" pkgs on DVDColin Percival2026-02-261-1/+1
| | | | | Approved by: re (implicit) Sponsored by: OpenSats Initiative
* pkg-stage.sh: Add ext2 and ntfsColin Percival2026-02-261-0/+2
| | | | | | | | | | | | Having these packages available on release media may help users who need to sneakernet other packages (e.g. firmware) from systems running Linux or Windows. Suggested by: vladlen, ziaee MFC after: 3 days (cherry picked from commit 6881fd278d80ac63b4d511fc130a79ff16d1bb48) (cherry picked from commit a2c2de82c053ba7596f90ebf7d7ea6cb41938587)
* pkg-stage.sh: Add emacs@nox and vimColin Percival2026-02-261-0/+2
| | | | | | | | | | | | | | | We have a bit of space left on the 14.4 DVDs; add packages for two editors, one of which is useful. Direct commit to stable/14: These packages were added to 15.0 but at the same time as removing kde, because shipping distribution sets *and* a pkgbase repository on 15 significantly cuts into the space available. On 14 we can keep kde and still add these packages. With hat: re MFC after: 3 days (cherry picked from commit d982b7bd4ebfa483a8fa03411fa798add225e6f5)
* release: Turn off debugging in pkg(8)Colin Percival2026-02-121-1/+1
| | | | | | | | | | | | | | Running `pkg -d` in pkg-stage.sh results in multiple GB of network traffic being written into the log files, which is less than helpful when it comes to tracking down build failures. Remove the -d flag. Approved by: re (cperciva) MFC after: 5 days X-MFC-note: The code in 15 has diverged from 14, but the flag is there, just in a different place. (cherry picked from commit 18721be356043f6749a6e2470bc9f7351c450c6e) (cherry picked from commit 721dfa7e5a34e04c463f5afec91df80ba755cdbc)
* Revert "release: Ship firmware from kmods repo on DVD"Colin Percival2026-02-062-25/+7
| | | | | | | | | | | | | | | | | | | | While all of the net/wifi-firmware-*-kmod packages are in the "kmod" pkg repository, the net/wifi-firmware-kmod metapackage itself is not; this results in the DVD build failing when it can't fetch that. I'm not sure if the correct fix here is to add kmod-related metapackages to the kmod repository (even if they themselves do not contain kmods) or something else; but this needs to be backed out at least temporarily so that 14.4-BETA1 can happen. This reverts commit 8c1de31097763ce1d918a3f82c61fd8d30edbe75. This is a direct commit to releng/14.4 since it is not yet clear whether this should be permanently removed from other branches and there is no urgency to do so (since DVD builds are disabled by default). With hat: re Approved by: re (cperciva)
* 14.4: create releng/14.4 branchColin Percival2026-02-061-2/+2
| | | | | | | | | Update from PRERELEASE to BETA1 Switch pkg(8) configuration to use the quarterly repository Bump __FreeBSD_version Approved by: re (implicit) Sponsored by: OpenSats Initiative
* release: Ship firmware from kmods repo on DVDColin Percival2026-02-052-7/+25
| | | | | | | | | | | | | | | | | | The packages for X.Y-RELEASE are a snapshot of the quarterly branch for stable/X, i.e. typically built on X.(Y-1)-RELEASE. (The case of Y=0 is an exception for obvious reasons.) This works for most ports but not for kernel modules, which may need to be built on the release in question; this is why we have a separate "kmods" repository. Make sure that we put the packages from the kmods repository onto the mini-pkg-repo on the DVD rather than shipping unusable firmware. Reviewed by: bz MFC after: 1 week Sponsored by: https://www.patreon.com/cperciva Differential Revision: https://reviews.freebsd.org/D52581 (cherry picked from commit bda8028146694ee490543b35e3349e060936fde4)
* loader: Prefer comma-separated list of values for "console"Michael Osipov2026-02-052-2/+2
| | | | | | | | | PR: 292595 Reviewed by: imp MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D54923 (cherry picked from commit 56970c3c4b0bc61d972837661a31cc2b9e8e8d7c)
* powerpc: fix release image building for Apple partitionsAdrian Chadd2026-01-301-1/+1
| | | | | | | | | | | | | | | awk changed somewhere between 14 and 15 and it stopped accepting a hexadecimal number as its input - it will always return 0. This results in a very badly written apple boot block. So just remove it; do the math in shell. PR: kern/292341 Differential Revision: https://reviews.freebsd.org/D54639 Reviewed by: imp MFC after: 1 week (cherry picked from commit 7afa03963c448a14b1735a10eaf84941b0b74862)
* lualoader: Add distinct brand for installerJoseph Mingrone2026-01-281-0/+3
| | | | | | | | | | Make it obvious to users that the system is booting into the installer. Reviewed by: kevans, manu Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D51001 (cherry picked from commit ac7a19d41ee5eb1271c46fbc620b2f98dffa2230)
* GCE: ARM64 Support: Add hw.pci.honor_msi_blacklist=0.William Carrel2026-01-181-0/+3
| | | | | | | | | | | | | This is required for MSI support on GCE ARM64 instances which is prerequisite to gve(4) not panicking at boot, and nvme(4) also has a real sad time without interrupts. Tested on a variety of c4a VMs. This is meant to be a temporary hack; long term fix would be to check for the hypervisor and quirk gve(4) device with PCI_QUIRK_ENABLE_MSI_VM. PR: kern/292081 (cherry picked from commit 9ae43352c89c776c8171f5881a984bc39acf5d6a)
* release: make sh the default shellBaptiste Daroussin2026-01-142-2/+2
| | | | | | | | | | | | The default shell for root has been changed to sh(1) followup changing in release images sh(1) the shell for the "freebsd" user. MFC After: 1 week Reviewed by: manu, emaste (re) Approved by: manu, emaste (re) Differential Revision: https://reviews.freebsd.org/D54602 (cherry picked from commit d64db8892f8519f108d838f8d7e1d3b675ed37cd)
* release: stop disabling sendmailBaptiste Daroussin2026-01-145-20/+0
| | | | | | | | | | | sendmail is already disabled by default everywhere since 14.0 MFC After: 1 week Approved by: emaste (re) Reviewed by: emaste (re) Differential Revision: https://reviews.freebsd.org/D54575 (cherry picked from commit d07198ff72aeddc5a884cfb81b22c22f2abf88f6)
* GCE: Fix growfs pathWilliam Carrel2026-01-101-1/+1
| | | | | | | | | | | The sed command was missing the ${DESTDIR} prefix, meaning it was attempting to modify the build host's /etc/rc.d/growfs instead of the target image's script. Tested in an arm64 builder that builds as non-root. PR: kern/292081 (cherry picked from commit 709c1049fe0c6d0217e81268d4f33f7191474453)
* GCE: Enable vtnet(4) Multiqueue.William Carrel2026-01-101-1/+0
| | | | | | | | | | | | | | | | Removes hw.vtnet.mq_disable=1. This workaround was originally introduced nearly a decade ago to address stability issues on KVM that have long since been resolved in both the FreeBSD driver and the GCE hypervisor. Removing this allows network interrupts to scale across multiple vCPUs. Tested on n2-highcpu-16 VM with 15.0-RELEASE and confirmed multiple queue pairs active and interrupts handling across cores. PR: kern/292081 (cherry picked from commit f604d84618ad478fa46ec374480cbcbc1d93bf07)
* GCE: Don't .error on unsupported targetsColin Percival2025-12-291-1/+1
| | | | | | | | | | | | We ingest Makefile.gce even when we're not trying to create GCE images so we don't want to .error here. Instead, set GCE_ARCH to a dummy value which should make the problem clear to anyone who attempts to create GCE images on an unsupported architecture. Reported by: Jenkins Fixes: 0a8ecca4e315 ("GCE: Specify the architecture of images") (cherry picked from commit 787d09753f70bb382a7cbfba742a612fa54069e6)
* GCE: Specify the architecture of imagesAndrew Jorgensen2025-12-291-0/+9
| | | | | | | | Without a specified architecture, a user can attempt to create an arm64 instance with an amd64 image or vice versa. With the change the API will prevent that mismatch. (cherry picked from commit 0a8ecca4e3156bcd4ebbfcb24d968e67a3a09434)
* GCE: Add TARGET and FS to image familyAndrew Jorgensen2025-12-291-2/+2
| | | | | | | | | | | | | GCE image family is meant to be unique per set of image characteristics so that a user can create instances using the image family instead of the image name to reliably get a similar image with updated software, but no other changes. Without this change, the instances create API would select the most recent non-deprecated image matching the name, regardless of architecture or filesystem. (cherry picked from commit fc83e6c5e1f20087314dc52b63e485db87a98b86)
* release: Include comms/usbmuxd to DVD to ensure ipheth(4) worksLi-Wen Hsu2025-12-081-0/+1
| | | | | | | | | | PR: 291370 Reviewed by: emaste, aokblast, dch MFC after: 3 days Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D54074 (cherry picked from commit 90eda629964cbe4c2472aa3f1b8a427e60e78834)
* release: Comply with Azure Marketplace requirements for aarch64Li-Wen Hsu2025-11-081-1/+5
| | | | | | | | | | | | | | | | | Azure requires the first 1 MB (2,048 sectors) of the OS disk to remain empty for VM images: https://learn.microsoft.com/partner-center/marketplace-offers/azure-vm-certification-faq#vm-images-must-have-1-mb-of-free-space Also append the BOOTPARTSOFFSET suffix for aarch64 images, which only has an ESP partition for booting. Co-authored-by: Brad Davis <brd@FreeBSD.org> Approved by: cperciva Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D53628 (cherry picked from commit 36095c942031f7f1613eec554f1c7615cbd891fd)
* release/RPI: Add RPI Zero 2W device tree blob dtbYoshiro MIHIRA2025-10-101-2/+3
| | | | | | | | | | | Enable Pi 02W support on the release SD card images by including the device tree. PR: 278816 MFC after: 3 days Approved by: cperciva (re) (cherry picked from commit e41e099ef199de096abd9a93289bdacfd83a5f48)
* release: remove the RPI CM4s .dtbKyle Evans2025-10-101-1/+1
| | | | | | | | | | This isn't actually packaged by the sysutils/rpi-firmware port, so we cannot include it in the image. Fix the RPI release build until an interested party adds it to the port and packages are available. Reported by: cperciva (cherry picked from commit 9245ced9c8357d876141975a6431ce34143d2753)
* add dtb support for RPI CM4, CM4s, CM4_ioBoardKlaus Küchemann2025-10-101-1/+2
| | | | | | | Signed-off-by: Klaus Küchemann <maciphone2@googlemail.com> Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/1182 (cherry picked from commit 1bd4f769caf8ffda35477e3c0b2c92348cf2fd5d)
* release: Remove a duplicate package listing in oracle.confMark Johnston2025-09-211-1/+0
| | | | | | | | | | sysutils/panicmail is specified again several lines down. MFC after: 1 week Sponsored by: The FreeBSD Foundation Sponsored by: Klara, Inc. (cherry picked from commit cc6e21cb946337e2b4584dd2b55209d45805fec2)
* release: Fix typo in powerpc mkisoimages.shColin Percival2025-09-181-1/+1
| | | | | | | | | | | | | "[ n foo ]" is an error and should have been "[ -n foo ]". Fortunately the only ill effect was to result in garbage in /tmp/ when creating powerpc ISO images. Fixes: 6c3e01bf8578 ("release: Randomize powerpc boot block file name") MFC after: 3 days Sponsored by: https://www.patreon.com/cperciva (cherry picked from commit 8c9a919abaa3f6f16a17586ca72bab939788bf69)
* Remove cached FreeBSD-kmods repo from cloudwareColin Percival2025-09-043-0/+3
| | | | | | | | | This is a direct commit to stable/14 but corresponds to part of 778bfd4e1033, which both chased the renaming of repositories in /etc/pkg/FreeBSD.conf and added cleanup of the FreeBSD-ports-kmods repository database (which is just "FreeBSD-kmods" on stable/14). Fixes: 8a2ce9f9dd67 ("pkg.conf: Use kmod repositories")
* packages: fix ownership of /tmp and /devLexi Winter2025-08-231-5/+0
| | | | | | | | | | | | | | | | | | | | | release/packages/runtime.ucl manually adds "/tmp" and "/dev" to the "directories" key, which causes them to be included in the manifest with the user/group owner of whoever built the package repository: drwxr-xr-x 7 ivy wheel 512 Jun 1 17:24 /dev drwxrwxrwt 10 ivy wheel 10 Jun 1 17:42 /tmp Remove the manual entries and instead put an explicit package tag in etc/mtree/BSD.root.dist. This also means /tmp gets the right mode by default and we can remove the chmod from the post-install script. PR: 288746 Reviewed by: manu, kevans, emaste Approved by: kevans (mentor) Differential Revision: https://reviews.freebsd.org/D50636 (cherry picked from commit 6b2993e74ebaacd46bd1e438787c23450cd2752d)
* bsd.files.mk: Fix FILESPACKAGELexi Winter2025-08-231-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Because TAGS may already have a package tag, assigning TAGS to FILESTAGS causes the value of FILESPACKAGE to be ignored. Only assign tags other than package, and take the default package from ${PACKAGE}, which matches the behaviour of bsd.confs.mk and bsd.man.mk. This fixes several files that were wrongly installed in utilities, including /usr/share/examples/sendmail/mailer.conf and some files in /usr/share/nls. The fix trips a bug in share/syscons where Makefile.inc was setting FILESPACKAGE to the wrong package, but the problem was hidden because the subdirectories set PACKAGE explicitly. Fix this by setting the correct FILESPACKAGE in Makefile.inc and removing the PACKAGEs. In stable/14, this creates a new FreeBSD-examples package, so add an entry to Makefile.packages. Reviewed by: manu Differential Revision: https://reviews.freebsd.org/D51784 (cherry picked from commit 1e629ebb15db9ee0cb11a3654d7bcd3046a0df54)
* release: Install wireless firmware to bootonly mediaJoseph Mingrone2025-07-201-0/+4
| | | | | | | | | | | | | Also install wireless firmware packages to the bootonly ISO and the mini-memstick image so users can fetch installation files over a wireless connection. Reported by: Mark Philips <mark@freebsdfoundation.org> Reviewed by: bz, emaste, imp, releng (cperciva) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D51348 (cherry picked from commit 655fcdde1aff164a3a02ad073334611117e20d4c)
* release/pkg-stage: Put each package on a separate lineEd Maste2025-06-171-2/+4
| | | | | | | | | | | | | The list of packages included in dvd1.iso is maintained in pkg-stage.sh itself, and sees regular additions and deletions. Rearrange the beginning and end of the variable so that each package is alone on a line, to make it easier to track changes. Reviewed by: cperciva Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D50221 (cherry picked from commit 16d0fe1f721f63d15c741ff4c0072390aaa27e73)
* package: fix dependency generationLexi Winter2025-05-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | A bug in release/packages/generate-ucl.sh causes package dependencies (other than shlib depends) to not be generated correctly, meaning packages are missing their dependencies. generate-ucl.sh creates the UCL file by: 1. copying ${uclsource} (template.ucl) to ${uclfile} 2. appending dependencies to ${uclfile} 3. calling generate-ucl.lua on ${uclsource} to create ${uclfile} This breaks because the dependencies added in step 2 are overwritten in step 3. Fix this by calling generate-ucl.lua with ${uclfile} as both the input and output file, so anything we added to ${uclfile} is preserved. PR: 286551 Reviewed by: des, imp Approved by: kevans (mentor, stable/14 mfc) Pull Request: https://github.com/freebsd/freebsd-src/pull/1203 (cherry picked from commit e05b6502f9ca36860236644884f12eff8e3243c4)
* EC2: Remove old broken_txfifo workaroundColin Percival2025-05-141-5/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Early versions of Xen, including those used in the early days of EC2, had a bug in their UART emulation whereby the TX FIFO wouldn't send the expected interrupt when emptying; as a result, FreeBSD would write 16 characters to the serial console and then stop because we thought the FIFO was forever full. In 2013 (1c60b24baa50) I added a loader tunable "hw.broken_txfifo" which spinwaits for the FIFO TX rather than relying on the interrupt, and enabled this in loader.conf in EC2 images. A decade later, this workaround is almost certainly no longer needed in EC2 -- most instances don't run Xen, and the bug was long since fixed in Xen anyway -- but we've been holding on to the workaround "just in case". Unfortunately, the spinwait behaviour is causing latency spikes and triggering warnings from the ena(4) driver. This commit removes the hw.broken_txfifo setting from loader.conf in EC2 images, but leaves the loader tunable and associated code, since it has been necessary in some other environments. (It seems that the TX FIFO missing-interrupts bug has been independently written at least three times!) MFC after: 1 minute Sponsored by: Amazon (cherry picked from commit 9a685c09f06a55b18589d75f9307563d84a17fa9)
* release: Don't put drm-kmod package onto DVDColin Percival2025-05-111-3/+0
| | | | | | | | | | | The X.Y-RELEASE DVDs use a quarterly package set which was built on X.(Y-1)-RELEASE, and those kernel modules are never going to be useful. MFC after: 30 seconds Sponsored by: Amazon (cherry picked from commit 94e44a074e5212cc3459e360a9de55500f7c41d0)
* pkg-stage.sh: kde5 -> kdeColin Percival2025-05-111-1/+1
| | | | | | | | | | | | | The "kde5" package no longer exists; KDE goes to 6. Note: Depending on the size of 13.5-BETA3 DVD images, KDE might end up being removed from this list in the near future. With hat: re@ MFC after: 30 seconds Sponsored by: Amazon (cherry picked from commit 0d7b98c06c5ec9638020844ee460af075cfc6e54)
* release: use "runtime" instead of "minimal" for OCI image nameDave Cottlehuber2025-04-302-2/+2
| | | | | | | | | | | | The runtime name is taken from the main pkg-base package that this image is built off. Sponsored by: SkunkWerks, GmbH MFC after: 3 days Reviewed by: dfr, emaste Differential Revision: https://reviews.freebsd.org/D50043 (cherry picked from commit a0165254bfeb5e310f92d4e0c88fcb5c6ea802bf)
* Turn off hw.pci.intx_reroute in EC2Colin Percival2025-04-261-0/+6
| | | | | | | | | | Having this enabled on Graviton systems prior to Graviton 4 results in a resource leak and a kernel panic after repeated hotplug/unplug. MFC after: 3 days Sponsored by: Amazon (cherry picked from commit ce9a34b1614e37dc3f8763586448063408c7bf16)
* release: Pass PKG_INSTALL_EPOCH (take 2)Colin Percival2025-04-261-0/+1
| | | | | | | | | | We need to pass this to cloudware builds, not just VM builds. MFC after: 4 days Fixes: 81ca663642ef ("release: Pass PKG_INSTALL_EPOCH to vmimage.subr") Sponsored by: Amazon (cherry picked from commit d14036ea424d5aa3eee20cc6f0b5d7117cc3931b)
* release: Pass PKG_INSTALL_EPOCH to vmimage.subrColin Percival2025-04-262-3/+7
| | | | | | | | | | | | | | | | This value, if not already set, comes from the timestamp of the most recent git commit (which is now also available in src/release code as GITEPOCH) or 0 if git is not installed. This should allow /var/db/pkg/local.sqlite to be reproducible in VM images which have packages installed (e.g. cloudware). Reviewed by: emaste, bapt MFC after: 5 days Sponsored by: Amazon Differential Revision: https://reviews.freebsd.org/D49760 (cherry picked from commit 81ca663642ef1ed5111a88d2e9102f6788fab407)
* EC2: Add AMI Builder AMI buildingColin Percival2025-04-264-2/+207
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Starting in 2015 I have published "AMI Builder AMIs" for FreeBSD/EC2: These boot into a memory disk, extract a "clean" copy of FreeBSD onto the root disk, mount it at /mnt, and allow the user to SSH in to make customizations before creating a new AMI from the "running" instance (in fact, from the FreeBSD installation which is not running but is mounted on /mnt). This provides a much cleaner mechanism for building customized FreeBSD AMIs than the traditional Linux approach of "launch an EC2 instance, SSH in and configure it, then try to wipe logs and credentials before creating an AMI"; and it's easier than building a customized AMI ab initio by modifying the FreeBSD release-building code. This commit brings that functionality into the FreeBSD src tree and into the collection of images built by the release engineering team: The EC2 "BUILDER" flavour AMI is essentially a "SMALL" flavour AMI with a compressed "BASE" flavour disk image, plus an init script which juggles disks around (rerooting into a memory disk and extracting the "BASE" image onto disk). Polished by: bz, emaste MFC after: 1 week Sponsored by: Amazon Differential Revision: https://reviews.freebsd.org/D49930 (cherry picked from commit 58426589030308cd632477d328b9536b1634c54d)
* EC2: Set PCIe eject timeout to 0Colin Percival2025-04-161-0/+6
| | | | | | | | | | | Since PCIe device detaching is done via API, there is no opportunity to "press the attention button a second time" and thus the 5 second timeout mandated by PCIe serves no purpose. MFC after: 2 weeks Sponsored by: Amazon (cherry picked from commit 80febaa1714e897d67a8217edc305a0e81498a6f)
* release: avoid sparse-file handling for container image layersDoug Rabson2025-04-151-2/+7
| | | | | | | | | This improves compatiblity with Podman. See https://github.com/containers/podman/issues/25270 for details. Differential Revision: https://reviews.freebsd.org/D49821 (cherry picked from commit 3a79ca65531adf9fc8799b39407fe4d1b51906f6)
* acpi_pci: Add quirk for DELAY-after-EJ0Colin Percival2025-04-141-2/+3
| | | | | | | | | | | | | | | | | | | | | | | On some EC2 instances, there is a race between removing a device from the system and making the PCI bus stop reporting the presence of the device. As a result, a PCI BUS_RESCAN performed immediately after the _EJ0 method returns "sees" the device which is being ejected, which then causes problems later (e.g. we won't recognize a new device being plugged into that slot because we never knew it was vacant). On other operating systems the bus is synchronously marked as needing to be rescanned but the rescan does not occur until O(1) seconds later. Create a new ACPI_Q_DELAY_BEFORE_EJECT_RESCAN quirk and set it in EC2 AMIs, and add a 10 ms DELAY between _EJ0 and BUS_RESCAN when tht quirk is set. Reviewed by: jhb MFC after: 1 month Sponsored by: Amazon Differential Revision: https://reviews.freebsd.org/D49252 (cherry picked from commit 55c3348ed78fb1d0891e8bb51a8948f95da3560b)
* release: add cloudware oracle targets to package and upload .oci filesDave Cottlehuber2025-04-087-0/+318
| | | | | | | | | | | | - requires base tar & flua, qemu-tools & curl from ports - set ORACLE_PAR_URL to upload to local file:/// dir or cloud buckets Reviewed by: emaste Approved by: cperciva Differential Revision: https://reviews.freebsd.org/D48382 Sponsored by: SkunkWerks, GmbH (cherry picked from commit 0ce9a414adc33af29607adbd81e0760e014fcd76)
* release: ensure default sudo flavor is selectedDave Cottlehuber2025-04-082-2/+2
| | | | | | | | | | | | | pkg behaviour selects the non-default flavour, this trims 0,5GiB per cloudware image, by being explicit. Approved by: cperciva Differential Revision: https://reviews.freebsd.org/D48599 Sponsored by: SkunkWerks, GmbH PR: 284278 MFC after: 10 days (cherry picked from commit 457d745d90a6b63793c9ca17bcd7ec5ff4cd8b93)
* acpi_pci: Add quirk for PSTAT_PME-before-detachColin Percival2025-04-011-2/+5
| | | | | | | | | | | | | | | | | | | | | | | In order to signal to Graviton [123] systems that a device is ready to be "ejected" (after a detach request is made via the EC2 API) we need to set PCIM_PSTAT_PME to 1 and PCIM_PSTAT_PMEENABLE to 0. We are not aware of any rationale for this requirement beyond "another OS kernel happens to do this", i.e. this is effectively bug-for-bug compatibility. Arguably this should be done by the ACPI _EJ0 method on these systems, but it is not. Create a new ACPI_Q_CLEAR_PME_ON_DETACH quirk and set it in EC2 AMIs, and add the PCI register write to acpi_pci_device_notify_handler when that quirk is set. Reviewed by: jhb MFC after: 1 month Sponsored by: Amazon Differential Revision: https://reviews.freebsd.org/D49146 (cherry picked from commit d70bac252d30adec4feba0c866dabe2c16a756d9)
* Copy the new ia32 loaderAhmad Khalifa2025-03-262-2/+12
| | | | | | | | | | | | | | | | | | 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 (cherry picked from commit 599273f942b8dc6f957487bb28f36694dab9dad2)
* release: build OCI images with shell scriptsDoug Rabson2025-03-046-58/+99
| | | | | | | | | | This avoids the need for buildah and skopeo for building releases. Reviewed by: cpersiva MFC after: 1 day Differential Revision: https://reviews.freebsd.org/D48574 (cherry picked from commit e8a5b9fd73f4f437a03c85e7644daa55652e224b)
* ports/filesystems: Fix falloutAlexander Ziaee2025-02-271-1/+1
| | | | | | | | | | | | | | | A new filesystems category was created in the ports tree, with 142 filesystem related ports moved to there, some of them renamed. Update all references in the src tree to the new locations. PR: 283881 Fixes: ports:6e2da9672f79f44 (filesystems: add new category) MFC after: 1 month Reviewed by: fuz, mhorne, bapt Accepted by: mhorne (mentor) Differential Revision: https://reviews.freebsd.org/D48406 (cherry picked from commit 066ef2aec187ae93a9df01d25fa8e47d67ff972b)
* release: Chase location of pkg repo databasesColin Percival2025-02-093-3/+3
| | | | | | | | | | | | | | | pkg used to store copies of upstream repository databases in /var/db/pkg/repo-*.sqlite. About a year ago this was moved to /var/db/pkg/repos/*/, resulting in FreeBSD cloud images no longer having those (unhelpful since they'll be long out of date before the cloud images are launched) databases removed. Remove the correct location, and hope that future pkg updates don't break the base system again. Sponsored by: Amazon (cherry picked from commit 078e8b34b13d6d0663661542eeac9007806fccdc)
* vmimage.subr: Redirect etcupdate log to stdoutColin Percival2025-02-062-2/+3
| | | | | | | | | | | | While we're here, send the etcupdate log from generating base.txz to stdout instead of /dev/null (see e972e408d19a) as well. Reviewed by: emaste, gordon, jrtc27 MFC after: 1 week Sponsored by: Amazon Differential Revision: https://reviews.freebsd.org/D48719 (cherry picked from commit ace4637ee0c666c6f5a1c664f8956f7302234edd)
generated by cgit v1.3 (git 2.53.0) at 2026-04-18 11:26:57 +0000