Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 10241

Summary: RHL 6.1 "bashrc" and "profile" comments.
Product: [Retired] Red Hat Linux Reporter: swear
Component: setupAssignee: Bill Nottingham <notting>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 6.1CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-10-10 13:54:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description swear 2000-03-19 19:55:04 UTC 
Various "bashrc" & and "profile" files refer to "aliases and functions".
That should instead be "aliases, non-exported functions, and
non-exported variables".

I could go on about the poor shell startup-script scheme (BASH_ENV,
/etc/profile.d, etc.), but I suppose it's a feature, not a bug.
Much of the fault belongs to bash.  They must have worked hard to
make something so simple so confusing, namely to control what
happens at the startup of four combinations of (non-)interactive
and (non-)login shells.  I've got a small "profile" which sets
a couple of variables for "bashrc" and everything else is there
in "exported" and "not exported" sections.
Comment 1 Bernhard Rosenkraenzer 2000-10-10 13:54:03 UTC 
/etc/profile etc. belong to the setup package, assigning
Comment 2 Bill Nottingham 2001-01-29 18:16:41 UTC 
This is not something that I think we'll change ATM.