From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from milton.u.washington.edu ([128.95.136.1]) by archone.tamu.edu with SMTP id <22544>; Fri, 2 Aug 1991 10:26:49 -0500
Received: by milton.u.washington.edu
	(5.65/UW-NDC Revision: 2.1 ) id AA15378; Fri, 2 Aug 91 08:26:39 -0700
Date: Fri, 2 Aug 1991 10:26:39 -0500
From: Donn Cave <donn@milton.u.washington.edu>
Message-Id: <9108021526.AA15378@milton.u.washington.edu>
To: rc@archone.tamu.edu
Subject: login shells

Speaking of login shells, have we discussed .rcrc vs. rsh yet?  I haven't
tried this with the latest version, but I believe that rc invoked by rshd
doesn't read its startup.  That means that if a program isn't in the machine's
standard execution path, it can't be invoked by name via rsh, without the
assistance of a wrapper script that sets path.  For example.

I'm not saying that it's impossible to cope with, or even hard for an
intermediate shell hacker.  Bash gets it right, that's all.

	Donn Cave, University Computing Services, University of Washington
	donn@cac.washington.edu