MIME-Version: 1.0
In-Reply-To: <20100326105007.GU7718@calimero.vinschen.de>
References: <announce.416096c61003252303y69f9eaderea6297b507ad5db9@mail.gmail.com> 	 <20100326105007.GU7718@calimero.vinschen.de>
Date: Sat, 27 Mar 2010 06:06:37 +0000
Message-ID: <416096c61003262306h1b499b79tb786fb2c20e18668@mail.gmail.com>
Subject: Re: [ANNOUNCEMENT] mintty-0.6.1-1
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Corinna Vinschen:
>> - Fall back to /bin/bash rather than /bin/sh if no shell is specified
>> otherwise. This is for the benefit of Windows domain account users,
>> for whom Cygwin setup does not create /etc/passwd entries by default.
>
> Wouldn't it be more helpful to open a MessageBox like this:
>
> "Your user account has no /etc/passwd entry. =C2=A0Ask your lazy administ=
rator
> =C2=A0to add it. =C2=A0And tell her not to forget to add the domain group=
s to
> =C2=A0/etc/group while being at it."

:)

I was just trying to dodge complaints about not getting the full
prompt and .bashrc or .bash_profile not being sourced. Didn't mean to
imply that setup should query the domain user database.

It would have helped though if I'd verified that the change to
/bin/bash as fallback actually makes a difference. It doesn't, because
the Cygwin DLL sets the SHELL variable according to the user's
/etc/passwd entry and to /bin/sh otherwise. And /etc/profile warns
about the missing /etc/passwd entry anyway. So I think I'll revert
that change.

Andy

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