Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: From: "Masterson, Dave" To: "'Earnie Boyd'" Cc: "'cygwin@sources.redhat.com'" Subject: RE: /etc/profile in BASH Date: Fri, 29 Sep 2000 12:41:06 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" > > Also, in order to be compatible with other UNIX system > > shells (Kshell), a user may have setup ~/.profile > > particularly for KShell and ~/.bash_profile > > particularly for BASH. Since BASH will not read > > ~/.profile if it finds ~/.bash_profile (or ~/.bash_login), > > I just tested this. Bash reads both ~/.profile and ~/.bash_profile > or ~/.bash_login. If both ~/.bash_profile and ~/.bash_login are > present then only ~/.bash_profile is executed. If true, that sounds like a bug in BASH. AFAIK, ~/.bash_profile (and ~/.bash_login) were setup to provide a simple way of ensuring that special BASH functionality could be isolated from other shells. According to the BASH man page, after /etc/profile on login, BASH is only supposed to read *one of* ~/.bash_profile, ~/.bash_login, and ~/.profile (in that order). Are you sure your test wasn't skewed because of the "source" in /etc/profile (or elsewhere)? -- David Masterson * Rational Software * 18880 Homestead Rd. * Cupertino, CA 95014 * (408) 863-5150 * dmasters@rational.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com