On 12/09/2025 19:04, polydue...@proton.me wrote:
recently decided to give a try to 15-stable so i grabbed the alpha 1 disc1 iso and decided to go the pkgbase way, the
installation went fine and smooth, finished the installation, rebooted into the freshly installed system, tried doing
man -k dtrace, got "apropos: nothing appropriate" weird, tried doing man -f dtrace, again got "whatis:
nothing appropriate", tried the same with other manpages like "sh" and the other result was the same, at
this point i startes the installer again and reinstalled 15-alpha1 but with "traditional installation" this
time and man -k and man -f started working properly in that traditional installation system
With legacy files instead of packages for base, I get more after
makewhatis than before makewhatis.
Is this normal?
Script started on Fri Sep 12 21:43:49 2025
root@alpha1-minimal-legacy:~ # echo $SHELL
/bin/csh
root@alpha1-minimal-legacy:~ # pkg bootstrap -y
Bootstrapping pkg from
pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/latest, please wait...
Verifying signature with trusted certificate
pkg.freebsd.org.2013102301... done
Installing pkg-2.2.2...
Extracting pkg-2.2.2: 0%
…
Extracting pkg-2.2.2: 100%
root@alpha1-minimal-legacy:~ # freebsd-version -kru ; uname -mvKU
15.0-ALPHA1
15.0-ALPHA1
15.0-ALPHA1
FreeBSD 15.0-ALPHA1 #0 stable/15-n280099-0b3d82579a01: Sat Sep 6
19:04:24 -00 2025
r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC
amd64 1500064 1500064
root@alpha1-minimal-legacy:~ # pkg prime-origins | sort -u
ports-mgmt/pkg
root@alpha1-minimal-legacy:~ # man -k dtrace
dtrace(1) - dynamic tracing compiler and tracing utility
dwatch(1) - watch processes as they trigger a particular DTrace probe
plockstat(1) - Trace pthread lock statistics using DTrace
root@alpha1-minimal-legacy:~ # makewhatis
root@alpha1-minimal-legacy:~ # man -k dtrace
dtrace(1) - dynamic tracing compiler and tracing utility
dwatch(1) - watch processes as they trigger a particular DTrace probe
plockstat(1) - Trace pthread lock statistics using DTrace
dtrace_audit, dtaudit(4) - A DTrace provider for tracing audit 4 events
dtrace_dtrace(4) - a DTrace provider for BEGIN, END, and ERROR probes
dtrace_fbt(4) - a DTrace provider for dynamic kernel tracing based on
function boundaries
dtrace_io(4) - a DTrace provider for tracing events related to disk I/O
dtrace_ip(4) - a DTrace provider for tracing events related to the IPv4
and IPv6 protocols
dtrace_kinst(4) - a DTrace provider for tracing arbitrary instructions
in a given kernel function
dtrace_lockstat(4) - a DTrace provider for tracing kernel locking events
dtrace_proc(4) - a DTrace provider for tracing events related to user
processes
dtrace_profile(4) - a DTrace provider for firing probes at a given time
interval
dtrace_sched(4) - a DTrace provider for tracing CPU scheduling events
dtrace_sctp(4) - a DTrace provider for tracing events related to the
sctp 4 protocol
dtrace_tcp(4) - a DTrace provider for tracing events related to the tcp
4 protocol
dtrace_udp(4) - a DTrace provider for tracing events related to the UDP
protocol
dtrace_udplite(4) - a DTrace provider for tracing events related to the
UDP-Lite protocol
d, D(7) - DTrace scripting language overview
SDT, SDT_PROBE_DECLARE, SDT_PROBE_DEFINE, SDT_PROVIDER_DECLARE,
SDT_PROVIDER_DEFINE, SDT_PROBE(9) - a DTrace framework for adding
statically-defined tracing probes
root@alpha1-minimal-legacy:~ # exit
exit
Script done on Fri Sep 12 21:45:23 2025
