BSD Commit Log Search

   fix lint build

   npf.conf.5: various grammar, spelling, formatting tweaks

   make: shorten diagnostic for invalid -J option

   In the manual page, there's more space to properly explain the
   complexity behind the warning.

   use uint32_t like the x86 file does.

   Layer 2 filtering man

   Ticket #1962

   Apply patch, requested by mrg in ticket #1962:

        external/gpl3/gdb/dist/sim/ppc/ld-insn.c (apply patch)
        external/gpl3/gdb/dist/sim/ppc/ld-insn.h (apply patch)

   fix -fno-common build breakage for powerpc gdb.

   define op tokens to kill warnings

   s/fieds/fields/ in comment.

   Rump testing for layer 2 filtering in NPF

   reviewed by christos@

   PR bin/59495

   Make umount less noisy when a single -v is used (just say
   what has been unmounted), and only include details of
   running (or not running) external umount_fstype progs
   when more than one -v is given.

   While here, make it more clear in the messages produce
   when the -F (fake it) option is used, that nothing was
   actually unmounted (just what would have been).

   Man page updated to match.

   userland code for layer 2 filtering in NPF

   reviewed by christos@

   kernel code for layer 2 filtering in NPF

   reviewed by christos@

   PR bin/59494

   Cause "mount -v [spec] filesystem" to indicate only what was
   mounted (and where), to obtain all the rest of the data that
   used to be printed, -v must be given twice.

   Implemented differently from the patch given in the PR from
   greywolf, but the same idea.

   While here, avoid the -d option, after indicating what mount
   command would have been run, but wasn't, going on to attempt
   to report statistics on the never mounted filesystem, and
   instead getting those from the intended mount point.

   Update the man page to match.

   doc: libarchive 3.8.1 out

   final (hopefully...) piece of PowerMac7,2 support - deal with multiple
   /u3/i2c/i2c-hwclock instances, figure out which one controls CPU speed, and
   call slew-high on it

   deal with sensor encoding on older G5
   now we have working fan control on PowerMac7,2

   defflag FCU_DEBUG

   correct the descriotion if KAUTH_CRED_COPY

   Noticed by Vasyl Maksym Lanko.
   Bump date.

   keylargo can have up to 4 pwm fans, act like it.
   Also, do a better job finding which fans are actually in use.

   tests/make: detect unintended "expect" lines in the .mk files

   tests/make: require "expect" comments to start a line

   Lua's string.gmatch function doesn't allow the anchor "^"; but its
   string.gsub function does.

   tests/make: force expected lines to be listed in execution order

   The diagnostics from the program to check the "expect" lines in the unit
   test files were hard to follow since the "out-of-order" lines were
   confusing. For out-of-order lines, state where they should be placed
   instead.

   deal with PowerMac7,2 sensor name encoding

   find sensor names etc. on older G5 like PowerMac7,2

   Make getstarttsc() conditional on BOOT_DURATION kernel option.
   Avoids use of rdtsc on i486-class CPUs which do not support it.

   tests/make: sort missing messages using a stable algorithm

   Lua's table.sort does not provide a stable sort.  No idea how this could
   go unnoticed for two years and a few days.

   Noticed in directive-for-escape.mk, which has several diagnostics in the
   same location, in the body of .for loops.

   make: if a condition is erroneous, skip the whole .if/.endif

   make: fix parsing of modifier parts for :gmtime and :localtime

   There's no practical use for escaping the ":" or "}" in these two
   modifiers, but the same scheme may prove useful for the :M and :N
   modifiers, which are currently parsed in a completely different manner,
   thus adding needless complexity.

   Parsing of the :M and :N modifiers is discussed in PR bin/46139.

   tests/make: demonstrate bug in parsing :gmtime and :localtime

   When the parsing of modifiers was unified a bit in May 2024, the :gmtime
   and :localtime modifiers were the only ones that had two different
   delimiters. Of these delimiters, only the second one can be escaped, but
   the intention was that both of them can be escaped.

   Since it doesn't make sense to have either ":" or "}" or ")" in a
   second-based timestamp, this bug has survived more than a year.