That's ok for me, but I thought that things work by default.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Wed, Mar 25
Tue, Mar 24
Mon, Mar 16
Mon, Mar 9
Sat, Mar 7
Fri, Mar 6
Wed, Mar 4
Mon, Mar 2
Feb 25 2026
Feb 24 2026
Feb 23 2026
Feb 21 2026
Feb 18 2026
Feb 16 2026
Feb 11 2026
Feb 3 2026
Feb 1 2026
Jan 30 2026
Jan 22 2026
Jan 20 2026
Jan 19 2026
Jan 15 2026
Jan 14 2026
Jan 12 2026
Jan 9 2026
Jan 8 2026
Jan 5 2026
Dec 31 2025
Dec 30 2025
Dec 27 2025
Dec 22 2025
Dec 16 2025
The real problem is mentioned here: https://wiki.freebsd.org/BjoernZeeb/Ten64
If loaded as module from multi-user we do not get the time set even if manually triggering a sysctl debug.clock_do_io=1. Reason for this is that vfs_moutroot() is responsible to have the clock set and calls CLOCK_GETTIME() indirectly so that log files or other timestamps do not appear to go backwards (if no RTC is found it'll use the vfs root node date?). Look for the inittodr() call.
Dec 15 2025
Dec 14 2025
Dec 6 2025
Dec 5 2025
Dec 4 2025
Nov 30 2025
Nov 27 2025
Nov 25 2025
Nov 19 2025
One note from a ports maintainer perspective: rust currently uses FreeBSD 11 syscalls. Although those are new binaries, they need COMPAT_FREEBSD11, even for powerpc64le (which was introduced in 13.0). There is long-going plan to bump that to 12, but even then we'll still need COMPAT_FREEBSD12.
Another thing: dropping support for running old binaries (as in compiled long ago) is not an issue for me (and probably most users), but then ELFv1 support should probably also be dropped. We switched to ELFv2 in 13.0.