This is the mail archive of the
mailing list for the Cygwin project.
Re: Use of SHELL env var by login
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Andrew Schulman <schulman dot andrew at epa dot gov>, cygwin at cygwin dot com
- Date: Tue, 27 Sep 2016 14:12:37 +0300
- Subject: Re: Use of SHELL env var by login
- Authentication-results: sourceware.org; auth=none
- Authentication-results: smtp1p.mail.yandex.net; dkim=pass email@example.com
- References: <firstname.lastname@example.org> <email@example.com>
- Reply-to: cygwin at cygwin dot com
Greetings, Andrew Schulman!
>> I just moved the cygwin installation. The "last" peculiarity I ran into
>> was that the login shell, with the shortcut "F:\cygwin64\bin\mintty.exe
>> -i /Cygwin-Terminal.ico -", a ps showed
>> instead of /usr/bin/bash
>> I tracked this down the the windows setting for SHELL, the one you get
>> to from windows' SystemProperties dialog, which was
>> C:/cygwin64/bin/bash. The /etc/passwd file specifies /bin/bash.
>> Is this expected behavior? (Though I can see why SHELL is there and I'd
>> need to change it)
> /etc/passwd is deprecated. Since Cygwin 2.5 IIRC, Cygwin no longer looks for it,
> getting information about users directly from the operating system instead.
> Unless you have a special need for it, you should remove it. Same for
> In the absence of /etc/passwd, setting SHELL is the right way to set your login
One of the right ways, I'd say.
If your aim is the integration of both environments, you MAY set variables,
but if you then start a login shell, they may be voided by the startup scripts.
I would advise using "more other" ways to configure Cygwin, i.e. using SAM DB
With best regards,
Tuesday, September 27, 2016 14:09:19
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple