RE: /etc/profile in BASH

RE: /etc/profile in BASH

[Earnie Boyd]

--- "Masterson, Dave" <dmasters@rational.com> wrote:
> 
> > > 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)?

You're right.  Removing the test for ~/.profile from /etc/profile causes only
~/.bash_profile to be executed.

I've modified my /etc/profile removing both tests.
I've created a ~/.bash_profile which tests for the ~/.bashrc and sources it if
found.

Cheers,

=====
Earnie Boyd
mailto:earnie_boyd@yahoo.com

---         < http://earniesystems.safeshopper.com >         ---
--- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > ---
---   Minimalist GNU for Windows < http://www.mingw.org/ >   ---

__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: /etc/profile in BASH

[Masterson, Dave]

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

RE: /etc/profile in BASH

[Earnie Boyd]

--- "Masterson, Dave" <dmasters@rational.com> wrote:
> I gotta learn to read more carefully... :-\
> 
> One more time -- having these two lines in /etc/profile means that
> ~/.profile will be (potentially) sourced twice 

IMO, the test for ~/.profile should be removed.

> (~/.bashrc might be as well depending on how the user handles it in >
~/.profile).  

IMO, setup should be modified to put the test for ~/.bashrc in ~/.bash_profile.

> This could have
> unintended consequences where people *add-to* instead of *set* their
> environment variables -- particularly PATH.  This could double the length of
> the PATH variable and slow down access to commands (particularly if one or
> more items on the PATH is a network share).
> 

I agree.  Caution has to be taken.  'Course, caution always has to be taken.

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

Cheers,

=====
Earnie Boyd
mailto:earnie_boyd@yahoo.com

---         < http://earniesystems.safeshopper.com >         ---
--- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > ---
---   Minimalist GNU for Windows < http://www.mingw.org/ >   ---

__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: /etc/profile in BASH

[Earnie Boyd]

--- Erik Nolte <enolte@campuspipeline.com> wrote:
> > > I didn't realize that a login BASH doesn't execute ~/.bashrc.  Be that
> as it
> > > may, I think it should be the decision of ~/.bash_profile (or
> ~/.profile)
> > > whether to execute ~/.bashrc -- *NOT* /etc/profile.  Putting this into
> > > /etc/profile makes it too BASH-centric.  What about the [T]CSH users?
> Also,
> > > what about ~/.bash_login files (as described in the MAN page)?
> > >
> >
> > IIRC [t]csh doesn't user /etc/profile.  Use the source, Luke. (tm)
> 
> But sh and ksh do.  I don't want my sh's executing .bashrc and failing on
> things like alias and 'export var=..."
> 

Uhm, only if they are executing the login code.  AFAICT there isn't a way to do
that in Cygwin with the provided sh (except for maybe renaming it as -sh).  As
for ksh I don't have the source for it but you would have to make it think it
were in login state for it to even look at /etc/profile or ~/.profile.  Those
files only get executed when the shell is used for "login".

That being said, as system admin you may change it to whatever you wish.  You
can even supply patches to the sources that create /etc/profile.  They will be
considered if they are appropriate patches.

Cheers,

=====
Earnie Boyd
mailto:earnie_boyd@yahoo.com

---         < http://earniesystems.safeshopper.com >         ---
--- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > ---
---   Minimalist GNU for Windows < http://www.mingw.org/ >   ---

__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: /etc/profile in BASH

[Masterson, Dave]

I gotta learn to read more carefully... :-\

One more time -- having these two lines in /etc/profile means that
~/.profile will be (potentially) sourced twice (~/.bashrc might be as well
depending on how the user handles it in ~/.profile).  This could have
unintended consequences where people *add-to* instead of *set* their
environment variables -- particularly PATH.  This could double the length of
the PATH variable and slow down access to commands (particularly if one or
more items on the PATH is a network share).

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), the user does not have to do any testing
in his .profile to handle BASH vs. KSH idiosyncracies.  With SAMBA, NFS, and
such, it is possible that the user has one and only one HOME directory that
is used on all systems.  Sourcing ~/.profile out of /etc/profile could cause
the wrong setup to occur (remember the previous paragraph).

