Page MenuHomeFreeBSD

pathconf.2: Document the _PC_HAS_HIDDENSYSTEM name
ClosedPublic

Authored by rmacklem on Sat, Jul 5, 11:47 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jul 11, 11:16 AM
Unknown Object (File)
Fri, Jul 11, 10:46 AM
Unknown Object (File)
Fri, Jul 11, 4:32 AM
Unknown Object (File)
Thu, Jul 10, 1:50 AM
Unknown Object (File)
Sun, Jul 6, 7:26 PM

Details

Summary

Commit afd5bc630930 added a new pathconf name
_PC_HAS_HIDDENSYSTEM.

This patch documents this new name.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

pauamma_gundo.com added inline comments.
lib/libsys/pathconf.2
183

Audience check: will intended readers understand that "UF_HIDDEN and UF_SYSTEM va_flags" refer to flags settable through chflags(2)?

Reword the description to reference chflags(2)
as suggested by Pau Amma.

chflags(3) calls these Dv's, we could call them Dv's to bring them into the apropos results, or maybe something else if it makes more sense.

This revision is now accepted and ready to land.Sun, Jul 6, 1:46 AM
lib/libsys/pathconf.2
183

va_flags is the kernel-side struct va_attr member, this documentation is for users.

Put .Dv before UF_HIDDEN and UF_SYSTEM as suggested
by ziaee@ and replaced va_flags with flags as suggested
by kib@. (I did not put .Ar in front of flags, since it is not
an argument to pathconf. Should I?)

This revision now requires review to proceed.Sun, Jul 6, 2:48 PM

Put .Dv before UF_HIDDEN and UF_SYSTEM as suggested
by ziaee@ and replaced va_flags with flags as suggested
by kib@. (I did not put .Ar in front of flags, since it is not
an argument to pathconf. Should I?)

IMO 'flags' there refers to the attribute of the file, so the .Ar markup is definitely not appropriate.

This revision is now accepted and ready to land.Sun, Jul 6, 3:11 PM

My litmus test for "should we mark it up" is "should users be able to find this page with apropos Ar=flags.