This is the mail archive of the
mailing list for the Cygwin project.
Re: chown with not existing user/group
- From: Eric Blake <ebb9 at byu dot net>
- To: cygwin at cygwin dot com, matthieu dot castet at parrot dot com
- Date: Tue, 04 Mar 2008 06:40:16 -0700
- Subject: Re: chown with not existing user/group
- References: <loom.20080228T135447email@example.com> <008b01c87a16$308a0540$2e08a8c0@CAM.ARTIMI.COM> <loom.20080229T091201firstname.lastname@example.org> <20080229092205.GQ9539@calimero.vinschen.de> <loom.20080304T132211email@example.com>
-----BEGIN PGP SIGNED MESSAGE-----
According to Matthieu CASTET on 3/4/2008 6:28 AM:
| Also according to my posix reading , chown should be able to change
| any uid/gid.
You read wrong. POSIX also allows chown implementations to impose
additional restrictions. And on cygwin, we impose the additional
restriction that you can't change to a uid/gid that isn't recognized by
| I was thinking cygwin goal was to emulate as much as possible posix
Yes, and cygwin's behavior in this case is still POSIX compliant.
Don't work too hard, make some time for fun as well!
Eric Blake firstname.lastname@example.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html