From: Donn Cave <donn@u.washington.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: rc and rsh
Date: Wed, 1 Jul 1992 16:49:03 -0400 [thread overview]
Message-ID: <9207012049.AA15956@milton.u.washington.edu> (raw)
| I don't think I understand the problems people are having with rsh and rc.
| Does this function do the 'right thing' ?
| fn rsh host1 host2... { flag= host=$0 {
| ~ $1 -n && { shift ; flag=-n }
| ~ $0 rsh && { host=$1 ; shift }
| eval 'rsh $flag $host rc -lc ''' ^ $* ^ ''''
| } }
Well, I can't resist pointing out that there are some implementation
details involving quotes. That's supposed to be one of the reasons
we like rc, right? Easy, straightforward quoting! Someone who knows
the language better than I maybe can straighten this one out so that
it doesn't require the user to quote the remote command (I think this
is just a matter of discarding the "^"s), and so that the eventual
rc -lc actually does get a quoted string.
But then, what happens when you use this?
; rsh wherever do something
rc not found
; /usr/ucb/rsh wherever whatis path
path=('' /usr/ucb /bin /usr/bin)
; rlogin wherever
welcome to wherever
; whatis rc
/usr/local/bin/rc
Not that there aren't ways to work around the problem. Some of them
made it onto this list recently, and the most workable of them involved
invoking rc differently from /etc/passwd - either as "-rc", or a script
that invokes "rc -l".
Donn Cave, University Computing Services, University of Washington
donn@cac.washington.edu
next reply other threads:[~1992-07-01 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-07-01 20:49 Donn Cave [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-07-01 20:58 rsalz
1992-07-01 19:13 rsalz
1992-07-01 20:59 ` Scott Schwartz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9207012049.AA15956@milton.u.washington.edu \
--to=donn@u.washington.edu \
--cc=rc@hawkwind.utcs.toronto.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).