Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
To: cygwin AT cygwin DOT com
X-Injected-Via-Gmane: http://gmane.org/
Path: not-for-mail
From: Thor Anders Aarhaug <taarhaug AT nuts DOT edu>
Newsgroups: gmane.os.cygwin
Subject: Re: v1.3.10 - must run bash twice to read .bashrc
Date: 05 Apr 2002 02:10:54 +0200
Lines: 22
Message-ID: <ud6xfovht.fsf@nuts.edu>
References: <5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20020403104228 DOT 00a9c1d8 AT tbri DOT com>
NNTP-Posting-Host: ti500720a080-0958.bb.online.no
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: main.gmane.org 1017965424 3109 80.213.75.190 (5 Apr 2002 00:10:24 GMT)
X-Complaints-To: usenet AT main DOT gmane DOT org
NNTP-Posting-Date: Fri, 5 Apr 2002 00:10:24 +0000 (UTC)
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1

Richard Brust <brust AT tbri DOT com> writes:

| BTW, the $HOME is /home/Administrator, not /home/myloginname, which
| does not seem to be an issue, as this is the way is was on other
| machines.  Additionally, when I do run the "bash" command the second
| time, the $HOME is still the same.

although no expert on this, I experienced this when logged onto a
domain.  when adding a local account with the same login name, it
somehow works.  use "mkpasswd -l > /etc/passwd" to 'activate' the new
account.

not sure why, but it certainly saved me from the 'login <user>' every
time :-)

TA



-- 
Thor Anders Aarhaug
"October 13. 1307 was on a Friday."



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/