du: Set BLOCKSIZE before running tests
Several testcases assume BLOCKSIZE=K, so set it at the top of the
script. This fixes an issue where the tests would sometimes fail
when run under sudo.
MFC after: 1 week
Sponsored by: Klara, Inc.
Reviewed by: kevans
Differential Revision: https://reviews.freebsd.org/D56476
(cherry picked from commit d618ba314d1452c1cb4360e15ae1c80adac48306)
du: Set BLOCKSIZE before running tests
Several testcases assume BLOCKSIZE=K, so set it at the top of the
script. This fixes an issue where the tests would sometimes fail
when run under sudo.
MFC after: 1 week
Sponsored by: Klara, Inc.
Reviewed by: kevans
Differential Revision: https://reviews.freebsd.org/D56476
(cherry picked from commit d618ba314d1452c1cb4360e15ae1c80adac48306)
du: Set BLOCKSIZE before running tests
Several testcases assume BLOCKSIZE=K, so set it at the top of the
script. This fixes an issue where the tests would sometimes fail
when run under sudo.
MFC after: 1 week
Sponsored by: Klara, Inc.
Reviewed by: kevans
Differential Revision: https://reviews.freebsd.org/D56476
(cherry picked from commit d618ba314d1452c1cb4360e15ae1c80adac48306)
du: Complete libxo transition
* Use xo_warn() / xo_err() instead of warn() / err().
* Add a test case for the POSIX-mandated stdout error check.
* While here, don't assume the size of off_t, address some style issues,
and broaden the use of bool instead of int.
* Reorder SEE ALSO section.
MFC after: 1 week
Sponsored by: Klara, Inc.
Reviewed by: allanjude
Differential Revision: https://reviews.freebsd.org/D56402
(cherry picked from commit 6c18dd3eb42b50fddb6d9605ddde1362ae9c504a)
printenv: Clean up
* Error out if more than one argument is given.
* Check for stdio errors.
* Clean up the code.
* Clean up and expand the tests.
MFC after: 1 week
Reviewed by: ngie
Differential Revision: https://reviews.freebsd.org/D56506
ident: Clean up
* Use libcasper instead of reinventing it.
* Add long option support.
* Drop pointless use of temporary locales.
* Consistently check for stdio errors.
* Clean up the code.
* Clean up and expand the tests.
MFC after: 1 week
Reviewed by: ngie
Differential Revision: https://reviews.freebsd.org/D56505
tests.7: Provide better examples
Previous authors appear to have prioritized brevity over clarity. This
unfortunately resulted in a manual page that left its reader with the
false impression that Kyua is difficult to use. Attempt to correct
this by providing more and simpler examples with longer explanations.
While here, correct outdated information about where Kyua stores its
logs and results.
MFC after: 1 week
Reviewed by: ziaee, ngie
Differential Revision: https://reviews.freebsd.org/D56475
dpaa2: Extract checksum statuses on ingress
In order to enable RX checksum offloading we need to check the
meta-information for the (good) frames to see if the L3/4 checksums
were calculated and if there was an error.
The way the buffere are setup, the needed frame meta-information is
already requested. All we have to do is make sure it is really part
of the RX frame, that it is valid, and if the respective bits are set.
Also do not forget to set the (dummy) csum_data as otherwise upper
layers will just be cranky. An artefact of the past which likely
should disappear.
PR: 292006
Reviewed by: bz, tuexen
Tested by: bz, tuexen
Approved by: tuexen
Obtained from: bz (initial version, D55320)
[5 lines not shown]
dpaa2: Extract frame-specific routines to dpaa2_frame.[h,c]
As soon as we need information from the hardware frame annotation to
make sure that checksums of the ingress frames were verified by the
DPAA2 HW, I've decided to make a preparation and extracted all of the
frame related routines into the separate dpaa2_frame.[h,c] along with
some clean up and improvements, e.g. no more dpaa2_fa, but dpaa2_swa
and dpaa2_hwa structures to describe software and hardware frame
annotations respectively, dpaa2_fa_get_swa/dpaa2_fa_get_hwa to obtain
those annotations from the frame descriptor. The next step is to
implement dpaa2_fa_get_hwa.
PR: 292006
Approved by: tuexen
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D56315
(cherry picked from commit 8e994533806d8aa0ae4582a52d811ede2b19bb26)
dpaa2: Extract checksum statuses on ingress
In order to enable RX checksum offloading we need to check the
meta-information for the (good) frames to see if the L3/4 checksums
were calculated and if there was an error.
The way the buffere are setup, the needed frame meta-information is
already requested. All we have to do is make sure it is really part
of the RX frame, that it is valid, and if the respective bits are set.
Also do not forget to set the (dummy) csum_data as otherwise upper
layers will just be cranky. An artefact of the past which likely
should disappear.
PR: 292006
Reviewed by: bz, tuexen
Tested by: bz, tuexen
Approved by: tuexen
Obtained from: bz (initial version, D55320)
[5 lines not shown]
dpaa2: Extract frame-specific routines to dpaa2_frame.[h,c]
As soon as we need information from the hardware frame annotation to
make sure that checksums of the ingress frames were verified by the
DPAA2 HW, I've decided to make a preparation and extracted all of the
frame related routines into the separate dpaa2_frame.[h,c] along with
some clean up and improvements, e.g. no more dpaa2_fa, but dpaa2_swa
and dpaa2_hwa structures to describe software and hardware frame
annotations respectively, dpaa2_fa_get_swa/dpaa2_fa_get_hwa to obtain
those annotations from the frame descriptor. The next step is to
implement dpaa2_fa_get_hwa.
PR: 292006
Approved by: tuexen
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D56315
(cherry picked from commit 8e994533806d8aa0ae4582a52d811ede2b19bb26)
java/sigar: fix running with openjdk8
Running Cassandra 3 gave:
java.lang.UnsupportedClassVersionError: org/hyperic/sigar/SigarException has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 52.0
PR: 294323
Reported-by: Lapo Luchini
Fixes: f3a12dc72aa72af22212e3e37c5f29652eae0cbb "fix compilation with jdk21"
MFH: 2026Q2
Pointy-hat: to me
(cherry picked from commit 39650b669d8253cfc1419e384741df7f5c7e2c4c)
NB: I included the portrevision bump of 86813e9ccf597695e26c8104e678f913689f1e93
although that commit is not merged. I think this makes it more clear that the
port in branch 2026Q2 is equal to the port in main now.
java/sigar: fix running with openjdk8
Running Cassandra 3 gave:
java.lang.UnsupportedClassVersionError: org/hyperic/sigar/SigarException has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 52.0
PR: 294323
Reported-by: Lapo Luchini
Fixes: f3a12dc72aa72af22212e3e37c5f29652eae0cbb "fix compilation with jdk21"
MFH: 2026Q2
Pointy-hat: to me
kdump(1): add sys/ prefix for exterror source file name
This makes it consistent with libc formatting.
Requested by: mckusick
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
science/hdf5-21: New port, copied from science/hdf5
HDF5 is a completely new Hierarchical Data Format product consisting of a data
format specification and a supporting library implementation. HDF5 is designed
to address some of the limitations of the older HDF product and to address
current and anticipated requirements of modern systems and applications.
HDF5 includes the following improvements:
- A new file format designed to address some of the deficiencies of HDF4.x,
particularly the need to store larger files and more objects per file.
- A simpler, more comprehensive data model that includes only two basic
structures: a multidimensional array of record structures, and a grouping
structure.
- A simpler, better-engineered library and API, with improved support for
parallel I/O, threads, and other requirements imposed by modern systems
and applications.
Tools/scripts: Add report-outdated-for-maintainer.py
report-outdated-for-maintainer.py checks Repology and GitHub
and produces a categorized report of outdated ports.
It produces a better report than Repology produces:
it produces 3 tables:
* Majorly outdated ports
* Moderately outdated ports
* Slightly outdated ports
and it sorts outdated ports by how much are they outdated.
There are still minor bugs. This is WIP.
