Um, yes you do. A client without a daemon is like a key without a lock. <G>
Either way. Linux does not use "telnetd", it uses the superserver "inetd"
and then that calls "in.telnetd" to start the inbound login session. That
is what is installed by the telnet-server rpm.
On my systems, the "telnetd" is a subdirectory in /usr/lib, that contains
the binary "login", which will be needed no matter whether you allow
inbound telnet or not.
Russ
Gary Bunker wrote:
> Of course the client and server are separate packages. However,
> telnetd is the telnet Daemon, and is therefore part of the SERVER. You
> don't need a daemon for a client.
>
> On 30 Apr, John Aldrich wrote:
> > On Sun, 30 Apr 2000, you wrote:
> >>
> >> But then how come I have telnetd but don't have telnet-server?
> >>
> > Listen closely as I repeat myself: THE TELNET SERVER IS A
> > SEPARATE PACKAGE!!!! Just because you have "telnetd" does
> > NOT mean you have telnet-server installed! That is a
> > SEPARATE PACKAGE FROM TELNET!!! Apparently, Mandrake, in
>
> --
>
> -----------
> Nil Carborundum Illegitimi
> http://andysocial.com
