Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!crdgw1!crdos1!davidsen
From: davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr)
Newsgroups: comp.unix.wizards
Subject: Re: SYS V Bourne Shell .shrc file
Message-ID: <1959@crdos1.crd.ge.COM>
Date: 27 Dec 89 14:08:41 GMT
References: <1792@ncrcce.StPaul.NCR.COM> <1864@sauron.Columbia.NCR.COM> <1803@ncrcce.StPaul.NCR.COM>
Organization: GE Corp R&D Center, Schenectady NY
Lines: 20
Reply-exos:@crdgw1:To: davidsen@crdos1.crd.ge.com (bill davidsen)


  Multiple startups are interesting. Since I have several maintenance
logins on machines I administrate, and must sometimes use sh rather than
ksh, I have my hierarchy set up like this:
	.profile ends with:
		if [ -f .kshrc ]; then ENV=$HOME/.kshrc; fi
	.kshrc ends with:
		if [ -f local.ksh ]; then . ./local.ksh; fi

  Then in the maintenance logins the profile is ". /u/staff/davidsen/.profile"
and the .kshrc is ". ~davidsen/.kshrc". The local.ksh is always tailored
to the needs of the id under which I'm operating. This allows me to
define a large set of aliases, macros, and symbols to keep a consistent
user interface, while still allowing me in if for some reason sh is
being used.
-- 
bill davidsen	(davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen)
"The world is filled with fools. They blindly follow their so-called
'reason' in the face of the church and common sense. Any fool can see
that the world is flat!" - anon