This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Use of SHELL env var by login

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.

With best regards,
Andrey Repin
Tuesday, September 27, 2016 14:09:19

Sorry for my terrible english...

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]