Re: CVS commit: src/usr.bin/chflags

[Valery Ushakov <uwe%stderr.spb.ru@localhost>]

On Thu, May 25, 2023 at 09:59:41 -0400, Greg Troxel wrote:

> Taylor R Campbell <campbell+netbsd-source-changes-d%mumble.net@localhost> writes:
> 
> > jschauma@'s change did help clarify (1) and (2).  Let's try to work
> > together to make it better?
[...] 
> I would recommend:
> 
>   Noting that archive flag represents something in some foreign
>   filesystems, currently known to exist only for some MSDOS filesystems,
>   and that the specific filesystem should document that.
> 
>   Explaining that the nodump flag is a request that backup programs omit
>   the file from backups and to see dump(8).
> 
>   Be clearer about permissions.
> 
>   Drop the restatement of tokens into a third only-here namespace.
>   Instead, use paragraphs following to describe that each token means.

I have added slightly more verbose descriptions to stat_flags(3) -
which are the functions in -lutil used by several programs that deal
with flag names and added a xref to it from chflags(1).  That man page
now lists all the alternative flag names too and explicitly mentions
dump/nonodump as negation of nodump.

I think that information *must* be there, as that's *the* place where
the names are (un)parsed.  I'm not sure whether this information has
to be duplicated as-is in chflags(1), or whether chflags(1) can have a
less verbose version.

-uwe