X-Recipient: archive-cygwin AT delorie DOT 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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=E0tIPCbbFRNixu8npqFzfgQQsorGLumVjiDIlfIIbgM
	JqrvoVK3xJJYaTVXF7bEN+TsNpgk6vrkehfAnQOaQI73P6No/Lt7FqzCDyWZVu48
	K1UFdYSGQKriNuLKFCcaeoCjs630QsEfctG2dYlsg2K/CD0hrjvF4xR73cn2PMP4
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=onf8urtUkDZ1mTqBYolWLDCnvw8=; b=mrmv8HvAeAGaSfJVl
	t44UmjUkPQkcWvfMm4cStUm5z8cWJe2fz+KLuaTsTicgmioWMI7EBDaMUgv4sco4
	28OlP3i2+GVyx/mVz/YfXHX9Zx7dJex66B6bQifrJL1mUCbv86PgzU2/kZSq/WYm
	g5hW6KZ0hqP0SbvZmsmhx/Xvwk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail.lysator.liu.se
Message-ID: <530E83DC.9090109@lysator.liu.se>
Date: Thu, 27 Feb 2014 01:16:28 +0100
From: Peter Rosin <peda AT lysator DOT liu DOT se>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin64 ignoring /etc/passwd shell field?
References: <6f9492621546f3eeca905b6281314451 AT mykolab DOT ch> <530CAA5C DOT 8060505 AT cygwin DOT com> <530D10B2 DOT 7050506 AT jsbc DOT cc> <20140225215511 DOT GB6065 AT calimero DOT vinschen DOT de> <530D261C DOT 5000403 AT jsbc DOT cc> <530D2932 DOT 5010906 AT cygwin DOT com> <20140226100712 DOT GS2246 AT calimero DOT vinschen DOT de> <530E7E8A DOT 1070303 AT jsbc DOT cc> <530E80E7 DOT 6060201 AT jsbc DOT cc>
In-Reply-To: <530E80E7.6060201@jsbc.cc>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 2014-02-27 01:03, Jim Burwell wrote:
> On 2/26/2014 15:53, Jim Burwell wrote:
>> On 2/26/2014 02:07, Corinna Vinschen wrote:
>>> On Feb 25 18:37, Larry Hall (Cygwin) wrote:
>>>> On 2/25/2014 6:24 PM, Jim Burwell wrote:
>>>>> On 2/25/2014 13:55, Corinna Vinschen wrote:
>>>>>> On Feb 25 13:52, Jim Burwell wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I've noticed after installing an update the Cygwin64 appears to ignore
>>>>>>> the contents of the shell field in /etc/passwd.  I normally run
>>>>>>> /bin/tcsh as my shell, and changing this field used to result in any new
>>>>>>> login shells running tcsh.  Now it just runs bash regardless.
>>>>>>>
>>>>>>> Has something changed?
>>>>>> No.  Works for me.  Do you start `mintty -'?
>>>>>>
>>>>>>
>>>>>> Corinna
>>>>>>
>>>>> Interestingly, it works as expected with mintty, but not with xterm,
>>>>> uxterm, uterm.
>>>>>
>>>>> Was going to try rxvt, but noticed it's not in Cygwin64.
>>>>>
>>>>> It also works when I ssh into my cygwin.
>>>>>
>>>>> So appears to be a problem with xterm and related?
>>>> Yes, and it's a conscious change.  See
>>>> <https://sourceware.org/ml/cygwin-xfree/2014-02/msg00005.html>.
>>> Weird, I was pretty sure we already have an /etc/shells file installed
>>> 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?
>>>
>> Well, at least it wasn't a subconscious decision.  :-)
>>
>> Thanks for the pointer!
>>
>> I agree.  Every distro should have a default /etc/shells with the
>> typical shells in it.
>>
> Or on second thought, the shells themselves should run a post install
> which add themselves to /etc/shells.

Really? What if someone doesn't want to allow e.g. /bin/fish for some
reason (missing from the list btw). It would be terrible to have it
reappear simply because the fish package was updated.

Cheers,
Peter


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