summaryrefslogtreecommitdiffstats
path: root/UPDATING
Commit message (Collapse)AuthorAgeFilesLines
* MFC r303103:brooks2016-08-031-5/+6
| | | | | | | Minor wording improvements to the note about pipe(2) removal. Approved by: re (gjb) Sponsored by: DARPA, AFRL
* - Remove debugging from GENERIC* kernel configurationsgjb2016-07-081-15/+0
| | | | | | | | | - Enable MALLOC_PRODUCTION - Default dumpdev=NO - Remove UPDATING entry regarding debugging features Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
* Fix two typos in r302152.brooks2016-06-231-2/+2
| | | | Approved by: re (implicit)
* Add an UPDATING entry for the pipe() -> pipe2() transition.brooks2016-06-231-0/+8
| | | | | Approved by: re (gjb) Sponsored by: DARPA, AFRL
* Fix typo from r300880asomers2016-05-271-1/+1
| | | | | | Reported by: rpokala MFC after: Never Sponsored by: Spectra Logic Corp
* Strip leading spaces off of a SCSI disk's serial numberasomers2016-05-271-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | sys/cam/scsi/scsi_xpt.c Strip leading spaces off of a SCSI disk's reported serial number when populating the CAM serial number. This affects the output of "diskinfo -v" and the names of /dev/diskid/DISK-* device nodes, among other things. SPC5r05 says that the Product Serial Number field from the Unit Serial Number VPD page is right-aligned. So any leading spaces are not part of the actual serial number. Most devices don't left-pad their serial numbers, but some do. In particular, the SN VPD page that an LSI HBA emulates for a SATA drive contains enough left-padding to fill a 20-byte field. UPDATING Add a note to UPDATING, because some users may have to update /etc/fstab or geom labels. Reviewed by: ken, mav MFC after: Never Sponsored by: Spectra Logic Corp Differential Revision: https://reviews.freebsd.org/D6516
* Add bit_count to the bitstring(3) apiasomers2016-05-231-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a bit_count function, which efficiently counts the number of bits set in a bitstring. sys/sys/bitstring.h tests/sys/sys/bitstring_test.c share/man/man3/bitstring.3 Add bit_alloc sys/kern/subr_unit.c Use bit_count instead of a naive counting loop in check_unrhdr, used when INVARIANTS are enabled. The userland test runs about 6x faster in a generic build, or 8.5x faster when built for Nehalem, which has the POPCNT instruction. sys/sys/param.h Bump __FreeBSD_version due to the addition of bit_alloc UPDATING Add a note about the ABI incompatibility of the bitstring(3) changes, as suggested by lidl. Suggested by: gibbs Reviewed by: gibbs, ngie MFC after: 9 days X-MFC-With: 299090, 300538 Relnotes: yes Sponsored by: Spectra Logic Corp Differential Revision: https://reviews.freebsd.org/D6255
* Add a note on how to update a self-hosted armv6hf system to the entryian2016-05-231-0/+4
| | | | describing the armv6hf->armv6 change.
* Remove brk and sbrk from arm64. They were defined in The Single UNIXandrew2016-05-201-0/+6
| | | | | | | | | | | | | | | | | | | | | Specification, Version 2, but marked as legacy, and have been removed from later specifications. After 12 years it is time to remove them from new architectures when the main use for sbrk is an invalid method to attempt to find how much memory has been allocated from malloc. There are a few places in the tree that still call sbrk, however they are not used on arm64. They will need to be fixed to cross build from arm64, but these will be fixed in a follow up commit. Old copies of binutils from ports called into sbrk, however this has been fixed around 6 weeks ago. It is advised to update binutils on arm64 before installing a world that includes this change. Reviewed by: brooks, emaste Obtained from: brooks Relnotes: yes Sponsored by: ABT Systems Ltd Differential Revision: https://reviews.freebsd.org/D6464
* Make armv6 hard float abi by default. Kill armv6hf.imp2016-05-181-0/+8
| | | | | | | Allow CPUTYPE=soft to build the current soft-float abi libraries. Add UPDATING entry to announce this. Approved by: re@ (gjb)
* Change the default installation directory for modules to /boot/modules.jhb2016-05-101-0/+8
| | | | | | | | | | | Kernel installs always override KMODDIR when installing modules, so this default setting is only used for standalone module builds. Many out-of-tree modules manually override KMODDIR already to avoid placing modules in /boot/kernel. This now makes that behavior the default. Discussed on: arch@ Reviewed by: imp Relnotes: yes
* Misc. build: minor spelling fixes.pfg2016-05-031-1/+1
| | | | No functional change.
* Add update.imp2016-04-151-5/+25
|
* Add note about CAM I/O scheduler.imp2016-04-141-0/+7
|
* Remove the old depend (mkdep) code and make FAST_DEPEND the one true way.bdrewery2016-03-301-0/+5
| | | | | | | Reviewed by: emaste, hselasky (partial), brooks (brief) Discussed on: arch@ Sponsored by: EMC / Isilon Storage Division Differential Revision: https://reviews.freebsd.org/D5742
* Use uintmax_t (typedef'd to rman_res_t type) for rman ranges.jhibbits2016-03-181-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On some architectures, u_long isn't large enough for resource definitions. Particularly, powerpc and arm allow 36-bit (or larger) physical addresses, but type `long' is only 32-bit. This extends rman's resources to uintmax_t. With this change, any resource can feasibly be placed anywhere in physical memory (within the constraints of the driver). Why uintmax_t and not something machine dependent, or uint64_t? Though it's possible for uintmax_t to grow, it's highly unlikely it will become 128-bit on 32-bit architectures. 64-bit architectures should have plenty of RAM to absorb the increase on resource sizes if and when this occurs, and the number of resources on memory-constrained systems should be sufficiently small as to not pose a drastic overhead. That being said, uintmax_t was chosen for source clarity. If it's specified as uint64_t, all printf()-like calls would either need casts to uintmax_t, or be littered with PRI*64 macros. Casts to uintmax_t aren't horrible, but it would also bake into the API for resource_list_print_type() either a hidden assumption that entries get cast to uintmax_t for printing, or these calls would need the PRI*64 macros. Since source code is meant to be read more often than written, I chose the clearest path of simply using uintmax_t. Tested on a PowerPC p5020-based board, which places all device resources in 0xfxxxxxxxx, and has 8GB RAM. Regression tested on qemu-system-i386 Regression tested on qemu-system-mips (malta profile) Tested PAE and devinfo on virtualbox (live CD) Special thanks to bz for his testing on ARM. Reviewed By: bz, jhb (previous) Relnotes: Yes Sponsored by: Alex Perez/Inertial Computing Differential Revision: https://reviews.freebsd.org/D4544
* Enable FAST_DEPEND by default.bdrewery2016-03-111-0/+10
| | | | | Discussed on: arch Sponsored by: EMC / Isilon Storage Division
* Add an UPDATING entry about installing the boot loaders after installingdim2016-03-061-0/+14
| | | | the kernel, on amd64.
* Upgrade our copies of clang, llvm, lldb and compiler-rt to 3.8.0dim2016-03-051-0/+5
| | | | | | | | | | | | | | | | release. Please note that from 3.5.0 onwards, clang, llvm and lldb require C++11 support to build; see UPDATING for more information. Release notes for llvm and clang will soon be available here: <http://llvm.org/releases/3.8.0/docs/ReleaseNotes.html> <http://llvm.org/releases/3.8.0/tools/clang/docs/ReleaseNotes.html> Thanks to Ed Maste, Roman Divacky, Davide Italiano and Antoine Brodin for their help. Relnotes: yes
* Add an UPDATING entry for the recent AIO changes.jhb2016-03-041-0/+8
| | | | Suggested by: maxim
* Correct date on ELF Tool Chain UPDATING entryemaste2016-02-271-1/+1
| | | | Reported by: dhw
* Install elftoolchain elfcopy(1) as objcopy(1) by defaultemaste2016-02-261-0/+7
| | | | | | | | | | | | As of r295661 elfcopy supports PE format for EFI boot binaries and is a viable objcopy implementation for the base system and ports. The (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set to obtain the GNU version if necessary. PR: 207091 [exp-run] Relnotes: Yes Sponsored by: The FreeBSD Foundation
* Add a sysctl to allow ZFS pools backed by zvolsasomers2016-01-291-0/+7
| | | | | | | | | | | | Change 294329 removed the ability to build ZFS pools that are backed by zvols, because having that ability (even if it's not used) leads to deadlocks. By popular demand, I'm adding an off-by-default sysctl to reenable that ability. Reviewed by: lidl, delphij MFC after: Never Sponsored by: Spectra Logic Corp Differential Revision: https://reviews.freebsd.org/D4998
* Enable DSA keys by default. They were disabled in OpenSSH 6.9p1.des2016-01-211-4/+0
| | | | Noticed by: glebius
* Note that new ssh(1) doesn't allow to use DSA keys by default.glebius2016-01-211-0/+4
|
* As previously threatened, remove the HPN patch from OpenSSH.des2016-01-191-0/+4
|
* ypldap(8) is a feature ready to be used to translate nis(8) database to ldap(3).araujo2016-01-131-0/+5
| | | | | | | | | | | | | | | This commit, fix a core dump on ypldap(8) related with memory allocation. Also an example of how to set the ypldap.conf(5) properly is added to examples files. A new user _ypldap is required to be able to run ypldap(8) as well as in a chroot mode. Reviewed by: rodrigc (mentor), bjk Approved by: bapt (mentor) Relnotes: Yes Sponsored by: gandi.net Differential Revision: https://reviews.freebsd.org/D4744
* pxeboot: make the tftp loader use the option root-path directivebapt2015-12-161-0/+6
| | | | | | | | | | | | | | | | | | | | pxeboot in tftp loader mode (when built with LOADER_TFTP_SUPPORT) now prefix all the path to open with the path obtained via the option 'root-path' directive. This allows to be able to use the traditional content /boot out of box. Meaning it now works pretty much like all other loaders. It simplifies hosting hosting multiple version of FreeBSD on a tftp server. As a consequence, pxeboot does not look anymore for a pxeboot.4th (which was never provided) Note: that pxeboot in tftp loader mode is not built by default. Reviewed by: rpokala Relnotes: yes Sponsored by: Gandi.net Differential Revision: https://reviews.freebsd.org/D4590
* The new pnp module records causes older kldxref to spew someimp2015-12-131-0/+8
| | | | warnings. Make a note of it to inform people how to get around it.
* Build and install userland .debug files by defaultemaste2015-12-071-0/+7
| | | | | | | | | | | | | Debug data files are now built by default with 'make buildworld' and installed with 'make installworld'. This facilitates debugging but requires more disk space both during the build and for the installed world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes in src.conf(5). Reviewed by: bdrewery, eadler, vangyzen Relnotes: Yes Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D4018
* Fix errors being ignored in many phases of the build since the bmake ↵bdrewery2015-12-011-8/+0
| | | | | | | | | | | | | | | | | | | | | | | | integration. Say it with me, "I will not chain commands with && in Makefiles" This was originally fixed and explained quite well by bde@ in r36074. The initial bmake integration caused 'set -e' to stop being used which lead to r252419. Later 'set -e' expectations were fixed with bmake in r254980. Because of the && here, errors would be ignored when building in parallel and a dependency failed. Such as bootstrap-tools since it builds everything in parallel. If any tool failed in obj/depend/all, it would just ignore the error and continue to build. This later would result in cascaded errors that only confused the real issue. This could also cause commands after the failed command to still execute, leading to more confusion. This should be fine if the command is in a sub-shell such as: (cmd1 && cmd2) This reverts r252419. MFC after: 1 week Sponsored by: EMC / Isilon Storage Division
* Document the __FreeBSD_version bump done for r291527 in UPDATING.rmacklem2015-11-301-0/+5
|
* Recommend only to remove the content of /usr/share/locale/ and not the directorybapt2015-11-181-2/+2
| | | | Add a missing full stop
* Fix two spelling errorseadler2015-11-171-2/+2
|
* Fix typobapt2015-11-171-1/+1
| | | | Submitted by: ngie
* install(1) is following symlinks when installing a files, which result inbapt2015-11-171-0/+5
| | | | | | | inconsistency when installing new locales and may also result in failures when reinstalling after having run make delete-old (due to previous inconsistencies) for now recommand removing all locales until install(1) is fixed
* Add a note about the inpact on databases of the changes in collation supportbapt2015-11-071-0/+3
| | | | Reported by: girgen
* Add an UPDATING entry about the changed of behaviour for listed files due tobapt2015-11-071-0/+5
| | | | now supporting correctly string collation
* Merge OpenSSL 1.0.2d.jkim2015-10-301-0/+4
|
* Document isp_*_multi firmware kernel modules removal at r289626.mav2015-10-201-0/+5
|
* Rework the 'make -n -n' feature such that '-n' recurses and '-N' does not.bdrewery2015-10-171-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | Bmake has a documented feature of '-N' to skip executing commands which is specifically intended for debugging top-level builds and not recursing into sub-directories. This matches the older 'make -n' behavior we added which made '-n -n' the recursing target and '-n' a non-recursing target. Removing the '-n -n' feature allows the build to work as documented in the bmake manpage with '-n' and '-N'. The older '-n -n' feature was also not documented anywhere that I could see. Note that the ${_+_} var is still needed as currently bmake incorrectly executes '+' commands when '-N' is specified. The '-n' and '-n -n' features were broken for several reasons prior to this. r251748 made '_+_' never expand with '-n -n' which resulted in many sub-directories not being visited until fixed 2 years later in r288391, and many targets were given .MAKE over the past few years which resulted in non-sub-make commands, such as rm and ln and mtree, to be executed. This should also allow removing some indirection hacks in bsd.subdir.mk and other cases of .USE that have a .MAKE by using '+'. Sponsored by: EMC / Isilon Storage Division Discussed on: arch@ (mostly silence)
* Fix ZFS ABI compat shims for `zfs receive` after r289362.mav2015-10-171-6/+0
| | | | Difference appeared much less drammatic then seemed originally.
* Bump version and add notice about incompatibility introduced by resumablemav2015-10-161-0/+6
| | | | send/receive support in ZFS.
* Rewrap UPDATING entry from r265422 to 80 columnsemaste2015-10-131-2/+2
|
* If world is built with a custom sendmail.cf, use it for the distributionpeter2015-10-121-0/+10
| | | | | | | | | | | | | target. This is the feeder for mergemaster / etcupdate. This change makes installworld/mergemaster/etcupdate behave the same regardless of whether SENDMAIL_MC or SENDMAIL_CF is used. If you use a custom SENDMAIL_MC/CF in make.conf and excluded it from mergemaster.rc/etcupdate.conf to work around the conflicts, you may wish to revert that or change it from 'ignore' to 'always install'. If you do not use a custom SENDMAIL_MC/CF, there should be no change in behavior.
* Remove compatibility shims for legacy ATA device names.mav2015-10-111-0/+6
| | | | | We got new ATA stack in FreeBSD 8.x, switched to it at 9.x, completely removed old stack at 10.x, so at 11.x it is time to remove compat shims.
* Update dates in UPDATING and ObsoleteFiles.inc.dim2015-10-061-1/+1
|
* Prepare for merging back to head.dim2015-10-051-4/+4
|
* Merge ^/head r288126 through r288196.dim2015-09-241-0/+13
|\
| * Correct UPDATING entry dateemaste2015-09-241-1/+1
| |
OpenPOWER on IntegriCloud