search for: 30mumble

$ man bash (INVOCATION) When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, 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

...orks. > > So ya, got it to work, but knowing the cascade of inclusions is > important. root is as important to me as my normal user. > Yes. If you are going to be playing around as root, then you really should know the consequences of what you are doing. When I started using Unix 30mumble years ago, the perceived wisdom was *always* invoke su as /bin/su, those where the days when '.' was frequently in a users path and some nasty user might leave scripts called 'su' lying around waiting for an admin to occidentally execute them. Second, invoke it as '/bin/su -...

...it to work, but knowing the cascade of inclusions is >> important. root is as important to me as my normal user. >> > > Yes. If you are going to be playing around as root, then you really > should know the consequences of what you are doing. When I started > using Unix 30mumble years ago, the perceived wisdom was *always* invoke > su as /bin/su, those where the days when '.' was frequently in a users > path and some nasty user might leave scripts called 'su' lying around > waiting for an admin to occidentally execute them. Second, invoke it >...