This is the mail archive of the
mailing list for the Cygwin project.
Re: Use of SHELL env var by login
Greetings, Andrew Schulman!
>> 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
>> >> /cygdrive/c/cygwin64/bin/bash
>> >> 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
>> > /etc/group.
>> > In the absence of /etc/passwd, setting SHELL is the right way to set your login
>> > shell.
>> 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
>> comment field.
> OK. First I've heard of that. Can you explain how Ernie would do it?
It's in the user's guide, right where you'd expect it to be ;)
With best regards,
Tuesday, September 27, 2016 18:00:31
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple