1ddea995dSGraham PerrinUpdating Information for users of FreeBSD-CURRENT. 253dfde79SWarner Losh 3456b5dd8SWarner LoshThis file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>. 4456b5dd8SWarner LoshSee end of file for further details. For commonly done items, please see the 5456b5dd8SWarner LoshCOMMON ITEMS: section later in the file. These instructions assume that you 6456b5dd8SWarner Loshbasically know what you are doing. If not, then please consult the FreeBSD 7e0fb6dc3SRobert Watsonhandbook: 8e0fb6dc3SRobert Watson 9c1a14887SCeri Davies https://docs.freebsd.org/en/books/handbook/cutting-edge/#makeworld 10e72fd46aSWarner Losh 112c724730SWarner LoshItems affecting the ports and packages system can be found in 126dadf78fSGlen Barber/usr/ports/UPDATING. Please read that file before updating system packages 136dadf78fSGlen Barberand/or ports. 142c724730SWarner Losh 15aee253d8SGlen BarberNOTE TO PEOPLE WHO THINK THAT FreeBSD 15.x IS SLOW: 16aee253d8SGlen Barber FreeBSD 15.x has many debugging features turned on, in both the kernel 17456b5dd8SWarner Losh and userland. These features attempt to detect incorrect use of 18456b5dd8SWarner Losh system primitives, and encourage loud failure through extra sanity 19456b5dd8SWarner Losh checking and fail stop semantics. They also substantially impact 20456b5dd8SWarner Losh system performance. If you want to do performance measurement, 21456b5dd8SWarner Losh benchmarking, and optimization, you'll want to turn them off. This 22456b5dd8SWarner Losh includes various WITNESS- related kernel options, INVARIANTS, malloc 23456b5dd8SWarner Losh debugging flags in userland, and various verbose features in the 24456b5dd8SWarner Losh kernel. Many developers choose to disable these features on build 2599e449f2SJason Evans machines to maximize performance. (To completely disable malloc 267d4374f6SDimitry Andric debugging, define WITH_MALLOC_PRODUCTION in /etc/src.conf and rebuild 277d4374f6SDimitry Andric world, or to merely disable the most expensive debugging functionality 287d4374f6SDimitry Andric at runtime, run "ln -s 'abort:false,junk:false' /etc/malloc.conf".) 295ad05815SWarner Losh 30*c4530dffSMitchell Horne20250127: 31*c4530dffSMitchell Horne The Allwinner a10_timer driver has been renamed to aw_driver. If you 32*c4530dffSMitchell Horne have a custom kernel configuration including the line 'device 33*c4530dffSMitchell Horne a10_timer', it must be adjusted to 'device aw_timer'. The same applies 34*c4530dffSMitchell Horne for device exclusions with 'nodevice'. 35*c4530dffSMitchell Horne 36582c8de0SAlexander Leidinger20250106: 37a071c767SEmmanuel Vadot A new SOC_ROCKCHIP options appeared, so if you have a custom kernel configuration 38a071c767SEmmanuel Vadot targetting Rockchip SoC you need to add it so shared and mandatory drivers for 39a071c767SEmmanuel Vadot this SoC familly will be selected. 40a071c767SEmmanuel Vadot Also a new rk8xx device was added, this select the base driver for Rockchip PMIC. 41a071c767SEmmanuel Vadot 42e0b7a9b6SMark Johnston20241223: 43e0b7a9b6SMark Johnston The layout of NFS file handles for the tarfs, tmpfs, cd9660, and ext2fs 44e0b7a9b6SMark Johnston file systems has changed. An NFS server that exports any of these file 45e0b7a9b6SMark Johnston systems will need its clients to unmount and remount the exports. 46e0b7a9b6SMark Johnston 4794e94d2dSEmmanuel Vadot20241216: 4894e94d2dSEmmanuel Vadot The iwm(4) firmwares are no longer compiled as kernel modules but instead 4994e94d2dSEmmanuel Vadot shipped as raw files. For pkgbase users if you use iwm(4) you will need 5094e94d2dSEmmanuel Vadot to install the FreeBSD-firmware-iwm package. 5194e94d2dSEmmanuel Vadot 528ea6c115SStefan Eßer20241124: 538ea6c115SStefan Eßer The OpenBSD derived bc and dc implementations and the WITHOUT_GH_BC 548ea6c115SStefan Eßer option that allowed building them instead of the advanced version 558ea6c115SStefan Eßer imported more than 4 years ago have been removed. 568ea6c115SStefan Eßer 57a5ad360fSMateusz Piotrowski20241025: 58a5ad360fSMateusz Piotrowski The support for the rc_fast_and_loose variable has been removed from 59a5ad360fSMateusz Piotrowski rc.subr(8). Users setting rc_fast_and_loose on their systems are 60a5ad360fSMateusz Piotrowski advised to make sure their customizations to rc service scripts 61a5ad360fSMateusz Piotrowski do not depend on having a single shell environment shared across 62a5ad360fSMateusz Piotrowski all the rc service scripts during booting and shutdown. 63a5ad360fSMateusz Piotrowski 64793c668eSWarner Losh20241013: 65793c668eSWarner Losh The ciss driver was updated to cope better with hotplug events that 66793c668eSWarner Losh caused it to panic before, and to support more than 48 drives attached 67793c668eSWarner Losh to the card. These changes were made w/o benefit of hardware for testing 68793c668eSWarner Losh and ciss(4) users should be on the lookout for regressions. 69793c668eSWarner Losh 70ba373fcaSEd Maste20240729: 71ba373fcaSEd Maste The build now defaults to WITHOUT_CLEAN - i.e., no automatic clean 72ba373fcaSEd Maste is performed at the beginning of buildworld or buildkernel. The 73ba373fcaSEd Maste WITH_CLEAN src.conf(5) knob can be used to restore the previous 74ba373fcaSEd Maste behaviour. 75ba373fcaSEd Maste 76ba373fcaSEd Maste If you encounter incremental build issues, please report them to the 77ba373fcaSEd Maste freebsd-current mailing list so that a special-case dependency can be 78ba373fcaSEd Maste added, if necessary. 79ba373fcaSEd Maste 8063e28228SWarner Losh20240715: 8163e28228SWarner Losh We now lean more heavily on ACPI enumeration for some traditional 8263e28228SWarner Losh devices. uart has moved from isa to acpi so the hints act as wiring 8363e28228SWarner Losh instead of device enumeration. Hints for parallel port, floppy, etc 8463e28228SWarner Losh have been removed. Before upgrading, grep your dmesg for lines like: 8563e28228SWarner Losh uart1: non-PNP ISA device will be removed from GENERIC in FreeBSD 15. 8663e28228SWarner Losh to see if you need to start including hints for the device on isa 8763e28228SWarner Losh in your loader.conf or device.hints file. APU1 (but not APU2) boards 8863e28228SWarner Losh are known to be affected, but there may be others. 8963e28228SWarner Losh 907818c2d3SAndrew Turner20240712: 917818c2d3SAndrew Turner Support for armv6 has been disconnected and is being removed. 927818c2d3SAndrew Turner 93e2ad879dSEd Maste20240617: 94e2ad879dSEd Maste ifconfig now treats IPv4 addresses without a width or mask as an error. 95e2ad879dSEd Maste Specify the desired mask or width along with the IP address on the 96e2ad879dSEd Maste ifconfig command line and in rc.conf. 97e2ad879dSEd Maste 981b3c07beSLexi Winter20240428: 991b3c07beSLexi Winter OpenBSM auditing runtime (auditd, etc.) has been moved into the new 1001b3c07beSLexi Winter package FreeBSD-audit. If you use OpenBSM auditing and pkgbase, you 1011b3c07beSLexi Winter should install FreeBSD-audit. 1021b3c07beSLexi Winter 1036b1d152dSLexi Winter20240424: 1046b1d152dSLexi Winter cron, lpr, and ntpd have been moved from FreeBSD-utilities into their 1056b1d152dSLexi Winter own packages. If you use pkgbase, you should install the relevant 1066b1d152dSLexi Winter packages: FreeBSD-cron, FreeBSD-lp, or FreeBSD-ntp. 1076b1d152dSLexi Winter 10815780223SDimitry Andric20240406: 10915780223SDimitry Andric Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have 11015780223SDimitry Andric been upgraded to 18.1.6. It is important that you run `make delete-old` 11115780223SDimitry Andric as described in the COMMON ITEMS section, otherwise several libc++ 11215780223SDimitry Andric headers that are obsolete and need to be removed can cause compilation 11315780223SDimitry Andric errors in C++ programs. 11415780223SDimitry Andric 1150d4f7723SBrooks Davis20240205: 1160d4f7723SBrooks Davis For dynamically linked programs, system calls are now made from 1170d4f7723SBrooks Davis libsys rather than libc. No change in linkage is required as 1180d4f7723SBrooks Davis libsys is an auxiliary filter for libc. People building custom 1190d4f7723SBrooks Davis images must ensure that libsys.so.7 is included. 1200d4f7723SBrooks Davis 121c475e61fSStéphane Rochoy20240202: 122c475e61fSStéphane Rochoy Loader now also read configuration files listed in local_loader_conf_files. 123c475e61fSStéphane Rochoy Files listed here are the last ones read. And /boot/loader.conf.local was 124c475e61fSStéphane Rochoy moved from loader_conf_files to local_loader_conf_files leaving only 125c475e61fSStéphane Rochoy loader.conf and device.hints in loader_conf_files by default. 126c475e61fSStéphane Rochoy 127c475e61fSStéphane Rochoy The following sequencing is applied: 128c475e61fSStéphane Rochoy 129c475e61fSStéphane Rochoy 1. Bootstrap: 130c475e61fSStéphane Rochoy /boot/defaults/loader.conf 131c475e61fSStéphane Rochoy 132c475e61fSStéphane Rochoy 2. Read loader_conf_files files: 133c475e61fSStéphane Rochoy /boot/device.hints 134c475e61fSStéphane Rochoy /boot/loader.conf 135c475e61fSStéphane Rochoy 136c475e61fSStéphane Rochoy 3. Read loader_conf_dirs files: 137c475e61fSStéphane Rochoy /boot/loader.conf.d/*.conf 138c475e61fSStéphane Rochoy 139c475e61fSStéphane Rochoy 4. And finally, rread local_loader_conf_files files: 140c475e61fSStéphane Rochoy /boot/loader.conf.local 141c475e61fSStéphane Rochoy 14221c1f1deSGregory Neil Shapiro20240201: 14321c1f1deSGregory Neil Shapiro sendmail 8.18.1 has been imported and merged. This version enforces 14421c1f1deSGregory Neil Shapiro stricter RFC compliance by default, especially with respect to line 14521c1f1deSGregory Neil Shapiro endings. This may cause issues with receiving messages from 14621c1f1deSGregory Neil Shapiro non-compliant MTAs; please see the first 8.18.1 release note in 14721c1f1deSGregory Neil Shapiro contrib/sendmail/RELEASE_NOTES for mitigations. 14821c1f1deSGregory Neil Shapiro 149d004554aSRick Macklem20240111: 150d004554aSRick Macklem Commit cc760de2183f changed the internal interface between 151d004554aSRick Macklem the nfscommon and nfscl modules. As such, both need to be 152d004554aSRick Macklem rebuilt from sources. Therefore, __FreeBSD_version was 153d004554aSRick Macklem bumped to 1500010. 154d004554aSRick Macklem 1550abe05aeSWarner Losh20231120: 1560abe05aeSWarner Losh If you have an arm64 system that uses ACPI, you will need to update your 1570abe05aeSWarner Losh loader.efi in the ESP when you update past this point. Detection of ACPI 1580abe05aeSWarner Losh was moved earlier in the binary so the scripts could use it, but old 1595d4f897fSWarner Losh binaries don't have this, so we default to 'no ACPI' in this case. You can 1605d4f897fSWarner Losh undisable ACPI by doing 1615d4f897fSWarner Losh OK unset hint.acpi.0.disabled 1625d4f897fSWarner Losh This can also be used to recover any other system that was updated in the 1635d4f897fSWarner Losh small window where amd64 was also broken. 1640abe05aeSWarner Losh 165ec4c2adbSBrooks Davis20231113: 166ec4c2adbSBrooks Davis The WITHOUT_LLD_IS_LD option has been removed. When LLD is enabled 167ec4c2adbSBrooks Davis it is always installed as /usr/bin/ld. 168ec4c2adbSBrooks Davis 1690527c9bdSWarner Losh20231027: 1700527c9bdSWarner Losh Forward compatibility (running the new code on old kernels) for the 1710527c9bdSWarner Losh "ino64" project have been removed. The need for it has passed long ago. 1720527c9bdSWarner Losh 173fb7140b1SRick Macklem20231018: 174fb7140b1SRick Macklem Commit 57ce37f9dcd0 changed the internal KAPI between the 175fb7140b1SRick Macklem nfscommon and nfscl modules. Both must be rebuilt from sources. 176fb7140b1SRick Macklem 177bb63e82eSBaptiste Daroussin20231010: 178bb63e82eSBaptiste Daroussin dialog(1) has been replaced in base by bsddialog(1), while most of the 179bb63e82eSBaptiste Daroussin time replacing a dialog(1) call by a bsddialog(1) call works out of the 180261cda20SCeri Davies box, bsddialog(1) is not considered as a drop-in replacement for 181261cda20SCeri Davies dialog(1). 182bb63e82eSBaptiste Daroussin 183261cda20SCeri Davies If you do depend on dialog(1) functionality, please install cdialog 184bb63e82eSBaptiste Daroussin from ports: 185bb63e82eSBaptiste Daroussin 186bb63e82eSBaptiste Daroussin pkg install cdialog 187bb63e82eSBaptiste Daroussin 188da695970SEd Maste20230927: 189da695970SEd Maste The EARLY_AP_STARTUP kernel option is mandatory on x86. The option 190da695970SEd Maste has been added to DEFAULTS, so it should automatically be included in 191da695970SEd Maste custom kernel configurations without any additional change. 192da695970SEd Maste 193366ef17bSZhenlei Huang20230922: 194366ef17bSZhenlei Huang A new loader tunable net.pf.default_to_drop allows pf(4)’s default 195366ef17bSZhenlei Huang behaviour to be changed from pass to drop. Previously this required 196366ef17bSZhenlei Huang recompiling the kernel with the option PF_DEFAULT_TO_DROP. 197366ef17bSZhenlei Huang 19874da9c39SDoug Rabson20230914: 19974da9c39SDoug Rabson Enable splitting out pkgbase manpages into separate packages by 20074da9c39SDoug Rabson default. To disable this, set WITHOUT_MANSPLITPKG=yes in src.conf. 20174da9c39SDoug Rabson 2024ff9d270SDoug Rabson20230911: 2034ff9d270SDoug Rabson Move standard include files to the clibs-dev package and move clang 2044ff9d270SDoug Rabson internal libraries and headers to clang and clang-dev. Upgrading systems 2054ff9d270SDoug Rabson installed using pkgbase past this change involves extra steps to allow 2064ff9d270SDoug Rabson for these file moves: 2074ff9d270SDoug Rabson 2084ff9d270SDoug Rabson pkg upgrade -y FreeBSD-utilities 2094ff9d270SDoug Rabson pkg upgrade -y FreeBSD-utilities-dev 2104ff9d270SDoug Rabson pkg upgrade -y 2114ff9d270SDoug Rabson 212c1b26df2SZhenlei Huang20230909: 213c1b26df2SZhenlei Huang Enable vnet sysctl variables to be loader tunable. SYSCTLs which 214c1b26df2SZhenlei Huang belongs to VNETs can be initialized during early boot or module 215c1b26df2SZhenlei Huang loading if they are marked with CTLFLAG_TUN and there are 216c1b26df2SZhenlei Huang corresponding kernel environment variables. 217c1b26df2SZhenlei Huang 2182befa269SBrooks Davis20230901: 21948d05737SBrooks Davis The WITH_INIT_ALL_PATTERN and WITH_INIT_ALL_ZERO build options have 2202befa269SBrooks Davis been replaced by INIT_ALL=pattern and INIT_ALL=zero respectively. 2212befa269SBrooks Davis 22252c1066fSGlen Barber20230824: 22352c1066fSGlen Barber FreeBSD 15.0-CURRENT. 22452c1066fSGlen Barber 2254722ceb7SEd Maste20230817: 2264722ceb7SEd Maste Serial communication (in boot loaders, kernel, and userland) has 2274722ceb7SEd Maste been changed to default to 115200 bps, in line with common industry 2284722ceb7SEd Maste practice and typcial firmware serial console redirection 2294722ceb7SEd Maste configuration. 2304722ceb7SEd Maste 2314722ceb7SEd Maste Note that the early x86 BIOS bootloader (i.e., boot0sio) does not 232edacf4b4SGraham Perrin support rates above 9600 bps and is not changed. boot0sio users may 2334722ceb7SEd Maste set BOOT_COMCONSOLE_SPEED=9600 to use 9600 for all of the boot 2344722ceb7SEd Maste components, or use the standard boot0 and have the boot2 stage start 2354722ceb7SEd Maste with the serial port at 115200. 2364722ceb7SEd Maste 23737c8ee88SMarius Strobl20230807: 23837c8ee88SMarius Strobl Following the general removal of MIPS support, the ath(4) AHB bus- 23937c8ee88SMarius Strobl frontend has been removed, too, and building of the PCI support is 24037c8ee88SMarius Strobl integrated with the ath(4) main module again. As a result, there's 24137c8ee88SMarius Strobl no longer a need for if_ath_pci_load="YES" in /boot/loader.conf or 24237c8ee88SMarius Strobl "device ath_pci" in the kernel configuration. 24337c8ee88SMarius Strobl 2449051987eSEd Maste20230803: 2459051987eSEd Maste MAXCPU has been increased to 1024 in the amd64 GENERIC kernel config. 2469051987eSEd Maste Out-of-tree kernel modules will need to be rebuilt. 2479051987eSEd Maste 248f475b710SWarner Losh20230724: 249f475b710SWarner Losh CAM has been mechanically updated s/u_int(64|32|16|8)_t/uint\1_t/g 250f475b710SWarner Losh to move to the standard uintXX_t types from the old, traditional 251f475b710SWarner Losh BSD u_intXX_t types. This should be a NOP, but may cause problems 252f475b710SWarner Losh for out of tree changes. The SIMs were not updated since most of 253f475b710SWarner Losh the old u_intXX_t uses weren't due to CAM interfaces. 254f475b710SWarner Losh 255cb0259b6SWarner Losh20230713: 256cb0259b6SWarner Losh stable/14 branch created. 257cb0259b6SWarner Losh 258319d2bf4SWarner Losh20230629: 259319d2bf4SWarner Losh The heuristic for detecting old chromebooks with an EC bug that requires 260319d2bf4SWarner Losh atkbdc driver workarounds has changed. There should be no functional 261319d2bf4SWarner Losh change, but if your old chromebook's keyboard stops working, please 262319d2bf4SWarner Losh file a PR and assign it to imp. 263319d2bf4SWarner Losh 264564c5314SEd Maste20230623: 265564c5314SEd Maste OpenSSL has been updated to version 3.0, including changes throughout 266564c5314SEd Maste the base system. It is important to rebuild third-party software 267564c5314SEd Maste after upgrading. 268564c5314SEd Maste 2693a1f834bSDoug Rabson20230619: 2703a1f834bSDoug Rabson To enable pf rdr rules for connections initiated from the host, pf 2713a1f834bSDoug Rabson filter rules can be optionally enabled for packets delivered 2723a1f834bSDoug Rabson locally. This can change the behavior of rules which match packets 2733a1f834bSDoug Rabson delivered to lo0. To enable this feature: 2743a1f834bSDoug Rabson 2753a1f834bSDoug Rabson sysctl net.pf.filter_local=1 2763a1f834bSDoug Rabson service pf restart 2773a1f834bSDoug Rabson 2783a1f834bSDoug Rabson When enabled, its best to ensure that packets delivered locally are not 2793a1f834bSDoug Rabson filtered, e.g. by adding a 'skip on lo' rule. 2803a1f834bSDoug Rabson 28121850106SDag-Erling Smørgrav20230613: 28221850106SDag-Erling Smørgrav Improvements to libtacplus(8) mean that tacplus.conf(5) now 28321850106SDag-Erling Smørgrav follows POSIX shell syntax rules. This may cause TACACS+ 28421850106SDag-Erling Smørgrav authentication to fail if the shared secret contains a single 28521850106SDag-Erling Smørgrav quote, double quote, or backslash character which isn't 28621850106SDag-Erling Smørgrav already properly quoted or escaped. 28721850106SDag-Erling Smørgrav 288bdc81eedSWarner Losh20230612: 289bdc81eedSWarner Losh Belatedly switch the default nvme block device on x86 from nvd to nda. 290bdc81eedSWarner Losh nda created nvd compatibility links by default, so this should be a 291bdc81eedSWarner Losh nop. If this causes problems for your application, set hw.nvme.use_nvd=1 292bdc81eedSWarner Losh in your loader.conf or add `options NVME_USE_NVD=1` to your kernel 293bd76e4c8SWarner Losh config. To disable the nvd compatibility aliases, add 294bd76e4c8SWarner Losh kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on 295bd76e4c8SWarner Losh all non-x86 platforms for some time now. If you need to fall back, 296bd76e4c8SWarner Losh please email imp@freebsd.org about why. 297bdc81eedSWarner Losh 298814722d2SWarner Losh Encrypted swap partitions need to be changed from nvd to nda if you 299814722d2SWarner Losh migrate, or you need to use the above to switch back to nvd. 300814722d2SWarner Losh 301df53ae0fSColin Percival20230422: 302df53ae0fSColin Percival Remove portsnap(8). Users are encouraged to obtain the ports tree 303df53ae0fSColin Percival using git instead. 304df53ae0fSColin Percival 3050df4d8adSSimon J. Gerraty20230420: 3060df4d8adSSimon J. Gerraty Add jobs.mk to save typing. Enables -j${JOB_MAX} and logging 3070df4d8adSSimon J. Gerraty eg. 3080df4d8adSSimon J. Gerraty make buildworld-jobs 3090df4d8adSSimon J. Gerraty runs 3100df4d8adSSimon J. Gerraty make -j${JOB_MAX} buildworld > ../buildworld.log 2>&1 3110df4d8adSSimon J. Gerraty 3120df4d8adSSimon J. Gerraty where JOB_MAX is derrived from ncpus in local.sys.mk if not set in env. 3130df4d8adSSimon J. Gerraty 314a4f8318aSEmmanuel Vadot20230316: 315a4f8318aSEmmanuel Vadot Video related devices for some arm devices have been renamed. 316a4f8318aSEmmanuel Vadot If you have a custom kernel config and want to use hdmi output on 317a4f8318aSEmmanuel Vadot IMX6 board you need to add "device dwc_hdmi" "device imx6_hdmi" and 318a4f8318aSEmmanuel Vadot "device imx6_ipu" to it. 319a4f8318aSEmmanuel Vadot If you have a custom kernel config and want to use hdmi output on 320a4f8318aSEmmanuel Vadot TI AM335X board you need to add "device tda19988" to it. 321a4f8318aSEmmanuel Vadot If you add "device hdmi" in it you need to remove it as it doesn't 322a4f8318aSEmmanuel Vadot exist anymore. 323a4f8318aSEmmanuel Vadot 3249b70ce71SMichael Paepcke20230221: 3259b70ce71SMichael Paepcke Introduce new kernel options KBD_DELAY1 and KBD_DELAY2. See atkbdc(4) 3269b70ce71SMichael Paepcke for details. 3279b70ce71SMichael Paepcke 32877934b7aSEd Maste20230206: 32977934b7aSEd Maste sshd now defaults to having X11Forwarding disabled, following upstream. 33077934b7aSEd Maste Administrators who wish to enable X11Forwarding should add 33177934b7aSEd Maste `X11Forwarding yes` to /etc/ssh/sshd_config. 33277934b7aSEd Maste 333c92790b3SMichael Paepcke20230204: 334c92790b3SMichael Paepcke Since commit 75d41cb6967 Huawei 3G/4G LTE Mobile Devices do not default 335c92790b3SMichael Paepcke to ECM, but NCM mode and need u3g and ucom modules loaded. See cdce(4). 336c92790b3SMichael Paepcke 3376eaaed42SAlexander V. Chernikov20230130: 3386eaaed42SAlexander V. Chernikov As of commit 7c40e2d5f685, the dependency on netlink(4) has been added 3396eaaed42SAlexander V. Chernikov to the linux_common(4) module. Users relying on linux_common may need 3406eaaed42SAlexander V. Chernikov to complile netlink(4) module if it is not present in their kernel. 341bf2dc42dSWarner Losh 342ac4c695aSEd Maste20230126: 343ac4c695aSEd Maste The WITHOUT_CXX option has been removed. C++ components in the base 344ac4c695aSEd Maste system are now built unconditionally. 345ac4c695aSEd Maste 3464b56afafSBjoern A. Zeeb20230113: 3474b56afafSBjoern A. Zeeb LinuxKPI pci.h changes may require out-of-tree drivers to be recompiled. 3484b56afafSBjoern A. Zeeb Bump _FreeBSD_version to 1400078 to be able to detect this change. 3494b56afafSBjoern A. Zeeb 35086edb11eSEd Maste20221212: 35186edb11eSEd Maste llvm-objump is now always installed as objdump. Previously there was 35286edb11eSEd Maste no /usr/bin/objdump unless the WITH_LLVM_BINUTILS knob was used. 35386edb11eSEd Maste 35486edb11eSEd Maste Some LLVM objdump options have a different output format compared to 35586edb11eSEd Maste GNU objdump; readelf is available for inspecting ELF files, and GNU 35686edb11eSEd Maste objdump is available from the devel/binutils port or package. 35786edb11eSEd Maste 3584d13184aSBaptiste Daroussin20221205: 3594d13184aSBaptiste Daroussin dma(8) has replaced sendmail(8) as the default mta. For people willing 3604d13184aSBaptiste Daroussin to reenable sendmail(8): 3614d13184aSBaptiste Daroussin 3624d13184aSBaptiste Daroussin $ cp /usr/share/examples/sendmail/mailer.conf /etc/mail/mailer.conf 3634d13184aSBaptiste Daroussin 3644d13184aSBaptiste Daroussin and add sendmail_enable="YES" to rc.conf. 3654d13184aSBaptiste Daroussin 36668c3f030SWarner Losh20221204: 36768c3f030SWarner Losh hw.bus.disable_failed_devices has changed from 'false' to 'true' by 36868c3f030SWarner Losh default. Now if newbus succeeds in probing a device, but fails to attach 36968c3f030SWarner Losh the device, we'll disable the device. In the past, we'd keep retrying 37068c3f030SWarner Losh the device on each new driver loaded. To get that behavior now, one 371cc564d23SWarner Losh needs to use devctl to re-enable the device, and reprobe it (or set 37268c3f030SWarner Losh the sysctl/tunable hw.bus.disable_failed_devices=false). 37368c3f030SWarner Losh 3743cf97e91SWarner Losh NOTE: This was reverted 20221205 due to unexpected compatibility issues 3753cf97e91SWarner Losh 37688e858e5SKristof Provost20221122: 37788e858e5SKristof Provost pf no longer accepts 'scrub fragment crop' or 'scrub fragment drop-ovl'. 37888e858e5SKristof Provost These configurations are no longer automatically reinterpreted as 37988e858e5SKristof Provost 'scrub fragment reassemble'. 38088e858e5SKristof Provost 38120a66ab4SEd Maste20221121: 38220a66ab4SEd Maste The WITHOUT_CLANG_IS_CC option has been removed. When Clang is enabled 38320a66ab4SEd Maste it is always installed as /usr/bin/cc (and c++, cpp). 38420a66ab4SEd Maste 3855575454dSEmmanuel Vadot20221026: 3868aa64f30SEd Maste Some programs have been moved into separate packages. It is recommended 3879c363005SEd Maste for pkgbase users to do: 3889c363005SEd Maste 3899c363005SEd Maste pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \ 3909c363005SEd Maste FreeBSD-devd FreeBSD-devmatch 3919c363005SEd Maste 3929c363005SEd Maste after upgrading to restore all the component that were previously 3939c363005SEd Maste installed. 3945575454dSEmmanuel Vadot 395d2c839eeSDag-Erling Smørgrav20221002: 396d2c839eeSDag-Erling Smørgrav OPIE has been removed from the base system. If needed, it can 397d2c839eeSDag-Erling Smørgrav be installed from ports (security/opie) or packages (opie). 398d2c839eeSDag-Erling Smørgrav Otherwise, make sure that your PAM policies do not reference 399d2c839eeSDag-Erling Smørgrav pam_opie or pam_opieaccess. 400d2c839eeSDag-Erling Smørgrav 4010e981d79SBjoern A. Zeeb20220610: 4020e981d79SBjoern A. Zeeb LinuxKPI pm.h changes require an update to the latest drm-kmod version 4030e981d79SBjoern A. Zeeb before re-compiling to avoid errors. 4040e981d79SBjoern A. Zeeb 4058303b8ffSCy Schubert20211230: 4068303b8ffSCy Schubert The macros provided for the manipulation of CPU sets (e.g. CPU_AND) 4078303b8ffSCy Schubert have been modified to take 2 source arguments instead of only 1. 4088303b8ffSCy Schubert Externally maintained sources that use these macros will have to 4098303b8ffSCy Schubert be adapted. The FreeBSD version has been bumped to 1400046 to 4108303b8ffSCy Schubert reflect this change. 4118303b8ffSCy Schubert 4128303b8ffSCy Schubert20211214: 4138303b8ffSCy Schubert A number of the kernel include files are able to be included by 4148303b8ffSCy Schubert themselves. A test has been added to buildworld to enforce this. 4158303b8ffSCy Schubert 41645b6b376SCy Schubert20211209: 41745b6b376SCy Schubert Remove mips as a recognized target. This starts the decommissioning of 41845b6b376SCy Schubert mips support in FreeBSD. mips related items will be removed wholesale in 41945b6b376SCy Schubert the coming days and weeks. 42045b6b376SCy Schubert 42145b6b376SCy Schubert This broke the NO_CLEAN build for some people. Either do a clean build 42245b6b376SCy Schubert or touch 42345b6b376SCy Schubert lib/clang/include/llvm/Config/Targets.def 42445b6b376SCy Schubert lib/clang/include/llvm/Config/AsmParsers.def 42545b6b376SCy Schubert lib/clang/include/llvm/Config/Disassemblers.def 42645b6b376SCy Schubert lib/clang/include/llvm/Config/AsmPrinters.def 42745b6b376SCy Schubert before the build to force everything to rebuild that needs to. 42845b6b376SCy Schubert 42972d0d523SCy Schubert20211202: 43072d0d523SCy Schubert Unbound support for RFC8375: The special-use domain 'home.arpa' is 43172d0d523SCy Schubert by default blocked. To unblock it use a local-zone nodefault 43272d0d523SCy Schubert statement in unbound.conf: 43372d0d523SCy Schubert local-zone: "home.arpa." nodefault 43472d0d523SCy Schubert 43572d0d523SCy Schubert Or use another type of local-zone to override with your choice. 43672d0d523SCy Schubert 43772d0d523SCy Schubert The reason for this is discussed in Section 6.1 of RFC8375: 43872d0d523SCy Schubert Because 'home.arpa.' is not globally scoped and cannot be secured 43972d0d523SCy Schubert using DNSSEC based on the root domain's trust anchor, there is no way 44072d0d523SCy Schubert to tell, using a standard DNS query, in which homenet scope an answer 44172d0d523SCy Schubert belongs. Consequently, users may experience surprising results with 44272d0d523SCy Schubert such names when roaming to different homenets. 44372d0d523SCy Schubert 444b8d60729SRandall Stewart20211110: 445d6953863SRandall Stewart Commit b8d60729deef changed the TCP congestion control framework so 446b8d60729SRandall Stewart that any of the included congestion control modules could be 447b8d60729SRandall Stewart the single module built into the kernel. Previously newreno 4489ad859daSGordon Tetlow was automatically built in through direct reference. As of 449b8d60729SRandall Stewart this commit you are required to declare at least one congestion 4509ad859daSGordon Tetlow control module (e.g. 'options CC_NEWRENO') and to also declare a 451b8d60729SRandall Stewart default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\"). 452bde57090SGordon Bergling The GENERIC configuration includes CC_NEWRENO and defines newreno 453b8d60729SRandall Stewart as the default. If no congestion control option is built into the 454b8d60729SRandall Stewart kernel and you are including networking, the kernel compile will 455b8d60729SRandall Stewart fail. Also if no default is declared the kernel compile will fail. 456b8d60729SRandall Stewart 45767301655SWarner Losh20211118: 45867301655SWarner Losh Mips has been removed from universe builds. It will be removed from the 45967301655SWarner Losh tree shortly. 46067301655SWarner Losh 46125b0021dSRick Macklem20211106: 46225b0021dSRick Macklem Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE. 46325b0021dSRick Macklem The NFS modules must be rebuilt from sources and any out 46425b0021dSRick Macklem of tree file systems that implement their own VOP_ALLOCATE 46525b0021dSRick Macklem may need to be modified. 46625b0021dSRick Macklem 4676aae3517SGleb Smirnoff20211022: 4686aae3517SGleb Smirnoff The synchronous PPP kernel driver sppp(4) has been removed. 4696aae3517SGleb Smirnoff The cp(4) and ce(4) drivers are now always compiled with netgraph(4) 4706aae3517SGleb Smirnoff support, formerly enabled by NETGRAPH_CRONYX option. 4716aae3517SGleb Smirnoff 472d410b585SBaptiste Daroussin20211020: 4736ae38ab4SBaptiste Daroussin sh(1) is now the default shell for the root user. To force root to use 474d410b585SBaptiste Daroussin the csh shell, please run the following command as root: 475d410b585SBaptiste Daroussin 4766ae38ab4SBaptiste Daroussin # chsh -s csh 477d410b585SBaptiste Daroussin 47816f1ee11SBaptiste Daroussin20211004: 47916f1ee11SBaptiste Daroussin Ncurses distribution has been split between libtinfow and libncurses 48016f1ee11SBaptiste Daroussin with libncurses.so becoming a linker (ld) script to seamlessly link 48116f1ee11SBaptiste Daroussin to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect 48216f1ee11SBaptiste Daroussin this change. 48316f1ee11SBaptiste Daroussin 4849cce0ef9SKristof Provost20210923: 4859cce0ef9SKristof Provost As of commit 8160a0f62be6, the dummynet module no longer depends on the 4869cce0ef9SKristof Provost ipfw module. Dummynet can now be used by pf as well as ipfw. As such 4879cce0ef9SKristof Provost users who relied on this dependency may need to include ipfw in the 4889cce0ef9SKristof Provost list of modules to load on their systems. 4899cce0ef9SKristof Provost 4909cce0ef9SKristof Provost20210922: 4910e94a306SHans Petter Selasky As of commit 903873ce1560, the mixer(8) utility has got a slightly 49290f6610bSHans Petter Selasky new syntax. Please refer to the mixer(8) manual page for more 4938bc5971bSHans Petter Selasky information. The old mixer utility can be installed from ports: 4948bc5971bSHans Petter Selasky audio/freebsd-13-mixer 4950e94a306SHans Petter Selasky 496ae87a08cSRick Macklem20210911: 497ae87a08cSRick Macklem As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has 498ae87a08cSRick Macklem been deleted from the nfscommon.ko. As such, nfsd.ko must be built 499ae87a08cSRick Macklem from up to date sources to avoid an undefined reference when 500ae87a08cSRick Macklem being loaded. 501ae87a08cSRick Macklem 502671a35b1SJohn Baldwin20210817: 503671a35b1SJohn Baldwin As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS 504671a35b1SJohn Baldwin by default. Users can enable kernel TLS via the "KTLS" SSL 505671a35b1SJohn Baldwin option. This can be enabled globally by using a custom 506671a35b1SJohn Baldwin OpenSSL config file via OPENSSL_CONF or via an 507671a35b1SJohn Baldwin application-specific configuration option for applications 508671a35b1SJohn Baldwin which permit setting SSL options via SSL_CONF_cmd(3). 509671a35b1SJohn Baldwin 510a3ff18e2SRick Macklem20210811: 511a3ff18e2SRick Macklem Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS 512a3ff18e2SRick Macklem modules. Therefore, all need to be rebuilt from sources. 513a3ff18e2SRick Macklem 51434129003SKristof Provost20210730: 51534129003SKristof Provost Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl. 51634129003SKristof Provost As of be70c7a50d32 it is no longer used by userspace, but it does mean 51734129003SKristof Provost users may not be able to enumerate pf states if they update the kernel 518a191b401SKristof Provost past b69019c14cd8 without first updating userspace past be70c7a50d32. 51934129003SKristof Provost 520728958fbSKristof Provost20210729: 521728958fbSKristof Provost As of commit 01ad0c007964 if_bridge member interfaces can no longer 522728958fbSKristof Provost change their MTU. Changing the MTU of the bridge itself will change the 523728958fbSKristof Provost MTU on all member interfaces instead. 524728958fbSKristof Provost 5257fa21b6dSRick Macklem20210716: 5267fa21b6dSRick Macklem Commit ee29e6f31111 changed the internal KAPI between the nfscommon 5277fa21b6dSRick Macklem and nfsd modules. Therefore, both need to be rebuilt from sources. 5287fa21b6dSRick Macklem Bump __FreeBSD_version to 1400026 for this KAPI change. 5297fa21b6dSRick Macklem 5305ede4fc0SWarner Losh20210715: 5315ede4fc0SWarner Losh The 20210707 awk update brought in a change in behavior. This has 5325ede4fc0SWarner Losh been corrected as of d4d252c49976. Between these dates, if you 5335ede4fc0SWarner Losh installed a new awk binary, you may not be able to build a new 5345ede4fc0SWarner Losh kernel because the change in behavior affected the genoffset 5355ede4fc0SWarner Losh script used to build the kernel. If you did update, the fix is 5365ede4fc0SWarner Losh to update your sources past the above hash and do 5375ede4fc0SWarner Losh % cd usr.bin/awk 5385ede4fc0SWarner Losh % make clean all 5395ede4fc0SWarner Losh % sudo -E make install 5405ede4fc0SWarner Losh to enable building kernels again. 5415ede4fc0SWarner Losh 542bd597b81SRick Macklem20210708: 543bd597b81SRick Macklem Commit 1e0a518d6548 changed the internal KAPI between the NFS 544bd597b81SRick Macklem modules. They all need to be rebuilt from sources. I did not 545bd597b81SRick Macklem bump __FreeBSD_version, since it was bumped recently. 546bd597b81SRick Macklem 5473f7b2317SWarner Losh20210707: 548a65fe39dSWarner Losh awk has been updated to the latest one-true-awk version 20210215. 5493f7b2317SWarner Losh This contains a number of minor bug fixes. 5503f7b2317SWarner Losh 551b49ba74dSRick Macklem20210624: 552b49ba74dSRick Macklem The NFSv4 client now uses the highest minor version of NFSv4 553b49ba74dSRick Macklem supported by the NFSv4 server by default instead of minor version 0, 554b49ba74dSRick Macklem for NFSv4 mounts. 555b49ba74dSRick Macklem The "minorversion" mount option may be used to override this default. 556b49ba74dSRick Macklem 55741dfd8bdSBjoern A. Zeeb20210618: 55841dfd8bdSBjoern A. Zeeb Bump __FreeBSD_version to 1400024 for LinuxKPI changes. 559800e82d1SMaigurs Stalidzans Most notably netdev.h can change now as the (last) dependencies 56041dfd8bdSBjoern A. Zeeb (mlx4/ofed) are now using struct ifnet directly, but also for PCI 56141dfd8bdSBjoern A. Zeeb additions and others. 56241dfd8bdSBjoern A. Zeeb 56341dfd8bdSBjoern A. Zeeb20210618: 56464e6e1e4SCeri Davies The directory "blacklisted" under /usr/share/certs/ has been 56564e6e1e4SCeri Davies renamed to "untrusted". 56664e6e1e4SCeri Davies 5675860696eSRick Macklem20210611: 5687cf9caf2SWarner Losh svnlite has been removed from base. Should you need svn for any reason 5697cf9caf2SWarner Losh please install the svn package or port. 5707cf9caf2SWarner Losh 5717cf9caf2SWarner Losh20210611: 5725860696eSRick Macklem Commit e1a907a25cfa changed the internal KAPI between the krpc 5735860696eSRick Macklem and nfsserver. As such, both modules must be rebuilt from 5745860696eSRick Macklem sources. Bump __FreeBSD_version to 1400022. 5755860696eSRick Macklem 5767cf9caf2SWarner Losh20210610: 5777cf9caf2SWarner Losh The an(4) driver has been removed from FreeBSD. 5787cf9caf2SWarner Losh 579b3823943SWarner Losh20210608: 580f530cce5SEd Maste The vendor/openzfs branch was renamed to vendor/openzfs/legacy to 581b3823943SWarner Losh start tracking OpenZFS upstream more closely. Please see 582b3823943SWarner Loshhttps://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html 583b3823943SWarner Losh for details on how to correct any errors that might result. The 584b3823943SWarner Losh short version is that you need to remove the old branch locally: 585b3823943SWarner Losh git update-ref -d refs/remotes/freebsd/vendor/openzfs 586b3823943SWarner Losh (assuming your upstream origin is named 'freebsd'). 587b3823943SWarner Losh 588d72cd275SBjoern A. Zeeb20210525: 589d72cd275SBjoern A. Zeeb Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI 590d72cd275SBjoern A. Zeeb which break drm-kmod. In addition various other additions where 591bde57090SGordon Bergling committed. Bump __FreeBSD_version to 1400015 to be able to 592bde57090SGordon Bergling detect this. 593d72cd275SBjoern A. Zeeb 5941c2ab28fSEmmanuel Vadot20210513: 5951c2ab28fSEmmanuel Vadot Commit ca179c4d74f2 changed the package in which the OpenSSL 5961c2ab28fSEmmanuel Vadot libraries and utilities are packaged. 59728ce2012SEmmanuel Vadot It is recommended for pkgbase user to do: 5981c2ab28fSEmmanuel Vadot pkg install -f FreeBSD-openssl 5991c2ab28fSEmmanuel Vadot before pkg upgrade otherwise some dependencies might not be met 6001c2ab28fSEmmanuel Vadot and pkg will stop working as libssl will not be present anymore 6011c2ab28fSEmmanuel Vadot on the system. 6021c2ab28fSEmmanuel Vadot 60301bad87aSRick Macklem20210426: 60401bad87aSRick Macklem Commit 875977314881 changed the internal KAPI between 60501bad87aSRick Macklem the nfsd and nfscommon modules. As such these modules 60601bad87aSRick Macklem need to be rebuilt from sources. 60701bad87aSRick Macklem Without this patch in your NFSv4.1/4.2 server, enabling 60801bad87aSRick Macklem delegations by setting vfs.nfsd.issue_delegations non-zero 60901bad87aSRick Macklem is not recommended. 61001bad87aSRick Macklem 61168b7d9b5SRick Macklem20210411: 61268b7d9b5SRick Macklem Commit 7763814fc9c2 changed the internal KAPI between 61368b7d9b5SRick Macklem the krpc and NFS. As such, the krpc, nfscommon and 61468b7d9b5SRick Macklem nfscl modules must all be rebuilt from sources. 615d647d0d4SRick Macklem Without this patch, NFSv4.1/4.2 mounts should not 616d647d0d4SRick Macklem be done with the nfscbd(8) daemon running, to avoid 617d647d0d4SRick Macklem needing a working back channel for server->client RPCs. 61868b7d9b5SRick Macklem 6192b98ea2eSRick Macklem20210330: 6202b98ea2eSRick Macklem Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it 6212b98ea2eSRick Macklem handles binding of the back channel as required by RFC5661. 6222b98ea2eSRick Macklem Until this patch is in your server, avoid use of the "nconnects" 6232b98ea2eSRick Macklem mount option for Linux NFSv4.1/4.2 mounts. 6242b98ea2eSRick Macklem 625ba7ede0bSEd Maste20210225: 626ba7ede0bSEd Maste For 64-bit architectures the base system is now built with Position 627ba7ede0bSEd Maste Independent Executable (PIE) support enabled by default. It may be 628ba7ede0bSEd Maste disabled using the WITHOUT_PIE knob. A clean build is required. 629ba7ede0bSEd Maste 630d386f3a3SBjoern A. Zeeb20210128: 631d386f3a3SBjoern A. Zeeb Various LinuxKPI functionality was added which conflicts with DRM. 632bde57090SGordon Bergling Please update your drm-kmod port to after the __FreeBSD_version 1400003 633d386f3a3SBjoern A. Zeeb update. 634d386f3a3SBjoern A. Zeeb 635cb0259b6SWarner Losh20210121: 636cb0259b6SWarner Losh stable/13 branch created. 637cb0259b6SWarner Losh 63817101a25SAlexander Leidinger20210108: 63917101a25SAlexander Leidinger PC Card attachments for all devices have been removed. In the case of 64017101a25SAlexander Leidinger wi and cmx, the entire drivers were removed because they were only 64117101a25SAlexander Leidinger PC Card devices. FreeBSD_version 1300134 should be used for this 64217101a25SAlexander Leidinger since it was bumped so recently. 64317101a25SAlexander Leidinger 64417101a25SAlexander Leidinger20210107: 64517101a25SAlexander Leidinger Transport-independent parts of HID support have been split off the USB 64617101a25SAlexander Leidinger code in to separate subsystem. Kernel configs which include one of 64717101a25SAlexander Leidinger ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should 64817101a25SAlexander Leidinger be updated with adding of "device hid" line. 64917101a25SAlexander Leidinger 65017101a25SAlexander Leidinger20210105: 65117101a25SAlexander Leidinger ncurses installation has been modified to only keep the widechar 65217101a25SAlexander Leidinger enabled version. Incremental build is broken for that change, so it 65317101a25SAlexander Leidinger requires a clean build. 65417101a25SAlexander Leidinger 65517101a25SAlexander Leidinger20201223: 65617101a25SAlexander Leidinger The FreeBSD project has migrated from Subversion to Git. Temporary 65717101a25SAlexander Leidinger instructions can be found at 65817101a25SAlexander Leidinger https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md 65917101a25SAlexander Leidinger and other documents in that repo. 66017101a25SAlexander Leidinger 66117101a25SAlexander Leidinger20201216: 66217101a25SAlexander Leidinger The services database has been updated to cover more of the basic 66317101a25SAlexander Leidinger services expected in a modern system. The database is big enough 66417101a25SAlexander Leidinger that it will cause issues in mergemaster in Releases previous to 66517101a25SAlexander Leidinger 12.2 and 11.3, or in very old current systems from before r358154. 66617101a25SAlexander Leidinger 66717101a25SAlexander Leidinger20201215: 66817101a25SAlexander Leidinger Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb) 66917101a25SAlexander Leidinger may be installed from ports or packages. 67017101a25SAlexander Leidinger 67117101a25SAlexander Leidinger20201124: 67217101a25SAlexander Leidinger ping6 has been merged into ping. It can now be called as "ping -6". 67317101a25SAlexander Leidinger See ping(8) for details. 67417101a25SAlexander Leidinger 67517101a25SAlexander Leidinger20201108: 67617101a25SAlexander Leidinger Default value of net.add_addr_allfibs has been changed to 0. 67717101a25SAlexander Leidinger If you have multi-fib configuration and rely on existence of all 67817101a25SAlexander Leidinger interface routes in every fib, you need to set the above sysctl to 1. 67917101a25SAlexander Leidinger 68017101a25SAlexander Leidinger20201030: 68117101a25SAlexander Leidinger The internal pre-processor in the calendar(1) program has been 68217101a25SAlexander Leidinger extended to support more C pre-processor commands (e.g. #ifdef, #else, 68317101a25SAlexander Leidinger and #undef) and to detect unbalanced conditional statements. 68417101a25SAlexander Leidinger Error messages have been extended to include the filename and line 68517101a25SAlexander Leidinger number if processing stops to help fixing malformed data files. 68617101a25SAlexander Leidinger 68717101a25SAlexander Leidinger20201026: 68817101a25SAlexander Leidinger All the data files for the calendar(1) program, except calendar.freebsd, 68917101a25SAlexander Leidinger have been moved to the deskutils/calendar-data port, much like the 69017101a25SAlexander Leidinger jewish calendar entries were moved to deskutils/hebcal years ago. After 69117101a25SAlexander Leidinger make delete-old-files, you need to install it to retain full 69217101a25SAlexander Leidinger functionality. calendar(1) will issue a reminder for files it can't 69317101a25SAlexander Leidinger find. 69417101a25SAlexander Leidinger 69517101a25SAlexander Leidinger20200923: 69617101a25SAlexander Leidinger LINT files are no longer generated. We now include the relevant NOTES 69717101a25SAlexander Leidinger files. Note: This may cause conflicts with updating in some cases. 69817101a25SAlexander Leidinger find sys -name LINT\* -delete 69917101a25SAlexander Leidinger is suggested across this commit to remove the generated LINT files. 70017101a25SAlexander Leidinger 70117101a25SAlexander Leidinger If you have tried to update with generated files there, the svn 70217101a25SAlexander Leidinger command you want to un-auger the tree is 70317101a25SAlexander Leidinger cd sys/amd64/conf 70417101a25SAlexander Leidinger svn revert -R . 70517101a25SAlexander Leidinger and then do the above find from the top level. Substitute 'amd64' 70617101a25SAlexander Leidinger above with where the error message indicates a conflict. 70717101a25SAlexander Leidinger 70817101a25SAlexander Leidinger20200824: 70917101a25SAlexander Leidinger OpenZFS support has been integrated. Do not upgrade root pools until 71017101a25SAlexander Leidinger the loader is updated to support zstd. Furthermore, we caution against 71117101a25SAlexander Leidinger 'zpool upgrade' for the next few weeks. The change should be transparent 71217101a25SAlexander Leidinger unless you want to use new features. 71317101a25SAlexander Leidinger 71417101a25SAlexander Leidinger Not all "NO_CLEAN" build scenarios work across these changes. Many 71517101a25SAlexander Leidinger scenarios have been tested and fixed, but rebuilding kernels without 71617101a25SAlexander Leidinger rebuilding world may fail. 71717101a25SAlexander Leidinger 71817101a25SAlexander Leidinger The ZFS cache file has moved from /boot to /etc to match the OpenZFS 71917101a25SAlexander Leidinger upstream default. A fallback to /boot has been added for mountroot. 72017101a25SAlexander Leidinger 72117101a25SAlexander Leidinger Pool auto import behavior at boot has been moved from the kernel module 72217101a25SAlexander Leidinger to an explicit "zpool import -a" in one of the rc scripts enabled by 72317101a25SAlexander Leidinger zfs_enable=YES. This means your non-root zpools won't auto import until 72417101a25SAlexander Leidinger you upgrade your /etc/rc.d files. 72517101a25SAlexander Leidinger 72617101a25SAlexander Leidinger20200824: 72717101a25SAlexander Leidinger The resume code now notifies devd with the 'kernel' system 72817101a25SAlexander Leidinger rather than the old 'kern' subsystem to be consistent with 72917101a25SAlexander Leidinger other use. The old notification will be created as well, but 73017101a25SAlexander Leidinger will be removed prior to FreeBSD 14.0. 73117101a25SAlexander Leidinger 73217101a25SAlexander Leidinger20200821: 73317101a25SAlexander Leidinger r362275 changed the internal API between the kernel RPC and the 73417101a25SAlexander Leidinger NFS modules. As such, all the modules must be recompiled from 73517101a25SAlexander Leidinger sources. 73617101a25SAlexander Leidinger 73717101a25SAlexander Leidinger20200817: 73817101a25SAlexander Leidinger r364330 modified the internal API used between the NFS modules. 73917101a25SAlexander Leidinger As such, all the NFS modules must be re-compiled from sources. 74017101a25SAlexander Leidinger 74117101a25SAlexander Leidinger20200816: 74217101a25SAlexander Leidinger Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have 74317101a25SAlexander Leidinger been upgraded to 11.0.0. Please see the 20141231 entry below for 74417101a25SAlexander Leidinger information about prerequisites and upgrading, if you are not already 74517101a25SAlexander Leidinger using clang 3.5.0 or higher. 74617101a25SAlexander Leidinger 74717101a25SAlexander Leidinger20200810: 74817101a25SAlexander Leidinger r364092 modified the internal ABI used between the kernel NFS 74917101a25SAlexander Leidinger modules. As such, all of these modules need to be rebuilt 75017101a25SAlexander Leidinger from sources, so a version bump was done. 75117101a25SAlexander Leidinger 75217101a25SAlexander Leidinger20200807: 75317101a25SAlexander Leidinger Makefile.inc has been updated to work around the issue documented in 75417101a25SAlexander Leidinger 20200729. It was a case where the optimization of using symbolic links 75517101a25SAlexander Leidinger to point to binaries created a situation where we'd run new binaries 75617101a25SAlexander Leidinger with old libraries starting midway through the installworld process. 75717101a25SAlexander Leidinger 75817101a25SAlexander Leidinger20200729: 75917101a25SAlexander Leidinger r363679 has redefined some undefined behavior in regcomp(3); notably, 76017101a25SAlexander Leidinger extraneous escapes of most ordinary characters will no longer be 76117101a25SAlexander Leidinger accepted. An exp-run has identified all of the problems with this in 76217101a25SAlexander Leidinger ports, but other non-ports software may need extra escapes removed to 76317101a25SAlexander Leidinger continue to function. 76417101a25SAlexander Leidinger 76517101a25SAlexander Leidinger Because of this change, installworld may encounter the following error 76617101a25SAlexander Leidinger from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that 76717101a25SAlexander Leidinger you do not halt installworld. Instead, let it run to completion (whether 76817101a25SAlexander Leidinger successful or not) and run installworld once more. 76917101a25SAlexander Leidinger 77017101a25SAlexander Leidinger20200627: 77117101a25SAlexander Leidinger A new implementation of bc and dc has been imported in r362681. This 77217101a25SAlexander Leidinger implementation corrects non-conformant behavior of the previous bc 77317101a25SAlexander Leidinger and adds GNU bc compatible options. It offers a number of extensions, 77417101a25SAlexander Leidinger is much faster on large values, and has support for message catalogs 77517101a25SAlexander Leidinger (a number of languages are already supported, contributions of further 77617101a25SAlexander Leidinger languages welcome). The option WITHOUT_GH_BC can be used to build the 77717101a25SAlexander Leidinger world with the previous versions of bc and dc. 77817101a25SAlexander Leidinger 77917101a25SAlexander Leidinger20200625: 78017101a25SAlexander Leidinger r362639 changed the internal API used between the NFS kernel modules. 78117101a25SAlexander Leidinger As such, they all need to be rebuilt from sources. 78217101a25SAlexander Leidinger 78317101a25SAlexander Leidinger20200613: 78417101a25SAlexander Leidinger r362158 changed the arguments for VFS_CHECKEXP(). As such, any 78517101a25SAlexander Leidinger out of tree file systems need to be modified and rebuilt. 78617101a25SAlexander Leidinger Also, any file systems that are modules must be rebuilt. 78717101a25SAlexander Leidinger 78817101a25SAlexander Leidinger20200604: 78917101a25SAlexander Leidinger read(2) of a directory fd is now rejected by default. root may 79017101a25SAlexander Leidinger re-enable it for system root only on non-ZFS filesystems with the 79117101a25SAlexander Leidinger security.bsd.allow_read_dir sysctl(8) MIB if 79217101a25SAlexander Leidinger security.bsd.suser_enabled=1. 79317101a25SAlexander Leidinger 79417101a25SAlexander Leidinger It may be advised to setup aliases for grep to default to `-d skip` if 79517101a25SAlexander Leidinger commonly non-recursively grepping a list that includes directories and 79617101a25SAlexander Leidinger the potential for the resulting stderr output is not tolerable. Example 79717101a25SAlexander Leidinger aliases are now installed, commented out, in /root/.cshrc and 79817101a25SAlexander Leidinger /root/.shrc. 79917101a25SAlexander Leidinger 80017101a25SAlexander Leidinger20200523: 80117101a25SAlexander Leidinger Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have 80217101a25SAlexander Leidinger been upgraded to 10.0.1. Please see the 20141231 entry below for 80317101a25SAlexander Leidinger information about prerequisites and upgrading, if you are not already 80417101a25SAlexander Leidinger using clang 3.5.0 or higher. 80517101a25SAlexander Leidinger 80617101a25SAlexander Leidinger20200512: 80717101a25SAlexander Leidinger Support for obsolete compilers has been removed from the build system. 80817101a25SAlexander Leidinger Clang 6 and GCC 6.4 are the minimum supported versions. 80917101a25SAlexander Leidinger 81017101a25SAlexander Leidinger20200424: 81117101a25SAlexander Leidinger closefrom(2) has been moved under COMPAT12, and replaced in libc with a 81217101a25SAlexander Leidinger stub that calls close_range(2). If using a custom kernel configuration, 81317101a25SAlexander Leidinger you may want to ensure that the COMPAT_FREEBSD12 option is included, as 81417101a25SAlexander Leidinger a slightly older -CURRENT userland and older FreeBSD userlands may not 81517101a25SAlexander Leidinger be functional without closefrom(2). 81617101a25SAlexander Leidinger 81717101a25SAlexander Leidinger20200414: 81817101a25SAlexander Leidinger Upstream DTS from Linux 5.6 was merged and they now have the SID 81917101a25SAlexander Leidinger and THS (Secure ID controller and THermal Sensor) node present. 82017101a25SAlexander Leidinger The DTB overlays have now been removed from the tree for the H3/H5 and 82117101a25SAlexander Leidinger A64 SoCs and the aw_sid and aw_thermal driver have been updated to 82217101a25SAlexander Leidinger deal with upstream DTS. If you are using those overlays you need to 82317101a25SAlexander Leidinger remove them from loader.conf and update the DTBs on the FAT partition. 82417101a25SAlexander Leidinger 82517101a25SAlexander Leidinger20200310: 82617101a25SAlexander Leidinger Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have 82717101a25SAlexander Leidinger been upgraded to 10.0.0. Please see the 20141231 entry below for 82817101a25SAlexander Leidinger information about prerequisites and upgrading, if you are not already 82917101a25SAlexander Leidinger using clang 3.5.0 or higher. 83017101a25SAlexander Leidinger 83117101a25SAlexander Leidinger20200309: 83217101a25SAlexander Leidinger The amd(8) automount daemon has been removed from the source tree. 83317101a25SAlexander Leidinger As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting. 83417101a25SAlexander Leidinger amd is still available in the sysutils/am-utils port. 83517101a25SAlexander Leidinger 83617101a25SAlexander Leidinger20200301: 83717101a25SAlexander Leidinger Removed brooktree driver (bktr.4) from the tree. 83817101a25SAlexander Leidinger 83917101a25SAlexander Leidinger20200229: 84017101a25SAlexander Leidinger The WITH_GPL_DTC option has been removed. The BSD-licenced device tree 84117101a25SAlexander Leidinger compiler in usr.bin/dtc is used on all architectures which use dtc, and 84217101a25SAlexander Leidinger the GPL dtc is available (if needed) from the sysutils/dtc port. 84317101a25SAlexander Leidinger 84417101a25SAlexander Leidinger20200229: 84517101a25SAlexander Leidinger The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind 84617101a25SAlexander Leidinger is used by all supported CPU architectures. 84717101a25SAlexander Leidinger 84817101a25SAlexander Leidinger20200229: 84917101a25SAlexander Leidinger GCC 4.2.1 has been removed from the tree. The WITH_GCC, 85017101a25SAlexander Leidinger WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available. 85117101a25SAlexander Leidinger Users who wish to build FreeBSD with GCC must use the external toolchain 85217101a25SAlexander Leidinger ports or packages. 85317101a25SAlexander Leidinger 85417101a25SAlexander Leidinger20200220: 85517101a25SAlexander Leidinger ncurses has been updated to a newer version (6.2-20200215). Given the ABI 85617101a25SAlexander Leidinger has changed, users will have to rebuild all the ports that are linked to 85717101a25SAlexander Leidinger ncurses. 85817101a25SAlexander Leidinger 85917101a25SAlexander Leidinger20200217: 86017101a25SAlexander Leidinger The size of struct vnet and the magic cookie have changed. 86117101a25SAlexander Leidinger Users need to recompile libkvm and all modules using VIMAGE 86217101a25SAlexander Leidinger together with their new kernel. 86317101a25SAlexander Leidinger 86417101a25SAlexander Leidinger20200212: 86517101a25SAlexander Leidinger Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB, 86617101a25SAlexander Leidinger NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update 86717101a25SAlexander Leidinger your Makefiles and scripts to define MK_<var>=no instead as required. 86817101a25SAlexander Leidinger 86917101a25SAlexander Leidinger One exception to this is that program or library Makefiles should 87017101a25SAlexander Leidinger define MAN to empty rather than setting MK_MAN=no. 87117101a25SAlexander Leidinger 87217101a25SAlexander Leidinger20200108: 87317101a25SAlexander Leidinger Clang/LLVM is now the default compiler and LLD the default 87417101a25SAlexander Leidinger linker for riscv64. 87517101a25SAlexander Leidinger 87617101a25SAlexander Leidinger20200107: 87717101a25SAlexander Leidinger make universe no longer uses GCC 4.2.1 on any architectures. 87817101a25SAlexander Leidinger Architectures not supported by in-tree Clang/LLVM require an 87917101a25SAlexander Leidinger external toolchain package. 88017101a25SAlexander Leidinger 88117101a25SAlexander Leidinger20200104: 88217101a25SAlexander Leidinger GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1 88317101a25SAlexander Leidinger retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX 88417101a25SAlexander Leidinger options default to off for all supported CPU architectures. As a 88517101a25SAlexander Leidinger short-term transition aid they may be enabled via WITH_* options. 88617101a25SAlexander Leidinger GCC 4.2.1 is expected to be removed from the tree on 2020-03-31. 88717101a25SAlexander Leidinger 88817101a25SAlexander Leidinger20200102: 88917101a25SAlexander Leidinger Support for armv5 has been disconnected and is being removed. The 89017101a25SAlexander Leidinger machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid. 89117101a25SAlexander Leidinger You must now use a MACHINE_ARCH of armv6 or armv7. The default 89217101a25SAlexander Leidinger MACHINE_ARCH for MACHINE=arm is now armv7. 89317101a25SAlexander Leidinger 89417101a25SAlexander Leidinger20191226: 89517101a25SAlexander Leidinger Clang/LLVM is now the default compiler for all powerpc architectures. 89617101a25SAlexander Leidinger LLD is now the default linker for powerpc64. The change for powerpc64 89717101a25SAlexander Leidinger also includes a change to the ELFv2 ABI, incompatible with the existing 89817101a25SAlexander Leidinger ABI. 89917101a25SAlexander Leidinger 90017101a25SAlexander Leidinger20191226: 90117101a25SAlexander Leidinger Kernel-loadable random(4) modules are no longer unloadable. 90217101a25SAlexander Leidinger 90317101a25SAlexander Leidinger20191222: 90417101a25SAlexander Leidinger Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have 90517101a25SAlexander Leidinger been upgraded to 9.0.1. Please see the 20141231 entry below for 90617101a25SAlexander Leidinger information about prerequisites and upgrading, if you are not already 90717101a25SAlexander Leidinger using clang 3.5.0 or higher. 90817101a25SAlexander Leidinger 90917101a25SAlexander Leidinger20191212: 91017101a25SAlexander Leidinger r355677 has modified the internal interface used between the 91117101a25SAlexander Leidinger NFS modules in the kernel. As such, they must all be upgraded 91217101a25SAlexander Leidinger simultaneously. I will do a version bump for this. 91317101a25SAlexander Leidinger 91417101a25SAlexander Leidinger20191205: 91517101a25SAlexander Leidinger The root certificates of the Mozilla CA Certificate Store have been 91617101a25SAlexander Leidinger imported into the base system and can be managed with the certctl(8) 91717101a25SAlexander Leidinger utility. If you have installed the security/ca_root_nss port or package 91817101a25SAlexander Leidinger with the ETCSYMLINK option (the default), be advised that there may be 91917101a25SAlexander Leidinger differences between those included in the port and those included in 92017101a25SAlexander Leidinger base due to differences in nss branch used as well as general update 92117101a25SAlexander Leidinger frequency. Note also that certctl(8) cannot manage certs in the 92217101a25SAlexander Leidinger format used by the security/ca_root_nss port. 92317101a25SAlexander Leidinger 92417101a25SAlexander Leidinger20191120: 92517101a25SAlexander Leidinger The amd(8) automount daemon has been disabled by default, and will be 92617101a25SAlexander Leidinger removed in the future. As of FreeBSD 10.1 the autofs(5) is available 92717101a25SAlexander Leidinger for automounting. 92817101a25SAlexander Leidinger 92917101a25SAlexander Leidinger20191107: 93017101a25SAlexander Leidinger The nctgpio and wbwd drivers have been moved to the superio bus. 93117101a25SAlexander Leidinger If you have one of these drivers in a kernel configuration, then 93217101a25SAlexander Leidinger you should add device superio to it. If you use one of these drivers 93317101a25SAlexander Leidinger as a module and you compile a custom set of modules, then you should 93417101a25SAlexander Leidinger add superio to the set. 93517101a25SAlexander Leidinger 93617101a25SAlexander Leidinger20191021: 93717101a25SAlexander Leidinger KPIs for network drivers to access interface addresses have changed. 93817101a25SAlexander Leidinger Users need to recompile NIC driver modules together with kernel. 93917101a25SAlexander Leidinger 94017101a25SAlexander Leidinger20191021: 94117101a25SAlexander Leidinger The net.link.tap.user_open sysctl no longer prevents user opening of 94217101a25SAlexander Leidinger already created /dev/tapNN devices. Access is still controlled by 94317101a25SAlexander Leidinger node permissions, just like tun devices. The net.link.tap.user_open 94417101a25SAlexander Leidinger sysctl is now used only to allow users to perform devfs cloning of 94517101a25SAlexander Leidinger tap devices, and the subsequent open may not succeed if the user is not 94617101a25SAlexander Leidinger in the appropriate group. This sysctl may be deprecated/removed 94717101a25SAlexander Leidinger completely in the future. 94817101a25SAlexander Leidinger 94917101a25SAlexander Leidinger20191009: 95017101a25SAlexander Leidinger mips, powerpc, and sparc64 are no longer built as part of 95117101a25SAlexander Leidinger universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If 95217101a25SAlexander Leidinger not defined, mips, powerpc, and sparc64 builds will look for 95317101a25SAlexander Leidinger the xtoolchain binaries and if installed use them for universe 95417101a25SAlexander Leidinger builds. As llvm 9.0 becomes vetted for these architectures, they 95517101a25SAlexander Leidinger will be removed from the list. 95617101a25SAlexander Leidinger 95717101a25SAlexander Leidinger20191009: 95817101a25SAlexander Leidinger Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have 95917101a25SAlexander Leidinger been upgraded to 9.0.0. Please see the 20141231 entry below for 96017101a25SAlexander Leidinger information about prerequisites and upgrading, if you are not already 96117101a25SAlexander Leidinger using clang 3.5.0 or higher. 96217101a25SAlexander Leidinger 96317101a25SAlexander Leidinger20191003: 96417101a25SAlexander Leidinger The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from 96517101a25SAlexander Leidinger GENERIC. They are available as modules and can be loaded by adding 96617101a25SAlexander Leidinger to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES", 96717101a25SAlexander Leidinger hptnr_load="YES", or hptrr_load="YES", respectively. 96817101a25SAlexander Leidinger 96917101a25SAlexander Leidinger20190913: 97017101a25SAlexander Leidinger ntpd no longer by default locks its pages in memory, allowing them 97117101a25SAlexander Leidinger to be paged out by the kernel. Use rlimit memlock to restore 97217101a25SAlexander Leidinger historic BSD behaviour. For example, add "rlimit memlock 32" 97317101a25SAlexander Leidinger to ntp.conf to lock up to 32 MB of ntpd address space in memory. 97417101a25SAlexander Leidinger 97517101a25SAlexander Leidinger20190823: 97617101a25SAlexander Leidinger Several of ping6's options have been renamed for better consistency 97717101a25SAlexander Leidinger with ping. If you use any of -ARWXaghmrtwx, you must update your 97817101a25SAlexander Leidinger scripts. See ping6(8) for details. 97917101a25SAlexander Leidinger 98017101a25SAlexander Leidinger20190727: 98117101a25SAlexander Leidinger The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls 98217101a25SAlexander Leidinger and the "-o sync_unmount" and "-o init_backgrounded" mount options have 98317101a25SAlexander Leidinger been removed from mount_fusefs(8). You can safely remove them from 98417101a25SAlexander Leidinger your scripts, because they had no effect. 98517101a25SAlexander Leidinger 98617101a25SAlexander Leidinger The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize, 98717101a25SAlexander Leidinger vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable, 98817101a25SAlexander Leidinger vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate 98917101a25SAlexander Leidinger sysctls have been removed. If you felt the need to set any of them to 99017101a25SAlexander Leidinger a non-default value, please tell asomers@FreeBSD.org why. 99117101a25SAlexander Leidinger 99217101a25SAlexander Leidinger20190713: 99317101a25SAlexander Leidinger Default permissions on the /var/account/acct file (and copies of it 99417101a25SAlexander Leidinger rotated by periodic daily scripts) are changed from 0644 to 0640 99517101a25SAlexander Leidinger because the file contains sensitive information that should not be 99617101a25SAlexander Leidinger world-readable. If the /var/account directory must be created by 99717101a25SAlexander Leidinger rc.d/accounting, the mode used is now 0750. Admins who use the 99817101a25SAlexander Leidinger accounting feature are encouraged to change the mode of an existing 99917101a25SAlexander Leidinger /var/account directory to 0750 or 0700. 100017101a25SAlexander Leidinger 100117101a25SAlexander Leidinger20190620: 100217101a25SAlexander Leidinger Entropy collection and the /dev/random device are no longer optional 100317101a25SAlexander Leidinger components. The "device random" option has been removed. 100417101a25SAlexander Leidinger Implementations of distilling algorithms can still be made loadable 100517101a25SAlexander Leidinger with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko). 100617101a25SAlexander Leidinger 100717101a25SAlexander Leidinger20190612: 100817101a25SAlexander Leidinger Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have 100917101a25SAlexander Leidinger been upgraded to 8.0.1. Please see the 20141231 entry below for 101017101a25SAlexander Leidinger information about prerequisites and upgrading, if you are not already 101117101a25SAlexander Leidinger using clang 3.5.0 or higher. 101217101a25SAlexander Leidinger 101317101a25SAlexander Leidinger20190608: 101417101a25SAlexander Leidinger A fix was applied to i386 kernel modules to avoid panics with 101517101a25SAlexander Leidinger dpcpu or vnet. Users need to recompile i386 kernel modules 101617101a25SAlexander Leidinger having pcpu or vnet sections or they will refuse to load. 101717101a25SAlexander Leidinger 101817101a25SAlexander Leidinger20190513: 101917101a25SAlexander Leidinger User-wired pages now have their own counter, 102017101a25SAlexander Leidinger vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed 102117101a25SAlexander Leidinger to vm.max_user_wired and changed from an unsigned int to an unsigned 102217101a25SAlexander Leidinger long. bhyve VMs wired with the -S are now subject to the user 102317101a25SAlexander Leidinger wiring limit; the vm.max_user_wired sysctl may need to be tuned to 102417101a25SAlexander Leidinger avoid running into the limit. 102517101a25SAlexander Leidinger 102617101a25SAlexander Leidinger20190507: 102717101a25SAlexander Leidinger The IPSEC option has been removed from GENERIC. Users requiring 102817101a25SAlexander Leidinger ipsec(4) must now load the ipsec(4) kernel module. 102917101a25SAlexander Leidinger 103017101a25SAlexander Leidinger20190507: 103117101a25SAlexander Leidinger The tap(4) driver has been folded into tun(4), and the module has been 103217101a25SAlexander Leidinger renamed to tuntap. You should update any kld_list="if_tap" or 103317101a25SAlexander Leidinger kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or 103417101a25SAlexander Leidinger if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap 103517101a25SAlexander Leidinger module instead, and "device tap" or "device tun" entries in kernel 103617101a25SAlexander Leidinger config files to select the tuntap device instead. 103717101a25SAlexander Leidinger 103817101a25SAlexander Leidinger20190418: 103917101a25SAlexander Leidinger The following knobs have been added related to tradeoffs between 104017101a25SAlexander Leidinger safe use of the random device and availability in the absence of 104117101a25SAlexander Leidinger entropy: 104217101a25SAlexander Leidinger 104317101a25SAlexander Leidinger kern.random.initial_seeding.bypass_before_seeding: tunable; set 104417101a25SAlexander Leidinger non-zero to bypass the random device prior to seeding, or zero to 104517101a25SAlexander Leidinger block random requests until the random device is initially seeded. 104617101a25SAlexander Leidinger For now, set to 1 (unsafe) by default to restore pre-r346250 boot 104717101a25SAlexander Leidinger availability properties. 104817101a25SAlexander Leidinger 104917101a25SAlexander Leidinger kern.random.initial_seeding.read_random_bypassed_before_seeding: 105017101a25SAlexander Leidinger read-only diagnostic sysctl that is set when bypass is enabled and 105117101a25SAlexander Leidinger read_random(9) is bypassed, to enable programmatic handling of this 105217101a25SAlexander Leidinger initial condition, if desired. 105317101a25SAlexander Leidinger 105417101a25SAlexander Leidinger kern.random.initial_seeding.arc4random_bypassed_before_seeding: 105517101a25SAlexander Leidinger Similar to the above, but for arc4random(9) initial seeding. 105617101a25SAlexander Leidinger 105717101a25SAlexander Leidinger kern.random.initial_seeding.disable_bypass_warnings: tunable; set 105817101a25SAlexander Leidinger non-zero to disable warnings in dmesg when the same conditions are 105917101a25SAlexander Leidinger met as for the diagnostic sysctls above. Defaults to zero, i.e., 106017101a25SAlexander Leidinger produce warnings in dmesg when the conditions are met. 106117101a25SAlexander Leidinger 106217101a25SAlexander Leidinger20190416: 106317101a25SAlexander Leidinger The loadable random module KPI has changed; the random_infra_init() 106417101a25SAlexander Leidinger routine now requires a 3rd function pointer for a bool (*)(void) 106517101a25SAlexander Leidinger method that returns true if the random device is seeded (and 106617101a25SAlexander Leidinger therefore unblocked). 106717101a25SAlexander Leidinger 106817101a25SAlexander Leidinger20190404: 106917101a25SAlexander Leidinger r345895 reverts r320698. This implies that an nfsuserd(8) daemon 107017101a25SAlexander Leidinger built from head sources between r320757 (July 6, 2017) and 107117101a25SAlexander Leidinger r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock" 107217101a25SAlexander Leidinger is added to the command line. 107317101a25SAlexander Leidinger nfsuserd daemons built from head sources that are post-r338192 are 107417101a25SAlexander Leidinger not affected and should continue to work. 107517101a25SAlexander Leidinger 107617101a25SAlexander Leidinger20190320: 107717101a25SAlexander Leidinger The fuse(4) module has been renamed to fusefs(4) for consistency with 107817101a25SAlexander Leidinger other filesystems. You should update any kld_load="fuse" entries in 107917101a25SAlexander Leidinger /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and 108017101a25SAlexander Leidinger "options FUSE" entries in kernel config files. 108117101a25SAlexander Leidinger 108217101a25SAlexander Leidinger20190304: 108317101a25SAlexander Leidinger Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 108417101a25SAlexander Leidinger 8.0.0. Please see the 20141231 entry below for information about 108517101a25SAlexander Leidinger prerequisites and upgrading, if you are not already using clang 3.5.0 108617101a25SAlexander Leidinger or higher. 108717101a25SAlexander Leidinger 108817101a25SAlexander Leidinger20190226: 108917101a25SAlexander Leidinger geom_uzip(4) depends on the new module xz. If geom_uzip is statically 109017101a25SAlexander Leidinger compiled into your custom kernel, add 'device xz' statement to the 109117101a25SAlexander Leidinger kernel config. 109217101a25SAlexander Leidinger 109317101a25SAlexander Leidinger20190219: 109417101a25SAlexander Leidinger drm and drm2 have been removed from the tree. Please see 109517101a25SAlexander Leidinger https://wiki.freebsd.org/Graphics for the latest information on 109617101a25SAlexander Leidinger migrating to the drm ports. 109717101a25SAlexander Leidinger 109817101a25SAlexander Leidinger20190131: 109917101a25SAlexander Leidinger Iflib is no longer unconditionally compiled into the kernel. Drivers 110017101a25SAlexander Leidinger using iflib and statically compiled into the kernel, now require 110117101a25SAlexander Leidinger the 'device iflib' config option. For the same drivers loaded as 110217101a25SAlexander Leidinger modules on kernels not having 'device iflib', the iflib.ko module 110317101a25SAlexander Leidinger is loaded automatically. 110417101a25SAlexander Leidinger 110517101a25SAlexander Leidinger20190125: 110617101a25SAlexander Leidinger The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration 110717101a25SAlexander Leidinger options no longer exist since r343219 and r343427 respectively; 110817101a25SAlexander Leidinger nothing uses them, so they should be just removed from custom 110917101a25SAlexander Leidinger kernel config files. 111017101a25SAlexander Leidinger 111117101a25SAlexander Leidinger20181230: 111217101a25SAlexander Leidinger r342635 changes the way efibootmgr(8) works by requiring users to add 111317101a25SAlexander Leidinger the -b (bootnum) parameter for commands where the bootnum was previously 111417101a25SAlexander Leidinger specified with each option. For example 'efibootmgr -B 0001' is now 111517101a25SAlexander Leidinger 'efibootmgr -B -b 0001'. 111617101a25SAlexander Leidinger 111717101a25SAlexander Leidinger20181220: 111817101a25SAlexander Leidinger r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport 111917101a25SAlexander Leidinger in the same as it is applied to NFSv2 and 3. This implies that NFSv4 112017101a25SAlexander Leidinger servers that have vfs.nfsd.nfs_privport set will only allow mounts 112117101a25SAlexander Leidinger from clients using a reserved port. Since both the FreeBSD and Linux 112217101a25SAlexander Leidinger NFSv4 clients use reserved ports by default, this should not affect 112317101a25SAlexander Leidinger most NFSv4 mounts. 112417101a25SAlexander Leidinger 112517101a25SAlexander Leidinger20181219: 112617101a25SAlexander Leidinger The XLP config has been removed. We can't support 64-bit atomics in this 112717101a25SAlexander Leidinger kernel because it is running in 32-bit mode. XLP users must transition 112817101a25SAlexander Leidinger to running a 64-bit kernel (XLP64 or XLPN32). 112917101a25SAlexander Leidinger 113017101a25SAlexander Leidinger The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is 113117101a25SAlexander Leidinger the preferred emulator today and we don't need two different ones. 113217101a25SAlexander Leidinger 113317101a25SAlexander Leidinger The old sibyte / swarm / Broadcom BCM1250 support has been 113417101a25SAlexander Leidinger removed from the mips port. 113517101a25SAlexander Leidinger 113617101a25SAlexander Leidinger20181211: 113717101a25SAlexander Leidinger Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 113817101a25SAlexander Leidinger 7.0.1. Please see the 20141231 entry below for information about 113917101a25SAlexander Leidinger prerequisites and upgrading, if you are not already using clang 3.5.0 114017101a25SAlexander Leidinger or higher. 114117101a25SAlexander Leidinger 114217101a25SAlexander Leidinger20181211: 114317101a25SAlexander Leidinger Remove the timed and netdate programs from the base tree. Setting 114417101a25SAlexander Leidinger the time with these daemons has been obsolete for over a decade. 114517101a25SAlexander Leidinger 114617101a25SAlexander Leidinger20181126: 114717101a25SAlexander Leidinger On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld 114817101a25SAlexander Leidinger linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as 114917101a25SAlexander Leidinger it produces broken binaries when ifuncs are in use. Users needing 115017101a25SAlexander Leidinger GNU ld should install the binutils port or package. 115117101a25SAlexander Leidinger 115217101a25SAlexander Leidinger20181123: 115317101a25SAlexander Leidinger The BSD crtbegin and crtend code has been enabled by default. It has 115417101a25SAlexander Leidinger had extensive testing on amd64, arm64, and i386. It can be disabled 115517101a25SAlexander Leidinger by building a world with -DWITHOUT_BSD_CRTBEGIN. 115617101a25SAlexander Leidinger 115717101a25SAlexander Leidinger20181115: 115817101a25SAlexander Leidinger The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue) 115917101a25SAlexander Leidinger has been converted to a port (misc/ctm) and will be removed from 116017101a25SAlexander Leidinger FreeBSD-13. It is available as a package (ctm) for all supported 116117101a25SAlexander Leidinger FreeBSD versions. 116217101a25SAlexander Leidinger 116317101a25SAlexander Leidinger20181110: 116417101a25SAlexander Leidinger The default newsyslog.conf(5) file has been changed to only include 116517101a25SAlexander Leidinger files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if 116617101a25SAlexander Leidinger the filenames end in '.conf' and do not begin with a '.'. 116717101a25SAlexander Leidinger 116817101a25SAlexander Leidinger You should check the configuration files in these two directories match 116917101a25SAlexander Leidinger this naming convention. You can verify which configuration files are 117017101a25SAlexander Leidinger being included using the command: 117117101a25SAlexander Leidinger $ newsyslog -Nrv 117217101a25SAlexander Leidinger 1173cb0259b6SWarner Losh20181019: 1174cb0259b6SWarner Losh Stable/12 was branched created. 1175cb0259b6SWarner Losh 117617101a25SAlexander Leidinger20181015: 117717101a25SAlexander Leidinger Ports for the DRM modules have been simplified. Now, amd64 users should 117817101a25SAlexander Leidinger just install the drm-kmod port. All others should install 117917101a25SAlexander Leidinger drm-legacy-kmod. 118017101a25SAlexander Leidinger 118117101a25SAlexander Leidinger Graphics hardware that's newer than about 2010 usually works with 118217101a25SAlexander Leidinger drm-kmod. For hardware older than 2013, however, some users will need 118317101a25SAlexander Leidinger to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older 118417101a25SAlexander Leidinger than 2008 usually only works in drm-legacy-kmod. The graphics team can 118517101a25SAlexander Leidinger only commit to hardware made since 2013 due to the complexity of the 118617101a25SAlexander Leidinger market and difficulty to test all the older cards effectively. If you 118717101a25SAlexander Leidinger have hardware supported by drm-kmod, you are strongly encouraged to use 118817101a25SAlexander Leidinger that as you will get better support. 118917101a25SAlexander Leidinger 119017101a25SAlexander Leidinger Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined 119117101a25SAlexander Leidinger elsewhere, the drm and drm2 modules will be eliminated from the src base 119217101a25SAlexander Leidinger soon (with a limited exception for arm). Please update to the package 119317101a25SAlexander Leidinger asap and report any issues to x11@freebsd.org. 119417101a25SAlexander Leidinger 119517101a25SAlexander Leidinger Generally, anybody using the drm*-kmod packages should add 119617101a25SAlexander Leidinger WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty 119717101a25SAlexander Leidinger cross-threading surprises, especially with automatic driver 119817101a25SAlexander Leidinger loading from X11 startup. These will become the defaults in 13-current 119917101a25SAlexander Leidinger shortly. 120017101a25SAlexander Leidinger 120117101a25SAlexander Leidinger20181012: 120217101a25SAlexander Leidinger The ixlv(4) driver has been renamed to iavf(4). As a consequence, 120317101a25SAlexander Leidinger custom kernel and module loading configuration files must be updated 120417101a25SAlexander Leidinger accordingly. Moreover, interfaces previous presented as ixlvN to the 120517101a25SAlexander Leidinger system are now exposed as iavfN and network configuration files must 120617101a25SAlexander Leidinger be adjusted as necessary. 120717101a25SAlexander Leidinger 120817101a25SAlexander Leidinger20181009: 120917101a25SAlexander Leidinger OpenSSL has been updated to version 1.1.1. This update included 121017101a25SAlexander Leidinger additional various API changes throughout the base system. It is 121117101a25SAlexander Leidinger important to rebuild third-party software after upgrading. The value 121217101a25SAlexander Leidinger of __FreeBSD_version has been bumped accordingly. 121317101a25SAlexander Leidinger 121417101a25SAlexander Leidinger20181006: 121517101a25SAlexander Leidinger The legacy DRM modules and drivers have now been added to the loader's 121617101a25SAlexander Leidinger module blacklist, in favor of loading them with kld_list in rc.conf(5). 121717101a25SAlexander Leidinger The module blacklist may be overridden with the loader.conf(5) 121817101a25SAlexander Leidinger 'module_blacklist' variable, but loading them via rc.conf(5) is strongly 121917101a25SAlexander Leidinger encouraged. 122017101a25SAlexander Leidinger 122117101a25SAlexander Leidinger20181002: 122217101a25SAlexander Leidinger The cam(4) based nda(4) driver will be used over nvd(4) by default on 122317101a25SAlexander Leidinger powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or 122417101a25SAlexander Leidinger loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing 122517101a25SAlexander Leidinger driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the 122617101a25SAlexander Leidinger nda device name. 122717101a25SAlexander Leidinger 122817101a25SAlexander Leidinger20180913: 122917101a25SAlexander Leidinger Reproducible build mode is now on by default, in preparation for 123017101a25SAlexander Leidinger FreeBSD 12.0. This eliminates build metadata such as the user, 123117101a25SAlexander Leidinger host, and time from the kernel (and uname), unless the working tree 123217101a25SAlexander Leidinger corresponds to a modified checkout from a version control system. 123317101a25SAlexander Leidinger The previous behavior can be obtained by setting the /etc/src.conf 123417101a25SAlexander Leidinger knob WITHOUT_REPRODUCIBLE_BUILD. 123517101a25SAlexander Leidinger 123617101a25SAlexander Leidinger20180826: 123717101a25SAlexander Leidinger The Yarrow CSPRNG has been removed from the kernel as it has not been 123817101a25SAlexander Leidinger supported by its designers since at least 2003. Fortuna has been the 123917101a25SAlexander Leidinger default since FreeBSD-11. 124017101a25SAlexander Leidinger 124117101a25SAlexander Leidinger20180822: 124217101a25SAlexander Leidinger devctl freeze/thaw have gone into the tree, the rc scripts have been 124317101a25SAlexander Leidinger updated to use them and devmatch has been changed. You should update 124417101a25SAlexander Leidinger kernel, userland and rc scripts all at the same time. 124517101a25SAlexander Leidinger 124617101a25SAlexander Leidinger20180818: 124717101a25SAlexander Leidinger The default interpreter has been switched from 4th to Lua. 124817101a25SAlexander Leidinger LOADER_DEFAULT_INTERP, documented in build(7), will override the default 124917101a25SAlexander Leidinger interpreter. If you have custom FORTH code you will need to set 125017101a25SAlexander Leidinger LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in 125117101a25SAlexander Leidinger src.conf for the build. This will create default hard links between 125217101a25SAlexander Leidinger loader and loader_4th instead of loader and loader_lua, the new default. 125317101a25SAlexander Leidinger If you are using UEFI it will create the proper hard link to loader.efi. 125417101a25SAlexander Leidinger 125517101a25SAlexander Leidinger bhyve uses userboot.so. It remains 4th-only until some issues are solved 125617101a25SAlexander Leidinger regarding coexisting with multiple versions of FreeBSD are resolved. 125717101a25SAlexander Leidinger 125817101a25SAlexander Leidinger20180815: 125917101a25SAlexander Leidinger ls(1) now respects the COLORTERM environment variable used in other 126017101a25SAlexander Leidinger systems and software to indicate that a colored terminal is both 126117101a25SAlexander Leidinger supported and desired. If ls(1) is suddenly emitting colors, they may 126217101a25SAlexander Leidinger be disabled again by either removing the unwanted COLORTERM from your 126317101a25SAlexander Leidinger environment, or using `ls --color=never`. The ls(1) specific CLICOLOR 126417101a25SAlexander Leidinger may not be observed in a future release. 126517101a25SAlexander Leidinger 126617101a25SAlexander Leidinger20180808: 126717101a25SAlexander Leidinger The default pager for most commands has been changed to "less". To 126817101a25SAlexander Leidinger restore the old behavior, set PAGER="more" and MANPAGER="more -s" in 126917101a25SAlexander Leidinger your environment. 127017101a25SAlexander Leidinger 127117101a25SAlexander Leidinger20180731: 127217101a25SAlexander Leidinger The jedec_ts(4) driver has been removed. A superset of its functionality 127317101a25SAlexander Leidinger is available in the jedec_dimm(4) driver, and the manpage for that 127417101a25SAlexander Leidinger driver includes migration instructions. If you have "device jedec_ts" 127517101a25SAlexander Leidinger in your kernel configuration file, it must be removed. 127617101a25SAlexander Leidinger 127717101a25SAlexander Leidinger20180730: 127817101a25SAlexander Leidinger amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default. 127917101a25SAlexander Leidinger This should have no effect if the kernel is booted via BIOS/legacy boot. 128017101a25SAlexander Leidinger EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system 128117101a25SAlexander Leidinger has a buggy firmware that prevents a successful boot due to use of 128217101a25SAlexander Leidinger runtime services. 128317101a25SAlexander Leidinger 128417101a25SAlexander Leidinger20180727: 128517101a25SAlexander Leidinger Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale 128617101a25SAlexander Leidinger support has been removed from the tree. These ports were 128717101a25SAlexander Leidinger obsolete and/or known to be broken for many years. 128817101a25SAlexander Leidinger 128917101a25SAlexander Leidinger20180723: 129017101a25SAlexander Leidinger loader.efi has been augmented to participate more fully in the 129117101a25SAlexander Leidinger UEFI boot manager protocol. loader.efi will now look at the 129217101a25SAlexander Leidinger BootXXXX environment variable to determine if a specific kernel 129317101a25SAlexander Leidinger or root partition was specified. XXXX is derived from BootCurrent. 129417101a25SAlexander Leidinger efibootmgr(8) manages these standard UEFI variables. 129517101a25SAlexander Leidinger 129617101a25SAlexander Leidinger20180720: 129717101a25SAlexander Leidinger zfsloader's functionality has now been folded into loader. 129817101a25SAlexander Leidinger zfsloader is no longer necessary once you've updated your 129917101a25SAlexander Leidinger boot blocks. For a transition period, we will install a 130017101a25SAlexander Leidinger hardlink for zfsloader to loader to allow a smooth transition 130117101a25SAlexander Leidinger until the boot blocks can be updated (hard link because old 130217101a25SAlexander Leidinger zfs boot blocks don't understand symlinks). 130317101a25SAlexander Leidinger 130417101a25SAlexander Leidinger20180719: 130517101a25SAlexander Leidinger ARM64 now have efifb support, if you want to have serial console 130617101a25SAlexander Leidinger on your arm64 board when an screen is connected and the bootloader 130717101a25SAlexander Leidinger setup a frame buffer for us to use, just add : 130817101a25SAlexander Leidinger boot_serial=YES 130917101a25SAlexander Leidinger boot_multicons=YES 131017101a25SAlexander Leidinger in /boot/loader.conf 131117101a25SAlexander Leidinger For Raspberry Pi 3 (RPI) users, this is needed even if you don't have 131217101a25SAlexander Leidinger an screen connected as the firmware will setup a frame buffer are that 131317101a25SAlexander Leidinger u-boot will expose as an EFI frame buffer. 131417101a25SAlexander Leidinger 131517101a25SAlexander Leidinger20180719: 131617101a25SAlexander Leidinger New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster 131717101a25SAlexander Leidinger or take steps to update /etc/passwd before doing installworld on 131817101a25SAlexander Leidinger existing systems. Do not skip the "mergemaster -Fp" step before 131917101a25SAlexander Leidinger installworld, as described in the update procedures near the bottom 132017101a25SAlexander Leidinger of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd 132117101a25SAlexander Leidinger if the new mac_ntpd(4) policy is available, unless ntpd_flags or 132217101a25SAlexander Leidinger the ntp config file contain options that change file/dir locations. 132317101a25SAlexander Leidinger When such options (e.g., "statsdir" or "crypto") are used, ntpd can 132417101a25SAlexander Leidinger still be run as non-root by setting ntpd_user=ntpd in rc.conf, after 132517101a25SAlexander Leidinger taking steps to ensure that all required files/dirs are accessible 132617101a25SAlexander Leidinger by the ntpd user. 132717101a25SAlexander Leidinger 132817101a25SAlexander Leidinger20180717: 132917101a25SAlexander Leidinger Big endian arm support has been removed. 133017101a25SAlexander Leidinger 133117101a25SAlexander Leidinger20180711: 133217101a25SAlexander Leidinger The static environment setup in kernel configs is no longer mutually 133317101a25SAlexander Leidinger exclusive with the loader(8) environment by default. In order to 133417101a25SAlexander Leidinger restore the previous default behavior of disabling the loader(8) 133517101a25SAlexander Leidinger environment if a static environment is present, you must specify 133617101a25SAlexander Leidinger loader_env.disabled=1 in the static environment. 133717101a25SAlexander Leidinger 133817101a25SAlexander Leidinger20180705: 133917101a25SAlexander Leidinger The ABI of syscalls used by management tools like sockstat and 134017101a25SAlexander Leidinger netstat has been broken to allow 32-bit binaries to work on 134117101a25SAlexander Leidinger 64-bit kernels without modification. These programs will need 134217101a25SAlexander Leidinger to match the kernel in order to function. External programs may 134317101a25SAlexander Leidinger require minor modifications to accommodate a change of type in 134417101a25SAlexander Leidinger structures from pointers to 64-bit virtual addresses. 134517101a25SAlexander Leidinger 134617101a25SAlexander Leidinger20180702: 134717101a25SAlexander Leidinger On i386 and amd64 atomics are now inlined. Out of tree modules using 134817101a25SAlexander Leidinger atomics will need to be rebuilt. 134917101a25SAlexander Leidinger 135017101a25SAlexander Leidinger20180701: 135117101a25SAlexander Leidinger The '%I' format in the kern.corefile sysctl limits the number of 135217101a25SAlexander Leidinger core files that a process can generate to the number stored in the 135317101a25SAlexander Leidinger debug.ncores sysctl. The '%I' format is replaced by the single digit 135417101a25SAlexander Leidinger index. Previously, if all indexes were taken the kernel would overwrite 135517101a25SAlexander Leidinger only a core file with the highest index in a filename. 135617101a25SAlexander Leidinger Currently the system will create a new core file if there is a free 135717101a25SAlexander Leidinger index or if all slots are taken it will overwrite the oldest one. 135817101a25SAlexander Leidinger 135917101a25SAlexander Leidinger20180630: 136017101a25SAlexander Leidinger Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 136117101a25SAlexander Leidinger 6.0.1. Please see the 20141231 entry below for information about 136217101a25SAlexander Leidinger prerequisites and upgrading, if you are not already using clang 3.5.0 136317101a25SAlexander Leidinger or higher. 136417101a25SAlexander Leidinger 136517101a25SAlexander Leidinger20180628: 136617101a25SAlexander Leidinger r335753 introduced a new quoting method. However, etc/devd/devmatch.conf 136717101a25SAlexander Leidinger needed to be changed to work with it. This change was made with r335763 136817101a25SAlexander Leidinger and requires a mergemaster / etcupdate / etc to update the installed 136917101a25SAlexander Leidinger file. 137017101a25SAlexander Leidinger 137117101a25SAlexander Leidinger20180612: 137217101a25SAlexander Leidinger r334930 changed the interface between the NFS modules, so they all 137317101a25SAlexander Leidinger need to be rebuilt. r335018 did a __FreeBSD_version bump for this. 137417101a25SAlexander Leidinger 137517101a25SAlexander Leidinger20180530: 137617101a25SAlexander Leidinger As of r334391 lld is the default amd64 system linker; it is installed 137717101a25SAlexander Leidinger as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no 137817101a25SAlexander Leidinger longer necessary. 137917101a25SAlexander Leidinger 138017101a25SAlexander Leidinger20180530: 138117101a25SAlexander Leidinger The kernel / userland interface for devinfo changed, so you'll 138217101a25SAlexander Leidinger need a new kernel and userland as a pair for it to work (rebuilding 138317101a25SAlexander Leidinger lib/libdevinfo is all that's required). devinfo and devmatch will 138417101a25SAlexander Leidinger not work, but everything else will when there's a mismatch. 138517101a25SAlexander Leidinger 138617101a25SAlexander Leidinger20180523: 138717101a25SAlexander Leidinger The on-disk format for hwpmc callchain records has changed to include 138817101a25SAlexander Leidinger threadid corresponding to a given record. This changes the field offsets 138917101a25SAlexander Leidinger and thus requires that libpmcstat be rebuilt before using a kernel 139017101a25SAlexander Leidinger later than r334108. 139117101a25SAlexander Leidinger 139217101a25SAlexander Leidinger20180517: 139317101a25SAlexander Leidinger The vxge(4) driver has been removed. This driver was introduced into 139417101a25SAlexander Leidinger HEAD one week before the Exar left the Ethernet market and is not 139517101a25SAlexander Leidinger known to be used. If you have device vxge in your kernel config file 139617101a25SAlexander Leidinger it must be removed. 139717101a25SAlexander Leidinger 139817101a25SAlexander Leidinger20180510: 139917101a25SAlexander Leidinger The amd64 kernel now requires a ld that supports ifunc to produce a 140017101a25SAlexander Leidinger working kernel, either lld or a newer binutils. lld is built by default 140117101a25SAlexander Leidinger on amd64, and the 'buildkernel' target uses it automatically. However, 140217101a25SAlexander Leidinger it is not the default linker, so building the kernel the traditional 140317101a25SAlexander Leidinger way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for 140417101a25SAlexander Leidinger binutils port/package). lld will soon be default, and this requirement 140517101a25SAlexander Leidinger will go away. 140617101a25SAlexander Leidinger 140717101a25SAlexander Leidinger NOTE: As of r334391 lld is the default system linker on amd64, and no 140817101a25SAlexander Leidinger workaround is necessary. 140917101a25SAlexander Leidinger 141017101a25SAlexander Leidinger20180508: 141117101a25SAlexander Leidinger The nxge(4) driver has been removed. This driver was for PCI-X 10g 141217101a25SAlexander Leidinger cards made by s2io/Neterion. The company was acquired by Exar and 141317101a25SAlexander Leidinger no longer sells or supports Ethernet products. If you have device 141417101a25SAlexander Leidinger nxge in your kernel config file it must be removed. 141517101a25SAlexander Leidinger 141617101a25SAlexander Leidinger20180504: 141717101a25SAlexander Leidinger The tz database (tzdb) has been updated to 2018e. This version more 141817101a25SAlexander Leidinger correctly models time stamps in time zones with negative DST such as 141917101a25SAlexander Leidinger Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and 142017101a25SAlexander Leidinger Africa/Windhoek (1994/2017). This does not affect the UT offsets, only 142117101a25SAlexander Leidinger time zone abbreviations and the tm_isdst flag. 142217101a25SAlexander Leidinger 142317101a25SAlexander Leidinger20180502: 142417101a25SAlexander Leidinger The ixgb(4) driver has been removed. This driver was for an early and 142517101a25SAlexander Leidinger uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel 142617101a25SAlexander Leidinger quickly shifted to the long lived ixgbe family. If you have device 142717101a25SAlexander Leidinger ixgb in your kernel config file it must be removed. 142817101a25SAlexander Leidinger 142917101a25SAlexander Leidinger20180501: 143017101a25SAlexander Leidinger The lmc(4) driver has been removed. This was a WAN interface 143117101a25SAlexander Leidinger card that was already reportedly rare in 2003, and had an ambiguous 143217101a25SAlexander Leidinger license. If you have device lmc in your kernel config file it must 143317101a25SAlexander Leidinger be removed. 143417101a25SAlexander Leidinger 143517101a25SAlexander Leidinger20180413: 143617101a25SAlexander Leidinger Support for Arcnet networks has been removed. If you have device 143717101a25SAlexander Leidinger arcnet or device cm in your kernel config file they must be 143817101a25SAlexander Leidinger removed. 143917101a25SAlexander Leidinger 144017101a25SAlexander Leidinger20180411: 144117101a25SAlexander Leidinger Support for FDDI networks has been removed. If you have device 144217101a25SAlexander Leidinger fddi or device fpa in your kernel config file they must be 144317101a25SAlexander Leidinger removed. 144417101a25SAlexander Leidinger 144517101a25SAlexander Leidinger20180406: 144617101a25SAlexander Leidinger In addition to supporting RFC 3164 formatted messages, the 144717101a25SAlexander Leidinger syslogd(8) service is now capable of parsing RFC 5424 formatted 144817101a25SAlexander Leidinger log messages. The main benefit of using RFC 5424 is that clients 144917101a25SAlexander Leidinger may now send log messages with timestamps containing year numbers, 145017101a25SAlexander Leidinger microseconds and time zone offsets. 145117101a25SAlexander Leidinger 145217101a25SAlexander Leidinger Similarly, the syslog(3) C library function has been altered to 145317101a25SAlexander Leidinger send RFC 5424 formatted messages to the local system logging 145417101a25SAlexander Leidinger daemon. On systems using syslogd(8), this change should have no 145517101a25SAlexander Leidinger negative impact, as long as syslogd(8) and the C library are 145617101a25SAlexander Leidinger updated at the same time. On systems using a different system 145717101a25SAlexander Leidinger logging daemon, it may be necessary to make configuration 145817101a25SAlexander Leidinger adjustments, depending on the software used. 145917101a25SAlexander Leidinger 146017101a25SAlexander Leidinger When using syslog-ng, add the 'syslog-protocol' flag to local 146117101a25SAlexander Leidinger input sources to enable parsing of RFC 5424 formatted messages: 146217101a25SAlexander Leidinger 146317101a25SAlexander Leidinger source src { 146417101a25SAlexander Leidinger unix-dgram("/var/run/log" flags(syslog-protocol)); 146517101a25SAlexander Leidinger } 146617101a25SAlexander Leidinger 146717101a25SAlexander Leidinger When using rsyslog, disable the 'SysSock.UseSpecialParser' option 146817101a25SAlexander Leidinger of the 'imuxsock' module to let messages be processed by the 146917101a25SAlexander Leidinger regular RFC 3164/5424 parsing pipeline: 147017101a25SAlexander Leidinger 147117101a25SAlexander Leidinger module(load="imuxsock" SysSock.UseSpecialParser="off") 147217101a25SAlexander Leidinger 147317101a25SAlexander Leidinger Do note that these changes only affect communication between local 147417101a25SAlexander Leidinger applications and syslogd(8). The format that syslogd(8) uses to 147517101a25SAlexander Leidinger store messages on disk or forward messages to other systems 147617101a25SAlexander Leidinger remains unchanged. syslogd(8) still uses RFC 3164 for these 147717101a25SAlexander Leidinger purposes. Options to customize this behaviour will be added in the 147817101a25SAlexander Leidinger future. Utilities that process log files stored in /var/log are 147917101a25SAlexander Leidinger thus expected to continue to function as before. 148017101a25SAlexander Leidinger 148117101a25SAlexander Leidinger __FreeBSD_version has been incremented to 1200061 to denote this 148217101a25SAlexander Leidinger change. 148317101a25SAlexander Leidinger 148417101a25SAlexander Leidinger20180328: 148517101a25SAlexander Leidinger Support for token ring networks has been removed. If you 148617101a25SAlexander Leidinger have "device token" in your kernel config you should remove 148717101a25SAlexander Leidinger it. No device drivers supported token ring. 148817101a25SAlexander Leidinger 148917101a25SAlexander Leidinger20180323: 149017101a25SAlexander Leidinger makefs was modified to be able to tag ISO9660 El Torito boot catalog 149117101a25SAlexander Leidinger entries as EFI instead of overloading the i386 tag as done previously. 149217101a25SAlexander Leidinger The amd64 mkisoimages.sh script used to build amd64 ISO images for 149317101a25SAlexander Leidinger release was updated to use this. This may mean that makefs must be 149417101a25SAlexander Leidinger updated before "make cdrom" can be run in the release directory. This 149517101a25SAlexander Leidinger should be as simple as: 149617101a25SAlexander Leidinger 149717101a25SAlexander Leidinger $ cd $SRCDIR/usr.sbin/makefs 149817101a25SAlexander Leidinger $ make depend all install 149917101a25SAlexander Leidinger 150017101a25SAlexander Leidinger20180212: 150117101a25SAlexander Leidinger FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for 150217101a25SAlexander Leidinger now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf. 150317101a25SAlexander Leidinger Co-existence for the transition period will come shortly. Booting is a 150417101a25SAlexander Leidinger complex environment and test coverage for Lua-enabled loaders has been 150517101a25SAlexander Leidinger thin, so it would be prudent to assume it might not work and make 150617101a25SAlexander Leidinger provisions for backup boot methods. 150717101a25SAlexander Leidinger 150817101a25SAlexander Leidinger20180211: 150917101a25SAlexander Leidinger devmatch functionality has been turned on in devd. It will automatically 151017101a25SAlexander Leidinger load drivers for unattached devices. This may cause unexpected drivers 151117101a25SAlexander Leidinger to be loaded. Please report any problems to current@ and 151217101a25SAlexander Leidinger imp@freebsd.org. 151317101a25SAlexander Leidinger 151417101a25SAlexander Leidinger20180114: 151517101a25SAlexander Leidinger Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 151617101a25SAlexander Leidinger 6.0.0. Please see the 20141231 entry below for information about 151717101a25SAlexander Leidinger prerequisites and upgrading, if you are not already using clang 3.5.0 151817101a25SAlexander Leidinger or higher. 151917101a25SAlexander Leidinger 152017101a25SAlexander Leidinger20180110: 152117101a25SAlexander Leidinger LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker. 152217101a25SAlexander Leidinger This means it is used to link the kernel and userland libraries and 152317101a25SAlexander Leidinger executables, but is not yet installed as /usr/bin/ld by default. 152417101a25SAlexander Leidinger 152517101a25SAlexander Leidinger To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set 152617101a25SAlexander Leidinger WITHOUT_LLD_BOOTSTRAP=yes 152717101a25SAlexander Leidinger 152817101a25SAlexander Leidinger20180110: 152917101a25SAlexander Leidinger On i386, pmtimer has been removed. Its functionality has been folded 153017101a25SAlexander Leidinger into apm. It was a no-op on ACPI in current for a while now (but was 153117101a25SAlexander Leidinger still needed on i386 in FreeBSD 11 and earlier). Users may need to 153217101a25SAlexander Leidinger remove it from kernel config files. 153317101a25SAlexander Leidinger 153417101a25SAlexander Leidinger20180104: 153517101a25SAlexander Leidinger The use of RSS hash from the network card aka flowid has been 153617101a25SAlexander Leidinger disabled by default for lagg(4) as it's currently incompatible with 153717101a25SAlexander Leidinger the lacp and loadbalance protocols. 153817101a25SAlexander Leidinger 153917101a25SAlexander Leidinger This can be re-enabled by setting the following in loader.conf: 154017101a25SAlexander Leidinger net.link.lagg.default_use_flowid="1" 154117101a25SAlexander Leidinger 154217101a25SAlexander Leidinger20180102: 154317101a25SAlexander Leidinger The SW_WATCHDOG option is no longer necessary to enable the 154417101a25SAlexander Leidinger hardclock-based software watchdog if no hardware watchdog is 154517101a25SAlexander Leidinger configured. As before, SW_WATCHDOG will cause the software 154617101a25SAlexander Leidinger watchdog to be enabled even if a hardware watchdog is configured. 154717101a25SAlexander Leidinger 154817101a25SAlexander Leidinger20171215: 154917101a25SAlexander Leidinger r326887 fixes the issue described in the 20171214 UPDATING entry. 155017101a25SAlexander Leidinger r326888 flips the switch back to building GELI support always. 155117101a25SAlexander Leidinger 155217101a25SAlexander Leidinger20171214: 155317101a25SAlexander Leidinger r362593 broke ZFS + GELI support for reasons unknown. However, 155417101a25SAlexander Leidinger it also broke ZFS support generally, so GELI has been turned off 155517101a25SAlexander Leidinger by default as the lesser evil in r326857. If you boot off ZFS and/or 155617101a25SAlexander Leidinger GELI, it might not be a good time to update. 155717101a25SAlexander Leidinger 155817101a25SAlexander Leidinger20171125: 155917101a25SAlexander Leidinger PowerPC users must update loader(8) by rebuilding world before 156017101a25SAlexander Leidinger installing a new kernel, as the protocol connecting them has 156117101a25SAlexander Leidinger changed. Without the update, loader metadata will not be passed 156217101a25SAlexander Leidinger successfully to the kernel and users will have to enter their 156317101a25SAlexander Leidinger root partition at the kernel mountroot prompt to continue booting. 156417101a25SAlexander Leidinger Newer versions of loader can boot old kernels without issue. 156517101a25SAlexander Leidinger 156617101a25SAlexander Leidinger20171110: 156717101a25SAlexander Leidinger The LOADER_FIREWIRE_SUPPORT build variable has been renamed to 156817101a25SAlexander Leidinger WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed 156917101a25SAlexander Leidinger to WITH/OUT_LOADER_GELI. 157017101a25SAlexander Leidinger 157117101a25SAlexander Leidinger20171106: 157217101a25SAlexander Leidinger The naive and non-compliant support of posix_fallocate(2) in ZFS 157317101a25SAlexander Leidinger has been removed as of r325320. The system call now returns EINVAL 157417101a25SAlexander Leidinger when used on a ZFS file. Although the new behavior complies with the 157517101a25SAlexander Leidinger standard, some consumers are not prepared to cope with it. 157617101a25SAlexander Leidinger One known victim is lld prior to r325420. 157717101a25SAlexander Leidinger 157817101a25SAlexander Leidinger20171102: 157917101a25SAlexander Leidinger Building in a FreeBSD src checkout will automatically create object 158017101a25SAlexander Leidinger directories now rather than store files in the current directory if 158117101a25SAlexander Leidinger 'make obj' was not ran. Calling 'make obj' is no longer necessary. 158217101a25SAlexander Leidinger This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in 158317101a25SAlexander Leidinger /etc/src-env.conf (not /etc/src.conf), or passing the option in the 158417101a25SAlexander Leidinger environment. 158517101a25SAlexander Leidinger 158617101a25SAlexander Leidinger20171101: 158717101a25SAlexander Leidinger The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native 158817101a25SAlexander Leidinger builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified 158917101a25SAlexander Leidinger /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old 159017101a25SAlexander Leidinger format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf, 159117101a25SAlexander Leidinger the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building. 159217101a25SAlexander Leidinger The UNIFIED_OBJDIR option is a transitional feature that will be 159317101a25SAlexander Leidinger removed for 12.0 release; please migrate to the new format for any 159417101a25SAlexander Leidinger tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather 159517101a25SAlexander Leidinger than hardcoding paths. 159617101a25SAlexander Leidinger 159717101a25SAlexander Leidinger20171028: 159817101a25SAlexander Leidinger The native-xtools target no longer installs the files by default to the 159917101a25SAlexander Leidinger OBJDIR. Use the native-xtools-install target with a DESTDIR to install 160017101a25SAlexander Leidinger to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin. 160117101a25SAlexander Leidinger 160217101a25SAlexander Leidinger20171021: 160317101a25SAlexander Leidinger As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT 160417101a25SAlexander Leidinger options are changing from controlling the build if defined / undefined 160517101a25SAlexander Leidinger to controlling the build with explicit 'yes' or 'no' values. They will 160617101a25SAlexander Leidinger shift to WITH/WITHOUT options to match other options in the system. 160717101a25SAlexander Leidinger 160817101a25SAlexander Leidinger20171010: 160917101a25SAlexander Leidinger libstand has turned into a private library for sys/boot use only. 161017101a25SAlexander Leidinger It is no longer supported as a public interface outside of sys/boot. 161117101a25SAlexander Leidinger 161217101a25SAlexander Leidinger20171005: 161317101a25SAlexander Leidinger The arm port has split armv6 into armv6 and armv7. armv7 is now 161417101a25SAlexander Leidinger a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system 161517101a25SAlexander Leidinger and are running a kernel from before r324363, you will need to add 161617101a25SAlexander Leidinger MACHINE_ARCH=armv7 to 'make buildworld' to do a native build. 161717101a25SAlexander Leidinger 161817101a25SAlexander Leidinger20171003: 161917101a25SAlexander Leidinger When building multiple kernels using KERNCONF, non-existent KERNCONF 162017101a25SAlexander Leidinger files will produce an error and buildkernel will fail. Previously 162117101a25SAlexander Leidinger missing KERNCONF files silently failed giving no indication as to 162217101a25SAlexander Leidinger why, only to subsequently discover during installkernel that the 162317101a25SAlexander Leidinger desired kernel was never built in the first place. 162417101a25SAlexander Leidinger 162517101a25SAlexander Leidinger20170912: 162617101a25SAlexander Leidinger The default serial number format for CTL LUNs has changed. This will 162717101a25SAlexander Leidinger affect users who use /dev/diskid/* device nodes, or whose FibreChannel 162817101a25SAlexander Leidinger or iSCSI clients care about their LUNs' serial numbers. Users who 162917101a25SAlexander Leidinger require serial number stability should hardcode serial numbers in 163017101a25SAlexander Leidinger /etc/ctl.conf . 163117101a25SAlexander Leidinger 163217101a25SAlexander Leidinger20170912: 163317101a25SAlexander Leidinger For 32-bit arm compiled for hard-float support, soft-floating point 163417101a25SAlexander Leidinger binaries now always get their shared libraries from 163517101a25SAlexander Leidinger LD_SOFT_LIBRARY_PATH (in the past, this was only used if 163617101a25SAlexander Leidinger /usr/libsoft also existed). Only users with a hard-float ld.so, but 163717101a25SAlexander Leidinger soft-float everything else should be affected. 163817101a25SAlexander Leidinger 163917101a25SAlexander Leidinger20170826: 164017101a25SAlexander Leidinger The geli password typed at boot is now hidden. To restore the previous 164117101a25SAlexander Leidinger behavior, see geli(8) for configuration options. 164217101a25SAlexander Leidinger 164317101a25SAlexander Leidinger20170825: 164417101a25SAlexander Leidinger Move PMTUD blackhole counters to TCPSTATS and remove them from bare 164517101a25SAlexander Leidinger sysctl values. Minor nit, but requires a rebuild of both world/kernel 164617101a25SAlexander Leidinger to complete. 164717101a25SAlexander Leidinger 164817101a25SAlexander Leidinger20170814: 164917101a25SAlexander Leidinger "make check" behavior (made in ^/head@r295380) has been changed to 165017101a25SAlexander Leidinger execute from a limited sandbox, as opposed to executing from 165117101a25SAlexander Leidinger ${TESTSDIR}. 165217101a25SAlexander Leidinger 165317101a25SAlexander Leidinger Behavioral changes: 165417101a25SAlexander Leidinger - The "beforecheck" and "aftercheck" targets are now specified. 165517101a25SAlexander Leidinger - ${CHECKDIR} (added in commit noted above) has been removed. 165617101a25SAlexander Leidinger - Legacy behavior can be enabled by setting 165717101a25SAlexander Leidinger WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment. 165817101a25SAlexander Leidinger 165917101a25SAlexander Leidinger If the limited sandbox mode is enabled, "make check" will execute 166017101a25SAlexander Leidinger "make distribution", then install, execute the tests, and clean up the 166117101a25SAlexander Leidinger sandbox if successful. 166217101a25SAlexander Leidinger 166317101a25SAlexander Leidinger The "make distribution" and "make install" targets are typically run as 166417101a25SAlexander Leidinger root to set appropriate permissions and ownership at installation time. 166517101a25SAlexander Leidinger The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the 166617101a25SAlexander Leidinger environment if executing "make check" with limited sandbox mode using 166717101a25SAlexander Leidinger an unprivileged user. 166817101a25SAlexander Leidinger 166917101a25SAlexander Leidinger20170808: 167017101a25SAlexander Leidinger Since the switch to GPT disk labels, fsck for UFS/FFS has been 167117101a25SAlexander Leidinger unable to automatically find alternate superblocks. As of r322297, 167217101a25SAlexander Leidinger the information needed to find alternate superblocks has been 167317101a25SAlexander Leidinger moved to the end of the area reserved for the boot block. 167417101a25SAlexander Leidinger Filesystems created with a newfs of this vintage or later 167517101a25SAlexander Leidinger will create the recovery information. If you have a filesystem 167617101a25SAlexander Leidinger created prior to this change and wish to have a recovery block 167717101a25SAlexander Leidinger created for your filesystem, you can do so by running fsck in 167817101a25SAlexander Leidinger foreground mode (i.e., do not use the -p or -y options). As it 167917101a25SAlexander Leidinger starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS'' 168017101a25SAlexander Leidinger to which you should answer yes. 168117101a25SAlexander Leidinger 168217101a25SAlexander Leidinger20170728: 168317101a25SAlexander Leidinger As of r321665, an NFSv4 server configuration that services 168417101a25SAlexander Leidinger Kerberos mounts or clients that do not support the uid/gid in 168517101a25SAlexander Leidinger owner/owner_group string capability, must explicitly enable 168617101a25SAlexander Leidinger the nfsuserd daemon by adding nfsuserd_enable="YES" to the 168717101a25SAlexander Leidinger machine's /etc/rc.conf file. 168817101a25SAlexander Leidinger 168917101a25SAlexander Leidinger20170722: 169017101a25SAlexander Leidinger Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0. 169117101a25SAlexander Leidinger Please see the 20141231 entry below for information about prerequisites 169217101a25SAlexander Leidinger and upgrading, if you are not already using clang 3.5.0 or higher. 169317101a25SAlexander Leidinger 169417101a25SAlexander Leidinger20170701: 169517101a25SAlexander Leidinger WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the 169617101a25SAlexander Leidinger r-commands (rlogin, rsh, etc.) to be built with the base system. 169717101a25SAlexander Leidinger 169817101a25SAlexander Leidinger20170625: 169917101a25SAlexander Leidinger The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is 170017101a25SAlexander Leidinger a very major ABI incompatible change, so users of FreeBSD/powerpc must 170117101a25SAlexander Leidinger be careful when performing source upgrades. It is best to run 170217101a25SAlexander Leidinger 'make installworld' from an alternate root system, either a live 170317101a25SAlexander Leidinger CD/memory stick, or a temporary root partition. Additionally, all ports 170417101a25SAlexander Leidinger must be recompiled. powerpc64 is largely unaffected, except in the case 170517101a25SAlexander Leidinger of 32-bit compatibility. All 32-bit binaries will be affected. 170617101a25SAlexander Leidinger 170717101a25SAlexander Leidinger20170623: 170817101a25SAlexander Leidinger Forward compatibility for the "ino64" project have been committed. This 170917101a25SAlexander Leidinger will allow most new binaries to run on older kernels in a limited 171017101a25SAlexander Leidinger fashion. This prevents many of the common foot-shooting actions in the 171117101a25SAlexander Leidinger upgrade as well as the limited ability to roll back the kernel across 171217101a25SAlexander Leidinger the ino64 upgrade. Complicated use cases may not work properly, though 171317101a25SAlexander Leidinger enough simpler ones work to allow recovery in most situations. 171417101a25SAlexander Leidinger 171517101a25SAlexander Leidinger20170620: 171617101a25SAlexander Leidinger Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC 171717101a25SAlexander Leidinger if you require the GPL compiler. 171817101a25SAlexander Leidinger 17190527c9bdSWarner Losh20170619: 17200527c9bdSWarner Losh Forward compatibility for the "ino64" project have been committed. This 17210527c9bdSWarner Losh will allow most new binaries to run on older kernels in a limited 17220527c9bdSWarner Losh fashion. This prevents many of the common foot-shooting actions in the 17230527c9bdSWarner Losh upgrade as well as the limited ability to roll back the kernel across 17240527c9bdSWarner Losh the ino64 upgrade. Complicated use cases may not work properly, though 17250527c9bdSWarner Losh enough simpler ones work to allow recovery in most situations. 17260527c9bdSWarner Losh 172717101a25SAlexander Leidinger20170618: 172817101a25SAlexander Leidinger The internal ABI used for communication between the NFS kernel modules 172917101a25SAlexander Leidinger was changed by r320085, so __FreeBSD_version was bumped to 173017101a25SAlexander Leidinger ensure all the NFS related modules are updated together. 173117101a25SAlexander Leidinger 173217101a25SAlexander Leidinger20170617: 173317101a25SAlexander Leidinger The ABI of struct event was changed by extending the data 173417101a25SAlexander Leidinger member to 64bit and adding ext fields. For upgrade, same 173517101a25SAlexander Leidinger precautions as for the entry 20170523 "ino64" must be 173617101a25SAlexander Leidinger followed. 173717101a25SAlexander Leidinger 173817101a25SAlexander Leidinger20170531: 173917101a25SAlexander Leidinger The GNU roff toolchain has been removed from base. To render manpages 174017101a25SAlexander Leidinger which are not supported by mandoc(1), man(1) can fallback on GNU roff 174117101a25SAlexander Leidinger from ports (and recommends to install it). 174217101a25SAlexander Leidinger To render roff(7) documents, consider using GNU roff from ports or the 174317101a25SAlexander Leidinger heirloom doctools roff toolchain from ports via pkg install groff or 174417101a25SAlexander Leidinger via pkg install heirloom-doctools. 174517101a25SAlexander Leidinger 174617101a25SAlexander Leidinger20170524: 174717101a25SAlexander Leidinger The ath(4) and ath_hal(4) modules now build piecemeal to allow for 174817101a25SAlexander Leidinger smaller runtime footprint builds. This is useful for embedded systems 174917101a25SAlexander Leidinger which only require one chipset support. 175017101a25SAlexander Leidinger 175117101a25SAlexander Leidinger If you load it as a module, make sure this is in /boot/loader.conf: 175217101a25SAlexander Leidinger 175317101a25SAlexander Leidinger if_ath_load="YES" 175417101a25SAlexander Leidinger 175517101a25SAlexander Leidinger This will load the HAL, all chip/RF backends and if_ath_pci. 175617101a25SAlexander Leidinger If you have if_ath_pci in /boot/loader.conf, ensure it is after 175717101a25SAlexander Leidinger if_ath or it will not load any HAL chipset support. 175817101a25SAlexander Leidinger 175917101a25SAlexander Leidinger If you want to selectively load things (eg on cheaper ARM/MIPS 176017101a25SAlexander Leidinger platforms where RAM is at a premium) you should: 176117101a25SAlexander Leidinger 176217101a25SAlexander Leidinger * load ath_hal 176317101a25SAlexander Leidinger * load the chip modules in question 176417101a25SAlexander Leidinger * load ath_rate, ath_dfs 176517101a25SAlexander Leidinger * load ath_main 176617101a25SAlexander Leidinger * load if_ath_pci and/or if_ath_ahb depending upon your particular 176717101a25SAlexander Leidinger bus bind type - this is where probe/attach is done. 176817101a25SAlexander Leidinger 176917101a25SAlexander Leidinger For further comments/feedback, poke adrian@ . 177017101a25SAlexander Leidinger 177117101a25SAlexander Leidinger20170523: 177217101a25SAlexander Leidinger The "ino64" 64-bit inode project has been committed, which extends 177317101a25SAlexander Leidinger a number of types to 64 bits. Upgrading in place requires care and 177417101a25SAlexander Leidinger adherence to the documented upgrade procedure. 177517101a25SAlexander Leidinger 177617101a25SAlexander Leidinger If using a custom kernel configuration ensure that the 177717101a25SAlexander Leidinger COMPAT_FREEBSD11 option is included (as during the upgrade the 177817101a25SAlexander Leidinger system will be running the ino64 kernel with the existing world). 177917101a25SAlexander Leidinger 178017101a25SAlexander Leidinger For the safest in-place upgrade begin by removing previous build 178117101a25SAlexander Leidinger artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full 178217101a25SAlexander Leidinger procedure documented below under the heading "To rebuild everything and 178317101a25SAlexander Leidinger install it on the current system." Specifically, a reboot is required 178417101a25SAlexander Leidinger after installing the new kernel before installing world. While an 178517101a25SAlexander Leidinger installworld normally works by accident from multiuser after rebooting 178617101a25SAlexander Leidinger the proper kernel, there are many cases where this will fail across this 178717101a25SAlexander Leidinger upgrade and installworld from single user is required. 178817101a25SAlexander Leidinger 178917101a25SAlexander Leidinger20170424: 179017101a25SAlexander Leidinger The NATM framework including the en(4), fatm(4), hatm(4), and 179117101a25SAlexander Leidinger patm(4) devices has been removed. Consumers should plan a 179217101a25SAlexander Leidinger migration before the end-of-life date for FreeBSD 11. 179317101a25SAlexander Leidinger 179417101a25SAlexander Leidinger20170420: 179517101a25SAlexander Leidinger GNU diff has been replaced by a BSD licensed diff. Some features of GNU 179617101a25SAlexander Leidinger diff has not been implemented, if those are needed a newer version of 179717101a25SAlexander Leidinger GNU diff is available via the diffutils package under the gdiff name. 179817101a25SAlexander Leidinger 179917101a25SAlexander Leidinger20170413: 180017101a25SAlexander Leidinger As of r316810 for ipfilter, keep frags is no longer assumed when 180117101a25SAlexander Leidinger keep state is specified in a rule. r316810 aligns ipfilter with 180217101a25SAlexander Leidinger documentation in man pages separating keep frags from keep state. 180317101a25SAlexander Leidinger This allows keep state to be specified without forcing keep frags 180417101a25SAlexander Leidinger and allows keep frags to be specified independently of keep state. 180517101a25SAlexander Leidinger To maintain previous behaviour, also specify keep frags with 180617101a25SAlexander Leidinger keep state (as documented in ipf.conf.5). 180717101a25SAlexander Leidinger 180817101a25SAlexander Leidinger20170407: 180917101a25SAlexander Leidinger arm64 builds now use the base system LLD 4.0.0 linker by default, 181017101a25SAlexander Leidinger instead of requiring that the aarch64-binutils port or package be 181117101a25SAlexander Leidinger installed. To continue using aarch64-binutils, set 181217101a25SAlexander Leidinger CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin . 181317101a25SAlexander Leidinger 181417101a25SAlexander Leidinger20170405: 181517101a25SAlexander Leidinger The UDP optimization in entry 20160818 that added the sysctl 181617101a25SAlexander Leidinger net.inet.udp.require_l2_bcast has been reverted. L2 broadcast 181717101a25SAlexander Leidinger packets will no longer be treated as L3 broadcast packets. 181817101a25SAlexander Leidinger 181917101a25SAlexander Leidinger20170331: 182017101a25SAlexander Leidinger Binds and sends to the loopback addresses, IPv6 and IPv4, will now 182117101a25SAlexander Leidinger use any explicitly assigned loopback address available in the jail 182217101a25SAlexander Leidinger instead of using the first assigned address of the jail. 182317101a25SAlexander Leidinger 182417101a25SAlexander Leidinger20170329: 182517101a25SAlexander Leidinger The ctl.ko module no longer implements the iSCSI target frontend: 182617101a25SAlexander Leidinger cfiscsi.ko does instead. 182717101a25SAlexander Leidinger 182817101a25SAlexander Leidinger If building cfiscsi.ko as a kernel module, the module can be loaded 182917101a25SAlexander Leidinger via one of the following methods: 183017101a25SAlexander Leidinger - `cfiscsi_load="YES"` in loader.conf(5). 183117101a25SAlexander Leidinger - Add `cfiscsi` to `$kld_list` in rc.conf(5). 183217101a25SAlexander Leidinger - ctladm(8)/ctld(8), when compiled with iSCSI support 183317101a25SAlexander Leidinger (`WITH_ISCSI=yes` in src.conf(5)) 183417101a25SAlexander Leidinger 183517101a25SAlexander Leidinger Please see cfiscsi(4) for more details. 183617101a25SAlexander Leidinger 183717101a25SAlexander Leidinger20170316: 183817101a25SAlexander Leidinger The mmcsd.ko module now additionally depends on geom_flashmap.ko. 183917101a25SAlexander Leidinger Also, mmc.ko and mmcsd.ko need to be a matching pair built from the 184017101a25SAlexander Leidinger same source (previously, the dependency of mmcsd.ko on mmc.ko was 184117101a25SAlexander Leidinger missing, but mmcsd.ko now will refuse to load if it is incompatible 184217101a25SAlexander Leidinger with mmc.ko). 184317101a25SAlexander Leidinger 184417101a25SAlexander Leidinger20170315: 184517101a25SAlexander Leidinger The syntax of ipfw(8) named states was changed to avoid ambiguity. 184617101a25SAlexander Leidinger If you have used named states in the firewall rules, you need to modify 184717101a25SAlexander Leidinger them after installworld and before rebooting. Now named states must 184817101a25SAlexander Leidinger be prefixed with colon. 184917101a25SAlexander Leidinger 185017101a25SAlexander Leidinger20170311: 185117101a25SAlexander Leidinger The old drm (sys/dev/drm/) drivers for i915 and radeon have been 185217101a25SAlexander Leidinger removed as the userland we provide cannot use them. The KMS version 185317101a25SAlexander Leidinger (sys/dev/drm2) supports the same hardware. 185417101a25SAlexander Leidinger 185517101a25SAlexander Leidinger20170302: 185617101a25SAlexander Leidinger Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0. 185717101a25SAlexander Leidinger Please see the 20141231 entry below for information about prerequisites 185817101a25SAlexander Leidinger and upgrading, if you are not already using clang 3.5.0 or higher. 185917101a25SAlexander Leidinger 186017101a25SAlexander Leidinger20170221: 186117101a25SAlexander Leidinger The code that provides support for ZFS .zfs/ directory functionality 186217101a25SAlexander Leidinger has been reimplemented. It's not possible now to create a snapshot 186317101a25SAlexander Leidinger by mkdir under .zfs/snapshot/. That should be the only user visible 186417101a25SAlexander Leidinger change. 186517101a25SAlexander Leidinger 186617101a25SAlexander Leidinger20170216: 186717101a25SAlexander Leidinger EISA bus support has been removed. The WITH_EISA option is no longer 186817101a25SAlexander Leidinger valid. 186917101a25SAlexander Leidinger 187017101a25SAlexander Leidinger20170215: 187117101a25SAlexander Leidinger MCA bus support has been removed. 187217101a25SAlexander Leidinger 187317101a25SAlexander Leidinger20170127: 187417101a25SAlexander Leidinger The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed 187517101a25SAlexander Leidinger WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC. 187617101a25SAlexander Leidinger 187717101a25SAlexander Leidinger20170112: 187817101a25SAlexander Leidinger The EM_MULTIQUEUE kernel configuration option is deprecated now that 187917101a25SAlexander Leidinger the em(4) driver conforms to iflib specifications. 188017101a25SAlexander Leidinger 188117101a25SAlexander Leidinger20170109: 188217101a25SAlexander Leidinger The igb(4), em(4) and lem(4) ethernet drivers are now implemented via 188317101a25SAlexander Leidinger IFLIB. If you have a custom kernel configuration that excludes em(4) 188417101a25SAlexander Leidinger but you use igb(4), you need to re-add em(4) to your custom 188517101a25SAlexander Leidinger configuration. 188617101a25SAlexander Leidinger 188717101a25SAlexander Leidinger20161217: 188817101a25SAlexander Leidinger Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1. 188917101a25SAlexander Leidinger Please see the 20141231 entry below for information about prerequisites 189017101a25SAlexander Leidinger and upgrading, if you are not already using clang 3.5.0 or higher. 189117101a25SAlexander Leidinger 189217101a25SAlexander Leidinger20161124: 189317101a25SAlexander Leidinger Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0. 189417101a25SAlexander Leidinger Please see the 20141231 entry below for information about prerequisites 189517101a25SAlexander Leidinger and upgrading, if you are not already using clang 3.5.0 or higher. 189617101a25SAlexander Leidinger 189717101a25SAlexander Leidinger20161119: 189817101a25SAlexander Leidinger The layout of the pmap structure has changed for powerpc to put the pmap 189917101a25SAlexander Leidinger statistics at the front for all CPU variations. libkvm(3) and all tools 190017101a25SAlexander Leidinger that link against it need to be recompiled. 190117101a25SAlexander Leidinger 190217101a25SAlexander Leidinger20161030: 190317101a25SAlexander Leidinger isl(4) and cyapa(4) drivers now require a new driver, 190417101a25SAlexander Leidinger chromebook_platform(4), to work properly on Chromebook-class hardware. 190517101a25SAlexander Leidinger On other types of hardware the drivers may need to be configured using 190617101a25SAlexander Leidinger device hints. Please see the corresponding manual pages for details. 190717101a25SAlexander Leidinger 190817101a25SAlexander Leidinger20161017: 190917101a25SAlexander Leidinger The urtwn(4) driver was merged into rtwn(4) and now consists of 191017101a25SAlexander Leidinger rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific 191117101a25SAlexander Leidinger parts. 191217101a25SAlexander Leidinger Also, firmware for RTL8188CE was renamed due to possible name 191317101a25SAlexander Leidinger conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B)) 191417101a25SAlexander Leidinger 191517101a25SAlexander Leidinger20161015: 191617101a25SAlexander Leidinger GNU rcs has been removed from base. It is available as packages: 191717101a25SAlexander Leidinger - rcs: Latest GPLv3 GNU rcs version. 191817101a25SAlexander Leidinger - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was 191917101a25SAlexander Leidinger removed from base. 192017101a25SAlexander Leidinger 192117101a25SAlexander Leidinger20161008: 192217101a25SAlexander Leidinger Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control 192317101a25SAlexander Leidinger modules now requires that the kernel configuration contain the 192417101a25SAlexander Leidinger TCP_HHOOK option. (This option is included in the GENERIC kernel.) 192517101a25SAlexander Leidinger 192617101a25SAlexander Leidinger20161003: 192717101a25SAlexander Leidinger The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired. 192817101a25SAlexander Leidinger ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy. 192917101a25SAlexander Leidinger 193017101a25SAlexander Leidinger20160924: 193117101a25SAlexander Leidinger Relocatable object files with the extension of .So have been renamed 193217101a25SAlexander Leidinger to use an extension of .pico instead. The purpose of this change is 193317101a25SAlexander Leidinger to avoid a name clash with shared libraries on case-insensitive file 193417101a25SAlexander Leidinger systems. On those file systems, foo.So is the same file as foo.so. 193517101a25SAlexander Leidinger 193617101a25SAlexander Leidinger20160918: 193717101a25SAlexander Leidinger GNU rcs has been turned off by default. It can (temporarily) be built 193817101a25SAlexander Leidinger again by adding WITH_RCS knob in src.conf. 193917101a25SAlexander Leidinger Otherwise, GNU rcs is available from packages: 194017101a25SAlexander Leidinger - rcs: Latest GPLv3 GNU rcs version. 194117101a25SAlexander Leidinger - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base. 194217101a25SAlexander Leidinger 194317101a25SAlexander Leidinger20160918: 194417101a25SAlexander Leidinger The backup_uses_rcs functionality has been removed from rc.subr. 194517101a25SAlexander Leidinger 194617101a25SAlexander Leidinger20160908: 194717101a25SAlexander Leidinger The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into 194817101a25SAlexander Leidinger two separate components, QUEUE_MACRO_DEBUG_TRACE and 194917101a25SAlexander Leidinger QUEUE_MACRO_DEBUG_TRASH. Define both for the original 195017101a25SAlexander Leidinger QUEUE_MACRO_DEBUG behavior. 195117101a25SAlexander Leidinger 195217101a25SAlexander Leidinger20160824: 195317101a25SAlexander Leidinger r304787 changed some ioctl interfaces between the iSCSI userspace 195417101a25SAlexander Leidinger programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be 195517101a25SAlexander Leidinger rebuilt to work with new kernels. __FreeBSD_version has been bumped 195617101a25SAlexander Leidinger to 1200005. 195717101a25SAlexander Leidinger 195817101a25SAlexander Leidinger20160818: 195917101a25SAlexander Leidinger The UDP receive code has been updated to only treat incoming UDP 196017101a25SAlexander Leidinger packets that were addressed to an L2 broadcast address as L3 196117101a25SAlexander Leidinger broadcast packets. It is not expected that this will affect any 196217101a25SAlexander Leidinger standards-conforming UDP application. The new behaviour can be 196317101a25SAlexander Leidinger disabled by setting the sysctl net.inet.udp.require_l2_bcast to 196417101a25SAlexander Leidinger 0. 196517101a25SAlexander Leidinger 196617101a25SAlexander Leidinger20160818: 196717101a25SAlexander Leidinger Remove the openbsd_poll system call. 196817101a25SAlexander Leidinger __FreeBSD_version has been bumped because of this. 196917101a25SAlexander Leidinger 197017101a25SAlexander Leidinger20160708: 197117101a25SAlexander Leidinger The stable/11 branch has been created from head@r302406. 197217101a25SAlexander Leidinger 197362adb1e9SWarner LoshAfter branch N is created, entries older than the N-2 branch point are removed 1974e8c1bd72SWarner Loshfrom this file. After stable/14 is branched and current becomes FreeBSD 15, 1975e8c1bd72SWarner Loshentries older than stable/12 branch point will be removed from current's 1976e8c1bd72SWarner LoshUPDATING file. 197717101a25SAlexander Leidinger 1978dc0dbf5cSWarner LoshCOMMON ITEMS: 1979dc0dbf5cSWarner Losh 1980a24eff53SWarner Losh General Notes 1981a24eff53SWarner Losh ------------- 19825780f3baSWarner Losh Sometimes, obscure build problems are the result of environment 19835780f3baSWarner Losh poisoning. This can happen because the make utility reads its 1984456b5dd8SWarner Losh environment when searching for values for global variables. To run 1985456b5dd8SWarner Losh your build attempts in an "environmental clean room", prefix all make 1986456b5dd8SWarner Losh commands with 'env -i '. See the env(1) manual page for more details. 198716ae8351SEd Maste Occasionally a build failure will occur with "make -j" due to a race 198816ae8351SEd Maste condition. If this happens try building again without -j, and please 198916ae8351SEd Maste report a bug if it happens consistently. 19905780f3baSWarner Losh 19915ad05815SWarner Losh When upgrading from one major version to another it is generally best to 19925ad05815SWarner Losh upgrade to the latest code in the currently installed branch first, then 19935ad05815SWarner Losh do an upgrade to the new branch. This is the best-tested upgrade path, 19945ad05815SWarner Losh and has the highest probability of being successful. Please try this 19955ad05815SWarner Losh approach if you encounter problems with a major version upgrade. Since 199644c1484aSJens Schweikhardt the stable 4.x branch point, one has generally been able to upgrade from 19975ad05815SWarner Losh anywhere in the most recent stable branch to head / current (or even the 19985ad05815SWarner Losh last couple of stable branches). See the top of this file when there's 19995ad05815SWarner Losh an exception. 2000081ff8acSDoug Barton 200156cd269eSEd Maste The update process will emit an error on an attempt to perform a build 200256cd269eSEd Maste or install from a FreeBSD version below the earliest supported version. 200356cd269eSEd Maste When updating from an older version the update should be performed one 200456cd269eSEd Maste major release at a time, including running `make delete-old` at each 200556cd269eSEd Maste step. 200656cd269eSEd Maste 20076eeab389SWarner Losh When upgrading a live system, having a root shell around before 2008da0e842aSWarner Losh installing anything can help undo problems. Not having a root shell 2009da0e842aSWarner Losh around can lead to problems if pam has changed too much from your 2010da0e842aSWarner Losh starting point to allow continued authentication after the upgrade. 2011da0e842aSWarner Losh 20129c80b8aaSWarner Losh This file should be read as a log of events. When a later event changes 20139c80b8aaSWarner Losh information of a prior event, the prior event should not be deleted. 20149c80b8aaSWarner Losh Instead, a pointer to the entry with the new information should be 20159c80b8aaSWarner Losh placed in the old entry. Readers of this file should also sanity check 20169c80b8aaSWarner Losh older entries before relying on them blindly. Authors of new entries 20179c80b8aaSWarner Losh should write them with this in mind. 20189c80b8aaSWarner Losh 20198fc25799SMartin Matuska ZFS notes 20208fc25799SMartin Matuska --------- 20210cd61266SWarner Losh When upgrading the boot ZFS pool to a new version (via zpool upgrade), 20220cd61266SWarner Losh always follow these three steps: 20238fc25799SMartin Matuska 20240cd61266SWarner Losh 1) recompile and reinstall the ZFS boot loader and boot block 20258fc25799SMartin Matuska (this is part of "make buildworld" and "make installworld") 20268fc25799SMartin Matuska 20270cd61266SWarner Losh 2) update the ZFS boot block on your boot drive (only required when 20280cd61266SWarner Losh doing a zpool upgrade): 20298fc25799SMartin Matuska 20300cd61266SWarner Losh When booting on x86 via BIOS, use the following to update the ZFS boot 20310cd61266SWarner Losh block on the freebsd-boot partition of a GPT partitioned drive ada0: 20320cd61266SWarner Losh gpart bootcode -p /boot/gptzfsboot -i $N ada0 20330cd61266SWarner Losh The value $N will typically be 1. For EFI booting, see EFI notes. 20340cd61266SWarner Losh 20350cd61266SWarner Losh 3) zpool upgrade the root pool. New bootblocks will work with old 20360cd61266SWarner Losh pools, but not vice versa, so they need to be updated before any 20370cd61266SWarner Losh zpool upgrade. 20388fc25799SMartin Matuska 20398fc25799SMartin Matuska Non-boot pools do not need these updates. 20408fc25799SMartin Matuska 20410cd61266SWarner Losh EFI notes 20420cd61266SWarner Losh --------- 20430cd61266SWarner Losh 20440cd61266SWarner Losh There are two locations the boot loader can be installed into. The 20450cd61266SWarner Losh current location (and the default) is \efi\freebsd\loader.efi and using 20460cd61266SWarner Losh efibootmgr(8) to configure it. The old location, that must be used on 20470cd61266SWarner Losh deficient systems that don't honor efibootmgr(8) protocols, is the 20480cd61266SWarner Losh fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy 20490cd61266SWarner Losh /boot/loader.efi to this location, but on systems installed a long time 20500cd61266SWarner Losh ago the ESP may be too small and /boot/boot1.efi may be needed unless 20510cd61266SWarner Losh the ESP has been expanded in the meantime. 20520cd61266SWarner Losh 20530cd61266SWarner Losh Recent systems will have the ESP mounted on /boot/efi, but older ones 20540cd61266SWarner Losh may not have it mounted at all, or mounted in a different 20550cd61266SWarner Losh location. Older arm SD images with MBR used /boot/msdos as the 20560cd61266SWarner Losh mountpoint. The ESP is a MSDOS filesystem. 20570cd61266SWarner Losh 20580cd61266SWarner Losh The EFI boot loader rarely needs to be updated. For ZFS booting, 20590cd61266SWarner Losh however, you must update loader.efi before you do 'zpool upgrade' the 20600cd61266SWarner Losh root zpool, otherwise the old loader.efi may reject the upgraded zpool 20610cd61266SWarner Losh since it does not automatically understand some new features. 20620cd61266SWarner Losh 20630cd61266SWarner Losh See loader.efi(8) and uefi(8) for more details. 20640cd61266SWarner Losh 2065dc0dbf5cSWarner Losh To build a kernel 2066dc0dbf5cSWarner Losh ----------------- 2067ba01eb20SWarner Losh If you are updating from a prior version of FreeBSD (even one just 20681cf0ef11SDavid E. O'Brien a few days old), you should follow this procedure. It is the most 20691cf0ef11SDavid E. O'Brien failsafe as it uses a /usr/obj tree with a fresh mini-buildworld, 20701cf0ef11SDavid E. O'Brien 20711cf0ef11SDavid E. O'Brien make kernel-toolchain 2072282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 2073282e0f01SRuslan Ermilov make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 2074dc0dbf5cSWarner Losh 2075fe830c3bSAlexander Ziaee If you are running kernel modules from ports, see FOOTNOTE [1]. 2076fe830c3bSAlexander Ziaee 20772e937dd6SAlexander Leidinger To test a kernel once 20782e937dd6SAlexander Leidinger --------------------- 20792e937dd6SAlexander Leidinger If you just want to boot a kernel once (because you are not sure 20802e937dd6SAlexander Leidinger if it works, or if you want to boot a known bad kernel to provide 20812e937dd6SAlexander Leidinger debugging information) run 20822e937dd6SAlexander Leidinger make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel 20832e937dd6SAlexander Leidinger nextboot -k testkernel 20842e937dd6SAlexander Leidinger 2085ba01eb20SWarner Losh To rebuild everything and install it on the current system. 2086ba01eb20SWarner Losh ----------------------------------------------------------- 208763cb445eSWarner Losh # Note: sometimes if you are running current you gotta do more than 208863cb445eSWarner Losh # is listed here if you are upgrading from a really old current. 208963cb445eSWarner Losh 2090f643de42SWarner Losh <make sure you have good level 0 dumps> 209163cb445eSWarner Losh make buildworld 2092e5f5a852SEitan Adler make buildkernel KERNCONF=YOUR_KERNEL_HERE 2093fe830c3bSAlexander Ziaee make installkernel KERNCONF=YOUR_KERNEL_HERE [1] 209463cb445eSWarner Losh <reboot in single user> [3] 2095e641c29aSDries Michiels etcupdate -p [5] 209663cb445eSWarner Losh make installworld 2097e641c29aSDries Michiels etcupdate -B [4] 209894877c06SAlexander Leidinger make delete-old [6] 209963cb445eSWarner Losh <reboot> 210063cb445eSWarner Losh 2101f27b1fceSJoseph Koshy To cross-install current onto a separate partition 2102f27b1fceSJoseph Koshy -------------------------------------------------- 2103f27b1fceSJoseph Koshy # In this approach we use a separate partition to hold 2104f27b1fceSJoseph Koshy # current's root, 'usr', and 'var' directories. A partition 2105f27b1fceSJoseph Koshy # holding "/", "/usr" and "/var" should be about 2GB in 2106f27b1fceSJoseph Koshy # size. 2107f27b1fceSJoseph Koshy 2108f27b1fceSJoseph Koshy <make sure you have good level 0 dumps> 2109f27b1fceSJoseph Koshy <boot into -stable> 2110f27b1fceSJoseph Koshy make buildworld 2111fe830c3bSAlexander Ziaee make buildkernel KERNCONF=YOUR_KERNEL_HERE [1] 2112f27b1fceSJoseph Koshy <maybe newfs current's root partition> 2113f27b1fceSJoseph Koshy <mount current's root partition on directory ${CURRENT_ROOT}> 2114af34024aSJohn-Mark Gurney make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC 21152d5cde04SRuslan Ermilov make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 21163ecf3bddSRuslan Ermilov make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 2117f27b1fceSJoseph Koshy cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 2118f27b1fceSJoseph Koshy <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 2119f27b1fceSJoseph Koshy <reboot into current> 2120f27b1fceSJoseph Koshy <do a "native" rebuild/install as described in the previous section> 2121737d990aSXin LI <maybe install compatibility libraries from ports/misc/compat*> 2122f27b1fceSJoseph Koshy <reboot> 2123f27b1fceSJoseph Koshy 2124f27b1fceSJoseph Koshy 212515974d55SGavin Atkinson To upgrade in-place from stable to current 2126f27b1fceSJoseph Koshy ---------------------------------------------- 2127f643de42SWarner Losh <make sure you have good level 0 dumps> 212821c075eaSWarner Losh make buildworld [9] 2129779f392bSJohn Baldwin make buildkernel KERNCONF=YOUR_KERNEL_HERE [8] 2130fe830c3bSAlexander Ziaee make installkernel KERNCONF=YOUR_KERNEL_HERE [1] 2131fc8c157fSWarner Losh <reboot in single user> [3] 2132e641c29aSDries Michiels etcupdate -p [5] 2133ba26da8eSWarner Losh make installworld 2134e641c29aSDries Michiels etcupdate -B [4] 213594877c06SAlexander Leidinger make delete-old [6] 2136ba26da8eSWarner Losh <reboot> 2137ba26da8eSWarner Losh 2138fdb9f54dSWarner Losh Make sure that you've read the UPDATING file to understand the 2139fdb9f54dSWarner Losh tweaks to various things you need. At this point in the life 2140fdb9f54dSWarner Losh cycle of current, things change often and you are on your own 2141fdb9f54dSWarner Losh to cope. The defaults can also change, so please read ALL of 2142fdb9f54dSWarner Losh the UPDATING entries. 2143ba26da8eSWarner Losh 21441dece4a9SWarner Losh Also, if you are tracking -current, you must be subscribed to 21451dece4a9SWarner Losh freebsd-current@freebsd.org. Make sure that before you update 21461dece4a9SWarner Losh your sources that you have read and understood all the recent 21471dece4a9SWarner Losh messages there. If in doubt, please track -stable which has 21481dece4a9SWarner Losh much fewer pitfalls. 21491dece4a9SWarner Losh 2150fe830c3bSAlexander ZiaeeFOOTNOTES: 2151fe830c3bSAlexander Ziaee 2152fe830c3bSAlexander Ziaee [1] If you have third party modules, such as drm-kmod or vmware, you 2153fe830c3bSAlexander Ziaee should disable them at this point so they don't crash your system on 2154d2799054SWarner Losh reboot. Alternatively, you should rebuild all the modules you have in 2155d2799054SWarner Losh your system and install them as well. If you are running -current, you 2156d2799054SWarner Losh should seriously consider placing all sources to all the modules for 2157d2799054SWarner Losh your system (or symlinks to them) in /usr/local/sys/modules so this 2158d2799054SWarner Losh happens automatically. If all your modules come from ports, then adding 2159d2799054SWarner Losh the port origin directories to PORTS_MODULES instead is also automatic 2160d2799054SWarner Losh and effective, eg: 2161d2799054SWarner Losh PORTS_MODULES+=x11/nvidia-driver 2162134d2e86SWarner Losh 2163ee6e1fc3SWarner Losh [3] From the bootblocks, boot -s, and then do 2164ee6e1fc3SWarner Losh fsck -p 2165ee6e1fc3SWarner Losh mount -u / 2166ee6e1fc3SWarner Losh mount -a 21678ed2d94aSWarner Losh sh /etc/rc.d/zfs start # mount zfs filesystem, if needed 21688ed2d94aSWarner Losh cd src # full path to source 216947d0d01fSWarner Losh adjkerntz -i # if CMOS is wall time 2170d2799054SWarner Losh Also, when doing a major release upgrade, it is required that you boot 2171d2799054SWarner Losh into single user mode to do the installworld. 2172ee6e1fc3SWarner Losh 2173a6cd4f9dSWarner Losh [4] Note: This step is non-optional. Failure to do this step 2174a6cd4f9dSWarner Losh can result in a significant reduction in the functionality of the 2175a6cd4f9dSWarner Losh system. Attempting to do it by hand is not recommended and those 2176a6cd4f9dSWarner Losh that pursue this avenue should read this file carefully, as well 2177a6cd4f9dSWarner Losh as the archives of freebsd-current and freebsd-hackers mailing lists 2178e641c29aSDries Michiels for potential gotchas. See etcupdate(8) for more information. 2179a6cd4f9dSWarner Losh 218044c1484aSJens Schweikhardt [5] Usually this step is a no-op. However, from time to time 2181835284beSWarner Losh you may need to do this if you get unknown user in the following 2182e641c29aSDries Michiels step. 2183835284beSWarner Losh 218494877c06SAlexander Leidinger [6] This only deletes old files and directories. Old libraries 218594877c06SAlexander Leidinger can be deleted by "make delete-old-libs", but you have to make 218694877c06SAlexander Leidinger sure that no program is using those libraries anymore. 218794877c06SAlexander Leidinger 2188ed651a74SWarner Losh [8] The new kernel must be able to run existing binaries used by an 2189ed651a74SWarner Losh installworld. When upgrading across major versions, the new kernel's 2190ed651a74SWarner Losh configuration must include the correct COMPAT_FREEBSD<n> option for 2191ed651a74SWarner Losh existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure 2192ed651a74SWarner Losh to do so may leave you with a system that is hard to boot to recover. A 2193ed651a74SWarner Losh GENERIC kernel will include suitable compatibility options to run 2194ed651a74SWarner Losh binaries from older branches. Note that the ability to run binaries 2195ed651a74SWarner Losh from unsupported branches is not guaranteed. 2196c74fe6afSWarner Losh 2197e5dc5f61SWarner Losh Make sure that you merge any new devices from GENERIC since the 21988ed2d94aSWarner Losh last time you updated your kernel config file. Options also 21998ed2d94aSWarner Losh change over time, so you may need to adjust your custom kernels 22008ed2d94aSWarner Losh for these as well. 2201e5dc5f61SWarner Losh 2202e5f5a852SEitan Adler [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the 2203e5dc5f61SWarner Losh "?=" instead of the "=" assignment operator, so that buildworld can 2204e5dc5f61SWarner Losh override the CPUTYPE if it needs to. 2205e5dc5f61SWarner Losh 2206e5dc5f61SWarner Losh MAKEOBJDIRPREFIX must be defined in an environment variable, and 2207e5dc5f61SWarner Losh not on the command line, or in /etc/make.conf. buildworld will 2208e5dc5f61SWarner Losh warn if it is improperly defined. 2209dc0dbf5cSWarner LoshFORMAT: 2210dc0dbf5cSWarner Losh 2211f699bbbbSMark OvensThis file contains a list, in reverse chronological order, of major 2212630f2154SGlen Barberbreakages in tracking -current. It is not guaranteed to be a complete 22139c80b8aaSWarner Loshlist of such breakages, and only contains entries since September 23, 2011. 2214630f2154SGlen BarberIf you need to see UPDATING entries from before that date, you will need 2215630f2154SGlen Barberto fetch an UPDATING file from an older FreeBSD release. 22161fc1a0dcSWarner Losh 2217e72fd46aSWarner LoshCopyright information: 2218e72fd46aSWarner Losh 2219f86e6000SWarner LoshCopyright 1998-2009 M. Warner Losh <imp@FreeBSD.org> 2220e72fd46aSWarner Losh 2221772730c7SWarner LoshRedistribution, publication, translation and use, with or without 2222772730c7SWarner Loshmodification, in full or in part, in any form or format of this 22239698f2c0SWarner Loshdocument are permitted without further permission from the author. 2224e72fd46aSWarner Losh 2225e72fd46aSWarner LoshTHIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 2226e72fd46aSWarner LoshIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 2227e72fd46aSWarner LoshWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 2228e72fd46aSWarner LoshDISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 2229e72fd46aSWarner LoshINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 2230e72fd46aSWarner Losh(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 2231e72fd46aSWarner LoshSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 2232e72fd46aSWarner LoshHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 2233e72fd46aSWarner LoshSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 2234e72fd46aSWarner LoshIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 2235e72fd46aSWarner LoshPOSSIBILITY OF SUCH DAMAGE. 2236e72fd46aSWarner Losh 223722306abcSWarner LoshContact Warner Losh if you have any questions about your use of 2238772730c7SWarner Loshthis document. 2239