Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!
mailrus!uwmcsd1!marque!uunet!mcvax!ukc!stl!grn
From: g...@stl.stc.co.uk
Newsgroups: comp.protocols.tcp-ip
Subject: Specification of Berkeley networking utilities
Message-ID: <845@acer.stl.stc.co.uk>
Date: 20 Oct 88 10:51:37 GMT
Sender: n...@stl.stc.co.uk
Reply-To: g...@stl.stc.co.uk ()
Organization: STC Technology Limited, London Road, Harlow, Essex, UK
Lines: 16
Is there a public domain specification of the Berkeley networking
utilities such as rlogin?
The type of question that I would expect to be able to answer given a
specification is the use made out-of-band data in rlogin for example.
A second and related question is why does the SunOS 4.0 implementation
of rlogin and rsh reject connections with client port numbers in the
range 0-512? My desire for specification of the interoperability
requirements of these networking utilities was partly prompted by the
failure of our local rlogin implementation to interwork with the new
Sun implementation.
Regards,
Gary Nebbett STL, London Road, Harlow, Essex CM17 9NA, UK
g...@stl.stc.co.uk <or> ...uunet!mcvax!ukc!stl!grn <or> PSI%234237100122::GRN
Path: utzoo!utgpu!water!watmath!clyde!att!ucbvax!OKEEFFE.BERKELEY.EDU!bostic
From: bos...@OKEEFFE.BERKELEY.EDU (Keith Bostic)
Newsgroups: comp.protocols.tcp-ip
Subject: Specification of Berkeley networking utilities
Message-ID: <8810232211.AA18006@okeeffe.Berkeley.EDU>
Date: 23 Oct 88 22:11:15 GMT
Sender: dae...@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 9
> Is there a public domain specification of the Berkeley networking
> utilities such as rlogin?
Unfortunately, no; the source code itself, however, while not public
domain, is freely redistributable. This includes inetd, ping, rcp,
rdist, rexecd, rlogin, rmt, route, rsh, rwho, rwhod, and talk among
other things.
Keith Bostic
Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!seismo!sundc!pitstop!sun!
decwrl!ucbvax!snoid.CRAY.COM!hrp
From: h...@snoid.CRAY.COM (Hal Peterson)
Newsgroups: comp.protocols.tcp-ip
Subject: Specification of Berkeley networking utilities
Message-ID: <8810252038.AA02164@rothko.cray.com>
Date: 25 Oct 88 20:38:03 GMT
Article-I.D.: rothko.8810252038.AA02164
References: <1988Oct24.200243.19459@utzoo.uucp>
Sender: dae...@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 13
According to Mike Karels, there are no plans to write specifications
for the protocols used by the r-commands because they were originally
hacks to try out TCP and should die a natural death. If they were
documented, then people would be implementing them, they would
proliferate, and there would be no getting rid of them. The party
line is that 4.3 telnet is better anyway, so we should all be using that.
[The information is from a the question and answer session at a
tutorial Mike Karels gave at the Monterey TCP/IP conference last year.]
--
Hal Peterson / Cray Research / 1440 Northland Dr. / Mendota Hts, MN 55120
hrp%hall.cray....@uc.msc.umn.edu bungia!cray!hrp (612) 681-3145