summaryrefslogtreecommitdiffstats
path: root/UPDATING
Commit message (Collapse)AuthorAgeFilesLines
* MFC r257138:brooks2013-10-311-0/+7
| | | | | | | | Switch the default mtree to nmtree our new NetBSD derived mtree. Exp-runs by: bdrewery (ports/182438) Sponsored by: DARPA/AFRL Approved by: re (gjb)
* MFC r256450:bdrewery2013-10-231-0/+9
| | | | | | | | Rename libbsdyml to libyaml, make private, and bump SHLIB_MAJOR to 1.0 Approved by: bapt Approved by: re (glebius)
* - Remove debugging from GENERIC* kernel configurationsgjb2013-10-101-16/+1
| | | | | | | | | | - Enable MALLOC_PRODUCTION - Default dumpdev=NO - Remove UPDATING entry regarding debugging features - Bump __FreeBSD_version to 1000500 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
|
* Fix a bug that allowed a tracing process (e.g. gdb) to writedes2013-06-181-0/+6
| | | | | | | | | | 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. Security: CVE-2013-2171 Security: FreeBSD-SA-13:06.mmap Approved by: so
* Remove CVS from the base system.eadler2013-06-151-0/+4
| | | | | | Discussed with: many Reviewed by: peter, zi Approved by: core
* Explain remedy for -J error from old makesjg2013-06-131-0/+17
|
* Mention the switch to bmake by default.sjg2013-05-211-0/+12
| | | | Reviewed by: obrien
* Fix typo in UPDATINGeadler2013-05-121-1/+1
| | | | Submitted by: Rainer Hurling <rhurlin@gwdg.de>
* Add a historic footnote.imp2013-05-011-1/+3
|
* Add some advice to get past the hurdle of install -l for the common, butbrooks2013-04-301-0/+8
| | | | | non-default (and unsupportable) case of setting INSTALL="install -C" in /etc/make.conf or /etc/src.conf.
* Forgot to update UPDATING in head last night.des2013-04-301-0/+3
|
* Remove IDEA from OptionalObsoleteFiles.inceadler2013-04-271-0/+4
| | | | Also add an UPDATING entry (requsted by gjb)
* Changed ZFS TRIM sysctl from vfs.zfs.trim_disable -> vfs.zfs.trim.enabledsmh2013-04-261-0/+5
| | | | | | | | Enabled ZFS TRIM by default Reviewed by: pjd (mentor) Approved by: pjd (mentor) MFC after: 2 weeks
* Use the system MAKEOBJDIRPREFIX when running make targets inbrooks2013-04-251-1/+11
| | | | | | | | | | mergemaster. This allows bootstrap verions of tools to be used. Add a note to UPDATING about this change. Discussed with: jhb Sponsored by: DARPA, AFRL MFC after: 5 days
* Fix typos in my last commit.imp2013-04-211-2/+2
| | | | Submitted by: Niclas Zeising and Benjamin Kaduk
* Add more details about updating across the clang divide.imp2013-04-201-5/+12
| | | | | Add hints about having a root shell around on live updates. Couple of additional nits.
* Add note about fagility of the clang upgrade process.imp2013-04-201-0/+5
|
* Add warning about SOCK_CLOEXEC and SOCK_NONBLOCK (r248534).jilles2013-04-061-0/+6
| | | | Reviewed by: rpaulo
* Document legacy ATA stack removal.mav2013-04-061-0/+7
|
* Merge r247814 from x86 modulo whitespace bug:marius2013-03-081-0/+4
| | | | | | | | Turn on the CTL disable tunable by default. This will allow GENERIC configurations to boot on small memory boxes, but not require end users who want to use CTL to recompile their kernel. They can simply set kern.cam.ctl.disable=0 in loader.conf.
* - Bump __FreeBSD_version after recent callout(9) changes.davide2013-03-041-0/+6
| | | | - Add an entry in UPDATING to notice users about breakages.
* Re-enable CTL in GENERIC on i386 and amd64, but turn on the CTL disableken2013-03-041-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | tunable by default. This will allow GENERIC configurations to boot on small memory boxes, but not require end users who want to use CTL to recompile their kernel. They can simply set kern.cam.ctl.disable=0 in loader.conf. The eventual solution to the memory usage problem is to change the way CTL allocates memory to be more configurable, but this should fix things for small memory situations in the mean time. UPDATING: Explain the change in the CTL configuration, and how users can enable CTL if they would like to use it. sys/conf/options: Add a new option, CTL_DISABLE, that prevents CTL from initializing. ctl.c: If CTL_DISABLE is turned on, don't initialize. i386/conf/GENERIC, amd64/conf/GENERIC: Re-enable device ctl, and add the CTL_DISABLE option.
OpenPOWER on IntegriCloud