Date: Thu, 18 Sep 2025 11:59:10 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 289683] OS installation with legacy files: results of whatis are incomplete Message-ID: <bug-289683-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289683 Bug ID: 289683 Summary: OS installation with legacy files: results of whatis are incomplete Product: Base System Version: 15.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: grahamperrin@gmail.com Spun off from <https://lists.freebsd.org/archives/freebsd-stable/2025-September/003158.html>. base ea5e50c2985b this morning is for OS installation with packages. I see a similar situation with legacy files instead of packages. Reproducible. In the example below, man -k dtrace finds nothing until after a run of makewhatis ---- Script started on Thu Sep 18 12:48:51 2025 root@whatis:~ # echo $SHELL /bin/sh root@whatis:~ # freebsd-version -kru ; uname -mvKU 15.0-ALPHA2 15.0-ALPHA2 15.0-ALPHA2 FreeBSD 15.0-ALPHA2 stable/15-n280122-da62a299de31 GENERIC amd64 1500064 1500064 root@whatis:~ # uptime 12:49PM up 41 secs, 1 user, load averages: 0.16, 0.04, 0.01 root@whatis:~ # man -k dtrace apropos: nothing appropriate root@whatis:~ # makewhatis root@whatis:~ # 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@whatis:~ # exit Script done on Thu Sep 18 12:49:26 2025 -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-289683-227>