summaryrefslogtreecommitdiffstats
path: root/UPDATING
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Disable the ctl driver in GENERIC.adrian2013-03-021-0/+7
| | | | | | It unfortunately steals a fair chunk of RAM at startup even if it's not actively used, which prevents FreeBSD VMs of 128MB from successfully booting and running.
* Minor wordsmithing.gjb2013-02-281-2/+2
| | | | X-MFC-Needs: r245617
* Add a reminder that the user should update boot block if they are upgradingdelphij2013-02-271-0/+7
| | | | | | | their existing system and use LZ4 compression for ZFS. Suggested by: mm MFC after: 3 days
* - Fix typogabor2013-01-301-1/+1
| | | | Submitted by: jkim
* - Add a BSD-licensed patch, ported by Pedro F. Giffuni (pfg) fromgabor2013-01-291-0/+7
| | | | | | | | DragonflyBSD and install it as bsdpatch. WITH_BSD_PATCH makes it default and installs GNU patch as gnupatch. Submitted by: pfg Obtained from: The DragonflyBSD Project
* Introduce six new options from NetBSD:brooks2013-01-181-0/+9
| | | | | | | | | | | | | | | | | | * -M <metalog> Log metadata in mtree format. * -D <destdir> Log paths relative to <destdir>. * -h <hash> Log digest of type <hash>. * -T <tags> Specify which mtree tags to log. * -l <linkflag> Create hard or symbolic links (allows logging). * -U Install without root privileges (owner, group, mode, and flags can be logged via -M NOTE: In the interest of compatibility with NetBSD and because it is the obvious letter, the nearly useless -M option (disable mmap) has been repurposed. Sponsored by: DARPA, AFRL Obtained from: NetBSD Reviewed by: bz
* UPDATING: add a note about the clang+zfs+i386 stack overflow issueavg2012-12-231-0/+5
|
* Mangle label names containing spaces, non-printable characters '%' orjh2012-12-221-0/+6
| | | | | | | | | '"'. Mangling is only done for label names read from file system metadata. Encoding resembles URL encoding. For example, the space character becomes %20. Help by: kib Discussed with: imp, kib, pjd
* Use new savecore(8) option and limit number of kernel dumps that willpjd2012-12-161-0/+7
| | | | | | | | | be kept around to the 10 most recent ones. Add UPDATING entry with info how to return to the previous behaviour (no limits). Obtained from: WHEEL Systems
* Specifically point at the Handbook instructions for world updates inrwatson2012-12-021-1/+8
| | | | | | | | UPDATING by URL. As there has been some confusion over the need to run "mergemaster -p", part of our standard upgrade procedure, following the recent addition of an "auditdistd" user, add a note about it to UPDATING explicitly.
* Document sin6_scope_id handling change and bump FreeBSD_version to 1000025.hrs2012-11-231-0/+8
|
* Fix a minor error in the clang update note.brooks2012-11-051-1/+1
| | | | Reported by: emaste
* After years of hard work by many FreeBSD and LLVM developers, makebrooks2012-11-051-0/+7
| | | | | | clang the default compiler on i386 and amd64 systems. Special thanks to: dim, ed, rdivacky
* Remove the recently added sysctl variable net.pfil.forward.ae2012-11-021-3/+2
| | | | | | | | | Instead, add protocol specific mbuf flags M_IP_NEXTHOP and M_IP6_NEXTHOP. Use them to indicate that the mbuf's chain contains the PACKET_TAG_IPFORWARD tag. And do a tag lookup only when this flag is set. Suggested by: andre
* Genericise the (out of date) instructions from moving from stable togavin2012-10-311-1/+1
| | | | | | current. MFC after: 3 days
* Note the removal of the IPFIREWALL_FORWARD kernel option.ae2012-10-251-0/+5
|
OpenPOWER on IntegriCloud