summaryrefslogtreecommitdiffstats
path: root/UPDATING
Commit message (Collapse)AuthorAgeFilesLines
* Rather than require a makeoptions DEBUG to get debug correct,imp2014-03-251-5/+14
| | | | | | | | | | | | | | | | | | | add it in kern.mk, but only if we're using clang. While this option is supported by both clang and gcc, in the future there may be changes to clang which change the defaults that require a tweak to build our kernel such that other tools in our tree will work. Set a good example by forcing -gdwarf-2 only for clang builds, and only if the user hasn't specified another dwarf level already. Update UPDATING to reflect the changed state of affairs. This also keeps us from having to update all the ARM kernels to add this, and also keeps us from in the future having to update all the MIPS kernels and is one less place the user will have to know to do something special for clang and one less thing developers will need to do when moving an architecture to clang. Reviewed by: ian@ MFC after: 1 week
* Add a note to UPDATING about customized kernel configuration files nowdim2014-03-241-1/+10
| | | | | | | requiring -gdwarf-2 for debug info, when using clang 3.4. Suggested by: adrian MFC after: 3 days
* Disable libwrap (TCP wrappers) support in rpcbind by default, introducingmav2014-03-061-0/+5
| | | | | | | | new command line options -W, to enable it when needed. On my tests this change by almost ten times improves rpcbind performance. No objections: many, net@
* Document the fact that OpenSSH default configuration requires Capsicumdelphij2014-03-031-0/+10
| | | | | capability mode support in kernel, which have been worked around later but it's still recommended to have it enabled.
* Add note about dtc switch.imp2014-03-031-0/+7
|
* since -F is safe, and an update from 10-HEAD to 10-STABLE is sooo bloodyjmg2014-02-281-4/+4
| | | | anoying w/o it.. recommend people use -F too...
* Upgrade our copy of llvm/clang to 3.4 release. This version supportsdim2014-02-161-0/+3
| | | | | | | | | | | | | | | | | all of the features in the current working draft of the upcoming C++ standard, provisionally named C++1y. The code generator's performance is greatly increased, and the loop auto-vectorizer is now enabled at -Os and -O2 in addition to -O3. The PowerPC backend has made several major improvements to code generation quality and compile time, and the X86, SPARC, ARM32, Aarch64 and SystemZ backends have all seen major feature work. Release notes for llvm and clang can be found here: <http://llvm.org/releases/3.4/docs/ReleaseNotes.html> <http://llvm.org/releases/3.4/tools/clang/docs/ReleaseNotes.html> MFC after: 1 month
* Add an UPDATING entry about the nve(4) driver removal.brueffer2014-02-161-0/+4
|
* Add a note to UPDATING about the ABI compatibility fix done in r261801.dim2014-02-121-0/+7
|
* Change date again.kaiw2014-01-281-1/+1
|
* Document libelf/libdwarf update in UPDATING.kaiw2014-01-251-0/+7
|
* Allow tests to provide a Kyuafile when they relied on auto-generation.jmmv2014-01-101-0/+8
| | | | | | | | | | | | | | | | | When generating a Kyuafile in the KYUAFILE=auto case, use a filename that is unlikely to clash with the filename used by explicitly-provided Kyuafiles. This allows a Makefile to set KYUAFILE=yes and provide a Kyuafile in the same directory when such Makefile was previously relying on KYUAFILE=auto. Fixes issues with new Kyuafiles not being picked up in NO_CLEAN builds (although manual intervention is required once, unfortunately, as described in UPDATING). Reviewed by: sjg MFC after: 1 week
* document how to install when src is newer than the world.. This allowsjmg2013-12-201-1/+1
| | | | | | people to build -current systems from older systems... Thanks to: Thomas Mueller
* Add an UPDATING entry for the gss_pseudo_random behavior changebjk2013-12-151-0/+11
| | | | Approved by: hrs (mentor, src committer)
* Also mention that drill(1) can be used, now that nslookup and dig are norodrigc2013-11-291-1/+1
| | | | | | longer in the base system. Suggested by: peter
* Add some text to clarify that nslookup and dig are no longer in the base systemrodrigc2013-11-281-1/+6
| | | | after the removal of BIND.
* Revert r258672. We clearly don't compile libraries enough times.peter2013-11-271-7/+0
|
* At great personal risk, change the default for LIB32 from yes to no. Aspeter2013-11-271-0/+7
| | | | | | mentioned in UPDATING, you can even do it as an as-needed operation after doing a buildworld/installworld. You can set WITH_LIB32=yes in make.conf or src.conf.
* Subsume the functionality of MK_ATF into MK_TESTS.jmmv2013-11-081-0/+6
| | | | | | | | | | There is no reason to keep the two knobs separate: if tests are enabled, the ATF libraries are required; and if tests are disabled, the ATF libraries are not necessary. Keeping the two just serves to complicate the build. Reviewed by: freebsd-testing Approved by: rpaulo (mentor)
* Switch the default mtree to nmtree our new NetBSD derived mtree.brooks2013-10-251-0/+7
| | | | | | Exp-run by: bdrewery MFC after: 3 days Sponsored by: DARPA/AFRL
* Rename libbsdyml to libyaml, make private, and bumpbdrewery2013-10-141-0/+9
| | | | | | | | SHLIB_MAJOR to 1.0 Suggested by: des Approved by: bapt MFC after: 1 week
* Turn it all the way up to 11:gjb2013-10-101-2/+2
| | | | | | | | | | | | | - Update FreeBSD version in: - UPDATING - sys/conf/newvers.sh - Add 11.0 FreeBSD version for manual pages - Bump __FreeBSD_version to 1100000 Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
* - Update rc.d/jail to use a jail(8) configuration file instead ofhrs2013-10-101-0/+19
| | | | | | | | | | | | command line options. The "jail_<jname>_*" rc.conf(5) variables for per-jail configuration are automatically converted to /var/run/jail.<jname>.conf before the jail(8) utility is invoked. This is transparently backward compatible. - Fix a minor bug in jail(8) which prevented it from returning false when jail -r failed. Approved by: re (glebius)
* Revert r256095, r256120 (partial), r256121:gjb2013-10-091-4/+0
| | | | | | | | | | | | | | | r256095: - Add gnu/usr.bin/rcs back to the base system. r256120: - Add WITHOUT_RCS back to src.conf.5. r256121: - Remove UPDATING entry regarding gnu/usr.bin/rcs removal. Requested by: many Approved by: re (marius) Discussed with: core
* Remove mention of [fixed] known issue not-specific to updating.dteske2013-10-081-13/+0
| | | | | | | | Vendor update to [c]dialog-1.2-20130925 has fixed known problems. Vendor update SVN revisions: 255917-255917, 255852, and 255958. Reviewed by: gjb Approved by: re (gjb)
* Add an UPDATING entry for the RCS removal.eadler2013-10-071-0/+4
| | | | | Requested by: kargl Approved by: re (glebius)
* Note the removal of BIND, where to find it, and how to usedes2013-09-301-0/+6
| | | | | | local_unbound instead. Approved by: re (gjb)
* - Reword the 20121201 entry.gjb2013-09-171-5/+5
| | | | | | | - Clean up minor whitespace nit. Approved by: re (hrs) Sponsored by: The FreeBSD Foundation
* Document that the 'unbound' user is required for installworld sincegjb2013-09-171-0/+5
| | | | | | | the import of ldns/unbound. Approved by: re (delphij) Sponsored by: The FreeBSD Foundation
* Note about the OpenSSH change.des2013-09-131-0/+6
| | | | Approved by: re (gjb)
* add note about gcc and aesni...jmg2013-09-101-0/+5
| | | | Approved by: re (gjb, kib)
* Add note in UPDATING about the no-gcc-by-default switch.theraven2013-09-071-0/+6
|
* Remove fallback to fork(2) if pdfork(2) is not available. If the parentpjd2013-09-051-0/+6
| | | | | | | | | | | | | | | | process dies, the process descriptor will be closed and pdfork(2)ed child will be killed, which is not the case when regular fork(2) is used. The PROCDESC option is now part of the GENERIC kernel configuration, so we can start depending on it. Add UPDATING entry to inform that this option is now required and log detailed instruction to syslog if pdfork(2) is not available: The pdfork(2) system call is not available; recompile the kernel with options PROCDESC Submitted by: Mariusz Zaborski <oshogbo@FreeBSD.org> Sponsored by: Google Summer of Code 2013
* Advise a full buildworld, because of the recent Capsicum changes.pjd2013-09-051-0/+8
| | | | Sponsored by: The FreeBSD Foundation
* Add note/reminder about dialog(1) regression in HEAD/10.0-C so that we don'tdteske2013-08-271-0/+13
| | | | forget about it in the multi-month run of things to fix prior to 10.0-R.
* The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.obrien2013-08-211-2/+7
| | | | | | | | | Thus "device padlock_rng" and "device rdrand_rng" should be used instead of "options PADLOCK_RNG" & "options RDRAND_RNG". Requested by: so@ (des) Submitted by: obrien, arthurmesh@gmail.com Obtained from: Juniper Networks
* Add a note that if you were WITH_ICONV before, you should turn onpeter2013-08-131-0/+2
| | | | WITH_LIBICONV_COMPAT.
* The iconv in libc did two things - implement the standard APIs, the GNUpeter2013-08-131-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | extensions and also tried to be link time compatible with ports libiconv. This splits that functionality and enables the parts that shouldn't interfere with the port by default. WITH_ICONV (now on by default) - adds iconv.h, iconv_open(3) etc. WITH_LIBICONV_COMPAT (off by default) adds the libiconv_open etc API, linker symbols and even a stub libiconv.so.3 that are good enough to be able to 'pkg delete -f libiconv' on a running system and reasonably expect it to work. I have tortured many machines over the last few days to try and reduce the possibilities of foot-shooting as much as I can. I've successfully recompiled to enable and disable the libiconv_compat modes, ports that use libiconv alongside system iconv etc. If you don't enable the WITH_LIBICONV_COMPAT switch, they don't share symbol space. This is an extension of behavior on other system. iconv(3) is a standard libc interface and libiconv port expects to be able to run alongside it on systems that have it. Bumped osreldate.
* opensolaris code: translate INVARIANTS to DEBUG and ZFS_DEBUGavg2013-08-061-0/+11
| | | | | | | | | | | | | | | | Do this by forcing inclusion of sys/cddl/compat/opensolaris/sys/debug_compat.h via -include option into all source files from OpenSolaris. Note that this -include option must always be after -include opt_global.h. Additionally, remove forced definition of DEBUG for some modules and fix their build without DEBUG. Also, meaning of DEBUG was overloaded to enable WITNESS support for some OpenSolaris (primarily ZFS) locks. Now this overloading is removed and that use of DEBUG is replaced with a new option OPENSOLARIS_WITNESS. MFC after: 17 days
* Document IPv6 timer value change in r253970.hrs2013-08-051-0/+7
|
* find: Allow -delete to delete files given as arguments.jilles2013-08-021-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | Formerly, a command like find dir1/dir2 -delete would delete everything under dir1/dir2 but not dir1/dir2 itself. When -L is not specified and "." can be opened, the fts(3) code underlying find(1) is careful to avoid following symlinks or being dropped in different locations by moving the directory fts is currently traversing. If a problematic concurrent modification is detected, fts will not enter the directory or abort. Files found in the search are returned via the current working directory and a pathname not containing a slash. For paranoia, find(1) verifies this when -delete is used. However, it is too paranoid about the root of the traversal. It is already assumed that the initial pathname does not refer to directories or symlinks that might be replaced by untrusted users; otherwise, the whole traversal would be unsafe. Therefore, it is not necessary to do the check for fts_level == FTS_ROOTLEVEL. 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. Tested by: Kurt Lidl Reviewed by: jhb
* Back out r253779 & r253786.obrien2013-07-311-13/+0
|
* Decouple yarrow from random(4) device.obrien2013-07-291-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Make Yarrow an optional kernel component -- enabled by "YARROW_RNG" option. The files sha2.c, hash.c, randomdev_soft.c and yarrow.c comprise yarrow. * random(4) device doesn't really depend on rijndael-*. Yarrow, however, does. * Add random_adaptors.[ch] which is basically a store of random_adaptor's. random_adaptor is basically an adapter that plugs in to random(4). random_adaptor can only be plugged in to random(4) very early in bootup. Unplugging random_adaptor from random(4) is not supported, and is probably a bad idea anyway, due to potential loss of entropy pools. We currently have 3 random_adaptors: + yarrow + rdrand (ivy.c) + nehemeiah * Remove platform dependent logic from probe.c, and move it into corresponding registration routines of each random_adaptor provider. probe.c doesn't do anything other than picking a specific random_adaptor from a list of registered ones. * If the kernel doesn't have any random_adaptor adapters present then the creation of /dev/random is postponed until next random_adaptor is kldload'ed. * Fix randomdev_soft.c to refer to its own random_adaptor, instead of a system wide one. Submitted by: arthurmesh@gmail.com, obrien Obtained from: Juniper Networks Reviewed by: obrien
* fix UPDATING entry in r253677avg2013-07-261-7/+7
| | | | | MFC after: 3 weeks X-MFC with: r253677
* make path matching in devfs rules consistent and sane (and safer)avg2013-07-261-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | Before this change path matching had the following features: - for device nodes the patterns were matched against full path - in the above case '/' in a path could be matched by a wildcard - for directories and links only the last component was matched So, for example, a pattern like 're*' could match the following entries: - re0 device - responder/u0 device - zvol/recpool directory Although it was possible to work around this behavior (once it was spotted and understood), it was very confusing and contrary to documentation. Now we always match a full path for all types of devfs entries (devices, directories, links) and a '/' has to be matched explicitly. This behavior follows the shell globbing rules. This change is originally developed by Jaakko Heinonen. Many thanks! PR: kern/122838 Submitted by: jh MFC after: 4 weeks
* 2 years, 10 months, 22 days after the projects/arm_eabi branch was createdandrew2013-07-161-0/+10
| | | | | | | | | | | | | | | | | | | | make the ARM EABI the default ABI on arm, armeb, armv6 and armv6eb. This is intended to be the default ABI from now on with the old ABI to be retired. Because of this all users are strongly suggested to upgrade to the ARM EABI. As the two ABIs are incompatible it is unlikely upgrading in place will work. Users should perform a full backup and either use an external machine to upgrade, or install to an alternative location on their media. They should also reinstall all ports or packages when these are available. The only known issues are: - pkg incorrectly detects the ABI. This is fixed upstream, and will a patch will be made to the port. - GDB can have issues with executables built with clang. __FreeBSD_version has been bumped.
* Fix a grammatical error.rpaulo2013-07-141-1/+1
|
* Disable building of pkg_install by defaultbapt2013-07-121-0/+4
| | | | If people still want to have pkg_install they can specify WITH_PKGTOOLS when building world
* Bump __FreeBSD_version to reflect changes in statistics structures.ae2013-07-091-0/+5
|
* Use && rather than ; when success of previous job matters.sjg2013-06-301-0/+8
|
OpenPOWER on IntegriCloud