X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=Yxklxz2InLL6H1hQOJmOz42wUdXaP/v8y7MUZ5hDW1GSrXUlUlMQ+
	Eza8FYtA8INw9HSJkaCoLmkKdFg+8dcmVAkLdY6MCKBzMGs1NQAv4hcSFmpw3INT
	UAnXSUjEYZZwXbmSv+p0fw4AZpeTNz4BWIuradWYPEWUe/ZKZxKRv8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=FLdOyz5d4T1j44p4GAy1VTMvc6E=; b=SgGiCxgu1xmDg8dP3LAgjzD8fse1
	bu+J5STwgE82i29AubWrm7SWhgDfPN3vfmQfBVEqrBRTOcoEPmgfoLvc9l5OdZOI
	WGmze0/Kut0uL38+lrTzzbhg3PZ01V/bgxPZ9k6NvIKVSye8OaqT0cBEzaXvEwgA
	Xp6TxYXZ55eS5TA=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO: calimero.vinschen.de
Date: Wed, 12 Mar 2014 10:27:18 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin64 ignoring /etc/passwd shell field?
Message-ID: <20140312092718.GF8066@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <530D10B2.7050506@jsbc.cc> <20140225215511.GB6065@calimero.vinschen.de> <530D261C.5000403@jsbc.cc> <530D2932.5010906@cygwin.com> <20140226100712.GS2246@calimero.vinschen.de> <531489E4.3000704@cwilson.fastmail.fm> <20140303150531.GD2469@calimero.vinschen.de> <5318CF17.40102@cornell.edu> <20140307103548.GA2542@calimero.vinschen.de> <531F790D.700@breisch.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="Ns7jmDPpOpCD+GE/"
Content-Disposition: inline
In-Reply-To: <531F790D.700@breisch.org>
User-Agent: Mutt/1.5.21 (2010-09-15)

--Ns7jmDPpOpCD+GE/
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mar 11 16:58, Chris J. Breisch wrote:
> Corinna Vinschen wrote:
> >On Mar  6 14:40, Ken Brown wrote:
> >>On 3/3/2014 10:05 AM, Corinna Vinschen wrote:
> >>>On Mar  3 08:55, Charles Wilson wrote:
> >>>>On 2/26/2014 5:07 AM, Corinna Vinschen wrote:
> >>>>>Weird, I was pretty sure we already have an /etc/shells file install=
ed
> >>>>>by default.  Apparently not.  So, shan't we add one?
> >>>>>
> >>>>>   /bin/sh
> >>>>>   /bin/bash
> >>>>>   /bin/dash
> >>>>>   /bin/mksh
> >>>>>   /bin/zsh
> >>>>>   /usr/bin/sh
> >>>>>   /usr/bin/bash
> >>>>>   /usr/bin/dash
> >>>>>   /usr/bin/mksh
> >>>>>   /usr/bin/zsh
> >>>>>
> >>>>>The base-files package would be a good place to be.  David?
> >>>>Currently inetutils-server provides /etc/defaults/etc/shells. If
> >>>>that file is required by base functionality now, then I've no
> >>>>problem removing it and modifying inetutils' postinstall/preremove
> >>>>scripts. But we'll need to synchronize the uploads of
> >>>>inetutils-server-$next and base-files-$next.
> >>>>
> >>>>Speaking of base-files, version 4.1-2 has been in test now for over
> >>>>two years...works fine here and fixes a problem with $TEMP and other
> >>>>"standard" variable names: 4.1-1 set both $TEMP and $temp, but these
> >>>>are not distinguished by native processes, leading to confusion if a
> >>>>native process reset $TEMP (but not $temp).
> >>>I had a problem when running it in an early stage of 64 bit developmen=
t,
> >>>but I don't remember at all what the problem was.  Do you run it on
> >>>64 bit as well?
> >>I think this is what you're trying to remember:
> >>
> >>   http://cygwin.com/ml/cygwin/2013-07/msg00114.html
> >
> >Thanks for finding this one!  Unfortunately David has left us,
> >apparently.
> >
> >Is anybody willing to take over maintainership of the base-files
> >package?
> >
> >
> >Thanks,
> >Corinna
> >
>=20
> It seems no one is interested.
>=20
> I don't know anything about package maintenance for Cygwin, but this
> particular package doesn't look that hard. I'd be willing to give it
> a shot.

Thanks!  Yes, it's really not overly hard to maintain, you just have to
be prepared for some nagging since that package is in the forefront of
user experience when starting Cygwin the first time.

> Is the information on this page (http://cygwin.com/setup.html) up-to-date?

More or less.  The upload now works differently and is described on
https://sourceware.org/cygwin-apps/package-upload.html


Corinna

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

--Ns7jmDPpOpCD+GE/
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTICh2AAoJEPU2Bp2uRE+gRe8P/28Z9IIykZMJ6P94lYTGhUgt
0+Ih9JelzH+Kzk4LAfPI2ahdOkbgzEvp34HkzOsVWHcpt/9Gd2+kvMEJRhZUROfg
90tFw5eZb1eI6ksEz/m0Taus2dUESpKnShmuEVRCZ8Q+EO8Cw3TmtRaco9ekHnZN
i0jV75/L195DgwBIA7GXNjUX6EpJeWGSzje+Rmd1W8rP3j1wsFF3ymYcaqf117+g
KjrgjMgZUFIAyAWwb7UAMsqR3bX/YPO4FSQL9Y7s1o1Y1+Z1qqZOM1/MoWmOtkcf
K0jgAD/ZHlvcpJZF2oNLr9jxRBQSoxlVh5wOz2eatI1hdC7KRl2IwSe4v7b6kmcs
zMRL840dOgfTkhr+jAGMGUnznEztS6abtn29uv5GKcxFX0czpDhDSFkWno3b65Ug
hxkb/lKgEwa2xfYZYHDGL86gD03uZnhvlQW8MZoXFp3nxwCCtroH84+oZ+FO4PdW
w5AyxkL57Kw2LSHaFQRzgoTtA0tHH7ZVOySLs3wwuKdkhIBPenMCTn25nylnqiGx
Ba98dJ8xOCh5ibGsBp8Wb1LnRHiG8agKc52J9My+i6DjqrRIAPaUxffLVBY+N7Kg
OffFXSW7wD4+rMfbFrRDYa2fDq8LcwMOSGACVTUPMBqQYqYZvVf6uHxpR+xBQuNE
E4u9Egmh7QpDfUbZvbNs
=ErTm
-----END PGP SIGNATURE-----

--Ns7jmDPpOpCD+GE/--
