summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>2004-03-03 07:52:36 +0000
committerJim Meyering <jim@meyering.net>2004-03-03 07:52:36 +0000
commit50c485dac0fe0075a570656fd0a168a07177d32f (patch)
tree5bd68158fb247e53653ce286538d913e9036c56f /doc
parentaa1ba5a545e27fae56c0e48b496520a11147c08d (diff)
downloadcoreutils-50c485dac0fe0075a570656fd0a168a07177d32f.tar.xz
(chown invocation): Document that chown now falls
back on USER.GROUP parsing regardless of POSIX version, as POSIX 1003.1-2001 allows that behavior as a compatible extension.
Diffstat (limited to 'doc')
-rw-r--r--doc/coreutils.texi12
1 files changed, 7 insertions, 5 deletions
diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 5d37be7d0..6e074f5fa 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -7712,11 +7712,13 @@ is omitted, only the group of the files is changed; in this case,
@end table
Some older scripts may still use @samp{.} in place of the @samp{:} separator.
-@acronym{POSIX} 1003.1-2001 (@pxref{Standards conformance}) does not allow that,
-but you may be able to work around the compatibility problems by setting
-@samp{_POSIX2_VERSION=199209} in your environment.
-New scripts should avoid the use of @samp{.} because @sc{gnu} @command{chown}
-may fail if @var{owner} contains @samp{.} characters.
+@acronym{POSIX} 1003.1-2001 (@pxref{Standards conformance}) does not
+require support for that, but for backward compatibility @acronym{GNU}
+@command{chown} supports @samp{.} so long as no ambiguity results.
+New scripts should avoid the use of @samp{.} because it is not
+portable, and because it has undesirable results if the entire
+@var{owner@samp{.}group} happens to identify a user whose name
+contains @samp{.}.
Warning: The @command{chown} command may clear the set-user-ID or
set-group-ID bits on some systems. The @command{chown} command is