summaryrefslogtreecommitdiffstats
path: root/UPDATING
Commit message (Collapse)AuthorAgeFilesLines
...
* Switch the default NFS mount mode from UDP to TCP. UDP mounts are akris2008-02-111-0/+6
| | | | | | | | | | historical relic, and are no longer appropriate for either LAN or WAN mounting. At modern (gigabit and 10 gigabit) LAN speeds packet loss from socket buffer fill events is common, and sequence numbers wrap quickly enough that data corruption is possible. TCP solves both of these problems without imposing significant overhead. MFC after: 1 month
* Note m_collapse addition.sam2008-02-081-0/+4
|
* Our fts(3) API, as inherited from 4.4BSD, suffers from integeryar2008-01-261-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fields in FTS and FTSENT structs being too narrow. In addition, the narrow types creep from there into fts.c. As a result, fts(3) consumers, e.g., find(1) or rm(1), can't handle file trees an ordinary user can create, which can have security implications. To fix the historic implementation of fts(3), OpenBSD and NetBSD have already changed <fts.h> in somewhat incompatible ways, so we are free to do so, too. This change is a superset of changes from the other BSDs with a few more improvements. It doesn't touch fts(3) functionality; it just extends integer types used by it to match modern reality and the C standard. Here are its points: o For C object sizes, use size_t unless it's 100% certain that the object will be really small. (Note that fts(3) can construct pathnames _much_ longer than PATH_MAX for its consumers.) o Avoid the short types because on modern platforms using them results in larger and slower code. Change shorts to ints as follows: - For variables than count simple, limited things like states, use plain vanilla `int' as it's the type of choice in C. - For a limited number of bit flags use `unsigned' because signed bit-wise operations are implementation-defined, i.e., unportable, in C. o For things that should be at least 64 bits wide, use long long and not int64_t, as the latter is an optional type. See FTSENT.fts_number aka FTS.fts_bignum. Extending fts_number `to satisfy future needs' is pointless because there is fts_pointer, which can be used to link to arbitrary data from an FTSENT. However, there already are fts(3) consumers that require fts_number, or fts_bignum, have at least 64 bits in it, so we must allow for them. o For the tree depth, use `long'. This is a trade-off between making this field too wide and allowing for 64-bit inode numbers and/or chain-mounted filesystems. On the one hand, `long' is almost enough for 32-bit filesystems on a 32-bit platform (our ino_t is uint32_t now). On the other hand, platforms with a 64-bit (or wider) `long' will be ready for 64-bit inode numbers, as well as for several 32-bit filesystems mounted one under another. Note that fts_level has to be signed because -1 is a magic value for it, FTS_ROOTPARENTLEVEL. o For the `nlinks' local var in fts_build(), use `long'. The logic in fts_build() requires that `nlinks' be signed, but our nlink_t currently is uint16_t. Therefore let's make the signed var wide enough to be able to represent 2^16-1 in pure C99, and even 2^32-1 on a 64-bit platform. Perhaps the logic should be changed just to use nlink_t, but it can be done later w/o breaking fts(3) ABI any more because `nlinks' is just a local var. This commit also inludes supporting stuff for the fts change: o Preserve the old versions of fts(3) functions through libc symbol versioning because the old versions appeared in all our former releases. o Bump __FreeBSD_version just in case. There is a small chance that some ill-written 3-rd party apps may fail to build or work correctly if compiled after this change. o Update the fts(3) manpage accordingly. In particular, remove references to fts_bignum, which was a FreeBSD-specific hack to work around the too narrow types of FTSENT members. Now fts_number is at least 64 bits wide (long long) and fts_bignum is an undocumented alias for fts_number kept around for compatibility reasons. According to Google Code Search, the only big consumers of fts_bignum are in our own source tree, so they can be fixed easily to use fts_number. o Mention the change in src/UPDATING. PR: bin/104458 Approved by: re (quite a while ago) Discussed with: deischen (the symbol versioning part) Reviewed by: -arch (mostly silence); das (generally OK, but we didn't agree on some types used; assuming that no objections on -arch let me to stick to my opinion)
* Support source upgrades from at least 6.0-RELEASE.ru2008-01-231-5/+2
| | | | Reviewed by: imp, obrien
* Quick note on how to disable malloc debugging in the top entry in this file.trhodes2008-01-221-1/+2
| | | | | | PR: 83621 Submitted by: Scott Robbins <scottro@nyc.rr.com> (original version) Reviewed by: imp
* Note change in the supported upgrade path. Prior to this 5.3-releaseimp2008-01-211-0/+8
| | | | | | | | | and newer were supported upgrade paths to -current. After today's commits, 6.0-RELEASE and newer is supported for jumping to current. Make that clear in the UPDATING entry. For the pedants out there, upgrading from FreeBSD_version 600029 and newer should still work. This represents a point from May 29, 2005 forward. The prior date was October 16th 2004.
* Mention ADAPTIVE_GIANT removal.matteo2007-11-281-0/+4
| | | | Reviewed by: attilio@
* Let sunkbd(4) emulate an AT keyboard by default.marius2007-11-181-0/+11
| | | | | | | | | | | | | | This has the following benefits: - allows to use the AT keyboard maps in share/syscons/keymaps with sunkbd(4), - allows to use kbdmux(4) with sunkbd(4), - allows Sun RS232 keyboards to be configured and used the same way as Sun USB keyboards driven by ukbd(4) (which also does AT keyboard emulation) with X.Org, putting an end to the problem of native support for the former in X.Org being broken over and over again. MFC after: 3 days
* Add ABI backwards compatibility to the FreeBSD 4/5/6 versions ofmarius2007-10-241-0/+13
| | | | | | | | | | | | | | the PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was broken with the introduction of PCI domain support. As the size of struct pci_conf_io wasn't changed with that commit, this unfortunately requires the ABI of PCIOCGETCONF to be broken again in order to be able to provide backwards compatibility to the old version of that IOCTL. Requested by: imp Discussed with: re (kensmith) Reviewed by: PCI maintainers (imp, jhb) MFC after: 5 days
* This time to the right branchjulian2007-10-211-0/+8
| | | | note the renaming of the kthread_xxx calls
* Note getfacl(1) changeskevlo2007-10-121-0/+5
| | | | Submitted by: Henrik Brix Andersen <henrik at brixandersen.dk>
* To honor the birth of RELENG_7 bump HEAD to 8.0-CURRENT.kensmith2007-10-111-2/+5
| | | | Approved by: re (implicit)
* Pulled the trigger 2hr 50min late (Pago Pago time).obrien2007-10-091-1/+1
| | | | | Submitted by: ru Approved by: re (implicit)
* Repo copy libpthreads to libkse.obrien2007-10-091-3/+7
| | | | | | This introduces the WITHOUT_LIBKSE nob, and changes WITHOUT_LIBPTHREADS to mean with neither threading libs. Approved by: re(kensmith)
* Make the PCI code aware of PCI domains (aka PCI segments) so we canmarius2007-09-301-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | support machines having multiple independently numbered PCI domains and don't support reenumeration without ambiguity amongst the devices as seen by the OS and represented by PCI location strings. This includes introducing a function pci_find_dbsf(9) which works like pci_find_bsf(9) but additionally takes a domain number argument and limiting pci_find_bsf(9) to only search devices in domain 0 (the only domain in single-domain systems). Bge(4) and ofw_pcibus(4) are changed to use pci_find_dbsf(9) instead of pci_find_bsf(9) in order to no longer report false positives when searching for siblings and dupe devices in the same domain respectively. Along with this change the sole host-PCI bridge driver converted to actually make use of PCI domain support is uninorth(4), the others continue to use domain 0 only for now and need to be converted as appropriate later on. Note that this means that the format of the location strings as used by pciconf(8) has been changed and that consumers of <sys/pciio.h> potentially need to be recompiled. Suggested by: jhb Reviewed by: grehan, jhb, marcel Approved by: re (kensmith), jhb (PCI maintainer hat)
* Finishing renaming of cached into nscd. etc/rc.d and usr.sbin/Makefilebushman2007-09-281-0/+7
| | | | | | updated. Note added to UPDATING. Approved by: re (kensmith, bmah), brooks (mentor)
* Fix typo.yongari2007-07-091-1/+1
| | | | | Reported by: Danny Braniss <danny at cs dot huji dot ac dot il> Approved by: re (bmah)
* Belately note default driver change for NVIDIA network adapters.yongari2007-07-061-0/+5
| | | | | Requested by: Michael Plass < mfp49_freebsd at plass-family dot net> Approved by: re (hrs)
* Document the move from FAST_IPSEC to IPSEC. Point out the need forgnn2007-07-041-0/+5
| | | | | | device crypto in the kernel configuration file when using IPSEC. Approved by: re
* Add a note about the pf update, mark libexec/ftp-proxy as obsolete and bumpmlaier2007-07-031-0/+7
| | | | | | __FreeBSD_version for ports. Approved by: re (implicit)
* Commit IPv6 support for FAST_IPSEC to the tree.gnn2007-07-011-0/+8
| | | | | | | | | This commit includes only the kernel files, the rest of the files will follow in a second commit. Reviewed by: bz Approved by: re Supported by: Secure Computing
* Remove wicontrol(8) from the base system. Using wicontrol to configure anthompsa2007-07-011-0/+5
| | | | | | | interface has been deprecated since 5.1, wi(4) wireless interfaces are managed via the net80211 stack and ifconfig. Approved by: re (rwatson)
* Spaces to tabgshapiro2007-06-121-4/+4
|
* Add a new rc.conf variable, sendmail_rebuild_aliases, which tellsgshapiro2007-06-121-0/+6
| | | | | | | | | | | | | | | /etc/rc.d/sendmail whether or not to run newaliases if the database is missing or the aliases text file is newer than aliases.db. In my opinion, the aliases file should never be automatically rebuilt. The current text form could represent a work in progress. Therefore, in FreeBSD 7.0, this new option will default to "NO". When this rc.d change is MFC'ed, it will need to remain "YES" to maintain backward compatibility. PR: conf/86252 Approved by: re (kensmith) MFC after: 3 days
* Import rewrite of IPv4 socket multicast layer to support source-specificbms2007-06-121-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and protocol-independent host mode multicast. The code is written to accomodate IPv6, IGMPv3 and MLDv2 with only a little additional work. This change only pertains to FreeBSD's use as a multicast end-station and does not concern multicast routing; for an IGMPv3/MLDv2 router implementation, consider the XORP project. The work is based on Wilbert de Graaf's IGMPv3 code drop for FreeBSD 4.6, which is available at: http://www.kloosterhof.com/wilbert/igmpv3.html Summary * IPv4 multicast socket processing is now moved out of ip_output.c into a new module, in_mcast.c. * The in_mcast.c module implements the IPv4 legacy any-source API in terms of the protocol-independent source-specific API. * Source filters are lazy allocated as the common case does not use them. They are part of per inpcb state and are covered by the inpcb lock. * struct ip_mreqn is now supported to allow applications to specify multicast joins by interface index in the legacy IPv4 any-source API. * In UDP, an incoming multicast datagram only requires that the source port matches the 4-tuple if the socket was already bound by source port. An unbound socket SHOULD be able to receive multicasts sent from an ephemeral source port. * The UDP socket multicast filter mode defaults to exclusive, that is, sources present in the per-socket list will be blocked from delivery. * The RFC 3678 userland functions have been added to libc: setsourcefilter, getsourcefilter, setipv4sourcefilter, getipv4sourcefilter. * Definitions for IGMPv3 are merged but not yet used. * struct sockaddr_storage is now referenced from <netinet/in.h>. It is therefore defined there if not already declared in the same way as for the C99 types. * The RFC 1724 hack (specify 0.0.0.0/8 addresses to IP_MULTICAST_IF which are then interpreted as interface indexes) is now deprecated. * A patch for the Rhyolite.com routed in the FreeBSD base system is available in the -net archives. This only affects individuals running RIPv1 or RIPv2 via point-to-point and/or unnumbered interfaces. * Make IPv6 detach path similar to IPv4's in code flow; functionally same. * Bump __FreeBSD_version to 700048; see UPDATING. This work was financially supported by another FreeBSD committer. Obtained from: p4://bms_netdev Submitted by: Wilbert de Graaf (original work) Reviewed by: rwatson (locking), silence from fenner, net@ (but with encouragement)
* note 802.11 changessam2007-06-111-0/+13
|
* Now pam_nologin(8) will provide an account management functionyar2007-06-101-0/+18
| | | | | | | | | | | | | | | | | | | | | | | instead of an authentication function. There are a design reason and a practical reason for that. First, the module belongs in account management because it checks availability of the account and does no authentication. Second, there are existing and potential PAM consumers that skip PAM authentication for good or for bad. E.g., sshd(8) just prefers internal routines for public key auth; OTOH, cron(8) and atrun(8) do implicit authentication when running a job on behalf of its owner, so their inability to use PAM auth is fundamental, but they can benefit from PAM account management. Document this change in the manpage. Modify /etc/pam.d files accordingly, so that pam_nologin.so is listed under the "account" function class. Bump __FreeBSD_version (mostly for ports, as this change should be invisible to C code outside pam_nologin.) PR: bin/112574 Approved by: des, re
* Sync ether_ioctl() with ioctl(2) and ifnet.if_ioctlyar2007-05-291-0/+6
| | | | | | | | | | | as to the type of the command argument: int -> u_long. These types have different widths in the 64-bit world. Add a note to UPDATING because the change breaks KBI on 64-bit platforms. Discussed on: -net, -current Reviewed by: bms, ru
* Revert config(8) version bump. It brings major pain for people working onwkoszek2007-05-161-0/+9
| | | | | | | | | | different versions of FreeBSD source tree. Old config(8) can now be used unless you want to use INCLUDE_CONFIG_FILE option. Approved by: imp Reviewed by: imp
* Add some notes about symbol versioning and the switch to libthr.deischen2007-05-131-0/+13
|
* Add a new note to revoke the 20070408 note. Is is no longer necessarygshapiro2007-04-231-0/+6
| | | | | | to recompile milters. MFC after: 4 days
* Back-out manual procedure for maintaining compatibility with old accountingdds2007-04-191-11/+0
| | | | files. This functionality will be built-into the corresponding tools.
* Notes on the acct(5) format switch.dds2007-04-181-0/+11
|
* Note the renaming of trunk(4) to lagg(4).thompsa2007-04-171-0/+4
|
* Include a note about recompiling ports which use the base libmilter.gshapiro2007-04-141-0/+5
| | | | Submitted by: Matthew Seaman
* Make the tunable names for Intel license agreement more obvious.brueffer2007-04-031-1/+1
|
* Note that the old firmware modules need to be removed.mlaier2007-04-011-1/+2
| | | | | Reported by: Jeremie Le Hen Suggested by: Stefan Ehmann
* - Add missing subdirectories in BSD.usr.dist mtree file.flz2007-03-021-0/+6
| | | | | | | | - Update hier(7) to reflect latest changes in mtree file. - Add UPDATING entry following Intel firmwares inclusion. Submitted by: mlaier MFC after: 1 month
* Bump the bootstrapping requirements for gensnmptree(1) and removeru2007-03-011-13/+0
| | | | | | | a note in UPDATING that tried to work around the build breakage. Tested by: jhb OK'ed by: njl
* Document removal of addr2ascii/ascii2addr and addition of AF_LINKbms2007-02-281-0/+8
| | | | support for getnameinfo.
* - Use a permanent URL to reference piso's mail.simon2007-02-241-1/+2
| | | | - Put URL on seperate line to not get very long lines.
* Reword addition about MROUTING.bms2007-02-241-3/+3
| | | | Submitted by: ru
* Update my previous note about newbus API breakage mentioning thepiso2007-02-241-2/+3
| | | | __FreeBSD_version bump.
* Note newbus API & ABI breakage.piso2007-02-241-0/+5
|
* Note that IPv6 multicast forwarding is now dynamically loadable.bms2007-02-241-0/+6
|
* Note problems I had with bsnmpd while updating from an older -current.njl2007-02-191-0/+13
| | | | | There may be better ways to fix/work around these issues but this worked for me.
* Retire most of the classful network behaviour of netstat -r output, for IPv4.bms2007-02-141-0/+11
| | | | | | | | | | | | | | | | Without -n, we now only print a "network name" without the prefix length under the following conditions: 1) the network address and mask matches a classful network prefix; 2) getnetbyaddr(3) returns a network name for this network address. With -n, we unconditionally print the full unabbreviated CIDR network prefix in the form "a.b.c.d/p". 0.0.0.0/0 is still printed as "default". This change is in preparation for changes such as equal-cost multipath, and to more generally assist operational deployment of FreeBSD as a modern IPv4 router. There are currently no plans to backport this change. Discussed on: freebsd-net
* Build PIM by default as part of the IPv4 multicast forwarding path.bms2007-02-101-0/+7
| | | | | | | | Make PIM dynamically loadable by using encap_attach_func(). PIM may now be loaded into a GENERIC kernel. Tested with: ports/net/pimdd && tcpreplay && wireshark Reviewed by: Pavlin Radoslavov
* Remove support for IPIP tunnels in IPv4 multicast forwarding. XORP hasbms2007-02-071-0/+9
| | | | | | | | | | | | | never used them; with mrouted, their functionality may be replaced by explicitly configuring gif(4) instances and specifying them with the 'phyint' keyword. Bump __FreeBSD_version to 700030, and update UPDATING. A doc update is forthcoming. Discussed on: net Reviewed by: fenner MFC after: 3 months
* Note the second coming of MSI support in the bge driver.jdp2006-12-221-0/+8
|
OpenPOWER on IntegriCloud