summaryrefslogtreecommitdiffstats
path: root/UPDATING
Commit message (Collapse)AuthorAgeFilesLines
* Rename the rc.conf(5) knob if_up_delay to defaultroute_delay to bettermtm2009-02-171-0/+6
| | | | reflect its purpose.
* o Trim EOL whitespaces.maxim2009-02-171-2/+2
|
* o Teminate sentences by dot.maxim2009-02-171-2/+2
|
* Add an entry for xorg+hal+USB2 not detecting input devices.thompsa2009-02-161-0/+8
|
* Switch over GENERIC kernels to USB2 by default.thompsa2009-02-151-0/+8
| | | | Tested by: make universe
* Add a note to document that ichsmb(4) now uses left-justified SMBus slavejhb2009-02-061-0/+7
| | | | addresses.
* Remove the single global unlocked route cache ip6_forward_rtbz2009-02-011-0/+4
| | | | | | | | | | | | | | | | | | from the inet6 stack along with statistics and make sure we properly free the rt in all cases. While the current situation is not better performance wise it prevents panics seen more often these days. After more inet6 and ipsec cleanup we should be able to improve the situation again passing the rt to ip6_forward directly. Leave the ip6_forward_rt entry in struct vinet6 but mark it for removal. PR: kern/128247, kern/131038 MFC after: 25 days Committed from: Bugathon #6 Tested by: Denis Ahrens <denis@h3q.com> (different initial version)
* Mention removal of NTFS from GENERIC/amd64.sobomax2009-01-191-0/+8
|
* Add TCP Appropriate Byte Counting (RFC 3465) support to kernel.lstewart2009-01-151-0/+6
| | | | | | | | | | | | | The new behaviour is on by default, and can be disabled by setting the net.inet.tcp.rfc3465 sysctl to 0 to obtain previous behaviour. The patch changes struct tcpcb in sys/netinet/tcp_var.h which breaks the ABI. Bump __FreeBSD_version to 800061 accordingly. User space tools that rely on the size of struct tcpcb (e.g. sockstat) need to be recompiled. Reviewed by: rpaulo, gnn Approved by: gnn, kmacy (mentors) Sponsored by: FreeBSD Foundation
* ng_tty(4) module updated to match the new TTY subsystem.mav2008-12-251-0/+6
|
* correct wordingsam2008-12-191-2/+2
|
* add makefs to the base system; FreeBSD_version bumped just in casesam2008-12-191-0/+5
| | | | Reviewed by: imp
* convert ifnet and afdata locks from mutexes to rwlockskmacy2008-12-171-0/+3
|
* This main goals of this project are:qingli2008-12-151-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. separating L2 tables (ARP, NDP) from the L3 routing tables 2. removing as much locking dependencies among these layers as possible to allow for some parallelism in the search operations 3. simplify the logic in the routing code, The most notable end result is the obsolescent of the route cloning (RTF_CLONING) concept, which translated into code reduction in both IPv4 ARP and IPv6 NDP related modules, and size reduction in struct rtentry{}. The change in design obsoletes the semantics of RTF_CLONING, RTF_WASCLONE and RTF_LLINFO routing flags. The userland applications such as "arp" and "ndp" have been modified to reflect those changes. The output from "netstat -r" shows only the routing entries. Quite a few developers have contributed to this project in the past: Glebius Smirnoff, Luigi Rizzo, Alessandro Cerri, and Andre Oppermann. And most recently: - Kip Macy revised the locking code completely, thus completing the last piece of the puzzle, Kip has also been conducting active functional testing - Sam Leffler has helped me improving/refactoring the code, and provided valuable reviews - Julian Elischer setup the perforce tree for me and has helped me maintaining that branch before the svn conversion
* White space only: Tabify; white space at EOL removed.schweikh2008-12-081-14/+14
|
* correct typosam2008-12-011-1/+1
| | | | Submitted by: Ole Vole
* Switch to ath hal source code. Note this removes the ath_halsam2008-12-011-0/+15
| | | | | | | | | | | | | | | | | module; the ath module now brings in the hal support. Kernel config files are almost backwards compatible; supplying device ath_hal gives you the same chip support that the binary hal did but you must also include options AH_SUPPORT_AR5416 to enable the extended format descriptors used by 11n parts. It is now possible to control the chip support included in a build by specifying exactly which chips are to be supported in the config file; consult ath_hal(4) for information.
* - bump __FreeBSD version to reflect added buf_ring, memory barriers,kmacy2008-11-221-0/+8
| | | | | | | | | | | | | | | | | and ifnet functions - add memory barriers to <machine/atomic.h> - update drivers to only conditionally define their own - add lockless producer / consumer ring buffer - remove ring buffer implementation from cxgb and update its callers - add if_transmit(struct ifnet *ifp, struct mbuf *m) to ifnet to allow drivers to efficiently manage multiple hardware queues (i.e. not serialize all packets through one ifq) - expose if_qflush to allow drivers to flush any driver managed queues This work was supported by Bitgravity Inc. and Chelsio Inc.
* Grammar.delphij2008-11-191-2/+2
| | | | Submitted by: "bf" <bf2006a at yahoo com>
* Mention that listsnapshots is disabled by default after latest ZFS import.delphij2008-11-181-0/+6
|
* Type of q_time (start of queue idle time) has changed: uint32_t -> uint64_t.oleg2008-10-281-0/+3
| | | | | | | | | | | | This should fix q_time overflow, which happens after 2^32/(86400*hz) days of uptime (~50days for hz = 1000). q_time overflow cause following: - traffic shaping may not work in 'fast' mode (not enabled by default). - incorrect average queue length calculation in RED/GRED algorithm. NB: due to ABI change this change is not applicable to stable. PR: kern/128401
* Add an entry about the split up of usb into usb+*hci modules.n_hibma2008-10-101-0/+10
| | | | Submitted by: Andrew Thompson
* Mention the libpmc/hwpmc ABI change introduced in SVN r183725.jkoshy2008-10-101-0/+5
|
* Don't mention lib/compat, it has gone long ago. Use ports/misc/compat*delphij2008-10-081-1/+6
| | | | instead.
* The si(4) and ufoma(4) drivers have been ported to the new TTY layer.ed2008-09-141-2/+2
| | | | | Remove the entries from the UPDATING entry, to cause less confusion among our users.
* Mention ntpd upgrade to 4.2.4p5.roberto2008-09-031-0/+3
|
* Belatedly add a notice about the reversed order of preference for OpenSSHdes2008-09-011-0/+15
| | | | authentication keys.
* Integrate the new MPSAFE TTY layer to the FreeBSD operating system.ed2008-08-201-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The last half year I've been working on a replacement TTY layer for the FreeBSD kernel. The new TTY layer was designed to improve the following: - Improved driver model: The old TTY layer has a driver model that is not abstract enough to make it friendly to use. A good example is the output path, where the device drivers directly access the output buffers. This means that an in-kernel PPP implementation must always convert network buffers into TTY buffers. If a PPP implementation would be built on top of the new TTY layer (still needs a hooks layer, though), it would allow the PPP implementation to directly hand the data to the TTY driver. - Improved hotplugging: With the old TTY layer, it isn't entirely safe to destroy TTY's from the system. This implementation has a two-step destructing design, where the driver first abandons the TTY. After all threads have left the TTY, the TTY layer calls a routine in the driver, which can be used to free resources (unit numbers, etc). The pts(4) driver also implements this feature, which means posix_openpt() will now return PTY's that are created on the fly. - Improved performance: One of the major improvements is the per-TTY mutex, which is expected to improve scalability when compared to the old Giant locking. Another change is the unbuffered copying to userspace, which is both used on TTY device nodes and PTY masters. Upgrading should be quite straightforward. Unlike previous versions, existing kernel configuration files do not need to be changed, except when they reference device drivers that are listed in UPDATING. Obtained from: //depot/projects/mpsafetty/... Approved by: philip (ex-mentor) Discussed: on the lists, at BSDCan, at the DevSummit Sponsored by: Snow B.V., the Netherlands dcons(4) fixed by: kan
* Extend the message in UPDATING on the sio(4) -> uart(4) change.ed2008-08-181-0/+11
| | | | | | | | | It turns out I forgot to mention that people really need to make sure their hints are up to date if they are updating a system through the serial console. Requested by: gavin Reviewed by: gavin
* o Trim whitespaces.maxim2008-07-251-9/+9
|
* o Fix grammar: see -> See.maxim2008-07-251-1/+1
|
* Make uart(4) the default serial port driver on i386 and amd64.ed2008-07-131-0/+11
| | | | | | | | | | | The uart(4) driver has the advantage of supporting a wider variety of hardware on a greater amount of platforms. This driver has already been the standard on platforms such as ia64, powerpc and sparc64. I've decided not to change anything on pc98. I'd rather let people from the pc98 team look at this. Approved by: philip (mentor), marcel
* Fix some spelling errors (improper review from myremko2008-07-071-1/+1
| | | | | | side). Submitted by: ed, danger
* Add missing information for geom_mirror metadata.remko2008-07-071-0/+14
| | | | | | | | PR: 124434 Submitted by: Philip M. Golluci <pgolluci at p6m7g8 dot com> MFC after: 3 days Prodded through: bugbusters@
* Note removal of gpt(8).marcel2008-06-091-0/+4
|
* Fix the date in the last commit.rdivacky2008-06-031-1/+1
| | | | Approved by: kib (mentor)
* Switch to emulating Linux 2.6 on default.rdivacky2008-06-031-0/+6
| | | | Approved by: kib (mentor)
* Remove ISDN4BSD (I4B) from HEAD as it is not MPSAFE andbz2008-05-261-0/+4
| | | | | | | | | | | | | | | | | | parts relied on the now removed NET_NEEDS_GIANT. Most of I4B has been disconnected from the build since July 2007 in HEAD/RELENG_7. This is what was removed: - configuration in /etc/isdn - examples - man pages - kernel configuration - sys/i4b (drivers, layers, include files) - user space tools - i4b support from ppp - further documentation Discussed with: rwatson, re
* Add a note about multiple routing tables supportjulian2008-05-091-0/+7
|
* More recommendationsimp2008-04-291-1/+3
|
* Add a breif example for the wlan change. Include an explicit pointerimp2008-04-271-0/+6
| | | | | | | | to rc.conf(5) to remind people where to look for all the details. People without network connectivity forget basics like this... This is in keeping with historic UPDATING entries which try to provide basic information in the entry, and a pointer to more extensive information documenting the new thing.
* 802.11 support moves to vapssam2008-04-201-0/+10
|
* - Add write(2) support for psm(4) in native operation level. Now arbitraryjkim2008-04-081-0/+7
| | | | | | | commands can be written to /dev/psm%d and status can be read back from it. - Reflect the change in psm(4) and bump version for ports. MFC after: 1 week
* - Add an UPDATING entry about the removal of KSE.jeff2008-03-121-0/+10
|
* Make the vm_pmap field of struct vmspace the last field in themarcel2008-03-011-0/+8
| | | | | | | structure. This allows per-CPU variations of struct pmap on a single architecture without affecting the machine-independent fields. As such, the PMAP variations don't affect the ABI. They become part of it.
* Detail the em/igb split so no one gets confused.jfv2008-02-291-0/+6
|
* Rename geom_lvm(4) to geom_linux_lvm(4).thompsa2008-02-201-0/+4
| | | | Requested by: des, phk
* 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)
OpenPOWER on IntegriCloud