Xref: utzoo comp.unix.i386:3487 comp.protocols.tcp-ip:10552 comp.sources.wanted:10923
Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!uwm.edu!ogicse!littlei!leonardo.intel.com!davidl
From: davidl@leonardo.intel.com (David D. Levine)
Newsgroups: comp.unix.i386,comp.protocols.tcp-ip,comp.sources.wanted
Subject: Re: rsh(1) for System V/386, Lachman TCP/IP
Message-ID: <898@gandalf.littlei.UUCP>
Date: 12 Mar 90 16:57:01 GMT
References: <11335@encore.Encore.COM> <M342BY8xds13@ficc.uu.net>
Sender: news@littlei.UUCP
Organization: Intel IMSO Tech Pubs
Lines: 13

> > This is for Lachman TCP/IP, if that matters. For some reason Lachman TCP/IP
> > doesn't come with a remote shell program that I can find anywhere... just
> > rlogin.
> 
> Try nsh.  LAI couldn't call it rsh because of a name conflict with the SysV
> restricted shell.  BTW, it uses rcmd(), not rexec().

In Intel's System V/386 v3.2 with Lachman TCP/IP, the "rsh" command is
called "rcmd".  Isn't name space pollution the pits?

- David D. Levine, Intel IMSO Tech Pubs
  davidl@leonardo.intel.com
  "Mr. LaForge, when I turned this ship over to you, it was in one piece!"