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 suppo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Matthieu CASTET on 3/4/2008 6:28 AM:
| Also according to my posix reading [1], chown should be able to change
perm to
| any uid/gid.
You read wrong. POSIX also allows chown implementations to impose
additional restrictions. And on cygw
Corinna Vinschen cygwin.com> writes:
>
> On Feb 29 09:16, Matthieu CASTET wrote:
> > Hi,
>
> Why do you want to fake security when yoi can get the real thing?
>
For the same reason that fakeroot is used on UNIX : I want to create images with
special unix right.
Also according to my posix read
On Feb 29 09:16, Matthieu CASTET wrote:
> Hi,
>
> Dave Korn artimi.com> writes:
>
> >
> > Because it has to emulate unix perms by relating uid/gid to windows RIDs,
> which are owned, allocated and
> > controlled by the system, and not under the arbitrary choice of the user, so
> the semantics
Hi,
Dave Korn artimi.com> writes:
>
> Because it has to emulate unix perms by relating uid/gid to windows RIDs,
which are owned, allocated and
> controlled by the system, and not under the arbitrary choice of the user, so
the semantics wouldn't be the
> same even if we did create ACLs with un
On Feb 28 14:55, Dave Korn wrote:
> On 28 February 2008 14:45, Matthieu CASTET wrote:
>
> > But then why does it works if I create dummy user in /etc/passwd.
>
> Because cygwin relies on the contents of /etc/passwd to be accurate. Cygwin
> cannot in general know what SIDs exist out there in a
On 28 February 2008 14:45, Matthieu CASTET wrote:
> But then why does it works if I create dummy user in /etc/passwd.
Because cygwin relies on the contents of /etc/passwd to be accurate. Cygwin
cannot in general know what SIDs exist out there in a domain (or even on a
local machine), it treats
Hi,
Dave Korn artimi.com> writes:
>
>
> Because it has to emulate unix perms by relating uid/gid to windows RIDs,
which are owned, allocated and
> controlled by the system, and not under the arbitrary choice of the user, so
the semantics wouldn't be the
> same even if we did create ACLs with
On 28 February 2008 13:59, Matthieu CASTET wrote:
> Hi,
>
> I wonder why on cygwin we can't use chown with numeric id that don't exist
> in /etc/passwd, /etc/group [1] ?
Because it has to emulate unix perms by relating uid/gid to windows RIDs,
which are owned, allocated and controlled by the
Hi,
I wonder why on cygwin we can't use chown with numeric id that don't exist in
/etc/passwd, /etc/group [1] ?
On linux this works perfectly [2]
Matthieu
[1]
$ touch /tmp/toto
$ chown 12345:12346 /tmp/toto
chown: changing ownership of `/tmp/toto': Invalid argument
[2]
$ touch /tmp/toto
$ sudo
10 matches
Mail list logo
