Re: PATH after creating .bashrc

2010-09-13 Thread John B Brown
If you have access to a UNIX system administrator from the age of Bell Labs and Mr. Thompson's shell, they will know about .surc. Wikipedia is just another side thread on the web of lies, to say nothing about university-restricted definitions pages. Original AT&T and Berkeley manuals from

Re: PATH after creating .bashrc

2010-09-13 Thread Brandon S Allbery KF8NH
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/13/10 00:21 , John B Brown wrote: > You could be correct, but then there was .surc; how does that fit into your > "run commands" general theory? So much for "theory": http://kb.iu.edu/data/abdr.html http://en.wikipedia.org/wiki/Run_commands (with

Re: PATH after creating .bashrc

2010-09-13 Thread Eckhard Wiemann
> Should be /opt/local/bin, not /opt/bin Shure. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: PATH after creating .bashrc

2010-09-12 Thread John B Brown
You could be correct, but then there was .surc; how does that fit into your "run commands" general theory? .surc was used to restrict commands in sh, ksh, csh, and finally bash. If "root" came in there were restrictions you set in .surc. On 9/12/10 8:17 PM, Brandon S Allbery KF8NH wrote: ---

Re: PATH after creating .bashrc

2010-09-12 Thread Brandon S Allbery KF8NH
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/12/10 22:08 , John B Brown wrote: > Wouldn't using .bashrc for it's original purpose be desirable? It was a > method of removing dangerous abilities from remote users; hence the rc, > short for remote commands. Isn't .bashrc the place to put t

Re: PATH after creating .bashrc

2010-09-12 Thread John B Brown
Dear Folk, Wouldn't using .bashrc for it's original purpose be desirable? It was a method of removing dangerous abilities from remote users; hence the rc, short for remote commands. Isn't .bashrc the place to put the detection and restriction of remote access. Shalom, John

Re: PATH after creating .bashrc

2010-09-12 Thread Brandon S Allbery KF8NH
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/11/10 13:24 , Eckhard Wiemann wrote: > Then the "port"-command did not work anymore. I expanded the PATH-variable by > inserting "/opt/bin" and exported it within the .bashrc. Should be /opt/local/bin, not /opt/bin. - -- brandon s. allbery

Re: PATH after creating .bashrc

2010-09-12 Thread Eckhard Wiemann
Ok, it seems that a .bashrc is not required anymore. I added its content to the .profile, removed the .bashrc and .bash_profile, and it works fine. Thanks to Rainer and Bradley! Eckhard > On 2010-09-11 19:24 , Eckhard Wiemann wrote: >> On my macbook with OS X 10.6.4 there was no .bashrc in my

Re: PATH after creating .bashrc

2010-09-11 Thread Rainer Müller
On 2010-09-11 19:24 , Eckhard Wiemann wrote: > On my macbook with OS X 10.6.4 there was no .bashrc in my home dir. MacPorts adds to .profile (or if it exists to .bash_profile). > I created it in order to install aliases and added a .bash_profile > with "source ~/.bashrc", because bash did not rea

PATH after creating .bashrc

2010-09-11 Thread Eckhard Wiemann
Just information: On my macbook with OS X 10.6.4 there was no .bashrc in my home dir. I created it in order to install aliases and added a .bash_profile with "source ~/.bashrc", because bash did not read the .bashrc after starting the terminal. Then the "port"-command did not work anymore. I ex