X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Tue, 4 Mar 2008 14:56:01 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: chown with not existing user/group Message-ID: <20080304135601.GT18407@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <008b01c87a16$308a0540$2e08a8c0@CAM.ARTIMI.COM> <20080229092205.GQ9539@calimero.vinschen.de> <47CD5140.5090306@byu.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47CD5140.5090306@byu.net> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Mar 4 06:40, Eric Blake wrote: > | I was thinking cygwin goal was to emulate as much as possible posix > | spec. > > Yes, and cygwin's behavior in this case is still POSIX compliant. Right. The error code in question is this: [EINVAL] The owner or group ID supplied is not a value supported by the implementation. We *could* create non-existant SIDs in the security descriptors of files, but I don't know what the sense would be. These SIDs would never, on no machine, have a real user or group representation. It's not quite comparable with using non-existant uids on a Unix box. These uids can exist on another machine where they make sense. That's not how it is with SIDs since SIDs are bound to a computer or domain. Fake SIDs are bound to nothing at all and are never correctly recognized. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/