IssueNo:https://gitcode.com/openharmony/third_party_FreeBSD/issues/199

Feature or Bugfix: Bugfix ~
Binary Source: No
Signed-off-by: y30015170 <1169998606@qq.com>

Signed-off-by: yang-pangyuan <1169998606@qq.com>

RELNOTES

@@ -10,6 +10,76 @@ newline.  Entries should be separated by a newline.
 
 Changes to this file should not be MFCed.
 
+1ee62f354ab0:
+	ps(1)'s options '-a' and '-A', when combined with any other one
+	affecting the selection of processes except for '-X' and '-x', would
+	have no effect, in contradiction with the rule that one process is
+	listed as soon as any of the specified options selects it (inclusive
+	OR), which is both mandated by POSIX and arguably a natural expectation.
+	This bug has been fixed.
+
+	As a practical consequence, specifying '-a'/'-A' now causes all
+	processes to be listed regardless of other selection options (except for
+	'-X' and '-x', which still apply).  In particular, to list only
+	processes from specific jails, one must not use '-a' with '-J'.  Option
+	'-J', contrary to its apparent initial intent, never worked as a filter
+	in practice (except by accident with '-a' due to the bug), but instead
+	as any other selection options (e.g., '-U', '-p', '-G', etc.) subject to
+	the "inclusive OR" rule.
+
+a2132d91739d:
+	ps(1)'s '-U' option has been changed to select processes by their real
+	user IDs instead of their effective one, in accordance with POSIX and
+	the use case of wanting to list processes launched by some user, which
+	is expected to be more frequent than listing processes having the rights
+	of some user.  This only affects the selection of processes whose real
+	and effective user IDs differ.	After this change, ps(1)'s '-U' flag
+	behaves differently then in other BSDs but identically to that of
+	Linux's procps and illumos.
+
+1e8dc267ca91:
+	ps(1)'s default list of processes now comes from matching its effective
+	user ID instead of its real user ID with the effective user ID of all
+	processes, in accordance with POSIX.  As ps(1) itself is not installed
+	setuid, this only affects processes having different real and effective
+	user IDs that launch ps(1) processes.
+
+4b4bd20e17e0-f9b5d5bf1186, f74cd62b5c71:
+	mac_do(4) is now considered production-ready and its functionality has
+	been considerably extended at the price of breaking credentials
+	transition rules' backwards compatibility.  All that could be specified
+	with old rules can also be with new rules.  Migrating old rules is just
+	a matter of adding "uid=" in front of the target part, substituting
+	commas (",") with semi-colons (";") and colons (":") with greater-than
+	signs (">").  Please consult the mac_do(4) manual page for the new rules
+	grammar.
+
+960ee8094913:
+	hw.snd.maxautovchans has been retired. The commit introduced a
+	hw.snd.vchans_enable sysctl, which along with
+	dev.pcm.X.{play|rec}.vchans, from now on work as tunables to only
+	enable/disable vchans, as opposed to setting their number and/or
+	(de-)allocating vchans. Since these sysctls do not trigger any
+	(de-)allocations anymore, their effect is instantaneous, whereas before
+	we could have frozen the machine (when trying to allocate new vchans)
+	when setting dev.pcm.X.{play|rec}.vchans to a very large value.
+
+ead3cd3ef628:
+	Add a new -a command line option to mountd(8).
+	If this command line option is specified, when
+	a line in exports(5) has the -alldirs export option,
+	the directory must be a server file system mount point.
+
+54974e731f27, 155987e20190, 4634282f8908, 7a3a0402aeb6, 6b1a5d3535d9:
+	The layout of NFS file handles for the tarfs, cd9660, and ext2fs
+	file systems has changed.  An NFS server that exports any of these file
+	systems will need its clients to unmount and remount the exports.
+
+83f1b98d8227:
+	grep(1) no longer follows symbolic links by default for
+	recursive searches.  This matches the documented behavior in
+	the manual page.
+
 c333758fca3e:
 	new MAC/do policy and mdo(1) utility which enables a user to
 	become another user without the requirement of setuid root.

UPDATING

@@ -12,8 +12,43 @@ Items affecting the ports and packages system can be found in
 /usr/ports/UPDATING.  Please read that file before updating system packages
 and/or ports.
 
-20241203:
-	14.2-RELEASE.
+20250610:
+	14.3-RELEASE.
+
+20250419:
+	LinuxKPI alloc routines were changed to return physically contiguous
+	memory where expected. These changes may require out-of-tree drivers
+	to be recompiled.
+	Bump __FreeBSD_version to 1402505 to be able to detect this change.
+
+20250419:
+	Intel iwlwifi firmware has been removed from the src repository.
+	Before updating their system, users of iwlwifi(4) or iwx(4) must
+	install the appropriate firmware for their chipset using fwget(8) or
+	building it from ports.
+
+20250403:
+	Commit 8aedc83c1cc2 ("New setcred() system call and associated MAC
+	hooks") introduces new MAC hooks for the new setcred() system call,
+	modifying the layout and size of 'struct mac_policy_ops'.  As a result,
+	all MAC modules need to be recompiled.
+
+20250228:
+	Commit 9fed5151903f modified the internal API between the
+	nfscommon and nfscl modules.  As such, both of these modules
+	need to be rebuilt from sources.
+	__FreeBSD_version was bumped to 1402504 for this patch.
+
+20250117:
+	The layout of NFS file handles for the tarfs, cd9660, and ext2fs
+	file systems has changed.  An NFS server that exports any of these file
+	systems will need its clients to unmount and remount the exports.
+
+20241222:
+	The ng_ubt(4) driver now requires firmwares to be loaded on Realtek
+	adaptors with rtlbtfw(8) utility. It no longer attaches to devices
+	standing in bootloader mode. Firmware files are available in the
+	comms/rtlbt-firmware port.
 
 20240419:
 	Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have