cr_canseeotheruids(), cr_canseeothergids(): Man pages: Impacts of rename

[olce]

Summary

When these functions were renamed 7 years ago, their man pages were not. Rename
the latter in accordance and fix the names inside them. Fix references to them
as well. Add the old man pages to the list of obsolete files.

[zlei]

Unless D40629 is approved.

[olce]

Update context lines after update of D40626.

[mhorne]

I do agree that the "can" part of the name is confusing. To me, it implies a boolean return value, but in actuality a return value of zero means "yes you can".

However, many functions in kern_prot.c follow this cr_can*() or p_can*() naming convention. At this point I think it is better to keep these functions consistent with the others, and update the names of the man pages.

[olce]

In D40630#935074, @mhorne wrote:

However, many functions in kern_prot.c follow this cr_can*() or p_can*() naming convention. At this point I think it is better to keep these functions consistent with the others, and update the names of the man pages.

Yes. But I thought I would rename these despite that since they are now internal functions, in order to reserve the cr_can and p_can prefixes for functions that can actually be called from outside. But I don't mind changing the man pages instead.

[olce]

Rename man pages and fix references instead of renaming the functions.

[mhorne]

What you have looks good. The only thing you are missing is to add the old names to ObsoleteFiles.inc. This ensures the old files will be cleaned up with make delete-old.

[olce]

Add old man pages to ObsoleteFiles.inc.

[olce]

Rebase.

[olce]

Revalidate after rebase.