From: Andrey Repin <anrdaemon@yandex.ru>
To: Andrew Schulman <schulman.andrew@epa.gov>, cygwin@cygwin.com
Subject: Re: Use of SHELL env var by login
Date: Tue, 27 Sep 2016 15:14:00 -0000 [thread overview]
Message-ID: <1737782863.20160927180107@yandex.ru> (raw)
In-Reply-To: <80skub16p5kh2dij73308plbrdcelgdafn@4ax.com>
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 ;)
https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch-desc
--
With best regards,
Andrey Repin
Tuesday, September 27, 2016 18:00:31
Sorry for my terrible english...
--
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
next prev parent reply other threads:[~2016-09-27 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 20:53 Ernie Rael
2016-09-27 2:24 ` Linda Walsh
2016-09-27 5:35 ` Ernie Rael
2016-09-27 11:20 ` Andrew Schulman
2016-09-27 13:13 ` Andrey Repin
2016-09-27 14:48 ` Andrew Schulman
2016-09-27 15:14 ` Andrey Repin [this message]
2016-09-27 16:50 ` Linda Walsh
2016-09-27 17:12 ` Andrey Repin
2016-09-27 17:22 ` Linda Walsh
2016-09-28 4:17 ` Ernie Rael
2016-09-27 17:18 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1737782863.20160927180107@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=schulman.andrew@epa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).