From owner-svn-src-all@freebsd.org Fri Apr 27 20:20:58 2018 Return-Path: Delivered-To: svn-src-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB2EAFB0FC8; Fri, 27 Apr 2018 20:20:57 +0000 (UTC) (envelope-from emaste@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 902CD743F1; Fri, 27 Apr 2018 20:20:57 +0000 (UTC) (envelope-from emaste@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8AF8F336C; Fri, 27 Apr 2018 20:20:57 +0000 (UTC) (envelope-from emaste@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w3RKKvxJ015346; Fri, 27 Apr 2018 20:20:57 GMT (envelope-from emaste@FreeBSD.org) Received: (from emaste@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w3RKKvNx015345; Fri, 27 Apr 2018 20:20:57 GMT (envelope-from emaste@FreeBSD.org) Message-Id: <201804272020.w3RKKvNx015345@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: emaste set sender to emaste@FreeBSD.org using -f From: Ed Maste Date: Fri, 27 Apr 2018 20:20:57 +0000 (UTC) To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: svn commit: r333072 - head X-SVN-Group: head X-SVN-Commit-Author: emaste X-SVN-Commit-Paths: head X-SVN-Commit-Revision: 333072 X-SVN-Commit-Repository: base MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2018 20:20:58 -0000 Author: emaste Date: Fri Apr 27 20:20:57 2018 New Revision: 333072 URL: https://svnweb.freebsd.org/changeset/base/333072 Log: Retire UPDATING entries prior to the stable/10 branch We do not support building from FreeBSD 9.x releases. Approved by: imp Sponsored by: The FreeBSD Foundation Modified: head/UPDATING Modified: head/UPDATING ============================================================================== --- head/UPDATING Fri Apr 27 19:50:30 2018 (r333071) +++ head/UPDATING Fri Apr 27 20:20:57 2018 (r333072) @@ -1425,512 +1425,6 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW: The stable/10 branch has been created in subversion from head revision r256279. -20131010: - The rc.d/jail script has been updated to support jail(8) - configuration file. The "jail__*" rc.conf(5) variables - for per-jail configuration are automatically converted to - /var/run/jail..conf before the jail(8) utility is invoked. - This is transparently backward compatible. See below about some - incompatibilities and rc.conf(5) manual page for more details. - - These variables are now deprecated in favor of jail(8) configuration - file. One can use "rc.d/jail config " command to generate - a jail(8) configuration file in /var/run/jail..conf without - running the jail(8) utility. The default pathname of the - configuration file is /etc/jail.conf and can be specified by - using $jail_conf or $jail__conf variables. - - Please note that jail_devfs_ruleset accepts an integer at - this moment. Please consider to rewrite the ruleset name - with an integer. - -20130930: - BIND has been removed from the base system. If all you need - is a local resolver, simply enable and start the local_unbound - service instead. Otherwise, several versions of BIND are - available in the ports tree. The dns/bind99 port is one example. - - With this change, nslookup(1) and dig(1) are no longer in the base - system. Users should instead use host(1) and drill(1) which are - in the base system. Alternatively, nslookup and dig can - be obtained by installing the dns/bind-tools port. - -20130916: - With the addition of unbound(8), a new unbound user is now - required during installworld. "mergemaster -p" can be used to - add the user prior to installworld, as documented in the handbook. - -20130911: - OpenSSH is now built with DNSSEC support, and will by default - silently trust signed SSHFP records. This can be controlled with - the VerifyHostKeyDNS client configuration setting. DNSSEC support - can be disabled entirely with the WITHOUT_LDNS option in src.conf. - -20130906: - The GNU Compiler Collection and C++ standard library (libstdc++) - are no longer built by default on platforms where clang is the system - compiler. You can enable them with the WITH_GCC and WITH_GNUCXX - options in src.conf. - -20130905: - The PROCDESC kernel option is now part of the GENERIC kernel - configuration and is required for the rwhod(8) to work. - If you are using custom kernel configuration, you should include - 'options PROCDESC'. - -20130905: - The API and ABI related to the Capsicum framework was modified - in backward incompatible way. The userland libraries and programs - have to be recompiled to work with the new kernel. This includes the - following libraries and programs, but the whole buildworld is - advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl, - kdump, procstat, rwho, rwhod, uniq. - -20130903: - AES-NI intrinsic support has been added to gcc. The AES-NI module - has been updated to use this support. A new gcc is required to build - the aesni module on both i386 and amd64. - -20130821: - The PADLOCK_RNG and RDRAND_RNG kernel options are now devices. - Thus "device padlock_rng" and "device rdrand_rng" should be - used instead of "options PADLOCK_RNG" & "options RDRAND_RNG". - -20130813: - WITH_ICONV has been split into two feature sets. WITH_ICONV now - enables just the iconv* functionality and is now on by default. - WITH_LIBICONV_COMPAT enables the libiconv api and link time - compatibility. Set WITHOUT_ICONV to build the old way. - If you have been using WITH_ICONV before, you will very likely - need to turn on WITH_LIBICONV_COMPAT. - -20130806: - INVARIANTS option now enables DEBUG for code with OpenSolaris and - Illumos origin, including ZFS. If you have INVARIANTS in your - kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG - explicitly. - DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS) - locks if WITNESS option was set. Because that generated a lot of - witness(9) reports and all of them were believed to be false - positives, this is no longer done. New option OPENSOLARIS_WITNESS - can be used to achieve the previous behavior. - -20130806: - Timer values in IPv6 data structures now use time_uptime instead - of time_second. Although this is not a user-visible functional - change, userland utilities which directly use them---ndp(8), - rtadvd(8), and rtsold(8) in the base system---need to be updated - to r253970 or later. - -20130802: - find -delete can now delete the pathnames given as arguments, - instead of only files found below them or if the pathname did - not contain any slashes. Formerly, the following error message - would result: - - find: -delete: : relative path potentially not safe - - Deleting the pathnames given as arguments can be prevented - without error messages using -mindepth 1 or by changing - directory and passing "." as argument to find. This works in the - old as well as the new version of find. - -20130726: - Behavior of devfs rules path matching has been changed. - Pattern is now always matched against fully qualified devfs - path and slash characters must be explicitly matched by - slashes in pattern (FNM_PATHNAME). Rulesets involving devfs - subdirectories must be reviewed. - -20130716: - The default ARM ABI has changed to the ARM EABI. The old ABI is - incompatible with the ARM EABI and all programs and modules will - need to be rebuilt to work with a new kernel. - - To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set. - - NOTE: Support for the old ABI will be removed in the future and - users are advised to upgrade. - -20130709: - pkg_install has been disconnected from the build if you really need it - you should add WITH_PKGTOOLS in your src.conf(5). - -20130709: - Most of network statistics structures were changed to be able - keep 64-bits counters. Thus all tools, that work with networking - statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.) - -20130618: - Fix a bug that allowed a tracing process (e.g. gdb) to write - to a memory-mapped file in the traced process's address space - even if neither the traced process nor the tracing process had - write access to that file. - -20130615: - CVS has been removed from the base system. An exact copy - of the code is available from the devel/cvs port. - -20130613: - Some people report the following error after the switch to bmake: - - make: illegal option -- J - usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable] - ... - *** [buildworld] Error code 2 - - this likely due to an old instance of make in - ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE}) - which src/Makefile will use that blindly, if it exists, so if - you see the above error: - - rm -rf `make -V MAKEPATH` - - should resolve it. - -20130516: - Use bmake by default. - Whereas before one could choose to build with bmake via - -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old - make. The goal is to remove these knobs for 10-RELEASE. - - It is worth noting that bmake (like gmake) treats the command - line as the unit of failure, rather than statements within the - command line. Thus '(cd some/where && dosomething)' is safer - than 'cd some/where; dosomething'. The '()' allows consistent - behavior in parallel build. - -20130429: - Fix a bug that allows NFS clients to issue READDIR on files. - -20130426: - The WITHOUT_IDEA option has been removed because - the IDEA patent expired. - -20130426: - The sysctl which controls TRIM support under ZFS has been renamed - from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been - enabled by default. - -20130425: - The mergemaster command now uses the default MAKEOBJDIRPREFIX - rather than creating it's own in the temporary directory in - order allow access to bootstrapped versions of tools such as - install and mtree. When upgrading from version of FreeBSD where - the install command does not support -l, you will need to - install a new mergemaster command if mergemaster -p is required. - This can be accomplished with the command (cd src/usr.sbin/mergemaster - && make install). - -20130404: - Legacy ATA stack, disabled and replaced by new CAM-based one since - FreeBSD 9.0, completely removed from the sources. Kernel modules - atadisk and atapi*, user-level tools atacontrol and burncd are - removed. Kernel option `options ATA_CAM` is now permanently enabled - and removed. - -20130319: - SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2) - and socketpair(2). Software, in particular Kerberos, may - automatically detect and use these during building. The resulting - binaries will not work on older kernels. - -20130308: - CTL_DISABLE has also been added to the sparc64 GENERIC (for further - information, see the respective 20130304 entry). - -20130304: - Recent commits to callout(9) changed the size of struct callout, - so the KBI is probably heavily disturbed. Also, some functions - in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced - by macros. Every kernel module using it won't load, so rebuild - is requested. - - The ctl device has been re-enabled in GENERIC for i386 and amd64, - but does not initialize by default (because of the new CTL_DISABLE - option) to save memory. To re-enable it, remove the CTL_DISABLE - option from the kernel config file or set kern.cam.ctl.disable=0 - in /boot/loader.conf. - -20130301: - The ctl device has been disabled in GENERIC for i386 and amd64. - This was done due to the extra memory being allocated at system - initialisation time by the ctl driver which was only used if - a CAM target device was created. This makes a FreeBSD system - unusable on 128MB or less of RAM. - -20130208: - A new compression method (lz4) has been merged to -HEAD. Please - refer to zpool-features(7) for more information. - - Please refer to the "ZFS notes" section of this file for information - on upgrading boot ZFS pools. - -20130129: - A BSD-licensed patch(1) variant has been added and is installed - as bsdpatch, being the GNU version the default patch. - To inverse the logic and use the BSD-licensed one as default, - while having the GNU version installed as gnupatch, rebuild - and install world with the WITH_BSD_PATCH knob set. - -20130121: - Due to the use of the new -l option to install(1) during build - and install, you must take care not to directly set the INSTALL - make variable in your /etc/make.conf, /etc/src.conf, or on the - command line. If you wish to use the -C flag for all installs - you may be able to add INSTALL+=-C to /etc/make.conf or - /etc/src.conf. - -20130118: - The install(1) option -M has changed meaning and now takes an - argument that is a file or path to append logs to. In the - unlikely event that -M was the last option on the command line - and the command line contained at least two files and a target - directory the first file will have logs appended to it. The -M - option served little practical purpose in the last decade so its - use is expected to be extremely rare. - -20121223: - After switching to Clang as the default compiler some users of ZFS - on i386 systems started to experience stack overflow kernel panics. - Please consider using 'options KSTACK_PAGES=4' in such configurations. - -20121222: - GEOM_LABEL now mangles label names read from file system metadata. - Mangling affect labels containing spaces, non-printable characters, - '%' or '"'. Device names in /etc/fstab and other places may need to - be updated. - -20121217: - By default, only the 10 most recent kernel dumps will be saved. To - restore the previous behaviour (no limit on the number of kernel dumps - stored in the dump directory) add the following line to /etc/rc.conf: - - savecore_flags="" - -20121201: - With the addition of auditdistd(8), a new auditdistd user is now - required during installworld. "mergemaster -p" can be used to - add the user prior to installworld, as documented in the handbook. - -20121117: - The sin6_scope_id member variable in struct sockaddr_in6 is now - filled by the kernel before passing the structure to the userland via - sysctl or routing socket. This means the KAME-specific embedded scope - id in sin6_addr.s6_addr[2] is always cleared in userland application. - This behavior can be controlled by net.inet6.ip6.deembed_scopeid. - __FreeBSD_version is bumped to 1000025. - -20121105: - On i386 and amd64 systems WITH_CLANG_IS_CC is now the default. - This means that the world and kernel will be compiled with clang - and that clang will be installed as /usr/bin/cc, /usr/bin/c++, - and /usr/bin/cpp. To disable this behavior and revert to building - with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions - of current may need to bootstrap WITHOUT_CLANG first if the clang - build fails (its compatibility window doesn't extend to the 9 stable - branch point). - -20121102: - The IPFIREWALL_FORWARD kernel option has been removed. Its - functionality now turned on by default. - -20121023: - The ZERO_COPY_SOCKET kernel option has been removed and - split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP. - NB: SOCKET_SEND_COW uses the VM page based copy-on-write - mechanism which is not safe and may result in kernel crashes. - NB: The SOCKET_RECV_PFLIP mechanism is useless as no current - driver supports disposeable external page sized mbuf storage. - Proper replacements for both zero-copy mechanisms are under - consideration and will eventually lead to complete removal - of the two kernel options. - -20121023: - The IPv4 network stack has been converted to network byte - order. The following modules need to be recompiled together - with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4), - pf(4), ipfw(4), ng_ipfw(4), stf(4). - -20121022: - Support for non-MPSAFE filesystems was removed from VFS. The - VFS_VERSION was bumped, all filesystem modules shall be - recompiled. - -20121018: - All the non-MPSAFE filesystems have been disconnected from - the build. The full list includes: codafs, hpfs, ntfs, nwfs, - portalfs, smbfs, xfs. - -20121016: - The interface cloning API and ABI has changed. The following - modules need to be recompiled together with kernel: - ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4), - vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4), - faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4). - -20121015: - The sdhci driver was split in two parts: sdhci (generic SD Host - Controller logic) and sdhci_pci (actual hardware driver). - No kernel config modifications are required, but if you - load sdhc as a module you must switch to sdhci_pci instead. - -20121014: - Import the FUSE kernel and userland support into base system. - -20121013: - The GNU sort(1) program has been removed since the BSD-licensed - sort(1) has been the default for quite some time and no serious - problems have been reported. The corresponding WITH_GNU_SORT - knob has also gone. - -20121006: - The pfil(9) API/ABI for AF_INET family has been changed. Packet - filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled - with new kernel. - -20121001: - The net80211(4) ABI has been changed to allow for improved driver - PS-POLL and power-save support. All wireless drivers need to be - recompiled to work with the new kernel. - -20120913: - The random(4) support for the VIA hardware random number - generator (`PADLOCK') is no longer enabled unconditionally. - Add the padlock_rng device in the custom kernel config if - needed. The GENERIC kernels on i386 and amd64 do include the - device, so the change only affects the custom kernel - configurations. - -20120908: - The pf(4) packet filter ABI has been changed. pfctl(8) and - snmp_pf module need to be recompiled to work with new kernel. - -20120828: - A new ZFS feature flag "com.delphix:empty_bpobj" has been merged - to -HEAD. Pools that have empty_bpobj in active state can not be - imported read-write with ZFS implementations that do not support - this feature. For more information read the zpool-features(5) - manual page. - -20120727: - The sparc64 ZFS loader has been changed to no longer try to auto- - detect ZFS providers based on diskN aliases but now requires these - to be explicitly listed in the OFW boot-device environment variable. - -20120712: - The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring - libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are - configuration changes. Make sure to merge /etc/ssl/openssl.cnf. - -20120712: - The following sysctls and tunables have been renamed for consistency - with other variables: - kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered - kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered - -20120628: - The sort utility has been replaced with BSD sort. For now, GNU sort - is also available as "gnusort" or the default can be set back to - GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be - installed as "bsdsort". - -20120611: - A new version of ZFS (pool version 5000) has been merged to -HEAD. - Starting with this version the old system of ZFS pool versioning - is superseded by "feature flags". This concept enables forward - compatibility against certain future changes in functionality of ZFS - pools. The first read-only compatible "feature flag" for ZFS pools - is named "com.delphix:async_destroy". For more information - read the new zpool-features(5) manual page. - Please refer to the "ZFS notes" section of this file for information - on upgrading boot ZFS pools. - -20120417: - The malloc(3) implementation embedded in libc now uses sources imported - as contrib/jemalloc. The most disruptive API change is to - /etc/malloc.conf. If your system has an old-style /etc/malloc.conf, - delete it prior to installworld, and optionally re-create it using the - new format after rebooting. See malloc.conf(5) for details - (specifically the TUNING section and the "opt.*" entries in the MALLCTL - NAMESPACE section). - -20120328: - Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb - is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is - now spelled mips. This is to aid compatibility with third-party - software that expects this naming scheme in uname(3). Little-endian - settings are unchanged. If you are updating a big-endian mips64 machine - from before this change, you may need to set MACHINE_ARCH=mips64 in - your environment before the new build system will recognize your machine. - -20120306: - Disable by default the option VFS_ALLOW_NONMPSAFE for all supported - platforms. - -20120229: - Now unix domain sockets behave "as expected" on nullfs(5). Previously - nullfs(5) did not pass through all behaviours to the underlying layer, - as a result if we bound to a socket on the lower layer we could connect - only to the lower path; if we bound to the upper layer we could connect - only to the upper path. The new behavior is one can connect to both the - lower and the upper paths regardless what layer path one binds to. - -20120211: - The getifaddrs upgrade path broken with 20111215 has been restored. - If you have upgraded in between 20111215 and 20120209 you need to - recompile libc again with your kernel. You still need to recompile - world to be able to configure CARP but this restriction already - comes from 20111215. - -20120114: - The set_rcvar() function has been removed from /etc/rc.subr. All - base and ports rc.d scripts have been updated, so if you have a - port installed with a script in /usr/local/etc/rc.d you can either - hand-edit the rcvar= line, or reinstall the port. - - An easy way to handle the mass-update of /etc/rc.d: - rm /etc/rc.d/* && mergemaster -i - -20120109: - panic(9) now stops other CPUs in the SMP systems, disables interrupts - on the current CPU and prevents other threads from running. - This behavior can be reverted using the kern.stop_scheduler_on_panic - tunable/sysctl. - The new behavior can be incompatible with kern.sync_on_panic. - -20111215: - The carp(4) facility has been changed significantly. Configuration - of the CARP protocol via ifconfig(8) has changed, as well as format - of CARP events submitted to devd(8) has changed. See manual pages - for more information. The arpbalance feature of carp(4) is currently - not supported anymore. - - Size of struct in_aliasreq, struct in6_aliasreq has changed. User - utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8), - need to be recompiled. - -20111122: - The acpi_wmi(4) status device /dev/wmistat has been renamed to - /dev/wmistat0. - -20111108: - The option VFS_ALLOW_NONMPSAFE option has been added in order to - explicitely support non-MPSAFE filesystems. - It is on by default for all supported platform at this present - time. - -20111101: - The broken amd(4) driver has been replaced with esp(4) in the amd64, - i386 and pc98 GENERIC kernel configuration files. - -20110930: - sysinstall has been removed - -20110923: - The stable/9 branch created in subversion. This corresponds to the - RELENG_9 branch in CVS. - COMMON ITEMS: General Notes