Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 382 - /etc/skel/.bash_profile is broken
/etc/skel/.bash_profile is broken
Product: Red Hat Linux
Classification: Retired
Component: etcskel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
Depends On:
  Show dependency treegraph
Reported: 1998-12-10 12:59 EST by Patrick J. LoPresti
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1998-12-11 17:52:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Patrick J. LoPresti 1998-12-10 12:59:40 EST
The default .bash_profile shipped with Red Hat 5.1 includes
the following line:


This is broken.  ENV is a Posix 1003.2 concept.  It is
recognized by *any* Bourne shell, not just bash.  As such,
it should not be pointing at a .bashrc file!

This is causing real problems for us in our cross-platform
environment.  Our users have their home directories on a
Linux server, and they usually use bash as their login
shell.  Thanks to this erroneous .bash_profile, ENV ends up
set to $HOME/.bashrc in their environment.

When they run /bin/sh scripts on a non-Linux system, that
system's /bin/sh (if it is Posix compliant) uses the
contents of ENV as an initialization script.  Such a Posix
compliant /bin/sh which is not bash will choke on the
bash-specific data in .bashrc.  The result is that *all*
shell scripts fail.

You can fix this either by eliminating the ENV= line (I do
not see what possible use it has in the first place), or by
using BASH_ENV instead of ENV.

 - Pat
Comment 1 Jay Turner 1998-12-10 13:41:59 EST
Confirmed in version 5.2 as well.
Comment 2 Cristian Gafton 1998-12-11 17:52:59 EST
It is fixed in 5.2

Note You need to log in before you can comment on or make changes to this bug.