summaryrefslogtreecommitdiffstats
path: root/UPDATING
Commit message (Collapse)AuthorAgeFilesLines
* 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)
* 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)
OpenPOWER on IntegriCloud