public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: HEADSUP: New getent tool to read passwd and group data
Date: Thu, 20 Feb 2014 19:38:00 -0000	[thread overview]
Message-ID: <20140220193814.GU2246@calimero.vinschen.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]

Hi guys,


I just uploaded the new getent package and sent the announcement,

I'm repeating myself here because this is really important and I'm
not sure everybody on this list reads the cygwin and cygwin-announce
lists.

In short, we want to get rid of the requirement to maintain /etc/passwd
and /etc/group files, per
http://cygwin.com/ml/cygwin/2014-02/msg00306.html

In future, tools and scripts, especially service installation helper
scripts like my ssh-host-config, must not rely on being able to grep
user and group information from /etc/passwd and /etc/group.

Rather, the scripts should be changed to use the getent tool as soon
as possible.  Usage for checking passwd:

  $ getent passwd <username...>

I'd like to ask all maintainers providing such scripts, including
myself, to look into their packages and fix them to use the getent tool.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2014-02-20 19:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 19:38 Corinna Vinschen [this message]
     [not found] ` <025d01cf2f2d$014b0040$03e100c0$@ieee.org>
2014-02-21 20:27   ` Corinna Vinschen
2014-02-21 21:10     ` Corinna Vinschen
2014-02-21 21:37       ` Corinna Vinschen
2014-02-21 21:21     ` Pierre A. Humblet
2014-02-21 21:42       ` Corinna Vinschen
2014-02-23 10:32         ` 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=20140220193814.GU2246@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-apps@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).