Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Subject:	RE: .bashrc not working (and yes I've read the FAQ etc as you'll see)
To:	Cygwin AT cygwin DOT com
Cc:	"Steve Mayes" <mayes DOT s AT UCLES DOT org DOT dot DOT uk>
Message-ID:	<OF61518F88.648A6DF8-ON88256FB3.0005EF0E-88256FB3.00070971@mck.us.ray.com>
From:	Arthur I Schwarz <Arthur_I_Schwarz AT raytheon DOT com>
Date:	Thu, 24 Feb 2005 17:16:50 -0800
MIME-Version:	1.0
X-SPAM:	0.00

Some thoughts which others have thought before me:

  1. /etc/password should reference shell and home to use
  2. /etc/profile is executed at 'login ...'
     a. Note comments on /etc/profile.d
  3. $HOME/.bashrc, $HOME/.inputrc are executed (for bash)
  4. If you use scripts and intend to import environment
     variables, export <name> should be used
     a. and 'source .bashrc' within a script helps
  5. If you use scripts and intend to import aliases
     then you need to supply a separate <shell> file
     for the system to execute (I just did this and
     <sigh> don't remember the steps.
  6. Info bash and read and read and ... helps
  7. Don't forget '#! /bin/bash` or equivalent as first line.

Bottom line, when things go wrong it really takes some
digging. In my case I always (always) do something wrong.
Note that /etc/profile contains information specific to
locating $HOME. After login have you done 'echo $HOME'?

art


Steve wrote:

>Forgive the defensive addendum but I've no wish to be either flamed or
>ignored when I've tried available pathways to solving this.

Must ... resist ... urge ... to .... flame ... }:-)>

>Situation:
>
>.bashrc not working and yes my $home variable is correctly
>defined but I
>put a copy of .bashrc into / anyway just in case.
>The --login and -i switches are used.
>I even used the --rcfile switch and pointed it directly to my .bashrc
>file at which point cygwin just bombs out.
>
>.bashrc file contains only the line
>
>Alias ls='ls -al --color=auto'
>
>I even made .bashrc executable using the command chmod +x
>(just in case)
>but this changed none of the behaviour.   What am I missing.

I'm pretty much missing a proper description of the problem. Whaddaya
mean ".bashrc not working"? And what's "cygwin just bombs out" supposed
to mean - is it some sort of new hacker language or technical term I
didn't pick up on?

What's your entry in /etc/passwd say?

Regards,

Jesper Vad Kristensen


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -