Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!snorkelwacker!think!zaphod.mps.ohio-state.edu!uwm.edu!rutgers!att!laidbak!daveb
From: daveb@i88.isc.com (Dave Burton)
Newsgroups: comp.unix.wizards
Subject: Re: SYS V Bourne Shell .shrc file
Message-ID: <1989Dec22.175637.8362@i88.isc.com>
Date: 22 Dec 89 17:56:37 GMT
References: <1792@ncrcce.StPaul.NCR.COM>
Sender: usenet@i88.isc.com (Usenet News)
Organization: Interactive Systems nee Lachman Associates
Lines: 14

In article <1792@ncrcce.StPaul.NCR.COM> mercer@ncrcce.StPaul.NCR.COM (Dan Mercer) writes:
|... I examined /bin/sh with a binary
|display program looking for undocumented options.  Instead,  I ran
|into the string .shrc. ....
|Other SYSV users,  let me know if you have it.
|Our system consists of two NCR Towers running SYSVR1 and SYSVR2 and
|I have confirmed it's existence on another Tower running SYSVR3.2.

The SVR3.2 sources from AT&T do not have any .shrc processing; only .profile
and /etc/profile are supported. Any sh that has .shrc has been modified by the
vendor and therefore (the use of .shrc) is non-portable.
--
Dave Burton
uunet!ism780c!laidbak!daveb