> -----Original Message-----
> From: Earnie Boyd [ mailto:earnie_boyd@yahoo.com ]
> Sent: Friday, September 29, 2000 11:36 AM
> To: Masterson, Dave
> Cc: 'cygwin@sources.redhat.com'
> Subject: RE: /etc/profile in BASH
> 
> 
> --- "Masterson, Dave" <dmasters@rational.com> wrote:
> > Doh! You're right!  Memory is the second thing to go as you 
> > get older...
> > 
> > However, I still don't think these two lines to run 
> > ~/.profile and ~/.bashrc
> > belong in /etc/profile (neither does "cd $HOME").  They subvert the
> > "--noprofile" and "--norc" options to BASH.
> > 
> 
> Subvert --noprofile?  No, /etc/profile wouldn't be sourced.  
> Subvert --norc? 
> No, /etc/profile isn't sourced unless it's login and 
> ~/.bashrc isn't sourced if
> it is login.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: /etc/profile in BASH

[Erik Nolte]

> > I didn't realize that a login BASH doesn't execute ~/.bashrc.  Be that
as it
> > may, I think it should be the decision of ~/.bash_profile (or
~/.profile)
> > whether to execute ~/.bashrc -- *NOT* /etc/profile.  Putting this into
> > /etc/profile makes it too BASH-centric.  What about the [T]CSH users?
Also,
> > what about ~/.bash_login files (as described in the MAN page)?
> >
>
> IIRC [t]csh doesn't user /etc/profile.  Use the source, Luke. (tm)

But sh and ksh do.  I don't want my sh's executing .bashrc and failing on
things like alias and 'export var=..."

- Erik


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: /etc/profile in BASH

[Earnie Boyd]

--- "Masterson, Dave" <dmasters@rational.com> wrote:
> Doh! You're right!  Memory is the second thing to go as you get older...
> 
> However, I still don't think these two lines to run ~/.profile and ~/.bashrc
> belong in /etc/profile (neither does "cd $HOME").  They subvert the
> "--noprofile" and "--norc" options to BASH.
> 

Subvert --noprofile?  No, /etc/profile wouldn't be sourced.  Subvert --norc? 
No, /etc/profile isn't sourced unless it's login and ~/.bashrc isn't sourced if
it is login.

-8<-
> 
> IIRC [t]csh doesn't user /etc/profile.  Use the source, Luke. (tm)
> 
> Cheers,
> 


=====
Earnie Boyd
mailto:earnie_boyd@yahoo.com

---         < http://earniesystems.safeshopper.com >         ---
--- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > ---
---   Minimalist GNU for Windows < http://www.mingw.org/ >   ---

__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: /etc/profile in BASH

[Masterson, Dave]

Doh! You're right!  Memory is the second thing to go as you get older...

However, I still don't think these two lines to run ~/.profile and ~/.bashrc
belong in /etc/profile (neither does "cd $HOME").  They subvert the
"--noprofile" and "--norc" options to BASH.

-----Original Message-----
From: Earnie Boyd [ mailto:earnie_boyd@yahoo.com ]
Sent: Friday, September 29, 2000 11:26 AM
To: Masterson, Dave; 'cygwin@sources.redhat.com'
Subject: RE: /etc/profile in BASH


--- "Masterson, Dave" <dmasters@rational.com> wrote:
> I didn't realize that a login BASH doesn't execute ~/.bashrc.  Be that as
it
> may, I think it should be the decision of ~/.bash_profile (or ~/.profile)
> whether to execute ~/.bashrc -- *NOT* /etc/profile.  Putting this into
> /etc/profile makes it too BASH-centric.  What about the [T]CSH users?
Also,
> what about ~/.bash_login files (as described in the MAN page)?
> 

IIRC [t]csh doesn't user /etc/profile.  Use the source, Luke. (tm)

Cheers,

=====
Earnie Boyd
mailto:earnie_boyd@yahoo.com

---         < http://earniesystems.safeshopper.com >         ---
--- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > ---
---   Minimalist GNU for Windows < http://www.mingw.org/ >   ---

__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: /etc/profile in BASH

[Earnie Boyd]

--- "Masterson, Dave" <dmasters@rational.com> wrote:
> I didn't realize that a login BASH doesn't execute ~/.bashrc.  Be that as it
> may, I think it should be the decision of ~/.bash_profile (or ~/.profile)
> whether to execute ~/.bashrc -- *NOT* /etc/profile.  Putting this into
> /etc/profile makes it too BASH-centric.  What about the [T]CSH users?  Also,
> what about ~/.bash_login files (as described in the MAN page)?
> 

IIRC [t]csh doesn't user /etc/profile.  Use the source, Luke. (tm)

Cheers,

=====
Earnie Boyd
mailto:earnie_boyd@yahoo.com

---         < http://earniesystems.safeshopper.com >         ---
--- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > ---
---   Minimalist GNU for Windows < http://www.mingw.org/ >   ---

