>From the followings inputs it should be expected to produce regarding the input format either error or a warning messages. As empty sets all the input tests have been conducted.
Format of input that were validated with no kind of message from coreutils: # chmod [ugoa][+-=][rwxXst] </file> [ugoa] – all parameter combinations with no length restriction or an empty parameter are allowed. [=+-] – all parameter combinations with no length restriction are allowed. [rwxXst] – no value has to be specified. Steps to Reproduce: 1. Open a terminal, log in as root and move to the folder containing the target file for testing purpose. 2. For testing purpose as well input has to meet that condition: After the symbolic mode parameter [+-=] the set of permissions that should be added/removed must not be specified which means has to be left empty. Examples of such validated combinations of format: # chmod o- </file> # chmod + </file> # chmod agogagagouugogogaauagooaguaguououau=========+++----==--++++--- </file> … and so on. Note: Web sites that TLS protocols are systematically better ranked by the major www search engines which may not be trivial in a competitive environment for publicity. On Linux in terminal, by invoking "man chmod 2" it is noticeable from the output that links related to internet sites are mentioned without HTTPS format while they are currently available: “GNU coreutils online help: <http://www.gnu.org/software/coreutils/> Report chmod translation bugs to <http://translationproject.org/team/>” The above mentioned knowledge in consideration, should reasonably be enough to motivate the update of the documentation with proper updated links.
