aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
Commit message (Collapse)AuthorAgeFilesLines
...
* Retire WITHOUT_CXX optionEd Maste2023-01-271-0/+4
| | | | | | | | | | | | Several important base system components are written in C++, and the WITHOUT_CXX option produced a system that was not fully functional. Just accept this, and remove the option to build without C++ support. This reverts commit adc3c128c6603054586a993d117e5dd808deac17. Reviewed by: brooks, kevans, jhb (earlier) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D33108
* UPDATING: fix typoWarner Losh2023-01-241-1/+1
| | | | | | | I'd forgotten to fix this from the review, and a couple of people have pointed it out after the commit. Sponsored by: Netflix
* UPDATING: Remove old entriesWarner Losh2023-01-201-850/+4
| | | | | | | | | | | | | Belatedly remove the entries older than the stable/11 branch point after stable/13 was created. This should be done shortly after the branch, not well after the branch point. Document this policy in UPDATING, though other checklists should likely be updated as well. Sponsored by: Netflix Reviewed by: emaste Differential Revision: https://reviews.freebsd.org/D37514
* UPDATING: update notes on EFI bootingWarner Losh2023-01-201-9/+37
| | | | | | | | | | The notes on EFI booting and updating for ZFS had become dated and only partially updated. Expand the notes with a few more details and a pointer to laoder.efi(8) and uefi(8). Sponsored by: Netflix Discussed with: pauamma, karels Differential Revision: https://reviews.freebsd.org/D36629
* LinuxKPI: implement irq_get_msi_desc()Bjoern A. Zeeb2023-01-131-0/+4
| | | | | | | | | | | | | | | | | | Add irq_get_msi_desc() as a wrapper around a PCI function which will allocate a single cached value (see comment on struct) for the msi_desc requested if it doesn't exist yet and handle freeing it when the PCI device goes away. We take the values from the ivars of the native (FreeBSD) device. While changing struct pci_dev also add the msi_cap field requested by a wireless driver. Bump __FreeBSD_version so these changes can be detected. MFC after: 3 days X-MFC: move fields to end of struct (alloc happens in linux_pci.c) Reviewed by: hselasky (earlier version) Differential Revision: https://reviews.freebsd.org/D37523
* Always install llvm-objdump as objdumpEd Maste2022-12-121-0/+8
| | | | | | | | | | Instead of providing no /usr/bin/objdump when LLVM_BINUTILS is false. PR: 267854 [exp-run] Reviewed by: dim MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D37445
* Revert "newbus: Change attach failure behavior"Warner Losh2022-12-061-0/+2
| | | | | | | | | This reverts commit 68c3f0302106643207dcdfe3b414810e245228e5. There are some weird crashes when KVMs switch caused by this, so revert this commit until they are sorted out. Reported by: cy@ Sponsored by: Netflix
* UPDATING: add notes on how to reenable sendmailBaptiste Daroussin2022-12-051-0/+8
|
* UPDATING: Fix typoWarner Losh2022-12-051-1/+1
| | | | | Noticed by: Gary Jennejohn Sponsored by: Netflix
* newbus: Change attach failure behaviorWarner Losh2022-12-041-0/+8
| | | | | | | | | | | | | | | In the rare case that we succeed in probing, but fail to attach, flip the default to be to disable the device. hw.bus.disable_failed_devices=false is no required to restore the old behavior. The old behavior dates form a time when dynamic control of devices wasn't yet present (devctl didn't exist). Now that one can retry probe/attach the device with devctl, the default doesn't make sense: The more desirable behaivor is to have stable device numbers when one has several instances of the same device in a system (common for NICs or HBAs). Reviewed by: jhb (verbal) Sponsored by: Netflix
* pf: drop support for fragment crop|drop-ovlKristof Provost2022-11-281-0/+5
| | | | | | | | | | | We removed the code for these modes back in 2015, but converted such configurations to 'scrub fragment reassemble'. It's been long enough, drop the backwards compatibility glue too. Reviewed by: mjg MFC after: never Sponsored by: Rubicon Communications, LLC ("Netgate") Differential Revision: https://reviews.freebsd.org/D37460
* Revert "Remove UPDATING entries from old branches."Alexander Leidinger2022-11-271-0/+2175
| | | | | | | | This reverts commit ff0c7816db696d31adc437134dcad45a70ad5889 as more history than just from branch N-1 to N is requested/needed by some downstram consumers. Requested by: imp
* Remove UPDATING entries from old branches.Alexander Leidinger2022-11-251-2175/+0
| | | | | | We only support updates from major version N to N+1: stable/13 was branched on 20210122, remove all old entries from stable/10 branch point in 2013 to 20210122.
* Retire CLANG_IS_CC optionEd Maste2022-11-211-0/+4
| | | | | | | | | | | | A small reduction in build infrastructure complexity; when we had both Clang and GCC in the tree it was useful to have both built, and choose one or the other to install as /usr/bin/cc. Now only Clang is in the tree, and there is no point in building and installing base Clang but not providing it as cc (and c++, cpp). Reviewed by: imp Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D37075
* UPDATING: correct spearate typoEd Maste2022-10-261-1/+1
| | | | | Reported by: manu Fixes: 9c36300582ec ("UPDATING: add an introductory...")
* UPDATING: add an introductory sentence to 20221026's entryEd Maste2022-10-261-4/+8
|
* UPDATING: Add note for pkgbase users after splitting packages.Emmanuel Vadot2022-10-261-0/+6
|
* LinuxKPI: move pm_message_t from kernel.h to pm.hBjoern A. Zeeb2022-06-101-0/+4
| | | | | | | | | | | | | | | | | | Move pm_message_t from kernel.h to pm.h and remove a private define in usb.h as well as adjust the implementation in linux_usb.c. This cleans up what I believe to be a historic shortcut and is needed for future wireless driver updates. Leave a note in UPDATING that drm-kmod users need to update to the latest version before re-compiling a new kernel to avoid errors (see PR). Sponsored by: The FreeBSD Foundation MFC after: 3 days PR: 264449 (drm-kmod port update, thanks wulf) Obtained from: bz_git_iwlwifi (Dec 2020) (partly) Reviewed by: hselasky, imp Differential Revision: https://reviews.freebsd.org/D35276
* UPDATING: Fix a few typosGordon Bergling2022-04-101-3/+4
| | | | | | | | - s/configuation/configuration/ - s/comitted/committed/ - s/verison/version/ MFC after: 3 days
* UPDATING: Remove a double word in an entryGordon Bergling2022-04-091-1/+1
| | | | | | - s/for for/for/ MFC after: 3 days
* Fix minor grammar nit.Gordon Tetlow2022-01-311-2/+2
|
* UPDATING: Sort by dateCy Schubert2022-01-241-13/+13
| | | | | | I still didn't sort it right. Pointy hat to: cy
* UPDATING: Sort by dateCy Schubert2022-01-241-11/+11
| | | | Sort unbound entry by date.
* UPDATING: Document unbound support of RFC8375Cy Schubert2022-01-241-0/+15
| | | | | | | | | As of unbound 1.14.0rc1, as per RFC8375 unbound by default blocks 'home.arpa'. Document this new behaviour and how to unblock it. Reported by: avg Discussed with: glebius, avg RFC: 8375, Section 6: Security Considerations
* Make CPU_SET macros compliant with other implementationsStefan Eßer2021-12-301-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The introduction of <sched.h> improved compatibility with some 3rd party software, but caused the configure scripts of some ports to assume that they were run in a GLIBC compatible environment. Parts of sched.h were made conditional on -D_WITH_CPU_SET_T being added to ports, but there still were compatibility issues due to invalid assumptions made in autoconfigure scripts. The differences between the FreeBSD version of macros like CPU_AND, CPU_OR, etc. and the GLIBC versions was in the number of arguments: FreeBSD used a 2-address scheme (one source argument is also used as the destination of the operation), while GLIBC uses a 3-adderess scheme (2 source operands and a separately passed destination). The GLIBC scheme provides a super-set of the functionality of the FreeBSD macros, since it does not prevent passing the same variable as source and destination arguments. In code that wanted to preserve both source arguments, the FreeBSD macros required a temporary copy of one of the source arguments. This patch set allows to unconditionally provide functions and macros expected by 3rd party software written for GLIBC based systems, but breaks builds of externally maintained sources that use any of the following macros: CPU_AND, CPU_ANDNOT, CPU_OR, CPU_XOR. One contributed driver (contrib/ofed/libmlx5) has been patched to support both the old and the new CPU_OR signatures. If this commit is merged to -STABLE, the version test will have to be extended to cover more ranges. Ports that have added -D_WITH_CPU_SET_T to build on -CURRENT do no longer require that option. The FreeBSD version has been bumped to 1400046 to reflect this incompatible change. Reviewed by: kib MFC after: 2 weeks Relnotes: yes Differential Revision: https://reviews.freebsd.org/D33451
* Test various header files to ensure they can be included by themselves.Warner Losh2021-12-151-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | A number of header files in sys/* have, going back to 7th Edition Unix in 1979, reqiured other files (like sys/types.h) to compile. Likewise the 4BSD networking code has had prerequisites. However, going back to around the turn of the 21st century, other systems have made them be independently include-able (wide-spread header include protection post-dates 7th edition Unix by maybe 3 or so years judging from USENET source postings). Start down the path of making them all independently include-able by creating this test that fails buildworld when they are not. The file 'badfiles.inc' contains a list of the currently broken files that cannot be included w/o any prerequisites. As files are fixed, 'make badfiles.inc' should be re-run to remove them from the list. Note: All files that start with an underscore are considered internal and not tested. Please note: once a file is removed from badfiles.inc, it must pass on all architectures. Buildworld through at least the _includes target is needed to ensure its working (though a buildkernel should also be done on all architectures as well). Sponsored by: Netflix Reviewed by: brooks, markj Differential Revision: https://reviews.freebsd.org/D32498
* UPDATING: Add warning about NO_CLEAN build after turning off llvm mips targetWarner Losh2021-12-151-0/+8
| | | | | | | | | | | | Due to the way that we configure llvm, there's a problem with NO_CLEAN builds. The *.def files listed in the commit change their behavior based on command line arguments. Since my flipping the default of the mips target, this meant there were .o files that were now inconsistent with how we'll now compile things, leading to errors. By touching the *.def files list, one can workaround this problem. Noticed by: jhb Sponsored by: Netflix
* mips: Remove mips as a recognized build target.Warner Losh2021-12-091-0/+5
| | | | | | | Remove mips as a recognized build target in advance of its removal from the tree. Sponsored by: Netflix
* Belatedly note that mips has been removed from universe/tinderbox buildsWarner Losh2021-12-091-0/+4
| | | | | | and that mips will be removed from the tree soon. Sponsored by: Netflix
* Add in the commit revision to the UPDATING file for the CC changesRandall Stewart2021-11-111-1/+1
| | | | | The UPDATING file had a xxx for the CC changes commit, now that its committed fix that.
* tcp: Congestion control cleanup.Randall Stewart2021-11-111-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | NOTE: HEADS UP read the note below if your kernel config is not including GENERIC!! This patch does a bit of cleanup on TCP congestion control modules. There were some rather interesting surprises that one could get i.e. where you use a socket option to change from one CC (say cc_cubic) to another CC (say cc_vegas) and you could in theory get a memory failure and end up on cc_newreno. This is not what one would expect. The new code fixes this by requiring a cc_data_sz() function so we can malloc with M_WAITOK and pass in to the init function preallocated memory. The CC init is expected in this case *not* to fail but if it does and a module does break the "no fail with memory given" contract we do fall back to the CC that was in place at the time. This also fixes up a set of common newreno utilities that can be shared amongst other CC modules instead of the other CC modules reaching into newreno and executing what they think is a "common and understood" function. Lets put these functions in cc.c and that way we have a common place that is easily findable by future developers or bug fixers. This also allows newreno to evolve and grow support for its features i.e. ABE and HYSTART++ without having to dance through hoops for other CC modules, instead both newreno and the other modules just call into the common functions if they desire that behavior or roll there own if that makes more sense. Note: This commit changes the kernel configuration!! If you are not using GENERIC in some form you must add a CC module option (one of CC_NEWRENO, CC_VEGAS, CC_CUBIC, CC_CDG, CC_CHD, CC_DCTCP, CC_HTCP, CC_HD). You can have more than one defined as well if you desire. Note that if you create a kernel configuration that does not define a congestion control module and includes INET or INET6 the kernel compile will break. Also you need to define a default, generic adds 'options CC_DEFAULT=\"newreno\" but you can specify any string that represents the name of the CC module (same names that show up in the CC module list under net.inet.tcp.cc). If you fail to add the options CC_DEFAULT in your kernel configuration the kernel build will also break. Reviewed by: Michael Tuexen Sponsored by: Netflix Inc. RELNOTES:YES Differential Revision: https://reviews.freebsd.org/D32693
* UPDATING: Change update procedure to use etcupdate(8) over mergemaster(8)Dries Michiels2021-11-101-10/+6
| | | | | | | | | | | This commit aligns the steps in UPDATING with the steps from the handbook which already prefers etcupdate(8). While here also remove a dubious comment. PR: 252417 Reviewed by: ceri Approved by: philip (mentor), imp Differential Revision: https://reviews.freebsd.org/D28062
* UPDATING: Add entry for commit f0c9847a6c47Rick Macklem2021-11-061-0/+6
|
* Retire synchronous PPP kernel driver sppp(4).Gleb Smirnoff2021-10-221-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The last two drivers that required sppp are cp(4) and ce(4). These devices are still produced and can be purchased at Cronyx <http://cronyx.ru/hardware/wan.html>. Since Roman Kurakin <rik@FreeBSD.org> has quit them, they no longer support FreeBSD officially. Later they have dropped support for Linux drivers to. As of mid-2020 they don't even have a developer to maintain their Windows driver. However, their support verbally told me that they could provide aid to a FreeBSD developer with documentaion in case if there appears a new customer for their devices. These drivers have a feature to not use sppp(4) and create an interface, but instead expose the device as netgraph(4) node. Then, you can attach ng_ppp(4) with help of ports/net/mpd5 on top of the node and get your synchronous PPP. Alternatively you can attach ng_frame_relay(4) or ng_cisco(4) for HDLC. Actually, last time I used cp(4) back in 2004, using netgraph(4) instead of sppp(4) was already the right way to do. Thus, remove the sppp(4) related part of the drivers and enable by default the negraph(4) part. Further maintenance of these drivers in the tree shouldn't be a big deal. While doing that, remove some cruft and enable cp(4) compilation on amd64. The ce(4) for some unknown reason marks its internal DDK functions with __attribute__ fastcall, which most likely is safe to remove, but without hardware I'm not going to do that, so ce(4) remains i386-only. Reviewed by: emaste, imp, donner Differential Revision: https://reviews.freebsd.org/D32590 See also: https://reviews.freebsd.org/D23928
* UPDATING: fix styleBaptiste Daroussin2021-10-201-2/+2
| | | | Reported by: danfe
* sh(1): make it the default shell for the root userBaptiste Daroussin2021-10-201-0/+6
| | | | | | | | | | | | | | | In the recent history sh(1) has gain the missing features for it to become a usable interractive shell: - command completion - persistent history support - improvements on the default bindings in emacs mode - improvements in the vi mode (repect $EDITOR) - print a newline when exiting via ^D - default prompt and improvements on how PS1 can be configured - and more. This changes also simplifies making tiny freebsd images with only sh(1) as a shell
* ncurses: document in UPDATING and bump _FreeBSD_versionBaptiste Daroussin2021-10-041-0/+6
|
* UPDATING: Update notes about new mixer(8) utility.Hans Petter Selasky2021-10-041-1/+2
| | | | | Differential Revision: https://reviews.freebsd.org/D31636 Sponsored by: NVIDIA Networking
* UPDATING: new entry about dummynetKristof Provost2021-09-241-1/+7
| | | | | | | | | Dummynet now no longer requires ipfw, so any users relying on this dependency to load ipfw will need to explicitly load ipfw. While here fix a typo in the date of the previous entry. Sponsored by: Rubicon Communications, LLC ("Netgate")
* UPDATING: Fix spelling.Hans Petter Selasky2021-09-231-1/+1
| | | | | | Submitted by: gljennjohn@gmail.com Differential Revision: https://reviews.freebsd.org/D31636 Sponsored by: NVIDIA Networking
* UPDATING: Add new entry about mixer(8) usage.Hans Petter Selasky2021-09-221-0/+5
| | | | | Differential Revision: https://reviews.freebsd.org/D31636 Sponsored by: NVIDIA Networking
* UPDATING: Add entry for commit 55089ef4f8bbRick Macklem2021-09-111-0/+6
|
* UPDATING: Add a note about OpenSSL defaulting KTLS to off.John Baldwin2021-08-171-0/+8
| | | | | | Sponsored by: Netflix MFC after: 5 days Differential Revision: https://reviews.freebsd.org/D31444
* UPDATING: Add an entry for commit 3ad1e1c1ce20Rick Macklem2021-08-121-0/+4
|
* UPDATING: fix incorrect hashKristof Provost2021-07-301-1/+1
| | | | Pointed out by: lwhsu
* UPDATING: Document the removal of DIOCGETSTATESNVKristof Provost2021-07-301-0/+6
| | | | | MFC after: 1 week Sponsored by: Rubicon Communications, LLC ("Netgate")
* UPDATING: document if_bridge MTU changesKristof Provost2021-07-291-0/+5
| | | | Sponsored by: Rubicon Communications, LLC ("Netgate")
* UPDATING: Add entry for commit ee29e6f31111Rick Macklem2021-07-161-0/+5
|
* UPDATING: Not unusual side effect of the awk bug fixed in d4d252c49976Warner Losh2021-07-161-0/+12
| | | | | | | | | You might not be able to build the kernel if you have an awk between Jul 7th and today. It does not affect all platforms due to the nature of the bug (so amd64 is unaffected in stable/13 or current, but is affected in stable/12. i386 seems to be affected everywhere). Sponsored by: Netflix
* UPDATING: fix typoWarner Losh2021-07-091-1/+1
| | | | | | | | The correct version is 20210215, not 20120215 :( Reported by: Yasuhiro Kimura Fixes: 3f7b23177f1d Sponsored by: Netflix
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-21 19:24:54 +0000