i still use rsh with cvs on occasion.  it's useful for things like
pretending to access a remote repository that's really local since i
can have:

	% ps $$
	PID TT STAT    TIME COMMAND
	664 p1 Ss   0:00.12 -csh (tcsh)
	% echo $CVS_RSH
	CVS_RSH: Undefined variable.
	% grep rsh /etc/inetd.conf 
	#shell          stream  tcp     nowait  root    /usr/libexec/rshd ...
	#shell          stream  tcp6    nowait  root    /usr/libexec/rshd ...
	#kshell         stream  tcp     nowait  root    /usr/libexec/rshd ...
	% cvs -d localhost:/cvsroot co postfix
	cvs server: Updating postfix
	U postfix/.indent.pro
	U postfix/.printfck
	U postfix/0README
	...

since i know that if i rsh to *localhost* to execute a command, i'll
get a connection over a socketpair() and not an inet/inet6 connection.
i also get better performance than over an inet/inet6 connection,
since all that wasteful checksumming isn't performed.  :)

it's tricks like this that allow me to have a local copy of the cvs
binary that's not suid to the owner of the cvs repository, but still
be able check stuff out that i can update/change/delete without having
to involve "privileges".

then again, i'm not claiming to be in the majority.  i'm just
providing a data point.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
werdna@squooshy.com       * "information is power -- share the wealth."