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.

2089 lines

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