public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Houder" <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.4
Date: Mon, 03 Nov 2014 15:09:00 -0000	[thread overview]
Message-ID: <352f4f69b0e3afa90974308099249e90.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <1415026765.23338.ezmlm@cygwin.com>

> On Nov  1 17:58, Christian Franke wrote:
>> Corinna Vinschen wrote:
>> >I just released a 4th TEST version of the next upcoming Cygwin release,
>> >1.7.33-0.4.
>>
>> There is an older regression in mkgroup.
>> A separator without a preceding domain name is printed for the builtin
>> groups:
>>
>> $ mkgroup -L THISHOST
>> SYSTEM:S-1-5-18:18:
>> TrustedInstaller:S-1-5-80-...
>> +Administratoren:S-1-5-32-544:544:
>> +Benutzer:S-1-5-32-545:545:
>> ...
>> THISHOST+HelpLibraryUpdaters:S-1-5-21-...
>>
>>
>> Introduced in mkgroup.c CVS 1.54, April 2014:
>>
>> @@ -415,8 +341,8 @@ enum_local_groups (...)
>> ...
>>           printf ("%ls%s%ls:%s:%" PRIu32 ":\n",
>> -                 with_dom && !is_builtin ? domain_name : L"",
>> -                 with_dom && !is_builtin ? sep : "",
>> +                 mach->with_dom && !is_builtin ? domain_name : L"",
>> +                 mach->with_dom || is_builtin ? sep : "", <==== Hmm.... :-)
>
> Thanks!  It would be nice if you could send a patch to cygwin-patches.
>
>> BTW: mkgroup should possibly also print the extra builtin groups which are
>> now reported by getgroups(), for example 4(Interactive), 11(Authenticated
>> Users), ...
>
> Doesn't make much sense.  Generating them via "db" is incredibly fast.
> There is also one person on the list (sorry, don't remember your name)

Me, perhaps? (Henri) ... https://cygwin.com/ml/cygwin/2014-10/msg00491.html

My "nsswitch.conf":

passwd:files
group: files

db_enum: files

In short, no problem at my end: id shows the short list (as before ...)

> claiming he would rather not see the big group list in id while using
> the "files"-only setting.
>
>
> Corinna

=====


--
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

       reply	other threads:[~2014-11-03 15:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1415026765.23338.ezmlm@cygwin.com>
2014-11-03 15:09 ` Houder [this message]
2014-11-03 16:22   ` Corinna Vinschen
2014-11-03 17:57     ` Houder
2014-10-29 12:15 Corinna Vinschen
2014-10-29 17:37 ` Denis Excoffier
2014-10-29 17:51   ` Tim Prince
2014-10-29 20:00   ` Corinna Vinschen
2014-10-29 19:06 ` Habermann, Dave (DA)
2014-10-29 20:02   ` Corinna Vinschen
2014-10-30 13:11     ` Habermann, Dave (DA)
2014-10-29 19:28 ` Habermann, Dave (DA)
2014-10-29 20:03   ` Corinna Vinschen
2014-10-30 13:03     ` Habermann, Dave (DA)
2014-10-30 14:06       ` Corinna Vinschen
2014-10-30 16:21         ` Habermann, David (D)
2014-10-30 17:19           ` Corinna Vinschen
2014-10-30 23:35           ` Andrey Repin
2014-10-31 12:29             ` Habermann, David (D)
2014-10-31 12:50               ` Andrey Repin
2014-11-01 16:59 ` Christian Franke
2014-11-01 17:40   ` Corinna Vinschen
2014-11-03 14:55     ` 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=352f4f69b0e3afa90974308099249e90.squirrel@webmail.xs4all.nl \
    --to=houder@xs4all.nl \
    --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).