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/
