BSD Commit Log Search

   Long ago, we took advantage of the "status" property to avoid attaching
   drivers to devices reporting themselves as in failing state.

   However, doing this on Mostek chips with dead batteries would cause no
   clock source to attach, and the kernel would then assume it is running on
   sun4v with the unix-gettod? OFW method being available, causing spurious
   (and puzzling) warnings on console on non-sun4v systems.

   Relax this logic to allow clock(4) to always attach regardless of its state,
   but distrust the clock value on devices reported as failing.

   This allow e.g. Enterprise 4000 systems with dead batteries on all
   motherboards to correctly attach clocks and hold the date on warm reboots,
   without scaring users.

   ok kettenis@ quite some time ago.

   update 8.13.0 -> 8.14.0

   Rename EVAL_RECONF to EVAL_REEVAL since this is a re-evaluation of the RIB
   that is triggered. Also use EVAL_REEVAL in the peer_dump upcall since
   there the re-evaluation also happens but just for a single peer.

   Adjust the peer_generate_update() prototype and drop the newpath and
   old_pathid_tx arguments. Those will no longer be used. Also adjust
   up_generate_addpath_all() which is currently unreachable.

   OK tb@

   Update ttyplot to 1.7.5.

   More prep for 52 disk partitions.

   Remove O_disklabel and O_DIOCGDINFO now that the ABI
   crossover should be complete. Lest these XXX bits take
   root.

   lang/gcc/15: regenerate i386 PLIST

   OK: sthen@

   Make divert-packet / divert(4) properly rdomain aware.

   divert(4) only partially handled rtables / rdomains. While it was used
   outbound, inbound packets did not check the rdomain. This is confusing
   and incorrect.

   Now inbound packets need to match the rdomain of the listening socket
   so one needs to listen on the rdomain the packets come in.
   If packets from multiple rdomains match the rule then userland
   needs to listen on each rdomain. If not the packet will be dropped.

   Report by Y Yang, et al from Tsinghua University
   With and OK bluhm@ OK sashan@ mvs@

   update to tomcat-11.0.23

   update to tomcat-10.1.56

   update to tomcat-9.0.119

   sndiod: Refactor and simplify the hello message handling

   Use proper enums for the resource type (audio device, midithru port,
   etc) in place of magic numbers and factor duplicated code.

   No behavior change.
   CCVS: ----------------------------------------------------------------------

   sndiod: Don't use midi_send() to generate MIDI messages

   midi_in() is the right function to do so. It handles multiple sources
   and does flow control.

   update to py3-dateparser-1.4.1

   net/nchat: prevent pick unrequired php build dependency

   Diff from Nazarenko Mykyta (maintainer), reported by naddy@

   sndiod: Initialize the array of unused opt_app structures

   sc_imlen is allowed to be >= NCR_MAX_MSG_LEN.

   Fixes subtle ncr53c9x_msgin breakage in previous.

   Pointed out by, tweak & ok miod@

   Extend multicast router counter.

   ip_mforward() contained a static variable that poorly implements a
   rate limited log message.  Replace the log with a counter, which
   is MP-safe.
   Also count drops due to time-to-live and hop-limit.  As the default
   ttl is 1, this is the most common pitfall when configuring a multicast
   router.  This counter helps debugging.

   OK claudio@ deraadt@

   Test runs out of file descriptors.  Increase ulimit number to 256.

   bump font-awesome consumers after change to multi-package (PLIST change)

   Avoid printf("%s", NULL) since it's not guaranteed to be safe and will
   segfault on some -portable platforms.

   update to 2026.06.149.4

   Fix FIFO handling to avoid overflowing sc_imess.

   Original diff from Stanislav Fort.

   ok deraadt@ claudio@

   Update to google-cloud-sdk-574.0.0.

   pkg_add: add regression test reproducing the recent gcc15 issue

   from espie

   For IPC_STAT (and KERN_SYSVIPC_SHM_INFO) the three fields
   __shm_atimensec/__shm_dtimensec/_shm_ctimensec fields leak kernel memory
   contents because we never initialize them, they should clearly be zero
   until such time as we add more precision.  The Tsinghua University group
   suggested clearing these at export time, but the real problem is the
   memory is being allocated without PR_ZERO.
   ok kettenis mvs

   Update to R 4.6.1

   Set MODTK_VERSION=9 as suggested by Stuart Cassoff.

   Replace two-value prompt_mode enum with a flag.

   Add some enums for prompt return values to make them a bit less confusing.

   Move our auto-mode-alist tweak to default.el

   This is the Right Way to do it according to the emacs docs. Users can
   then ignore this custom file with emacs -q if it becomes an issue. Also
   using default.el avoids possible patch conflicts when upgrading to newer
   emacs releases.

   Initial version from Timo Myyra, thanks!

   Attach aplmbox(4) early in RAMDISK kernels too.