Hi,
wdaver wrote on Sun, Jun 19, 2022 at 02:09:06PM -0700:
> Ah - mangl returns
Whoa, i wasn't even aware that "mangl" exists, but it appears it
does exist and we even have a port for it: sysutils/mangl.
It isn't very happy on my machine, though:
schwarze@isnote $ mangl mangl
Segmentation fault (core dumped)
schwarze@isnote $ mangl man
Segmentation fault (core dumped)
schwarze@isnote $ mangl apm
Segmentation fault (core dumped)
schwarze@isnote $ mangl 4 apm
Segmentation fault (core dumped)
schwarze@isnote $ mangl
schwarze@isnote $
It appears mangl is using an embedded copy of mandoc code that
is between two and three years old. Consequently, using it is
probably a bad idea.
That said, adding to what Theo explained,
man 4 apm
and
man -s 4 apm
also return the "Alliance ProMotion video driver" manual
on all architectures except amd64, arm64, i386, loongson, and macppc,
which you can verify with these commands even on amd64:
schwarze@isnote $ man -k ^apm\$
apm(4/amd64) - power management interface
apm(4/arm64) - power management interface
apm(4/i386) - advanced power management device interface
apm(4/loongson) - advanced power management device interface
apm(4/macppc) - advanced power management device interface
apm(4) - Alliance ProMotion video driver
apm, zzz, ZZZ(8) - Advanced Power Management control program
schwarze@isnote $ man -S foo -s 4 apm | head -n 4
APM(4) Device Drivers Manual APM(4)
NAME
apm - Alliance ProMotion video driver
Admittedly, it is unfortunate that the Xenocara apm(4) page clashes
with the base system apm(4) pages. But i don't think we can do
anything about it. The system works as designed: the man(1) command
prefers base system pages over Xenocara pages by default, so on the
platforms having "advanced power management", you get that, and on the
others, you get "Alliance ProMotion". It's not a bug, it's a
feature; even if an unfortunate feature in this particular case.
> Should I send this as a bug to ports or bugs mailing list?
No, i think this thread can be closed as "invalid report".
By the way, next time you report a bug, please state, up front,
1. the architecture you are running on
2. the version of OpenBSD you are using
3. and the exact, complete command you are typing.
Yours,
Ingo
