On Mon, 9 Apr 2001, Aaron Brashears wrote:
> Hm, interesting. It's the only way I've found to keep things straight
> when using ssh. I don't actually run any scripts in my .bashrc - the
> contents are:
>
> . ~/.env
>
> And .env sets the environment.
I use ssh daily and don't have any problems
On Mon, Apr 09, 2001 at 12:49:56PM -0500, Joi Ellis wrote:
> On Mon, 9 Apr 2001, Aaron Brashears wrote:
> >
> > $ cat .bash_profile >> .bashrc
> > $ rm .bash_profile
> > $ ln -s .bashrc .bash_profile
>
> No, no no. Don't DO this! Now you're running everything multiple times!
Hm, interesting.
On Mon, 9 Apr 2001, Aaron Brashears wrote:
> Be sure to copy anything important out of .bash_profile into
> .bashrc. Of course, if you just append the contents, it will save some
> time.
Uh. This is NOT a good idea. .bashrc is run whenever a child shell
is launched. IE every time a command yo
Since you're using linux, I'll give my examples assuming you're using
bash as your primary shell. I've usually had the best luck setting
environment variables in my .bashrc file and deleting my .bash_profile
and then setting .bash_profile as a symlink to my .bashrc.
To see what I'm talking about,
You can either set the path in the system boot up script or better still if
you set it in your profile file. In linux your profile files will be in
your home directory for instane if your login userid is liuchao, then your
home directory will be /home/liuchao. look for profiles by typing ls -a at
