gary ng wrote:
> oh, I see it now. So the "to" that I change to must
> satisfy 2 conditions :
>
> 1. I am only changing the owner to myself
> 2. I must also be a member of the group owner that I
> change to
Yes. You have it.
> I can understand (1) but it is (2) that I don't find
> mentioned anywhere.
Not that people will think this is the most obvious place to look but
look in the chown(2) man page.
man 2 chown
These system calls change the owner and group of the file specified by
path or by fd. Only a privileged process (Linux: one with the
CAP_CHOWN capability) may change the owner of a file. The owner of a
file may change the group of the file to any group of which that owner
is a member. A privileged process (Linux: with CAP_CHOWN) may change
the group arbitrarily.
...
CONFORMING TO
The chown call conforms to SVr4, SVID, POSIX, X/OPEN. The 4.4BSD ver-
sion can only be used by the superuser (that is, ordinary users cannot
give away files). SVr4 documents EINVAL, EINTR, ENOLINK and EMULTIHOP
returns, but no ENOMEM. POSIX.1 does not document ENOMEM or ELOOP
error conditions.
> Would it be better to mention it somewhere in the faq.
Good suggestion. I will add that to the FAQ.
> Forgive my ignorance and please close the bug.
I am not the package maintainer.
http://www.debian.org/Bugs/Developer
Normally, the only people that are allowed to close a bug report are
the submitter of the bug and the maintainer(s) of the package
against which the bug is filed.
As the submitter you may close the bug.
With the emails received from the bug tracking system, all you
need to do to close the bug is to make a Reply in your mail reader
program and edit the To field to say [EMAIL PROTECTED]
instead of [EMAIL PROTECTED] (nnn-close is provided as an alias
for nnn-done).
Bob
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
