From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: gettext - acl tests - cygwin specific code path
Date: Wed, 22 Aug 2018 22:36:00 -0000 [thread overview]
Message-ID: <9fe5a5a8-de22-b945-964d-ebbfa138a1a9@gmail.com> (raw)
In-Reply-To: <20180822081504.GG3348@calimero.vinschen.de>
On 8/22/2018 4:15 AM, Corinna Vinschen wrote:
> On Aug 21 19:57, cyg Simple wrote:
>> On 8/21/2018 4:13 PM, Andrey Repin wrote:
>>> Greetings, cyg Simple!
>>>
>>>> During the testing at least one of the tests does `setfacl -m group:0:1
>>>> tmpfile0`. Obviously this gets a 'permission denied' error as group 0
>>>> doesn't exist. What do you suggest for reasonable replacement for 0?
>>>
>>> Nothing. Not all systems have a concept of "group 0". Just skip this test.
>>
>> I'm not interested in skipping the test; after all the path for the test
>> is Cygwin specific. It's just not the correct thing to do for the
>> Cygwin specific path. I believe 11 to be the correct test and will
>> pursue that upstream. Marco suggested maybe 544(Administrator) but that
>> doesn't work with a typical user build while doing the same in Linux for
>> root group 0 as a typical user I would need to have elevated privilege
>> in Windows to use 544.
>
> Exactly as on another system when using group 0. If these tests are
> really only performed on Cygwin, I don't know what the creator intended.
Cygwin is treated specifically to do this instead of that. As I review
more cases of the specifically treated Cygwin I think the tests are old
as setfacl options being used don't exist today.
> Otherwise, if you want to reproduce what the testcase did, you should in
> fact use an admin group.
That depends on the purpose of the test and based on the comments the
testing could use any group. It should also check that the /tmp
filesystem can support ACL as it assumes /tmp to be locally mounted and
skip the testing if not.
--
cyg Simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-08-22 13:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 20:53 cyg Simple
2018-08-21 23:57 ` cyg Simple
2018-08-22 8:13 ` Marco Atzeri
2018-08-22 8:16 ` Andrey Repin
2018-08-22 10:19 ` cyg Simple
2018-08-22 13:37 ` Corinna Vinschen
2018-08-22 22:36 ` cyg Simple [this message]
2018-08-22 13:49 ` Andrey Repin
2018-08-22 10:24 ` Corinna Vinschen
2018-08-23 2:54 ` cyg Simple
2018-08-23 23:13 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9fe5a5a8-de22-b945-964d-ebbfa138a1a9@gmail.com \
--to=cygsimple@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).