__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: /etc/profile in BASH

[Masterson, Dave]

I didn't realize that a login BASH doesn't execute ~/.bashrc.  Be that as it
may, I think it should be the decision of ~/.bash_profile (or ~/.profile)
whether to execute ~/.bashrc -- *NOT* /etc/profile.  Putting this into
/etc/profile makes it too BASH-centric.  What about the [T]CSH users?  Also,
what about ~/.bash_login files (as described in the MAN page)?

-----Original Message-----
From: Earnie Boyd [ mailto:earnie_boyd@yahoo.com ]
Sent: Friday, September 29, 2000 5:04 AM
To: Masterson, Dave; 'cygwin@sources.redhat.com'
Subject: Re: /etc/profile in BASH


--- "Masterson, Dave" <dmasters@rational.com> wrote:
> Question:
> 
> In Cygwin 1.1, why are the last two lines of the installed /etc/profile
the
> following?
> 
> 	test -f ./.profile && . ./.profile
> 	test -f ./.bashrc && . ./.bashrc
> 
> As described in the BASH MAN page, it would seem that BASH does this
already
> after reading /etc/profile.  Is this required because of the
implementation
> of Cygwin on MS-Windows?
> 

IMO, the test -f ./.profile && . ./.profile isn't needed, it will get
executed
by bash anyway.  The test -f ./.bashrc && . ./.bashrc is needed because when
bash is in login state it doesn't process ~/.bashrc.  In login state both
/etc/profile and ~/.profile are executed.  In non-login state /etc/profile
and
~/.profile aren't executed but ~/.bashrc is but IIRC only for the
interactive
state.

Cheers,

=====
Earnie Boyd
mailto:earnie_boyd@yahoo.com

---         < http://earniesystems.safeshopper.com >         ---
--- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > ---
---   Minimalist GNU for Windows < http://www.mingw.org/ >   ---

__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: /etc/profile in BASH

[Earnie Boyd]

--- "Masterson, Dave" <dmasters@rational.com> wrote:
> Question:
> 
> In Cygwin 1.1, why are the last two lines of the installed /etc/profile the
> following?
> 
> 	test -f ./.profile && . ./.profile
> 	test -f ./.bashrc && . ./.bashrc
> 
> As described in the BASH MAN page, it would seem that BASH does this already
> after reading /etc/profile.  Is this required because of the implementation
> of Cygwin on MS-Windows?
> 

IMO, the test -f ./.profile && . ./.profile isn't needed, it will get executed
by bash anyway.  The test -f ./.bashrc && . ./.bashrc is needed because when
bash is in login state it doesn't process ~/.bashrc.  In login state both
/etc/profile and ~/.profile are executed.  In non-login state /etc/profile and
~/.profile aren't executed but ~/.bashrc is but IIRC only for the interactive
state.

Cheers,

=====
Earnie Boyd
mailto:earnie_boyd@yahoo.com

---         < http://earniesystems.safeshopper.com >         ---
--- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > ---
---   Minimalist GNU for Windows < http://www.mingw.org/ >   ---

__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: /etc/profile in BASH

[Masterson, Dave]

Example?  Why would it be?  And if it is, wouldn't BASH use the new value to
determine where to get ~/.profile and ~/.bashrc?  (I should test that,
but...)

Point is that doing this in /etc/profile subverts --noprofile and --norc
options in BASH.

-----Original Message-----
From: DJ Delorie [ mailto:dj@delorie.com ]
Sent: Thursday, September 28, 2000 1:04 PM
To: dmasters@Rational.Com
Cc: cygwin@sources.redhat.com
Subject: Re: /etc/profile in BASH



> As described in the BASH MAN page, it would seem that BASH does this
already
> after reading /etc/profile.  Is this required because of the
implementation
> of Cygwin on MS-Windows?

It's in case $HOME is set or changed by /etc/profile.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: /etc/profile in BASH

[DJ Delorie]

> As described in the BASH MAN page, it would seem that BASH does this already
> after reading /etc/profile.  Is this required because of the implementation
> of Cygwin on MS-Windows?

It's in case $HOME is set or changed by /etc/profile.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

/etc/profile in BASH

[Masterson, Dave]

Question:

In Cygwin 1.1, why are the last two lines of the installed /etc/profile the
following?

	test -f ./.profile && . ./.profile
	test -f ./.bashrc && . ./.bashrc

As described in the BASH MAN page, it would seem that BASH does this already
after reading /etc/profile.  Is this required because of the implementation
of Cygwin on MS-Windows?

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