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 17:57:00 -0000	[thread overview]
Message-ID: <fd55e5740e0874afaf89abab3b4f15d1.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <20141103162208.GD28636@calimero.vinschen.de>

>> > 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
>
> It might have been you, but it's not that thread.  I'm referring to
> some discussion a few months ago when I asked for testing the new
> stuff in the snapshots.  My memory for names is really bad, sorry.

February perhaps? I made a similar remark about the output of id then ...

    https://cygwin.com/ml/cygwin/2014-02/msg00545.htm

>> My "nsswitch.conf":
>>
>> passwd:files
>> group: files
>>
>> db_enum: files
>>
>> In short, no problem at my end: id shows the short list (as before ...)
>
> The question would be:  What's the problem with the long list from id?
> Enumerating the builtin accounts is very fast and you shouldn't have
> any downside.  On the upside, *iff* there are files owned by some
> account not listed in /etc/passwd or /etc/group, the additional "db"
> setting would still allow to show the ownership correctly...

Should? :-) I have no doubt that you did an excellent job ... and that it all
very fast ...

Perhaps, it is mere matter of perspective ?????

 - you want to be informed "about what the machine does" ...
 - I am only interested in "my files" (a specific point on the filesystem), a
   point where I have "rucksichtlos" eliminated all references to identities I
   do not care about

(as I noted before, Windows is not really 'my cup of tea')

In short, there is no problem that requires your immediate attention. And I am
happy, that I can still control Cygwin to do it in the "old-fashioned" way.

Sorry.

Regards,

Henri

=====


--
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 17:57 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
2014-11-03 16:22   ` Corinna Vinschen
2014-11-03 17:57     ` Houder [this message]
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=fd55e5740e0874afaf89abab3b4f15d1.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).