HardenedBSD src tree
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

2192 lines

  1. Updating Information for FreeBSD current users.
  2. This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
  3. See end of file for further details. For commonly done items, please see the
  4. COMMON ITEMS: section later in the file. These instructions assume that you
  5. basically know what you are doing. If not, then please consult the FreeBSD
  6. handbook:
  7. https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
  8. Items affecting the ports and packages system can be found in
  9. /usr/ports/UPDATING. Please read that file before running portupgrade.
  11. FreeBSD 13.x has many debugging features turned on, in both the kernel
  12. and userland. These features attempt to detect incorrect use of
  13. system primitives, and encourage loud failure through extra sanity
  14. checking and fail stop semantics. They also substantially impact
  15. system performance. If you want to do performance measurement,
  16. benchmarking, and optimization, you'll want to turn them off. This
  17. includes various WITNESS- related kernel options, INVARIANTS, malloc
  18. debugging flags in userland, and various verbose features in the
  19. kernel. Many developers choose to disable these features on build
  20. machines to maximize performance. (To completely disable malloc
  21. debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
  22. disable the most expensive debugging functionality run
  23. "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
  24. 20200108:
  25. Clang/LLVM is now the default compiler and LLD the default
  26. linker for riscv64.
  27. 20200107:
  28. make universe no longer uses GCC 4.2.1 on any architectures.
  29. Architectures not supported by in-tree Clang/LLVM require an
  30. external toolchain package.
  31. 20200104:
  32. GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
  33. retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
  34. options default to off for all supported CPU architectures. As a
  35. short-term transition aid they may be enabled via WITH_* options.
  36. GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
  37. 20200102:
  38. Support for armv5 has been disconnected and is being removed. The
  39. machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
  40. You must now use a MACHINE_ARCH of armv6 or armv7. The default
  41. MACHINE_ARCH for MACHINE=arm is now armv7.
  42. 20191226:
  43. Clang/LLVM is now the default compiler for all powerpc architectures.
  44. LLD is now the default linker for powerpc64. The change for powerpc64
  45. also includes a change to the ELFv2 ABI, incompatible with the existing
  46. ABI.
  47. 20191226:
  48. Kernel-loadable random(4) modules are no longer unloadable.
  49. 20191222:
  50. Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
  51. been upgraded to 9.0.1. Please see the 20141231 entry below for
  52. information about prerequisites and upgrading, if you are not already
  53. using clang 3.5.0 or higher.
  54. 20191212:
  55. r355677 has modified the internal interface used between the
  56. NFS modules in the kernel. As such, they must all be upgraded
  57. simultaneously. I will do a version bump for this.
  58. 20191205:
  59. The root certificates of the Mozilla CA Certificate Store have been
  60. imported into the base system and can be managed with the certctl(8)
  61. utility. If you have installed the security/ca_root_nss port or package
  62. with the ETCSYMLINK option (the default), be advised that there may be
  63. differences between those included in the port and those included in
  64. base due to differences in nss branch used as well as general update
  65. frequency. Note also that certctl(8) cannot manage certs in the
  66. format used by the security/ca_root_nss port.
  67. 20191120:
  68. The amd(8) automount daemon has been disabled by default, and will be
  69. removed in the future. As of FreeBSD 10.1 the autofs(5) is available
  70. for automounting.
  71. 20191107:
  72. The nctgpio and wbwd drivers have been moved to the superio bus.
  73. If you have one of these drivers in a kernel configuration, then
  74. you should add device superio to it. If you use one of these drivers
  75. as a module and you compile a custom set of modules, then you should
  76. add superio to the set.
  77. 20191021:
  78. KPIs for network drivers to access interface addresses have changed.
  79. Users need to recompile NIC driver modules together with kernel.
  80. 20191021:
  81. The net.link.tap.user_open sysctl no longer prevents user opening of
  82. already created /dev/tapNN devices. Access is still controlled by
  83. node permissions, just like tun devices. The net.link.tap.user_open
  84. sysctl is now used only to allow users to perform devfs cloning of
  85. tap devices, and the subsequent open may not succeed if the user is not
  86. in the appropriate group. This sysctl may be deprecated/removed
  87. completely in the future.
  88. 20191009:
  89. mips, powerpc, and sparc64 are no longer built as part of
  90. universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
  91. not defined, mips, powerpc, and sparc64 builds will look for
  92. the xtoolchain binaries and if installed use them for universe
  93. builds. As llvm 9.0 becomes vetted for these architectures, they
  94. will be removed from the list.
  95. 20191009:
  96. Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
  97. been upgraded to 9.0.0. Please see the 20141231 entry below for
  98. information about prerequisites and upgrading, if you are not already
  99. using clang 3.5.0 or higher.
  100. 20191003:
  101. The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
  102. GENERIC. They are available as modules and can be loaded by adding
  103. to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
  104. hptnr_load="YES", or hptrr_load="YES", respectively.
  105. 20190913:
  106. ntpd no longer by default locks its pages in memory, allowing them
  107. to be paged out by the kernel. Use rlimit memlock to restore
  108. historic BSD behaviour. For example, add "rlimit memlock 32"
  109. to ntp.conf to lock up to 32 MB of ntpd address space in memory.
  110. 20190823:
  111. Several of ping6's options have been renamed for better consistency
  112. with ping. If you use any of -ARWXaghmrtwx, you must update your
  113. scripts. See ping6(8) for details.
  114. 20190727:
  115. The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
  116. and the "-o sync_unmount" and "-o init_backgrounded" mount options have
  117. been removed from mount_fusefs(8). You can safely remove them from
  118. your scripts, because they had no effect.
  119. The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
  120. vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
  121. vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
  122. sysctls have been removed. If you felt the need to set any of them to
  123. a non-default value, please tell asomers@FreeBSD.org why.
  124. 20190713:
  125. Default permissions on the /var/account/acct file (and copies of it
  126. rotated by periodic daily scripts) are changed from 0644 to 0640
  127. because the file contains sensitive information that should not be
  128. world-readable. If the /var/account directory must be created by
  129. rc.d/accounting, the mode used is now 0750. Admins who use the
  130. accounting feature are encouraged to change the mode of an existing
  131. /var/account directory to 0750 or 0700.
  132. 20190620:
  133. Entropy collection and the /dev/random device are no longer optional
  134. components. The "device random" option has been removed.
  135. Implementations of distilling algorithms can still be made loadable
  136. with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
  137. 20190612:
  138. Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
  139. been upgraded to 8.0.1. Please see the 20141231 entry below for
  140. information about prerequisites and upgrading, if you are not already
  141. using clang 3.5.0 or higher.
  142. 20190608:
  143. A fix was applied to i386 kernel modules to avoid panics with
  144. dpcpu or vnet. Users need to recompile i386 kernel modules
  145. having pcpu or vnet sections or they will refuse to load.
  146. 20190513:
  147. User-wired pages now have their own counter,
  148. vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
  149. to vm.max_user_wired and changed from an unsigned int to an unsigned
  150. long. bhyve VMs wired with the -S are now subject to the user
  151. wiring limit; the vm.max_user_wired sysctl may need to be tuned to
  152. avoid running into the limit.
  153. 20190507:
  154. The IPSEC option has been removed from GENERIC. Users requiring
  155. ipsec(4) must now load the ipsec(4) kernel module.
  156. 20190507:
  157. The tap(4) driver has been folded into tun(4), and the module has been
  158. renamed to tuntap. You should update any kld_list="if_tap" or
  159. kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
  160. if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
  161. module instead, and "device tap" or "device tun" entries in kernel
  162. config files to select the tuntap device instead.
  163. 20190418:
  164. The following knobs have been added related to tradeoffs between
  165. safe use of the random device and availability in the absence of
  166. entropy:
  167. kern.random.initial_seeding.bypass_before_seeding: tunable; set
  168. non-zero to bypass the random device prior to seeding, or zero to
  169. block random requests until the random device is initially seeded.
  170. For now, set to 1 (unsafe) by default to restore pre-r346250 boot
  171. availability properties.
  172. kern.random.initial_seeding.read_random_bypassed_before_seeding:
  173. read-only diagnostic sysctl that is set when bypass is enabled and
  174. read_random(9) is bypassed, to enable programmatic handling of this
  175. initial condition, if desired.
  176. kern.random.initial_seeding.arc4random_bypassed_before_seeding:
  177. Similar to the above, but for for arc4random(9) initial seeding.
  178. kern.random.initial_seeding.disable_bypass_warnings: tunable; set
  179. non-zero to disable warnings in dmesg when the same conditions are
  180. met as for the diagnostic sysctls above. Defaults to zero, i.e.,
  181. produce warnings in dmesg when the conditions are met.
  182. 20190416:
  183. The loadable random module KPI has changed; the random_infra_init()
  184. routine now requires a 3rd function pointer for a bool (*)(void)
  185. method that returns true if the random device is seeded (and
  186. therefore unblocked).
  187. 20190404:
  188. r345895 reverts r320698. This implies that an nfsuserd(8) daemon
  189. built from head sources between r320757 (July 6, 2017) and
  190. r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
  191. is added to the command line.
  192. nfsuserd daemons built from head sources that are post-r338192 are
  193. not affected and should continue to work.
  194. 20190320:
  195. The fuse(4) module has been renamed to fusefs(4) for consistency with
  196. other filesystems. You should update any kld_load="fuse" entries in
  197. /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
  198. "options FUSE" entries in kernel config files.
  199. 20190304:
  200. Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
  201. 8.0.0. Please see the 20141231 entry below for information about
  202. prerequisites and upgrading, if you are not already using clang 3.5.0
  203. or higher.
  204. 20190226:
  205. geom_uzip(4) depends on the new module xz. If geom_uzip is statically
  206. compiled into your custom kernel, add 'device xz' statement to the
  207. kernel config.
  208. 20190219:
  209. drm and drm2 have been removed from the tree. Please see
  210. https://wiki.freebsd.org/Graphics for the latest information on
  211. migrating to the drm ports.
  212. 20190131:
  213. Iflib is no longer unconditionally compiled into the kernel. Drivers
  214. using iflib and statically compiled into the kernel, now require
  215. the 'device iflib' config option. For the same drivers loaded as
  216. modules on kernels not having 'device iflib', the iflib.ko module
  217. is loaded automatically.
  218. 20190125:
  219. The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
  220. options no longer exist since r343219 and r343427 respectively;
  221. nothing uses them, so they should be just removed from custom
  222. kernel config files.
  223. 20181230:
  224. r342635 changes the way efibootmgr(8) works by requiring users to add
  225. the -b (bootnum) parameter for commands where the bootnum was previously
  226. specified with each option. For example 'efibootmgr -B 0001' is now
  227. 'efibootmgr -B -b 0001'.
  228. 20181220:
  229. r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
  230. in the same as it is applied to NFSv2 and 3. This implies that NFSv4
  231. servers that have vfs.nfsd.nfs_privport set will only allow mounts
  232. from clients using a reserved port#. Since both the FreeBSD and Linux
  233. NFSv4 clients use reserved port#s by default, this should not affect
  234. most NFSv4 mounts.
  235. 20181219:
  236. The XLP config has been removed. We can't support 64-bit atomics in this
  237. kernel because it is running in 32-bit mode. XLP users must transition
  238. to running a 64-bit kernel (XLP64 or XLPN32).
  239. The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
  240. the preferred emulator today and we don't need two different ones.
  241. The old sibyte / swarm / Broadcom BCM1250 support has been
  242. removed from the mips port.
  243. 20181211:
  244. Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
  245. 7.0.1. Please see the 20141231 entry below for information about
  246. prerequisites and upgrading, if you are not already using clang 3.5.0
  247. or higher.
  248. 20181211:
  249. Remove the timed and netdate programs from the base tree. Setting
  250. the time with these daemons has been obsolete for over a decade.
  251. 20181126:
  252. On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
  253. linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
  254. it produces broken binaries when ifuncs are in use. Users needing
  255. GNU ld should install the binutils port or package.
  256. 20181123:
  257. The BSD crtbegin and crtend code has been enabled by default. It has
  258. had extensive testing on amd64, arm64, and i386. It can be disabled
  259. by building a world with -DWITHOUT_BSD_CRTBEGIN.
  260. 20181115:
  261. The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
  262. has been converted to a port (misc/ctm) and will be removed from
  263. FreeBSD-13. It is available as a package (ctm) for all supported
  264. FreeBSD versions.
  265. 20181110:
  266. The default newsyslog.conf(5) file has been changed to only include
  267. files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
  268. the filenames end in '.conf' and do not begin with a '.'.
  269. You should check the configuration files in these two directories match
  270. this naming convention. You can verify which configuration files are
  271. being included using the command:
  272. $ newsyslog -Nrv
  273. 20181015:
  274. Ports for the DRM modules have been simplified. Now, amd64 users should
  275. just install the drm-kmod port. All others should install
  276. drm-legacy-kmod.
  277. Graphics hardware that's newer than about 2010 usually works with
  278. drm-kmod. For hardware older than 2013, however, some users will need
  279. to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
  280. than 2008 usually only works in drm-legacy-kmod. The graphics team can
  281. only commit to hardware made since 2013 due to the complexity of the
  282. market and difficulty to test all the older cards effectively. If you
  283. have hardware supported by drm-kmod, you are strongly encouraged to use
  284. that as you will get better support.
  285. Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
  286. elsewhere, the drm and drm2 modules will be eliminated from the src base
  287. soon (with a limited exception for arm). Please update to the package
  288. asap and report any issues to x11@freebsd.org.
  289. Generally, anybody using the drm*-kmod packages should add
  290. WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
  291. cross-threading surprises, especially with automatic driver
  292. loading from X11 startup. These will become the defaults in 13-current
  293. shortly.
  294. 20181012:
  295. The ixlv(4) driver has been renamed to iavf(4). As a consequence,
  296. custom kernel and module loading configuration files must be updated
  297. accordingly. Moreover, interfaces previous presented as ixlvN to the
  298. system are now exposed as iavfN and network configuration files must
  299. be adjusted as necessary.
  300. 20181009:
  301. OpenSSL has been updated to version 1.1.1. This update included
  302. additional various API changes throughout the base system. It is
  303. important to rebuild third-party software after upgrading. The value
  304. of __FreeBSD_version has been bumped accordingly.
  305. 20181006:
  306. The legacy DRM modules and drivers have now been added to the loader's
  307. module blacklist, in favor of loading them with kld_list in rc.conf(5).
  308. The module blacklist may be overridden with the loader.conf(5)
  309. 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
  310. encouraged.
  311. 20181002:
  312. The cam(4) based nda(4) driver will be used over nvd(4) by default on
  313. powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
  314. loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
  315. driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
  316. nda device name.
  317. 20180913:
  318. Reproducible build mode is now on by default, in preparation for
  319. FreeBSD 12.0. This eliminates build metadata such as the user,
  320. host, and time from the kernel (and uname), unless the working tree
  321. corresponds to a modified checkout from a version control system.
  322. The previous behavior can be obtained by setting the /etc/src.conf
  324. 20180826:
  325. The Yarrow CSPRNG has been removed from the kernel as it has not been
  326. supported by its designers since at least 2003. Fortuna has been the
  327. default since FreeBSD-11.
  328. 20180822:
  329. devctl freeze/thaw have gone into the tree, the rc scripts have been
  330. updated to use them and devmatch has been changed. You should update
  331. kernel, userland and rc scripts all at the same time.
  332. 20180818:
  333. The default interpreter has been switched from 4th to Lua.
  334. LOADER_DEFAULT_INTERP, documented in build(7), will override the default
  335. interpreter. If you have custom FORTH code you will need to set
  336. LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
  337. src.conf for the build. This will create default hard links between
  338. loader and loader_4th instead of loader and loader_lua, the new default.
  339. If you are using UEFI it will create the proper hard link to loader.efi.
  340. bhyve uses userboot.so. It remains 4th-only until some issues are solved
  341. regarding coexisting with multiple versions of FreeBSD are resolved.
  342. 20180815:
  343. ls(1) now respects the COLORTERM environment variable used in other
  344. systems and software to indicate that a colored terminal is both
  345. supported and desired. If ls(1) is suddenly emitting colors, they may
  346. be disabled again by either removing the unwanted COLORTERM from your
  347. environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
  348. may not be observed in a future release.
  349. 20180808:
  350. The default pager for most commands has been changed to "less". To
  351. restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
  352. your environment.
  353. 20180731:
  354. The jedec_ts(4) driver has been removed. A superset of its functionality
  355. is available in the jedec_dimm(4) driver, and the manpage for that
  356. driver includes migration instructions. If you have "device jedec_ts"
  357. in your kernel configuration file, it must be removed.
  358. 20180730:
  359. amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
  360. This should have no effect if the kernel is booted via BIOS/legacy boot.
  361. EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
  362. has a buggy firmware that prevents a successful boot due to use of
  363. runtime services.
  364. 20180727:
  365. Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
  366. support has been removed from the tree. These ports were
  367. obsolete and/or known to be broken for many years.
  368. 20180723:
  369. loader.efi has been augmented to participate more fully in the
  370. UEFI boot manager protocol. loader.efi will now look at the
  371. BootXXXX environment variable to determine if a specific kernel
  372. or root partition was specified. XXXX is derived from BootCurrent.
  373. efibootmgr(8) manages these standard UEFI variables.
  374. 20180720:
  375. zfsloader's functionality has now been folded into loader.
  376. zfsloader is no longer necessary once you've updated your
  377. boot blocks. For a transition period, we will install a
  378. hardlink for zfsloader to loader to allow a smooth transition
  379. until the boot blocks can be updated (hard link because old
  380. zfs boot blocks don't understand symlinks).
  381. 20180719:
  382. ARM64 now have efifb support, if you want to have serial console
  383. on your arm64 board when an screen is connected and the bootloader
  384. setup a frame buffer for us to use, just add :
  385. boot_serial=YES
  386. boot_multicons=YES
  387. in /boot/loader.conf
  388. For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
  389. an screen connected as the firmware will setup a frame buffer are that
  390. u-boot will expose as an EFI frame buffer.
  391. 20180719:
  392. New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
  393. or take steps to update /etc/passwd before doing installworld on
  394. existing systems. Do not skip the "mergemaster -Fp" step before
  395. installworld, as described in the update procedures near the bottom
  396. of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
  397. if the new mac_ntpd(4) policy is available, unless ntpd_flags or
  398. the ntp config file contain options that change file/dir locations.
  399. When such options (e.g., "statsdir" or "crypto") are used, ntpd can
  400. still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
  401. taking steps to ensure that all required files/dirs are accessible
  402. by the ntpd user.
  403. 20180717:
  404. Big endian arm support has been removed.
  405. 20180711:
  406. The static environment setup in kernel configs is no longer mutually
  407. exclusive with the loader(8) environment by default. In order to
  408. restore the previous default behavior of disabling the loader(8)
  409. environment if a static environment is present, you must specify
  410. loader_env.disabled=1 in the static environment.
  411. 20180705:
  412. The ABI of syscalls used by management tools like sockstat and
  413. netstat has been broken to allow 32-bit binaries to work on
  414. 64-bit kernels without modification. These programs will need
  415. to match the kernel in order to function. External programs may
  416. require minor modifications to accommodate a change of type in
  417. structures from pointers to 64-bit virtual addresses.
  418. 20180702:
  419. On i386 and amd64 atomics are now inlined. Out of tree modules using
  420. atomics will need to be rebuilt.
  421. 20180701:
  422. The '%I' format in the kern.corefile sysctl limits the number of
  423. core files that a process can generate to the number stored in the
  424. debug.ncores sysctl. The '%I' format is replaced by the single digit
  425. index. Previously, if all indexes were taken the kernel would overwrite
  426. only a core file with the highest index in a filename.
  427. Currently the system will create a new core file if there is a free
  428. index or if all slots are taken it will overwrite the oldest one.
  429. 20180630:
  430. Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
  431. 6.0.1. Please see the 20141231 entry below for information about
  432. prerequisites and upgrading, if you are not already using clang 3.5.0
  433. or higher.
  434. 20180628:
  435. r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
  436. needed to be changed to work with it. This change was made with r335763
  437. and requires a mergemaster / etcupdate / etc to update the installed
  438. file.
  439. 20180612:
  440. r334930 changed the interface between the NFS modules, so they all
  441. need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
  442. 20180530:
  443. As of r334391 lld is the default amd64 system linker; it is installed
  444. as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
  445. longer necessary.
  446. 20180530:
  447. The kernel / userland interface for devinfo changed, so you'll
  448. need a new kernel and userland as a pair for it to work (rebuilding
  449. lib/libdevinfo is all that's required). devinfo and devmatch will
  450. not work, but everything else will when there's a mismatch.
  451. 20180523:
  452. The on-disk format for hwpmc callchain records has changed to include
  453. threadid corresponding to a given record. This changes the field offsets
  454. and thus requires that libpmcstat be rebuilt before using a kernel
  455. later than r334108.
  456. 20180517:
  457. The vxge(4) driver has been removed. This driver was introduced into
  458. HEAD one week before the Exar left the Ethernet market and is not
  459. known to be used. If you have device vxge in your kernel config file
  460. it must be removed.
  461. 20180510:
  462. The amd64 kernel now requires a ld that supports ifunc to produce a
  463. working kernel, either lld or a newer binutils. lld is built by default
  464. on amd64, and the 'buildkernel' target uses it automatically. However,
  465. it is not the default linker, so building the kernel the traditional
  466. way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
  467. binutils port/package). lld will soon be default, and this requirement
  468. will go away.
  469. NOTE: As of r334391 lld is the default system linker on amd64, and no
  470. workaround is necessary.
  471. 20180508:
  472. The nxge(4) driver has been removed. This driver was for PCI-X 10g
  473. cards made by s2io/Neterion. The company was acquired by Exar and
  474. no longer sells or supports Ethernet products. If you have device
  475. nxge in your kernel config file it must be removed.
  476. 20180504:
  477. The tz database (tzdb) has been updated to 2018e. This version more
  478. correctly models time stamps in time zones with negative DST such as
  479. Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
  480. Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
  481. time zone abbreviations and the tm_isdst flag.
  482. 20180502:
  483. The ixgb(4) driver has been removed. This driver was for an early and
  484. uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
  485. quickly shifted to the long lived ixgbe family. If you have device
  486. ixgb in your kernel config file it must be removed.
  487. 20180501:
  488. The lmc(4) driver has been removed. This was a WAN interface
  489. card that was already reportedly rare in 2003, and had an ambiguous
  490. license. If you have device lmc in your kernel config file it must
  491. be removed.
  492. 20180413:
  493. Support for Arcnet networks has been removed. If you have device
  494. arcnet or device cm in your kernel config file they must be
  495. removed.
  496. 20180411:
  497. Support for FDDI networks has been removed. If you have device
  498. fddi or device fpa in your kernel config file they must be
  499. removed.
  500. 20180406:
  501. In addition to supporting RFC 3164 formatted messages, the
  502. syslogd(8) service is now capable of parsing RFC 5424 formatted
  503. log messages. The main benefit of using RFC 5424 is that clients
  504. may now send log messages with timestamps containing year numbers,
  505. microseconds and time zone offsets.
  506. Similarly, the syslog(3) C library function has been altered to
  507. send RFC 5424 formatted messages to the local system logging
  508. daemon. On systems using syslogd(8), this change should have no
  509. negative impact, as long as syslogd(8) and the C library are
  510. updated at the same time. On systems using a different system
  511. logging daemon, it may be necessary to make configuration
  512. adjustments, depending on the software used.
  513. When using syslog-ng, add the 'syslog-protocol' flag to local
  514. input sources to enable parsing of RFC 5424 formatted messages:
  515. source src {
  516. unix-dgram("/var/run/log" flags(syslog-protocol));
  517. }
  518. When using rsyslog, disable the 'SysSock.UseSpecialParser' option
  519. of the 'imuxsock' module to let messages be processed by the
  520. regular RFC 3164/5424 parsing pipeline:
  521. module(load="imuxsock" SysSock.UseSpecialParser="off")
  522. Do note that these changes only affect communication between local
  523. applications and syslogd(8). The format that syslogd(8) uses to
  524. store messages on disk or forward messages to other systems
  525. remains unchanged. syslogd(8) still uses RFC 3164 for these
  526. purposes. Options to customize this behaviour will be added in the
  527. future. Utilities that process log files stored in /var/log are
  528. thus expected to continue to function as before.
  529. __FreeBSD_version has been incremented to 1200061 to denote this
  530. change.
  531. 20180328:
  532. Support for token ring networks has been removed. If you
  533. have "device token" in your kernel config you should remove
  534. it. No device drivers supported token ring.
  535. 20180323:
  536. makefs was modified to be able to tag ISO9660 El Torito boot catalog
  537. entries as EFI instead of overloading the i386 tag as done previously.
  538. The amd64 mkisoimages.sh script used to build amd64 ISO images for
  539. release was updated to use this. This may mean that makefs must be
  540. updated before "make cdrom" can be run in the release directory. This
  541. should be as simple as:
  542. $ cd $SRCDIR/usr.sbin/makefs
  543. $ make depend all install
  544. 20180212:
  545. FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
  546. now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
  547. Co-existence for the transition period will come shortly. Booting is a
  548. complex environment and test coverage for Lua-enabled loaders has been
  549. thin, so it would be prudent to assume it might not work and make
  550. provisions for backup boot methods.
  551. 20180211:
  552. devmatch functionality has been turned on in devd. It will automatically
  553. load drivers for unattached devices. This may cause unexpected drivers
  554. to be loaded. Please report any problems to current@ and
  555. imp@freebsd.org.
  556. 20180114:
  557. Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
  558. 6.0.0. Please see the 20141231 entry below for information about
  559. prerequisites and upgrading, if you are not already using clang 3.5.0
  560. or higher.
  561. 20180110:
  562. LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
  563. This means it is used to link the kernel and userland libraries and
  564. executables, but is not yet installed as /usr/bin/ld by default.
  565. To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
  567. 20180110:
  568. On i386, pmtimer has been removed. Its functionality has been folded
  569. into apm. It was a no-op on ACPI in current for a while now (but was
  570. still needed on i386 in FreeBSD 11 and earlier). Users may need to
  571. remove it from kernel config files.
  572. 20180104:
  573. The use of RSS hash from the network card aka flowid has been
  574. disabled by default for lagg(4) as it's currently incompatible with
  575. the lacp and loadbalance protocols.
  576. This can be re-enabled by setting the following in loader.conf:
  577. net.link.lagg.default_use_flowid="1"
  578. 20180102:
  579. The SW_WATCHDOG option is no longer necessary to enable the
  580. hardclock-based software watchdog if no hardware watchdog is
  581. configured. As before, SW_WATCHDOG will cause the software
  582. watchdog to be enabled even if a hardware watchdog is configured.
  583. 20171215:
  584. r326887 fixes the issue described in the 20171214 UPDATING entry.
  585. r326888 flips the switch back to building GELI support always.
  586. 20171214:
  587. r362593 broke ZFS + GELI support for reasons unknown. However,
  588. it also broke ZFS support generally, so GELI has been turned off
  589. by default as the lesser evil in r326857. If you boot off ZFS and/or
  590. GELI, it might not be a good time to update.
  591. 20171125:
  592. PowerPC users must update loader(8) by rebuilding world before
  593. installing a new kernel, as the protocol connecting them has
  594. changed. Without the update, loader metadata will not be passed
  595. successfully to the kernel and users will have to enter their
  596. root partition at the kernel mountroot prompt to continue booting.
  597. Newer versions of loader can boot old kernels without issue.
  598. 20171110:
  599. The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
  602. 20171106:
  603. The naive and non-compliant support of posix_fallocate(2) in ZFS
  604. has been removed as of r325320. The system call now returns EINVAL
  605. when used on a ZFS file. Although the new behavior complies with the
  606. standard, some consumers are not prepared to cope with it.
  607. One known victim is lld prior to r325420.
  608. 20171102:
  609. Building in a FreeBSD src checkout will automatically create object
  610. directories now rather than store files in the current directory if
  611. 'make obj' was not ran. Calling 'make obj' is no longer necessary.
  612. This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
  613. /etc/src-env.conf (not /etc/src.conf), or passing the option in the
  614. environment.
  615. 20171101:
  616. The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
  617. builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
  618. /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
  619. format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
  620. the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
  621. The UNIFIED_OBJDIR option is a transitional feature that will be
  622. removed for 12.0 release; please migrate to the new format for any
  623. tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
  624. than hardcoding paths.
  625. 20171028:
  626. The native-xtools target no longer installs the files by default to the
  627. OBJDIR. Use the native-xtools-install target with a DESTDIR to install
  628. to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
  629. 20171021:
  630. As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
  631. options are changing from controlling the build if defined / undefined
  632. to controlling the build with explicit 'yes' or 'no' values. They will
  633. shift to WITH/WITHOUT options to match other options in the system.
  634. 20171010:
  635. libstand has turned into a private library for sys/boot use only.
  636. It is no longer supported as a public interface outside of sys/boot.
  637. 20171005:
  638. The arm port has split armv6 into armv6 and armv7. armv7 is now
  639. a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
  640. and are running a kernel from before r324363, you will need to add
  641. MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
  642. 20171003:
  643. When building multiple kernels using KERNCONF, non-existent KERNCONF
  644. files will produce an error and buildkernel will fail. Previously
  645. missing KERNCONF files silently failed giving no indication as to
  646. why, only to subsequently discover during installkernel that the
  647. desired kernel was never built in the first place.
  648. 20170912:
  649. The default serial number format for CTL LUNs has changed. This will
  650. affect users who use /dev/diskid/* device nodes, or whose FibreChannel
  651. or iSCSI clients care about their LUNs' serial numbers. Users who
  652. require serial number stability should hardcode serial numbers in
  653. /etc/ctl.conf .
  654. 20170912:
  655. For 32-bit arm compiled for hard-float support, soft-floating point
  656. binaries now always get their shared libraries from
  657. LD_SOFT_LIBRARY_PATH (in the past, this was only used if
  658. /usr/libsoft also existed). Only users with a hard-float ld.so, but
  659. soft-float everything else should be affected.
  660. 20170826:
  661. The geli password typed at boot is now hidden. To restore the previous
  662. behavior, see geli(8) for configuration options.
  663. 20170825:
  664. Move PMTUD blackhole counters to TCPSTATS and remove them from bare
  665. sysctl values. Minor nit, but requires a rebuild of both world/kernel
  666. to complete.
  667. 20170814:
  668. "make check" behavior (made in ^/head@r295380) has been changed to
  669. execute from a limited sandbox, as opposed to executing from
  670. ${TESTSDIR}.
  671. Behavioral changes:
  672. - The "beforecheck" and "aftercheck" targets are now specified.
  673. - ${CHECKDIR} (added in commit noted above) has been removed.
  674. - Legacy behavior can be enabled by setting
  675. WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
  676. If the limited sandbox mode is enabled, "make check" will execute
  677. "make distribution", then install, execute the tests, and clean up the
  678. sandbox if successful.
  679. The "make distribution" and "make install" targets are typically run as
  680. root to set appropriate permissions and ownership at installation time.
  681. The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
  682. environment if executing "make check" with limited sandbox mode using
  683. an unprivileged user.
  684. 20170808:
  685. Since the switch to GPT disk labels, fsck for UFS/FFS has been
  686. unable to automatically find alternate superblocks. As of r322297,
  687. the information needed to find alternate superblocks has been
  688. moved to the end of the area reserved for the boot block.
  689. Filesystems created with a newfs of this vintage or later
  690. will create the recovery information. If you have a filesystem
  691. created prior to this change and wish to have a recovery block
  692. created for your filesystem, you can do so by running fsck in
  693. foreground mode (i.e., do not use the -p or -y options). As it
  694. starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
  695. to which you should answer yes.
  696. 20170728:
  697. As of r321665, an NFSv4 server configuration that services
  698. Kerberos mounts or clients that do not support the uid/gid in
  699. owner/owner_group string capability, must explicitly enable
  700. the nfsuserd daemon by adding nfsuserd_enable="YES" to the
  701. machine's /etc/rc.conf file.
  702. 20170722:
  703. Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
  704. Please see the 20141231 entry below for information about prerequisites
  705. and upgrading, if you are not already using clang 3.5.0 or higher.
  706. 20170701:
  707. WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
  708. r-commands (rlogin, rsh, etc.) to be built with the base system.
  709. 20170625:
  710. The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
  711. a very major ABI incompatible change, so users of FreeBSD/powerpc must
  712. be careful when performing source upgrades. It is best to run
  713. 'make installworld' from an alternate root system, either a live
  714. CD/memory stick, or a temporary root partition. Additionally, all ports
  715. must be recompiled. powerpc64 is largely unaffected, except in the case
  716. of 32-bit compatibility. All 32-bit binaries will be affected.
  717. 20170623:
  718. Forward compatibility for the "ino64" project have been committed. This
  719. will allow most new binaries to run on older kernels in a limited
  720. fashion. This prevents many of the common foot-shooting actions in the
  721. upgrade as well as the limited ability to roll back the kernel across
  722. the ino64 upgrade. Complicated use cases may not work properly, though
  723. enough simpler ones work to allow recovery in most situations.
  724. 20170620:
  725. Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
  726. if you require the GPL compiler.
  727. 20170618:
  728. The internal ABI used for communication between the NFS kernel modules
  729. was changed by r320085, so __FreeBSD_version was bumped to
  730. ensure all the NFS related modules are updated together.
  731. 20170617:
  732. The ABI of struct event was changed by extending the data
  733. member to 64bit and adding ext fields. For upgrade, same
  734. precautions as for the entry 20170523 "ino64" must be
  735. followed.
  736. 20170531:
  737. The GNU roff toolchain has been removed from base. To render manpages
  738. which are not supported by mandoc(1), man(1) can fallback on GNU roff
  739. from ports (and recommends to install it).
  740. To render roff(7) documents, consider using GNU roff from ports or the
  741. heirloom doctools roff toolchain from ports via pkg install groff or
  742. via pkg install heirloom-doctools.
  743. 20170524:
  744. The ath(4) and ath_hal(4) modules now build piecemeal to allow for
  745. smaller runtime footprint builds. This is useful for embedded systems
  746. which only require one chipset support.
  747. If you load it as a module, make sure this is in /boot/loader.conf:
  748. if_ath_load="YES"
  749. This will load the HAL, all chip/RF backends and if_ath_pci.
  750. If you have if_ath_pci in /boot/loader.conf, ensure it is after
  751. if_ath or it will not load any HAL chipset support.
  752. If you want to selectively load things (eg on ye cheape ARM/MIPS
  753. platforms where RAM is at a premium) you should:
  754. * load ath_hal
  755. * load the chip modules in question
  756. * load ath_rate, ath_dfs
  757. * load ath_main
  758. * load if_ath_pci and/or if_ath_ahb depending upon your particular
  759. bus bind type - this is where probe/attach is done.
  760. For further comments/feedback, poke adrian@ .
  761. 20170523:
  762. The "ino64" 64-bit inode project has been committed, which extends
  763. a number of types to 64 bits. Upgrading in place requires care and
  764. adherence to the documented upgrade procedure.
  765. If using a custom kernel configuration ensure that the
  766. COMPAT_FREEBSD11 option is included (as during the upgrade the
  767. system will be running the ino64 kernel with the existing world).
  768. For the safest in-place upgrade begin by removing previous build
  769. artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
  770. procedure documented below under the heading "To rebuild everything and
  771. install it on the current system." Specifically, a reboot is required
  772. after installing the new kernel before installing world. While an
  773. installworld normally works by accident from multiuser after rebooting
  774. the proper kernel, there are many cases where this will fail across this
  775. upgrade and installworld from single user is required.
  776. 20170424:
  777. The NATM framework including the en(4), fatm(4), hatm(4), and
  778. patm(4) devices has been removed. Consumers should plan a
  779. migration before the end-of-life date for FreeBSD 11.
  780. 20170420:
  781. GNU diff has been replaced by a BSD licensed diff. Some features of GNU
  782. diff has not been implemented, if those are needed a newer version of
  783. GNU diff is available via the diffutils package under the gdiff name.
  784. 20170413:
  785. As of r316810 for ipfilter, keep frags is no longer assumed when
  786. keep state is specified in a rule. r316810 aligns ipfilter with
  787. documentation in man pages separating keep frags from keep state.
  788. This allows keep state to be specified without forcing keep frags
  789. and allows keep frags to be specified independently of keep state.
  790. To maintain previous behaviour, also specify keep frags with
  791. keep state (as documented in ipf.conf.5).
  792. 20170407:
  793. arm64 builds now use the base system LLD 4.0.0 linker by default,
  794. instead of requiring that the aarch64-binutils port or package be
  795. installed. To continue using aarch64-binutils, set
  796. CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
  797. 20170405:
  798. The UDP optimization in entry 20160818 that added the sysctl
  799. net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
  800. packets will no longer be treated as L3 broadcast packets.
  801. 20170331:
  802. Binds and sends to the loopback addresses, IPv6 and IPv4, will now
  803. use any explicitly assigned loopback address available in the jail
  804. instead of using the first assigned address of the jail.
  805. 20170329:
  806. The ctl.ko module no longer implements the iSCSI target frontend:
  807. cfiscsi.ko does instead.
  808. If building cfiscsi.ko as a kernel module, the module can be loaded
  809. via one of the following methods:
  810. - `cfiscsi_load="YES"` in loader.conf(5).
  811. - Add `cfiscsi` to `$kld_list` in rc.conf(5).
  812. - ctladm(8)/ctld(8), when compiled with iSCSI support
  813. (`WITH_ISCSI=yes` in src.conf(5))
  814. Please see cfiscsi(4) for more details.
  815. 20170316:
  816. The mmcsd.ko module now additionally depends on geom_flashmap.ko.
  817. Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
  818. same source (previously, the dependency of mmcsd.ko on mmc.ko was
  819. missing, but mmcsd.ko now will refuse to load if it is incompatible
  820. with mmc.ko).
  821. 20170315:
  822. The syntax of ipfw(8) named states was changed to avoid ambiguity.
  823. If you have used named states in the firewall rules, you need to modify
  824. them after installworld and before rebooting. Now named states must
  825. be prefixed with colon.
  826. 20170311:
  827. The old drm (sys/dev/drm/) drivers for i915 and radeon have been
  828. removed as the userland we provide cannot use them. The KMS version
  829. (sys/dev/drm2) supports the same hardware.
  830. 20170302:
  831. Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
  832. Please see the 20141231 entry below for information about prerequisites
  833. and upgrading, if you are not already using clang 3.5.0 or higher.
  834. 20170221:
  835. The code that provides support for ZFS .zfs/ directory functionality
  836. has been reimplemented. It's not possible now to create a snapshot
  837. by mkdir under .zfs/snapshot/. That should be the only user visible
  838. change.
  839. 20170216:
  840. EISA bus support has been removed. The WITH_EISA option is no longer
  841. valid.
  842. 20170215:
  843. MCA bus support has been removed.
  844. 20170127:
  845. The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
  846. WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
  847. 20170112:
  848. The EM_MULTIQUEUE kernel configuration option is deprecated now that
  849. the em(4) driver conforms to iflib specifications.
  850. 20170109:
  851. The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
  852. IFLIB. If you have a custom kernel configuration that excludes em(4)
  853. but you use igb(4), you need to re-add em(4) to your custom
  854. configuration.
  855. 20161217:
  856. Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
  857. Please see the 20141231 entry below for information about prerequisites
  858. and upgrading, if you are not already using clang 3.5.0 or higher.
  859. 20161124:
  860. Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
  861. Please see the 20141231 entry below for information about prerequisites
  862. and upgrading, if you are not already using clang 3.5.0 or higher.
  863. 20161119:
  864. The layout of the pmap structure has changed for powerpc to put the pmap
  865. statistics at the front for all CPU variations. libkvm(3) and all tools
  866. that link against it need to be recompiled.
  867. 20161030:
  868. isl(4) and cyapa(4) drivers now require a new driver,
  869. chromebook_platform(4), to work properly on Chromebook-class hardware.
  870. On other types of hardware the drivers may need to be configured using
  871. device hints. Please see the corresponding manual pages for details.
  872. 20161017:
  873. The urtwn(4) driver was merged into rtwn(4) and now consists of
  874. rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
  875. parts.
  876. Also, firmware for RTL8188CE was renamed due to possible name
  877. conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
  878. 20161015:
  879. GNU rcs has been removed from base. It is available as packages:
  880. - rcs: Latest GPLv3 GNU rcs version.
  881. - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
  882. removed from base.
  883. 20161008:
  884. Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
  885. modules now requires that the kernel configuration contain the
  886. TCP_HHOOK option. (This option is included in the GENERIC kernel.)
  887. 20161003:
  888. The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
  889. ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
  890. 20160924:
  891. Relocatable object files with the extension of .So have been renamed
  892. to use an extension of .pico instead. The purpose of this change is
  893. to avoid a name clash with shared libraries on case-insensitive file
  894. systems. On those file systems, foo.So is the same file as foo.so.
  895. 20160918:
  896. GNU rcs has been turned off by default. It can (temporarily) be built
  897. again by adding WITH_RCS knob in src.conf.
  898. Otherwise, GNU rcs is available from packages:
  899. - rcs: Latest GPLv3 GNU rcs version.
  900. - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
  901. 20160918:
  902. The backup_uses_rcs functionality has been removed from rc.subr.
  903. 20160908:
  904. The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
  905. two separate components, QUEUE_MACRO_DEBUG_TRACE and
  906. QUEUE_MACRO_DEBUG_TRASH. Define both for the original
  907. QUEUE_MACRO_DEBUG behavior.
  908. 20160824:
  909. r304787 changed some ioctl interfaces between the iSCSI userspace
  910. programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
  911. rebuilt to work with new kernels. __FreeBSD_version has been bumped
  912. to 1200005.
  913. 20160818:
  914. The UDP receive code has been updated to only treat incoming UDP
  915. packets that were addressed to an L2 broadcast address as L3
  916. broadcast packets. It is not expected that this will affect any
  917. standards-conforming UDP application. The new behaviour can be
  918. disabled by setting the sysctl net.inet.udp.require_l2_bcast to
  919. 0.
  920. 20160818:
  921. Remove the openbsd_poll system call.
  922. __FreeBSD_version has been bumped because of this.
  923. 20160708:
  924. The stable/11 branch has been created from head@r302406.
  925. 20160622:
  926. The libc stub for the pipe(2) system call has been replaced with
  927. a wrapper that calls the pipe2(2) system call and the pipe(2)
  928. system call is now only implemented by the kernels that include
  929. "options COMPAT_FREEBSD10" in their config file (this is the
  930. default). Users should ensure that this option is enabled in
  931. their kernel or upgrade userspace to r302092 before upgrading their
  932. kernel.
  933. 20160527:
  934. CAM will now strip leading spaces from SCSI disks' serial numbers.
  935. This will affect users who create UFS filesystems on SCSI disks using
  936. those disk's diskid device nodes. For example, if /etc/fstab
  937. previously contained a line like
  938. "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
  939. change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
  940. transforms like gmirror may also be affected. ZFS users should
  941. generally be fine.
  942. 20160523:
  943. The bitstring(3) API has been updated with new functionality and
  944. improved performance. But it is binary-incompatible with the old API.
  945. Objects built with the new headers may not be linked against objects
  946. built with the old headers.
  947. 20160520:
  948. The brk and sbrk functions have been removed from libc on arm64.
  949. Binutils from ports has been updated to not link to these
  950. functions and should be updated to the latest version before
  951. installing a new libc.
  952. 20160517:
  953. The armv6 port now defaults to hard float ABI. Limited support
  954. for running both hardfloat and soft float on the same system
  955. is available using the libraries installed with -DWITH_LIBSOFT.
  956. This has only been tested as an upgrade path for installworld
  957. and packages may fail or need manual intervention to run. New
  958. packages will be needed.
  959. To update an existing self-hosted armv6hf system, you must add
  960. TARGET_ARCH=armv6 on the make command line for both the build
  961. and the install steps.
  962. 20160510:
  963. Kernel modules compiled outside of a kernel build now default to
  964. installing to /boot/modules instead of /boot/kernel. Many kernel
  965. modules built this way (such as those in ports) already overrode
  966. KMODDIR explicitly to install into /boot/modules. However,
  967. manually building and installing a module from /sys/modules will
  968. now install to /boot/modules instead of /boot/kernel.
  969. 20160414:
  970. The CAM I/O scheduler has been committed to the kernel. There should be
  971. no user visible impact. This does enable NCQ Trim on ada SSDs. While the
  972. list of known rogues that claim support for this but actually corrupt
  973. data is believed to be complete, be on the lookout for data
  974. corruption. The known rogue list is believed to be complete:
  975. o Crucial MX100, M550 drives with MU01 firmware.
  976. o Micron M510 and M550 drives with MU01 firmware.
  977. o Micron M500 prior to MU07 firmware
  978. o Samsung 830, 840, and 850 all firmwares
  979. o FCCT M500 all firmwares
  980. Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
  981. with working NCQ TRIM. For Micron branded drives, see your sales rep for
  982. updated firmware. Black listed drives will work correctly because these
  983. drives work correctly so long as no NCQ TRIMs are sent to them. Given
  984. this list is the same as found in Linux, it's believed there are no
  985. other rogues in the market place. All other models from the above
  986. vendors work.
  987. To be safe, if you are at all concerned, you can quirk each of your
  988. drives to prevent NCQ from being sent by setting:
  989. kern.cam.ada.X.quirks="0x2"
  990. in loader.conf. If the drive requires the 4k sector quirk, set the
  991. quirks entry to 0x3.
  992. 20160330:
  993. The FAST_DEPEND build option has been removed and its functionality is
  994. now the one true way. The old mkdep(1) style of 'make depend' has
  995. been removed. See 20160311 for further details.
  996. 20160317:
  997. Resource range types have grown from unsigned long to uintmax_t. All
  998. drivers, and anything using libdevinfo, need to be recompiled.
  999. 20160311:
  1000. WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
  1001. builds. It no longer runs mkdep(1) during 'make depend', and the
  1002. 'make depend' stage can safely be skipped now as it is auto ran
  1003. when building 'make all' and will generate all SRCS and DPSRCS before
  1004. building anything else. Dependencies are gathered at compile time with
  1005. -MF flags kept in separate .depend files per object file. Users should
  1006. run 'make cleandepend' once if using -DNO_CLEAN to clean out older
  1007. stale .depend files.
  1008. 20160306:
  1009. On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
  1010. kernel modules. Therefore, if you load any kernel modules at boot time,
  1011. please install the boot loaders after you install the kernel, but before
  1012. rebooting, e.g.:
  1013. make buildworld
  1014. make buildkernel KERNCONF=YOUR_KERNEL_HERE
  1015. make installkernel KERNCONF=YOUR_KERNEL_HERE
  1016. make -C sys/boot install
  1017. <reboot in single user>
  1018. Then follow the usual steps, described in the General Notes section,
  1019. below.
  1020. 20160305:
  1021. Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
  1022. see the 20141231 entry below for information about prerequisites and
  1023. upgrading, if you are not already using clang 3.5.0 or higher.
  1024. 20160301:
  1025. The AIO subsystem is now a standard part of the kernel. The
  1026. VFS_AIO kernel option and aio.ko kernel module have been removed.
  1027. Due to stability concerns, asynchronous I/O requests are only
  1028. permitted on sockets and raw disks by default. To enable
  1029. asynchronous I/O requests on all file types, set the
  1030. vfs.aio.enable_unsafe sysctl to a non-zero value.
  1031. 20160226:
  1032. The ELF object manipulation tool objcopy is now provided by the
  1033. ELF Tool Chain project rather than by GNU binutils. It should be a
  1034. drop-in replacement, with the addition of arm64 support. The
  1035. (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
  1036. to obtain the GNU version if necessary.
  1037. 20160129:
  1038. Building ZFS pools on top of zvols is prohibited by default. That
  1039. feature has never worked safely; it's always been prone to deadlocks.
  1040. Using a zvol as the backing store for a VM guest's virtual disk will
  1041. still work, even if the guest is using ZFS. Legacy behavior can be
  1042. restored by setting vfs.zfs.vol.recursive=1.
  1043. 20160119:
  1044. The NONE and HPN patches has been removed from OpenSSH. They are
  1045. still available in the security/openssh-portable port.
  1046. 20160113:
  1047. With the addition of ypldap(8), a new _ypldap user is now required
  1048. during installworld. "mergemaster -p" can be used to add the user
  1049. prior to installworld, as documented in the handbook.
  1050. 20151216:
  1051. The tftp loader (pxeboot) now uses the option root-path directive. As a
  1052. consequence it no longer looks for a pxeboot.4th file on the tftp
  1053. server. Instead it uses the regular /boot infrastructure as with the
  1054. other loaders.
  1055. 20151211:
  1056. The code to start recording plug and play data into the modules has
  1057. been committed. While the old tools will properly build a new kernel,
  1058. a number of warnings about "unknown metadata record 4" will be produced
  1059. for an older kldxref. To avoid such warnings, make sure to rebuild
  1060. the kernel toolchain (or world). Make sure that you have r292078 or
  1061. later when trying to build 292077 or later before rebuilding.
  1062. 20151207:
  1063. Debug data files are now built by default with 'make buildworld' and
  1064. installed with 'make installworld'. This facilitates debugging but
  1065. requires more disk space both during the build and for the installed
  1066. world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
  1067. in src.conf(5).
  1068. 20151130:
  1069. r291527 changed the internal interface between the nfsd.ko and
  1070. nfscommon.ko modules. As such, they must both be upgraded to-gether.
  1071. __FreeBSD_version has been bumped because of this.
  1072. 20151108:
  1073. Add support for unicode collation strings leads to a change of
  1074. order of files listed by ls(1) for example. To get back to the old
  1075. behaviour, set LC_COLLATE environment variable to "C".
  1076. Databases administrators will need to reindex their databases given
  1077. collation results will be different.
  1078. Due to a bug in install(1) it is recommended to remove the ancient
  1079. locales before running make installworld.
  1080. rm -rf /usr/share/locale/*
  1081. 20151030:
  1082. The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
  1083. libcrypto.so.7 or libssl.so.7 must be recompiled.
  1084. 20151020:
  1085. Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
  1086. Kernel modules isp_2400_multi and isp_2500_multi were removed and
  1087. should be replaced with isp_2400 and isp_2500 modules respectively.
  1088. 20151017:
  1089. The build previously allowed using 'make -n' to not recurse into
  1090. sub-directories while showing what commands would be executed, and
  1091. 'make -n -n' to recursively show commands. Now 'make -n' will recurse
  1092. and 'make -N' will not.
  1093. 20151012:
  1094. If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
  1095. and etcupdate will now use this file. A custom sendmail.cf is now
  1096. updated via this mechanism rather than via installworld. If you had
  1097. excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
  1098. want to remove the exclusion or change it to "always install".
  1099. /etc/mail/sendmail.cf is now managed the same way regardless of
  1100. whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
  1101. SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
  1102. 20151011:
  1103. Compatibility shims for legacy ATA device names have been removed.
  1104. It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
  1105. and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
  1106. environment variables, /dev/ad* and /dev/ar* symbolic links.
  1107. 20151006:
  1108. Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
  1109. Please see the 20141231 entry below for information about prerequisites
  1110. and upgrading, if you are not already using clang 3.5.0 or higher.
  1111. 20150924:
  1112. Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
  1113. and renamed from .symbols to .debug. This reduces the size requirements
  1114. on the boot partition or file system and provides consistency with
  1115. userland debug files.
  1116. When using the supported kernel installation method the
  1117. /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
  1118. as is done with /boot/kernel.
  1119. Developers wishing to maintain the historical behavior of installing
  1120. debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
  1121. 20150827:
  1122. The wireless drivers had undergone changes that remove the 'parent
  1123. interface' from the ifconfig -l output. The rc.d network scripts
  1124. used to check presence of a parent interface in the list, so old
  1125. scripts would fail to start wireless networking. Thus, etcupdate(3)
  1126. or mergemaster(8) run is required after kernel update, to update your
  1127. rc.d scripts in /etc.
  1128. 20150827:
  1129. pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
  1130. These configurations are now automatically interpreted as
  1131. 'scrub fragment reassemble'.
  1132. 20150817:
  1133. Kernel-loadable modules for the random(4) device are back. To use
  1134. them, the kernel must have
  1135. device random
  1136. options RANDOM_LOADABLE
  1137. kldload(8) can then be used to load random_fortuna.ko
  1138. or random_yarrow.ko. Please note that due to the indirect
  1139. function calls that the loadable modules need to provide,
  1140. the build-in variants will be slightly more efficient.
  1141. The random(4) kernel option RANDOM_DUMMY has been retired due to
  1142. unpopularity. It was not all that useful anyway.
  1143. 20150813:
  1144. The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
  1145. Control over building the ELF Tool Chain tools is now provided by
  1146. the WITHOUT_TOOLCHAIN knob.
  1147. 20150810:
  1148. The polarity of Pulse Per Second (PPS) capture events with the
  1149. uart(4) driver has been corrected. Prior to this change the PPS
  1150. "assert" event corresponded to the trailing edge of a positive PPS
  1151. pulse and the "clear" event was the leading edge of the next pulse.
  1152. As the width of a PPS pulse in a typical GPS receiver is on the
  1153. order of 1 millisecond, most users will not notice any significant
  1154. difference with this change.
  1155. Anyone who has compensated for the historical polarity reversal by
  1156. configuring a negative offset equal to the pulse width will need to
  1157. remove that workaround.
  1158. 20150809:
  1159. The default group assigned to /dev/dri entries has been changed
  1160. from 'wheel' to 'video' with the id of '44'. If you want to have
  1161. access to the dri devices please add yourself to the video group
  1162. with:
  1163. # pw groupmod video -m $USER
  1164. 20150806:
  1165. The menu.rc and loader.rc files will now be replaced during
  1166. upgrades. Please migrate local changes to menu.rc.local and
  1167. loader.rc.local instead.
  1168. 20150805:
  1169. GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
  1170. strings and strip have been removed. The src.conf(5) knob
  1171. WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
  1172. 20150728:
  1173. As ZFS requires more kernel stack pages than is the default on some
  1174. architectures e.g. i386, it now warns if KSTACK_PAGES is less than
  1175. ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
  1176. Please consider using 'options KSTACK_PAGES=X' where X is greater
  1177. than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
  1178. 20150706:
  1179. sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
  1180. and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
  1181. default, i.e., they will not contain "::". For example, instead
  1182. of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
  1183. to have a more specific match, such as different map entries for
  1184. IPv6:0:0 vs IPv6:0. This change requires that configuration
  1185. data (including maps, files, classes, custom ruleset, etc.) must
  1186. use the same format, so make certain such configuration data is
  1187. upgrading. As a very simple check search for patterns like
  1188. 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
  1189. behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
  1190. the cf option UseCompressedIPv6Addresses.
  1191. 20150630:
  1192. The default kernel entropy-processing algorithm is now
  1193. Fortuna, replacing Yarrow.
  1194. Assuming you have 'device random' in your kernel config
  1195. file, the configurations allow a kernel option to override
  1196. this default. You may choose *ONE* of:
  1197. options RANDOM_YARROW # Legacy /dev/random algorithm.
  1198. options RANDOM_DUMMY # Blocking-only driver.
  1199. If you have neither, you get Fortuna. For most people,
  1200. read no further, Fortuna will give a /dev/random that works
  1201. like it always used to, and the difference will be irrelevant.
  1202. If you remove 'device random', you get *NO* kernel-processed
  1203. entropy at all. This may be acceptable to folks building
  1204. embedded systems, but has complications. Carry on reading,
  1205. and it is assumed you know what you need.
  1206. *PLEASE* read random(4) and random(9) if you are in the
  1207. habit of tweaking kernel configs, and/or if you are a member
  1208. of the embedded community, wanting specific and not-usual
  1209. behaviour from your security subsystems.
  1210. NOTE!! If you use RANDOM_DUMMY and/or have no 'device
  1211. random', you will NOT have a functioning /dev/random, and
  1212. many cryptographic features will not work, including SSH.
  1213. You may also find strange behaviour from the random(3) set
  1214. of library functions, in particular sranddev(3), srandomdev(3)
  1215. and arc4random(3). The reason for this is that the KERN_ARND
  1216. sysctl only returns entropy if it thinks it has some to
  1217. share, and with RANDOM_DUMMY or no 'device random' this
  1218. will never happen.
  1219. 20150623:
  1220. An additional fix for the issue described in the 20150614 sendmail
  1221. entry below has been committed in revision 284717.
  1222. 20150616:
  1223. FreeBSD's old make (fmake) has been removed from the system. It is
  1224. available as the devel/fmake port or via pkg install fmake.
  1225. 20150615:
  1226. The fix for the issue described in the 20150614 sendmail entry
  1227. below has been committed in revision 284436. The work
  1228. around described in that entry is no longer needed unless the
  1229. default setting is overridden by a confDH_PARAMETERS configuration
  1230. setting of '5' or pointing to a 512 bit DH parameter file.
  1231. 20150614:
  1232. ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
  1233. atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
  1234. and devel/kyua to version 0.20+ and adjust any calling code to work
  1235. with Kyuafile and kyua.
  1236. 20150614:
  1237. The import of openssl to address the FreeBSD-SA-15:10.openssl
  1238. security advisory includes a change which rejects handshakes
  1239. with DH parameters below 768 bits. sendmail releases prior
  1240. to 8.15.2 (not yet released), defaulted to a 512 bit
  1241. DH parameter setting for client connections. To work around
  1242. this interoperability, sendmail can be configured to use a
  1243. 2048 bit DH parameter by:
  1244. 1. Edit /etc/mail/`hostname`.mc
  1245. 2. If a setting for confDH_PARAMETERS does not exist or
  1246. exists and is set to a string beginning with '5',
  1247. replace it with '2'.
  1248. 3. If a setting for confDH_PARAMETERS exists and is set to
  1249. a file path, create a new file with:
  1250. openssl dhparam -out /path/to/file 2048
  1251. 4. Rebuild the .cf file:
  1252. cd /etc/mail/; make; make install
  1253. 5. Restart sendmail:
  1254. cd /etc/mail/; make restart
  1255. A sendmail patch is coming, at which time this file will be
  1256. updated.
  1257. 20150604:
  1258. Generation of legacy formatted entries have been disabled by default
  1259. in pwd_mkdb(8), as all base system consumers of the legacy formatted
  1260. entries were converted to use the new format by default when the new,
  1261. machine independent format have been added and supported since FreeBSD
  1262. 5.x.
  1263. Please see the pwd_mkdb(8) manual page for further details.
  1264. 20150525:
  1265. Clang and llvm have been upgraded to 3.6.1 release. Please see the
  1266. 20141231 entry below for information about prerequisites and upgrading,
  1267. if you are not already using 3.5.0 or higher.
  1268. 20150521:
  1269. TI platform code switched to using vendor DTS files and this update
  1270. may break existing systems running on Beaglebone, Beaglebone Black,
  1271. and Pandaboard:
  1272. - dtb files should be regenerated/reinstalled. Filenames are the
  1273. same but content is different now
  1274. - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
  1275. has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
  1276. addressing scheme is now pin 25 on /dev/gpioc3.
  1277. - Pandaboard: /etc/ttys should be updated, serial console device is
  1278. now /dev/ttyu2, not /dev/ttyu0
  1279. 20150501:
  1280. soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
  1281. If you need the GNU extension from groff soelim(1), install groff
  1282. from package: pkg install groff, or via ports: textproc/groff.
  1283. 20150423:
  1284. chmod, chflags, chown and chgrp now affect symlinks in -R mode as
  1285. defined in symlink(7); previously symlinks were silently ignored.
  1286. 20150415:
  1287. The const qualifier has been removed from iconv(3) to comply with
  1288. POSIX. The ports tree is aware of this from r384038 onwards.
  1289. 20150416:
  1290. Libraries specified by LIBADD in Makefiles must have a corresponding
  1291. DPADD_<lib> variable to ensure correct dependencies. This is now
  1292. enforced in src.libnames.mk.
  1293. 20150324:
  1294. From legacy ata(4) driver was removed support for SATA controllers
  1295. supported by more functional drivers ahci(4), siis(4) and mvs(4).
  1296. Kernel modules ataahci and ataadaptec were removed completely,
  1297. replaced by ahci and mvs modules respectively.
  1298. 20150315:
  1299. Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
  1300. the 20141231 entry below for information about prerequisites and
  1301. upgrading, if you are not already using 3.5.0 or higher.
  1302. 20150307:
  1303. The 32-bit PowerPC kernel has been changed to a position-independent
  1304. executable. This can only be booted with a version of loader(8)
  1305. newer than January 31, 2015, so make sure to update both world and
  1306. kernel before rebooting.
  1307. 20150217:
  1308. If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
  1309. but before r278950, the RNG was not seeded properly. Immediately
  1310. upgrade the kernel to r278950 or later and regenerate any keys (e.g.
  1311. ssh keys or openssl keys) that were generated w/ a kernel from that
  1312. range. This does not affect programs that directly used /dev/random
  1313. or /dev/urandom. All userland uses of arc4random(3) are affected.
  1314. 20150210:
  1315. The autofs(4) ABI was changed in order to restore binary compatibility
  1316. with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
  1317. with the new kernel.
  1318. 20150131:
  1319. The powerpc64 kernel has been changed to a position-independent
  1320. executable. This can only be booted with a new version of loader(8),
  1321. so make sure to update both world and kernel before rebooting.
  1322. 20150118:
  1323. Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
  1324. only release, no new features have been added. Please see the 20141231
  1325. entry below for information about prerequisites and upgrading, if you
  1326. are not already using 3.5.0.
  1327. 20150107:
  1328. ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
  1329. taken from the ELF Tool Chain project rather than GNU binutils. They
  1330. should be drop-in replacements, with the addition of arm64 support.
  1331. The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
  1332. binutils tools, if necessary. See 20150805 for updated information.
  1333. 20150105:
  1334. The default Unbound configuration now enables remote control
  1335. using a local socket. Users who have already enabled the
  1336. local_unbound service should regenerate their configuration
  1337. by running "service local_unbound setup" as root.
  1338. 20150102:
  1339. The GNU texinfo and GNU info pages have been removed.
  1340. To be able to view GNU info pages please install texinfo from ports.
  1341. 20141231:
  1342. Clang, llvm and lldb have been upgraded to 3.5.0 release.
  1343. As of this release, a prerequisite for building clang, llvm and lldb is
  1344. a C++11 capable compiler and C++11 standard library. This means that to
  1345. be able to successfully build the cross-tools stage of buildworld, with
  1346. clang as the bootstrap compiler, your system compiler or cross compiler
  1347. should either be clang 3.3 or later, or gcc 4.8 or later, and your
  1348. system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
  1349. later.
  1350. On any standard FreeBSD 10.x or 11.x installation, where clang and
  1351. libc++ are on by default (that is, on x86 or arm), this should work out
  1352. of the box.
  1353. On 9.x installations where clang is enabled by default, e.g. on x86 and
  1354. powerpc, libc++ will not be enabled by default, so libc++ should be
  1355. built (with clang) and installed first. If both clang and libc++ are
  1356. missing, build clang first, then use it to build libc++.
  1357. On 8.x and earlier installations, upgrade to 9.x first, and then follow
  1358. the instructions for 9.x above.
  1359. Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
  1360. default, and do not build clang.
  1361. Many embedded systems are resource constrained, and will not be able to
  1362. build clang in a reasonable time, or in some cases at all. In those
  1363. cases, cross building bootable systems on amd64 is a workaround.
  1364. This new version of clang introduces a number of new warnings, of which
  1365. the following are most likely to appear:
  1366. -Wabsolute-value
  1367. This warns in two cases, for both C and C++:
  1368. * When the code is trying to take the absolute value of an unsigned
  1369. quantity, which is effectively a no-op, and almost never what was
  1370. intended. The code should be fixed, if at all possible. If you are
  1371. sure that the unsigned quantity can be safely cast to signed, without
  1372. loss of information or undefined behavior, you can add an explicit
  1373. cast, or disable the warning.
  1374. * When the code is trying to take an absolute value, but the called
  1375. abs() variant is for the wrong type, which can lead to truncation.
  1376. If you want to disable the warning instead of fixing the code, please
  1377. make sure that truncation will not occur, or it might lead to unwanted
  1378. side-effects.
  1379. -Wtautological-undefined-compare and
  1380. -Wundefined-bool-conversion
  1381. These warn when C++ code is trying to compare 'this' against NULL, while
  1382. 'this' should never be NULL in well-defined C++ code. However, there is
  1383. some legacy (pre C++11) code out there, which actively abuses this
  1384. feature, which was less strictly defined in previous C++ versions.
  1385. Squid and openjdk do this, for example. The warning can be turned off
  1386. for C++98 and earlier, but compiling the code in C++11 mode might result
  1387. in unexpected behavior; for example, the parts of the program that are
  1388. unreachable could be optimized away.
  1389. 20141222:
  1390. The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
  1391. kernel sources have been removed. The .h files remain, since some
  1392. utilities include them. This will need to be fixed later.
  1393. If "mount -t oldnfs ..." is attempted, it will fail.
  1394. If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
  1395. the utilities will report errors.
  1396. 20141121:
  1397. The handling of LOCAL_LIB_DIRS has been altered to skip addition of
  1398. directories to top level SUBDIR variable when their parent
  1399. directory is included in LOCAL_DIRS. Users with build systems with
  1400. such hierarchies and without SUBDIR entries in the parent
  1401. directory Makefiles should add them or add the directories to
  1402. LOCAL_DIRS.
  1403. 20141109:
  1404. faith(4) and faithd(8) have been removed from the base system. Faith
  1405. has been obsolete for a very long time.
  1406. 20141104:
  1407. vt(4), the new console driver, is enabled by default. It brings
  1408. support for Unicode and double-width characters, as well as
  1409. support for UEFI and integration with the KMS kernel video
  1410. drivers.
  1411. You may need to update your console settings in /etc/rc.conf,
  1412. most probably the keymap. During boot, /etc/rc.d/syscons will
  1413. indicate what you need to do.
  1414. vt(4) still has issues and lacks some features compared to
  1415. syscons(4). See the wiki for up-to-date information:
  1416. https://wiki.freebsd.org/Newcons
  1417. If you want to keep using syscons(4), you can do so by adding
  1418. the following line to /boot/loader.conf:
  1419. kern.vty=sc
  1420. 20141102:
  1421. pjdfstest has been integrated into kyua as an opt-in test suite.
  1422. Please see share/doc/pjdfstest/README for more details on how to
  1423. execute it.
  1424. 20141009:
  1425. gperf has been removed from the base system for architectures
  1426. that use clang. Ports that require gperf will obtain it from the
  1427. devel/gperf port.
  1428. 20140923:
  1429. pjdfstest has been moved from tools/regression/pjdfstest to
  1430. contrib/pjdfstest .
  1431. 20140922:
  1432. At svn r271982, The default linux compat kernel ABI has been adjusted
  1433. to 2.6.18 in support of the linux-c6 compat ports infrastructure
  1434. update. If you wish to continue using the linux-f10 compat ports,
  1435. add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
  1436. encouraged to update their linux-compat packages to linux-c6 during
  1437. their next update cycle.
  1438. 20140729:
  1439. The ofwfb driver, used to provide a graphics console on PowerPC when
  1440. using vt(4), no longer allows mmap() of all physical memory. This
  1441. will prevent Xorg on PowerPC with some ATI graphics cards from
  1442. initializing properly unless x11-servers/xorg-server is updated to
  1443. 1.12.4_8 or newer.
  1444. 20140723:
  1445. The xdev targets have been converted to using TARGET and
  1446. TARGET_ARCH instead of XDEV and XDEV_ARCH.
  1447. 20140719:
  1448. The default unbound configuration has been modified to address
  1449. issues with reverse lookups on networks that use private
  1450. address ranges. If you use the local_unbound service, run
  1451. "service local_unbound setup" as root to regenerate your
  1452. configuration, then "service local_unbound reload" to load the
  1453. new configuration.
  1454. 20140709:
  1455. The GNU texinfo and GNU info pages are not built and installed
  1456. anymore, WITH_INFO knob has been added to allow to built and install
  1457. them again.
  1458. UPDATE: see 20150102 entry on texinfo's removal
  1459. 20140708:
  1460. The GNU readline library is now an INTERNALLIB - that is, it is
  1461. statically linked into consumers (GDB and variants) in the base
  1462. system, and the shared library is no longer installed. The
  1463. devel/readline port is available for third party software that
  1464. requires readline.
  1465. 20140702:
  1466. The Itanium architecture (ia64) has been removed from the list of
  1467. known architectures. This is the first step in the removal of the
  1468. architecture.
  1469. 20140701:
  1470. Commit r268115 has added NFSv4.1 server support, merged from
  1471. projects/nfsv4.1-server. Since this includes changes to the
  1472. internal interfaces between the NFS related modules, a full
  1473. build of the kernel and modules will be necessary.
  1474. __FreeBSD_version has been bumped.
  1475. 20140629:
  1476. The WITHOUT_VT_SUPPORT kernel config knob has been renamed
  1477. WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
  1478. which differs from the behaviour controlled by this knob.)
  1479. 20140619:
  1480. Maximal length of the serial number in CTL was increased from 16 to
  1481. 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
  1482. and ctld, need to be rebuilt to work with a new kernel.
  1483. 20140606:
  1484. The libatf-c and libatf-c++ major versions were downgraded to 0 and
  1485. 1 respectively to match the upstream numbers. They were out of
  1486. sync because, when they were originally added to FreeBSD, the
  1487. upstream versions were not respected. These libraries are private
  1488. and not yet built by default, so renumbering them should be a
  1489. non-issue. However, unclean source trees will yield broken test
  1490. programs once the operator executes "make delete-old-libs" after a
  1491. "make installworld".
  1492. Additionally, the atf-sh binary was made private by moving it into
  1493. /usr/libexec/. Already-built shell test programs will keep the
  1494. path to the old binary so they will break after "make delete-old"
  1495. is run.
  1496. If you are using WITH_TESTS=yes (not the default), wipe the object
  1497. tree and rebuild from scratch to prevent spurious test failures.
  1498. This is only needed once: the misnumbered libraries and misplaced
  1499. binaries have been added to OptionalObsoleteFiles.inc so they will
  1500. be removed during a clean upgrade.
  1501. 20140512:
  1502. Clang and llvm have been upgraded to 3.4.1 release.
  1503. 20140508:
  1504. We bogusly installed src.opts.mk in /usr/share/mk. This file should
  1505. be removed to avoid issues in the future (and has been added to
  1506. ObsoleteFiles.inc).
  1507. 20140505:
  1508. /etc/src.conf now affects only builds of the FreeBSD src tree. In the
  1509. past, it affected all builds that used the bsd.*.mk files. The old
  1510. behavior was a bug, but people may have relied upon it. To get this
  1511. behavior back, you can .include /etc/src.conf from /etc/make.conf
  1512. (which is still global and isn't changed). This also changes the
  1513. behavior of incremental builds inside the tree of individual
  1514. directories. Set MAKESYSPATH to ".../share/mk" to do that.
  1515. Although this has survived make universe and some upgrade scenarios,
  1516. other upgrade scenarios may have broken. At least one form of
  1517. temporary breakage was fixed with MAKESYSPATH settings for buildworld
  1518. as well... In cases where MAKESYSPATH isn't working with this
  1519. setting, you'll need to set it to the full path to your tree.
  1520. One side effect of all this cleaning up is that bsd.compiler.mk
  1521. is no longer implicitly included by bsd.own.mk. If you wish to
  1522. use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
  1523. as well.
  1524. 20140430:
  1525. The lindev device has been removed since /dev/full has been made a
  1526. standard device. __FreeBSD_version has been bumped.
  1527. 20140424:
  1528. The knob WITHOUT_VI was added to the base system, which controls
  1529. building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
  1530. in order to reorder files share/termcap and didn't build ex(1) as a
  1531. build tool, so building/installing with WITH_VI is highly advised for
  1532. build hosts for older releases.
  1533. This issue has been fixed in stable/9 and stable/10 in r277022 and
  1534. r276991, respectively.
  1535. 20140418:
  1536. The YES_HESIOD knob has been removed. It has been obsolete for
  1537. a decade. Please move to using WITH_HESIOD instead or your builds
  1538. will silently lack HESIOD.
  1539. 20140405:
  1540. The uart(4) driver has been changed with respect to its handling
  1541. of the low-level console. Previously the uart(4) driver prevented
  1542. any process from changing the baudrate or the CLOCAL and HUPCL
  1543. control flags. By removing the restrictions, operators can make
  1544. changes to the serial console port without having to reboot.
  1545. However, when getty(8) is started on the serial device that is
  1546. associated with the low-level console, a misconfigured terminal
  1547. line in /etc/ttys will now have a real impact.
  1548. Before upgrading the kernel, make sure that /etc/ttys has the
  1549. serial console device configured as 3wire without baudrate to
  1550. preserve the previous behaviour. E.g:
  1551. ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
  1552. 20140306:
  1553. Support for libwrap (TCP wrappers) in rpcbind was disabled by default
  1554. to improve performance. To re-enable it, if needed, run rpcbind
  1555. with command line option -W.
  1556. 20140226:
  1557. Switched back to the GPL dtc compiler due to updates in the upstream
  1558. dts files not being supported by the BSDL dtc compiler. You will need
  1559. to rebuild your kernel toolchain to pick up the new compiler. Core dumps
  1560. may result while building dtb files during a kernel build if you fail
  1561. to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
  1562. 20140216:
  1563. Clang and llvm have been upgraded to 3.4 release.
  1564. 20140216:
  1565. The nve(4) driver has been removed. Please use the nfe(4) driver
  1566. for NVIDIA nForce MCP Ethernet adapters instead.
  1567. 20140212:
  1568. An ABI incompatibility crept into the libc++ 3.4 import in r261283.
  1569. This could cause certain C++ applications using shared libraries built
  1570. against the previous version of libc++ to crash. The incompatibility
  1571. has now been fixed, but any C++ applications or shared libraries built
  1572. between r261283 and r261801 should be recompiled.
  1573. 20140204:
  1574. OpenSSH will now ignore errors caused by kernel lacking of Capsicum
  1575. capability mode support. Please note that enabling the feature in
  1576. kernel is still highly recommended.
  1577. 20140131:
  1578. OpenSSH is now built with sandbox support, and will use sandbox as
  1579. the default privilege separation method. This requires Capsicum
  1580. capability mode support in kernel.
  1581. 20140128:
  1582. The libelf and libdwarf libraries have been updated to newer
  1583. versions from upstream. Shared library version numbers for
  1584. these two libraries were bumped. Any ports or binaries
  1585. requiring these two libraries should be recompiled.
  1586. __FreeBSD_version is bumped to 1100006.
  1587. 20140110:
  1588. If a Makefile in a tests/ directory was auto-generating a Kyuafile
  1589. instead of providing an explicit one, this would prevent such
  1590. Makefile from providing its own Kyuafile in the future during
  1591. NO_CLEAN builds. This has been fixed in the Makefiles but manual
  1592. intervention is needed to clean an objdir if you use NO_CLEAN:
  1593. # find /usr/obj -name Kyuafile | xargs rm -f
  1594. 20131213:
  1595. The behavior of gss_pseudo_random() for the krb5 mechanism
  1596. has changed, for applications requesting a longer random string
  1597. than produced by the underlying enctype's pseudo-random() function.
  1598. In particular, the random string produced from a session key of
  1599. enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
  1600. be different at the 17th octet and later, after this change.
  1601. The counter used in the PRF+ construction is now encoded as a
  1602. big-endian integer in accordance with RFC 4402.
  1603. __FreeBSD_version is bumped to 1100004.
  1604. 20131108:
  1605. The WITHOUT_ATF build knob has been removed and its functionality
  1606. has been subsumed into the more generic WITHOUT_TESTS. If you were
  1607. using the former to disable the build of the ATF libraries, you
  1608. should change your settings to use the latter.
  1609. 20131025:
  1610. The default version of mtree is nmtree which is obtained from
  1611. NetBSD. The output is generally the same, but may vary
  1612. slightly. If you found you need identical output adding
  1613. "-F freebsd9" to the command line should do the trick. For the
  1614. time being, the old mtree is available as fmtree.
  1615. 20131014:
  1616. libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
  1617. This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
  1618. 1.1.4_8 and verify bsdyml not linked in, before running "make
  1619. delete-old-libs":
  1620. # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
  1621. or
  1622. # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
  1623. 20131010:
  1624. The stable/10 branch has been created in subversion from head
  1625. revision r256279.
  1627. General Notes
  1628. -------------
  1629. Sometimes, obscure build problems are the result of environment
  1630. poisoning. This can happen because the make utility reads its
  1631. environment when searching for values for global variables. To run
  1632. your build attempts in an "environmental clean room", prefix all make
  1633. commands with 'env -i '. See the env(1) manual page for more details.
  1634. Occasionally a build failure will occur with "make -j" due to a race
  1635. condition. If this happens try building again without -j, and please
  1636. report a bug if it happens consistently.
  1637. When upgrading from one major version to another it is generally best to
  1638. upgrade to the latest code in the currently installed branch first, then
  1639. do an upgrade to the new branch. This is the best-tested upgrade path,
  1640. and has the highest probability of being successful. Please try this
  1641. approach if you encounter problems with a major version upgrade. Since
  1642. the stable 4.x branch point, one has generally been able to upgrade from
  1643. anywhere in the most recent stable branch to head / current (or even the
  1644. last couple of stable branches). See the top of this file when there's
  1645. an exception.
  1646. When upgrading a live system, having a root shell around before
  1647. installing anything can help undo problems. Not having a root shell
  1648. around can lead to problems if pam has changed too much from your
  1649. starting point to allow continued authentication after the upgrade.
  1650. This file should be read as a log of events. When a later event changes
  1651. information of a prior event, the prior event should not be deleted.
  1652. Instead, a pointer to the entry with the new information should be
  1653. placed in the old entry. Readers of this file should also sanity check
  1654. older entries before relying on them blindly. Authors of new entries
  1655. should write them with this in mind.
  1656. ZFS notes
  1657. ---------
  1658. When upgrading the boot ZFS pool to a new version, always follow
  1659. these two steps:
  1660. 1.) recompile and reinstall the ZFS boot loader and boot block
  1661. (this is part of "make buildworld" and "make installworld")
  1662. 2.) update the ZFS boot block on your boot drive
  1663. The following example updates the ZFS boot block on the first
  1664. partition (freebsd-boot) of a GPT partitioned drive ada0:
  1665. "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
  1666. Non-boot pools do not need these updates.
  1667. To build a kernel
  1668. -----------------
  1669. If you are updating from a prior version of FreeBSD (even one just
  1670. a few days old), you should follow this procedure. It is the most
  1671. failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
  1672. make kernel-toolchain
  1675. To test a kernel once
  1676. ---------------------
  1677. If you just want to boot a kernel once (because you are not sure
  1678. if it works, or if you want to boot a known bad kernel to provide
  1679. debugging information) run
  1680. make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
  1681. nextboot -k testkernel
  1682. To rebuild everything and install it on the current system.
  1683. -----------------------------------------------------------
  1684. # Note: sometimes if you are running current you gotta do more than
  1685. # is listed here if you are upgrading from a really old current.
  1686. <make sure you have good level 0 dumps>
  1687. make buildworld
  1688. make buildkernel KERNCONF=YOUR_KERNEL_HERE
  1689. make installkernel KERNCONF=YOUR_KERNEL_HERE
  1690. [1]
  1691. <reboot in single user> [3]
  1692. mergemaster -Fp [5]
  1693. make installworld
  1694. mergemaster -Fi [4]
  1695. make delete-old [6]
  1696. <reboot>
  1697. To cross-install current onto a separate partition
  1698. --------------------------------------------------
  1699. # In this approach we use a separate partition to hold
  1700. # current's root, 'usr', and 'var' directories. A partition
  1701. # holding "/", "/usr" and "/var" should be about 2GB in
  1702. # size.
  1703. <make sure you have good level 0 dumps>
  1704. <boot into -stable>
  1705. make buildworld
  1706. make buildkernel KERNCONF=YOUR_KERNEL_HERE
  1707. <maybe newfs current's root partition>
  1708. <mount current's root partition on directory ${CURRENT_ROOT}>
  1709. make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
  1710. make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
  1712. cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
  1713. <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
  1714. <reboot into current>
  1715. <do a "native" rebuild/install as described in the previous section>
  1716. <maybe install compatibility libraries from ports/misc/compat*>
  1717. <reboot>
  1718. To upgrade in-place from stable to current
  1719. ----------------------------------------------
  1720. <make sure you have good level 0 dumps>
  1721. make buildworld [9]
  1722. make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
  1723. make installkernel KERNCONF=YOUR_KERNEL_HERE
  1724. [1]
  1725. <reboot in single user> [3]
  1726. mergemaster -Fp [5]
  1727. make installworld
  1728. mergemaster -Fi [4]
  1729. make delete-old [6]
  1730. <reboot>
  1731. Make sure that you've read the UPDATING file to understand the
  1732. tweaks to various things you need. At this point in the life
  1733. cycle of current, things change often and you are on your own
  1734. to cope. The defaults can also change, so please read ALL of
  1735. the UPDATING entries.
  1736. Also, if you are tracking -current, you must be subscribed to
  1737. freebsd-current@freebsd.org. Make sure that before you update
  1738. your sources that you have read and understood all the recent
  1739. messages there. If in doubt, please track -stable which has
  1740. much fewer pitfalls.
  1741. [1] If you have third party modules, such as vmware, you
  1742. should disable them at this point so they don't crash your
  1743. system on reboot.
  1744. [3] From the bootblocks, boot -s, and then do
  1745. fsck -p
  1746. mount -u /
  1747. mount -a
  1748. sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
  1749. cd src # full path to source
  1750. adjkerntz -i # if CMOS is wall time
  1751. Also, when doing a major release upgrade, it is required that
  1752. you boot into single user mode to do the installworld.
  1753. [4] Note: This step is non-optional. Failure to do this step
  1754. can result in a significant reduction in the functionality of the
  1755. system. Attempting to do it by hand is not recommended and those
  1756. that pursue this avenue should read this file carefully, as well
  1757. as the archives of freebsd-current and freebsd-hackers mailing lists
  1758. for potential gotchas. The -U option is also useful to consider.
  1759. See mergemaster(8) for more information.
  1760. [5] Usually this step is a no-op. However, from time to time
  1761. you may need to do this if you get unknown user in the following
  1762. step. It never hurts to do it all the time. You may need to
  1763. install a new mergemaster (cd src/usr.sbin/mergemaster && make
  1764. install) after the buildworld before this step if you last updated
  1765. from current before 20130425 or from -stable before 20130430.
  1766. [6] This only deletes old files and directories. Old libraries
  1767. can be deleted by "make delete-old-libs", but you have to make
  1768. sure that no program is using those libraries anymore.
  1769. [8] The new kernel must be able to run existing binaries used by an
  1770. installworld. When upgrading across major versions, the new kernel's
  1771. configuration must include the correct COMPAT_FREEBSD<n> option for
  1772. existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
  1773. to do so may leave you with a system that is hard to boot to recover. A
  1774. GENERIC kernel will include suitable compatibility options to run
  1775. binaries from older branches. Note that the ability to run binaries
  1776. from unsupported branches is not guaranteed.
  1777. Make sure that you merge any new devices from GENERIC since the
  1778. last time you updated your kernel config file. Options also
  1779. change over time, so you may need to adjust your custom kernels
  1780. for these as well.
  1781. [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
  1782. "?=" instead of the "=" assignment operator, so that buildworld can
  1783. override the CPUTYPE if it needs to.
  1784. MAKEOBJDIRPREFIX must be defined in an environment variable, and
  1785. not on the command line, or in /etc/make.conf. buildworld will
  1786. warn if it is improperly defined.
  1787. FORMAT:
  1788. This file contains a list, in reverse chronological order, of major
  1789. breakages in tracking -current. It is not guaranteed to be a complete
  1790. list of such breakages, and only contains entries since September 23, 2011.
  1791. If you need to see UPDATING entries from before that date, you will need
  1792. to fetch an UPDATING file from an older FreeBSD release.
  1793. Copyright information:
  1794. Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
  1795. Redistribution, publication, translation and use, with or without
  1796. modification, in full or in part, in any form or format of this
  1797. document are permitted without further permission from the author.
  1809. Contact Warner Losh if you have any questions about your use of
  1810. this document.
  1811. $FreeBSD$