On Fri, 30 Mar 2001, otto porter wrote: op> op> op> RE: suse 7.1 op> op> How can local configuration options such as op> op> alias blah 'blahblah' op> op> be done, and WHERE? op> there are numerous places, most commonly /etc/profile, ~/.profile and ~/.alias (which is called through .profile or .bashrc), plus some others. You'll also find numerous examples within the /etc/profile file which will show you how they should be written. op> Also, where are my boot commands op> for ipx_configure and ncpmount op> supposed to be placed. op> usually /etc/rc.d which is linked to /usr/sbin op> op> This is starting to seem more like windows op> all over again. Where is the ability to modify op> the configuration which used to be a linux op> strong point. op> op> Are the .cshrc, .login, and .alias files ever op> used anymore. op> Yeah, there all still used, but they need to be called by the users .profile connect script like the following does <snip from ~/.profile> test -z "$PROFILEREAD" && . /etc/profile test -f $HOME/.bashrc && . $HOME/.bashrc <end snip> The above lines are at the top of the users .profile file. The first line checks to see if the /etc/profile file was read, if so then the $PROFILEREAD string length should be greater then 0, if it hasn't been read ($PROFILEREAD is empty) then it will read it. The second part checks to see if the user has a .bashrc file in their home directory, if so, it reads it. At the bottom of my .bashrc file, I have the following added <snip from ~/.bashrc> test -f $HOME/.alias && . $HOME/.alias <end snip> WHich calls my personal aliases that arn't included in the systems /etc/profile file. op> thanks, Otto Porter op> op> -- S.Toms - tomas@primenet.com - www.primenet.com/~tomas SuSE Linux v7.0+ - Kernel 2.2.18 "If the King's English was good enough for Jesus, it's good enough for me!" -- "Ma" Ferguson, Governor of Texas (circa 1920)