Bob Proulx wrote:
> Please see this frequently given answer in the reference below.
>
> http://www.gnu.org/software/coreutils/faq/
>
> Look for "Why can only root chown files?"
Incidently, there is an incomplete sentence in that section of the FAQ
("Such as creating...").
BrianIndex: coreutils-faq.texinfo
===================================================================
RCS file: /webcvs/coreutils/coreutils/faq/coreutils-faq.texinfo,v
retrieving revision 1.16
diff -u -r1.16 coreutils-faq.texinfo
--- coreutils-faq.texinfo 13 Aug 2005 04:44:50 -0000 1.16
+++ coreutils-faq.texinfo 1 Sep 2005 16:07:07 -0000
@@ -351,7 +351,7 @@
@item
A user can create files that they cannot remove. With the old semantics
it was possible for normal users to create situations that only the
-superuser could fix. Such as creating a non-writable directory of files
+superuser could fix, such as creating a non-writable directory of files
and then giving the ownership away. Since they no longer own the files
they can't change them, nor can they remove them. This is commonly a
problem when untaring files that other people created with restrictive
_______________________________________________
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
