- 1. Re: acl and attr: Fix path walking code (score: 1)
- Author: Timothy Shimmin <tes@xxxxxxx>
- Date: Fri, 09 Nov 2007 16:41:21 +1100
- Hi Andreas, Andreas Gruenbacher wrote: Hello, the tree walking code in acl and attr broke when resolve_symlinks() was introduced (by me, unfortunately). Following symlinks passed in on the command li
- /archives/xfs/2007-11/msg00087.html (11,117 bytes)
- 2. Re: acl and attr: Fix path walking code (score: 1)
- Author: Timothy Shimmin <tes@xxxxxxx>
- Date: Fri, 09 Nov 2007 18:39:56 +1100
- the tree walking code in acl and attr broke when resolve_symlinks() was introduced (by me, unfortunately). Following symlinks passed in on the command line is the intended behavior for the tools (unl
- /archives/xfs/2007-11/msg00088.html (9,487 bytes)
- 3. Re: acl and attr: Fix path walking code (score: 1)
- Author: Andreas Gruenbacher <agruen@xxxxxxx>
- Date: Sat, 10 Nov 2007 21:52:05 +0100
- With -h, the utilities operate on the symlinks rather than the files that the symlinks point to. The test case sets attributes on SCRATCH_MNT/lnk, but not on descend/and. The -h and -L options togeth
- /archives/xfs/2007-11/msg00091.html (10,684 bytes)
- 4. Re: acl and attr: Fix path walking code (score: 1)
- Author: Andreas Gruenbacher <agruen@xxxxxxx>
- Date: Sat, 10 Nov 2007 22:36:52 +0100
- Hmm, -L and -P define which files and directories are visited, and -h defines whether we are looking at symlinks or the files they point to. The two concepts are orthogonal. -P is not about skipping
- /archives/xfs/2007-11/msg00092.html (9,182 bytes)
- 5. Re: acl and attr: Fix path walking code (score: 1)
- Author: Timothy Shimmin <tes@xxxxxxx>
- Date: Wed, 14 Nov 2007 16:08:54 +1100
- Oops, yep, there is no EA on descend/and. No they don't :) So will it not follow the argument but follow any descendents that it finds on the walk. It kind of looked from the manpage that the -h is a
- /archives/xfs/2007-11/msg00139.html (12,342 bytes)
- 6. Re: acl and attr: Fix path walking code (score: 1)
- Author:
- Date: Tue, 20 Nov 2007 16:11:12 +1100
- defines about not Oh okay. There is the concept of following the symlink for traversal versus following the symlink to get the EA on. So with -L should it just follow the symlink or look at the syml
- /archives/xfs/2007-11/msg00191.html (10,747 bytes)
- 7. Re: acl and attr: Fix path walking code (score: 1)
- Author:
- Date: Fri, 23 Nov 2007 13:24:40 +0100
- Yes. No, -h never skips symlinks. (But depending on -L and -P, it may not follow symlinks to directories.) Here is an additional comment for do_print, and an equivalent version of the if in there. I
- /archives/xfs/2007-11/msg00244.html (10,137 bytes)
- 8. Re: acl and attr: Fix path walking code (score: 1)
- Author:
- Date: Fri, 09 Nov 2007 16:41:21 +1100
- Hi Andreas, Andreas Gruenbacher wrote: Hello, the tree walking code in acl and attr broke when resolve_symlinks() was introduced (by me, unfortunately). Following symlinks passed in on the command li
- /archives/xfs/2007-11/msg00403.html (11,117 bytes)
- 9. Re: acl and attr: Fix path walking code (score: 1)
- Author:
- Date: Fri, 09 Nov 2007 18:39:56 +1100
- the tree walking code in acl and attr broke when resolve_symlinks() was introduced (by me, unfortunately). Following symlinks passed in on the command line is the intended behavior for the tools (unl
- /archives/xfs/2007-11/msg00404.html (9,487 bytes)
- 10. Re: acl and attr: Fix path walking code (score: 1)
- Author:
- Date: Sat, 10 Nov 2007 21:52:05 +0100
- With -h, the utilities operate on the symlinks rather than the files that the symlinks point to. The test case sets attributes on SCRATCH_MNT/lnk, but not on descend/and. The -h and -L options togeth
- /archives/xfs/2007-11/msg00407.html (10,684 bytes)
- 11. Re: acl and attr: Fix path walking code (score: 1)
- Author:
- Date: Sat, 10 Nov 2007 22:36:52 +0100
- Hmm, -L and -P define which files and directories are visited, and -h defines whether we are looking at symlinks or the files they point to. The two concepts are orthogonal. -P is not about skipping
- /archives/xfs/2007-11/msg00408.html (9,182 bytes)
- 12. Re: acl and attr: Fix path walking code (score: 1)
- Author:
- Date: Wed, 14 Nov 2007 16:08:54 +1100
- Oops, yep, there is no EA on descend/and. No they don't :) So will it not follow the argument but follow any descendents that it finds on the walk. It kind of looked from the manpage that the -h is a
- /archives/xfs/2007-11/msg00455.html (12,342 bytes)
- 13. Re: acl and attr: Fix path walking code (score: 1)
- Author: )
- Date: Tue, 20 Nov 2007 16:11:12 +1100
- defines about not Oh okay. There is the concept of following the symlink for traversal versus following the symlink to get the EA on. So with -L should it just follow the symlink or look at the syml
- /archives/xfs/2007-11/msg00507.html (10,747 bytes)
- 14. Re: acl and attr: Fix path walking code (score: 1)
- Author: >
- Date: Fri, 23 Nov 2007 13:24:40 +0100
- Yes. No, -h never skips symlinks. (But depending on -L and -P, it may not follow symlinks to directories.) Here is an additional comment for do_print, and an equivalent version of the if in there. I
- /archives/xfs/2007-11/msg00560.html (10,137 bytes)
- 15. acl and attr: Fix path walking code (score: 1)
- Author:
- Date: Sun, 28 Oct 2007 18:58:24 +0100
- the tree walking code in acl and attr broke when resolve_symlinks() was introduced (by me, unfortunately). Following symlinks passed in on the command line is the intended behavior for the tools (un
- /archives/xfs/2007-10/msg00256.html (8,375 bytes)
- 16. acl and attr: Fix path walking code (score: 1)
- Author: >
- Date: Sun, 28 Oct 2007 18:58:24 +0100
- the tree walking code in acl and attr broke when resolve_symlinks() was introduced (by me, unfortunately). Following symlinks passed in on the command line is the intended behavior for the tools (un
- /archives/xfs/2007-10/msg00583.html (8,375 bytes)
This search system is powered by
Namazu