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
X-Authentication-Warning:	slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date:	Tue, 7 Jan 2003 12:31:24 -0500 (EST)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	Tianming Kong <tmkong AT yahoo DOT com>
cc:	cygwin AT cygwin DOT com
Subject:	Re: bash 2.05b-8 doesnot execute .bashrc even if HOME is defined
	and .bashrc is under both ~/ and /
In-Reply-To:	<20030107170352.61252.qmail@web40204.mail.yahoo.com>
Message-ID:	<Pine.GSO.4.44.0301071228290.10883-100000@slinky.cs.nyu.edu>
Importance:	Normal
MIME-Version:	1.0

On Tue, 7 Jan 2003, Tianming Kong wrote:

> --- Max Bowsher <maxb AT ukf DOT net> wrote:
> > Original Message From: "Tianming Kong" <tmkong AT yahoo DOT com>
> > > I'm using cygwin v1.3.18 under Windows XP
> > > Professional. Unfortunately bash 2.05b-8 does not
> > > exectute my startup script ~/.bashrc
> > >
> > > I defined environement variable HOME as "d:\" using
> > > windows control panel. I also copy my .bashrc file to
> > > cygwin / directory.
> >
> > Why / ? Bash certainly doesn't look there. I suggest
> > that you make sure that
> > HOME in the environment and your home dir in
> > /etc/passwd are consistent, and
> > that .bashrc is located in that directory.
> >
> > Max.
>
> I remember reading from some previous email, saying
> that if bash cannot find HOME environment variables
> from everywhere else (like Windows Environment
> variables, /etc/profile, /etc/passwd, etc.), then it
> will try /.
>
> I didn't set home dir in /etc/passwd -- actually I
> didn't set any user entry there. Do you think this
> caused the problem? Previously when I was using an
> older version cygwin 1.3.10 and bash 2.05a(3), it
> worked perfectly fine.
>
> -Tim

Cygwin 1.3.10 didn't have ntsec on by default, so it didn't require your
/etc/passwd to be up to date.  Ntsec became default starting 1.3.13, IIRC.
So now you should update your /etc/passwd (and /etc/group) for everything
to work as intended.
Either that, or turn off ntsec, but be aware that you'll be missing out
on some of the newer features...
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune


--
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/

- Raw text -