> > I use bash shell.
> > I found /etc/bash.bashrc file.
> > What should I use this file for??
>
> You should leave it alone, and create a private ~/.bashrc in /root if you
> want to customize the environment for user root. /etc/bash.bashrc should be
> used for systemwide customizations that affect all uses, and even then you
> are better off creating a separate /etc/bash.bashrc-local to contain your
> local changes and modifying /etc/bash.bashrc to call your local script.
> /etc/bash.bashrc is fair game for the Linux distributions to change at any
> time.
Dave is right.
Avoid changing any /etc/*sh*rc* or /etc/*profile* files.
FURTHERMORE, /etc/bash.bashrc was installed from a package.
Changing it will leave you vulnerable to the dreaded
"modification management monster". (It can get overlaid.)
On CMS, we made one small change to SYSPROF EXEC and that is to
effect calling our LCLPROF EXEC which resides on a different disk.
The change is isolated to a "fragment" which gets inserted into
each new SYSPROF that IBM ships us (with each release of CMS).
Same should be done with shell profiles on Linux (or any Unix).
On Unix, long before Linux was popular, we made one small change
to /etc/profile (and to /etc/csh.login) to call ("source") our own
/usr/local/etc/profile (similar hack for CSH). Every new Unix system
would have a fresh vendor-supplied /etc/profile needing attention,
so the change was kept minimal and designed for automation.
The point was to minimize the work needed for each new OS release
both in terms of the steps required when installing and in the
viability of our customzed profiles and scripts. There was some
discussion a couple weeks back on this list about shells and that
BASH is standard on Linux. I think my position was less popular:
Don't box yourself into any single shell, not even BASH.
Interoperability is vital. Linux or Unix, X or "text mode",
any of the shells (BASH, TCSH, KSH, ASH, ZSH), all should function.
Defend your options!
Find out what the basic fundamentals are and cling to them.
Use that reliable bed-rock to build your systems and networks.
[Whoah! Feeling a bit patriotic, I guess. Was in DC last week.]
-- R;
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
