Date: Thu, 21 Nov 1996 09:54:32 +0100 (MET) From: Greg Lehey <grog@lemis.de> To: MDM+aSACODEF%Sacodefense@mcimail.com (MDM) Cc: questions@FreeBSD.org (FreeBSD Questions) Subject: Re: ld.so and emacs problems Message-ID: <199611210854.JAA02159@freebie.lemis.de> In-Reply-To: <53961120211735/0006695923PK1EM@MCIMAIL.COM> from MDM at "Nov 20, 96 04:17:00 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
MDM writes:
> I have completed installing FreeBSD 4.4-Lite from the Walnut Creek 2.1.5
> CD-Rom; there are three problems that I need some help with.
Mail to support is currently being forwarded to
freebsd-questions@freebsd.org. You'll probably get better responses
by sending to that list.
> 3. I "chsh"ed the root shell to Bash (and also of my normal account), but
> paths and aliases written in the either the /root/.bashrc ( or the
> /usr/home/myhome/.bashrc) do not get "accessed" or read or "used". What's
> up?
You need a .bash_profile as well for a login shell. To quote the man
page:
When bash is invoked as a login shell, it first reads and
executes commands from the file /etc/profile, if that file
exists. After reading that file, it looks for
~/.bash_profile, ~/.bash_login, and ~/.profile, in that
order, and reads and executes commands from the first one
that exists and is readable. The --noprofile option may
be used when the shell is started to inhibit this behav-
ior.
When an interactive shell that is not a login shell is
started, bash reads and executes commands from ~/.bashrc,
if that file exists. This may be inhibited by using the
--norc option. The --rcfile file option will force bash
to read and execute commands from file instead of
~/.bashrc.
My .bash_profile contains simply:
if [ -f ~/.bashrc ]; then source ~/.bashrc; fi
Thinking about it, it would seem logical just to link them together.
Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611210854.JAA02159>