Let me take a try on Achim's case with/refining the "alternative
idea"; this seems one of the kinds of cases that it is intended to
help.
(Corinna, I hope at least some of the ideas here prove helpful to you,
and my posting this isn't (too) annoying. Again, please
expect/forgive glitches as I'm n
On Apr 23 20:44, Achim Gratz wrote:
> Corinna Vinschen writes:
> > You may be right here. The problem is that we have two kinds of ACLs
> > to handle, the ones created by Windows means, and the ones created
> > by recent or older Cygwin versions. It's rather bad that we can't
> > distinguish them
Corinna Vinschen writes:
> You may be right here. The problem is that we have two kinds of ACLs
> to handle, the ones created by Windows means, and the ones created
> by recent or older Cygwin versions. It's rather bad that we can't
> distinguish them.
I thought that this was the point of the NU
On Apr 22 20:35, Achim Gratz wrote:
> Corinna Vinschen writes:
> > Hmm. Can you try the same with the latest developer snapshot I just
> > created? I found this problem which created undesired DENY ACEs,
> > maybe this was the reason /knock on wood/.
>
> I ran out of time, but I've managed to in
Corinna Vinschen writes:
> Hmm. Can you try the same with the latest developer snapshot I just
> created? I found this problem which created undesired DENY ACEs,
> maybe this was the reason /knock on wood/.
I ran out of time, but I've managed to install the snapshot and did a
quick test before g
On Apr 21 19:18, Achim Gratz wrote:
> Corinna Vinschen writes:
> > It's not about rsync exactly.
>
> Well, rsync creates that mess somehow.
>
> > The problem is that I'm missing the
> > context a bit. I take it the permissions are supposed to be inherited
> > from the ".." dir, basically. The "
Corinna Vinschen writes:
> It's not about rsync exactly.
Well, rsync creates that mess somehow.
> The problem is that I'm missing the
> context a bit. I take it the permissions are supposed to be inherited
> from the ".." dir, basically. The ".." dir has been created by
> non-Cygwin means, righ
On Apr 21 09:33, Achim Gratz wrote:
> Corinna Vinschen cygwin.com> writes:
> > New 2.0.0-0.7 test release:
>
> It looks like I found a bug or at least some extremely undesirable
> behaviour. We back up some data via rsync, the script doesn't use the --acl
> option yet (that will need to change).
Corinna Vinschen cygwin.com> writes:
> New 2.0.0-0.7 test release:
It looks like I found a bug or at least some extremely undesirable
behaviour. We back up some data via rsync, the script doesn't use the --acl
option yet (that will need to change). The bug happens without this option,
so rsync
Thanks for the explanation/correction about umask's non-impact if
there are default ACL entries. I'm not recalling exactly what I had
seen on Linux that made me think there was an impact.
>> If the incoming, inherited ACL contains the three entries for user,
group, and other, it's with very hi
On Apr 19 13:50, random user wrote:
> >>> I note that chmod doesn't keep these to-be-inherited entries in
> sync with the directory's mode;
> >>Yep. Did you check against Linux behaviour?
>
> The difference to my eye is that on Linux there is no such
> to-be-inherited CREATOR OWNER ACL entry
Hmm... Seems my Item 1 and Item 2 are more related in your design
thinking than I had realized.
>>> "extended ACLs" (is that the proper phrasing?),
>> (default ACL entries in POSIX speak, inheritable ACEs in Windows)
I'm looking for the term that would distinguish whether on Linux ls
shows a '+'
Corinna Vinschen writes:
> What we *could* try to do is to tweak the actual SYSTEM and Admins ACE,
> though. Rather than ignoring the CLASS_OBJ/ACL_MASK value completely
> for them, we could apply the execute bit part only. Usually it doesn't
> make sense for SYSTEM/Admins having execute perms if
On Apr 18 12:48, Achim Gratz wrote:
> Corinna Vinschen writes:
> > Right. It's a compromise. I take it you don't like the extra behaviour
> > for SYSTEM/Admins. Neither do I. Others are desperately waiting for
> > more. The problem with compromises is, they are usually best if nobody
> > is co
Corinna Vinschen writes:
> Right. It's a compromise. I take it you don't like the extra behaviour
> for SYSTEM/Admins. Neither do I. Others are desperately waiting for
> more. The problem with compromises is, they are usually best if nobody
> is completely satisfied ;)
I have argued against t
On Apr 18 11:47, Achim Gratz wrote:
> Corinna Vinschen writes:
> > In theory, the access(2)/faccessat(2) functions should not rely at all
> > on the new code. The reason is that they are implemented using the
> > underlying OS function to evaluate ACLs. That means, they provide the
> > actual acc
Hi random user (at least a first name would be nice, you know my first name
as well, isn't it?),
On Apr 17 22:58, random user wrote:
> Hi again, Corinna.
>
> I appreciate these recent changes, the more complete Posix ACL support
> looks beneficial for sharing/syncing files between Cygwin and Linu
Corinna Vinschen writes:
>> -rw---+ 1 ASSI Kein 48880 5. Apr 2014 ucl.log
>> # file: ucl.log
>> # owner: ASSI
>> # group: Kein
>> user::rw-
>> group::---
>> group:SYSTEM:rwx#effective:---
>> group:Administratoren:rwx #effective:---
>> mask:---
>> other:--
Hi Achim,
On Apr 17 22:09, Achim Gratz wrote:
> Corinna Vinschen writes:
> > New 2.0.0-0.7 test release:
> >
> > - Improved setfacl tool. It now handles mask recomputation just like
> > the Linux tool. -d option renamed to -x (but -d is still accepted
> > for backward compat). New -n,--no-m
Hi again, Corinna.
I appreciate these recent changes, the more complete Posix ACL support
looks beneficial for sharing/syncing files between Cygwin and Linux
machines, and for more compatible scripting.
But I've noticed a few possibly-concerning items:
Item 1:
>> - I introduced a change in chmo
Corinna Vinschen writes:
> New 2.0.0-0.7 test release:
>
> - Improved setfacl tool. It now handles mask recomputation just like
> the Linux tool. -d option renamed to -x (but -d is still accepted
> for backward compat). New -n,--no-mask and --mask options.
"setfacl -b -k" still errors out i
On Fri, Apr 17, 2015 at 7:46 AM, Jim Reisert AD1C wrote:
> Is there a way to change my default home directory without using
> /etc/passwd, other than creating a symbolic link inside of /home?
You can modify /etc/fstab like this
c:/home /home . acl
Example
http://github.com/svnpenn/dotfiles/b
> https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch-home
Very helpful, Corinna! Working as advertised.
- Jim
--
Jim Reisert AD1C, , http://www.ad1c.us
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On Apr 17 15:16, Corinna Vinschen wrote:
> On Apr 17 06:46, Jim Reisert AD1C wrote:
> > I finally understand what happened.
> >
> > In my /etc/passwd, I have configured a different home directory for
> > myself. Without that file, it goes to /home/Jim Reisert which does
> > not exist!
> >
> > Is
On Apr 17 06:46, Jim Reisert AD1C wrote:
> I finally understand what happened.
>
> In my /etc/passwd, I have configured a different home directory for
> myself. Without that file, it goes to /home/Jim Reisert which does
> not exist!
>
> Is there a way to change my default home directory without
I finally understand what happened.
In my /etc/passwd, I have configured a different home directory for
myself. Without that file, it goes to /home/Jim Reisert which does
not exist!
Is there a way to change my default home directory without using
/etc/passwd, other than creating a symbolic link
On Apr 17 06:27, Jim Reisert AD1C wrote:
> There's still something funky going on. ssh won't recognize my
> ~/.ssh/config file.
>
> With my existing passwd and group files, I get this error (notice that
> the warned permissions are different that what "ls" reports):
>
> -rw---+ 1 Jim Reisert
On Apr 17 06:15, Jim Reisert AD1C wrote:
> > New 2.0.0-0.7 test release:
>
> I'm happy to report that Xwin now starts up straight away, even with
> "missing" /etc/passwd and /etc/group files.
>
> Thanks for fixing this!
Sure, thanks for your feedback!
Corinna
--
Corinna Vinschen
There's still something funky going on. ssh won't recognize my
~/.ssh/config file.
With my existing passwd and group files, I get this error (notice that
the warned permissions are different that what "ls" reports):
-rw---+ 1 Jim Reisert None 205 Apr 17 06:19 .ssh/config
[JJR:~] $ ssh ad1c
> New 2.0.0-0.7 test release:
I'm happy to report that Xwin now starts up straight away, even with
"missing" /etc/passwd and /etc/group files.
Thanks for fixing this!
--
Jim Reisert AD1C, , http://www.ad1c.us
--
Problem reports: http://cygwin.com/problems.html
FAQ: http
Hi Cygwin friends and users,
New 2.0.0-0.7 test release:
- Improved setfacl tool. It now handles mask recomputation just like
the Linux tool. -d option renamed to -x (but -d is still accepted
for backward compat). New -n,--no-mask and --mask options.
- Improved getfacl tool. It now prin
31 matches
Mail list logo
