Xref: utzoo comp.sys.dec:4633 comp.unix.ultrix:5485 comp.protocols.nfs:1581 alt.sys.sun:2217
Path: utzoo!utgpu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!news.funet.fi!funic!santra!news
From: jkp@cs.HUT.FI (Jyrki Kuoppala)
Newsgroups: comp.sys.dec,comp.unix.ultrix,comp.protocols.nfs,alt.sys.sun
Subject: Re: rexd functionality for Ultrix 3.1 and PC-NFS?
Message-ID: <1990Dec2.194659.504@santra.uucp>
Date: 2 Dec 90 19:46:59 GMT
References: <979@iiasa.UUCP> <3489@jaytee.East.Sun.COM>
Sender: news@santra.uucp (Cnews - USENET news system)
Reply-To: jkp@cs.HUT.FI (Jyrki Kuoppala)
Organization: Helsinki University of Technology, Finland
Lines: 16
In-Reply-To: geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)

In article <3489@jaytee.East.Sun.COM>, geoff@hinode (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:
>On the PC-NFS clients, you need to think about the differences
>between rsh and on/rex. The added value that on/rex brings is
>that it arranges for your current directory context to get mounted
>on the target system so that "cd foo; on bar bletch" will run the
>command bletch on the system bar within the directory foo.

One added value is also that you don't have to worry about those
.rhosts files and passwords rshd for some reason wants, as rexd will
happily execute any correctly formed request for any user id != 0 from
any host on the same TCP/IP network, with no overhead of
authentication or silly things like the demanding of a password.

That's open networking, for sure.

//Jyrki


Brought to you by Super Global Mega Corp .com