Page MenuHomeFreeBSD

sndctl(8): Add libxo support
ClosedPublic

Authored by christos on Dec 2 2025, 1:20 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Jan 26, 3:11 AM
Unknown Object (File)
Sat, Jan 24, 1:27 PM
Unknown Object (File)
Fri, Jan 23, 11:43 AM
Unknown Object (File)
Thu, Jan 22, 11:09 PM
Unknown Object (File)
Thu, Jan 22, 11:08 PM
Unknown Object (File)
Tue, Jan 20, 5:30 PM
Unknown Object (File)
Sat, Jan 17, 11:03 AM
Unknown Object (File)
Thu, Jan 15, 8:13 PM
Subscribers

Details

Summary

Sponsored by: The FreeBSD Foundation
MFC after: 1 week

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

christos created this revision.
usr.sbin/sndctl/sndctl.8
185–186

I think xo_options is really what's relevant to the reader of sndctl. That links to libxo(3) if they're curious.

usr.sbin/sndctl/sndctl.8
185–186

I followed what w(1) and wc(1)'s man pages say.

usr.sbin/sndctl/sndctl.8
185–186

I think it's wrong there too, but that isn't a good argument for why we should do it here.

What does the reader or soundctl might want to see also? xo_options explains how to actually use it.

usr.sbin/sndctl/sndctl.8
185–186

I think xo_options(7) is the reasonable think to refer to, since this isn't a programing manual about how the internals of sndctl(8) work, but how to use the utility with --libxo, which is explained in xo_options(7). This isn't wrong.

usr.sbin/sndctl/sndctl.8
185–186

That is what I am saying. You should link to xo_options(7). The diff is currently linking to libxo(3) instead.

christos marked 3 inline comments as done.

Refer to xo_options(7), not libxo(3).

usr.sbin/sndctl/sndctl.8
185–186

...Scratch that. I am an idiot. I thought you said the opposite, and I also thought the patch did the right thing.

usr.sbin/sndctl/sndctl.8
185–186

Actually it happens to everyone!

This revision is now accepted and ready to land.Dec 6 2025, 2:30 PM
This revision was automatically updated to reflect the committed changes.