My point exactly... Or didn't you see the <G> at the end of that sentence....
Gary Bunker wrote:
> You only need the telnet Daemon running if you intend to telnet into
> your machine. The Client can run without a local daemon, it just needs
> a daemon on the server it wishes to communicate with. Therefore, there
> is no need to install the TelnetD package unless you plan to host
> telnet services.
>
> Unless I'm completely insane and mistaken about all the Unix and VMS
> stuff I've been using for the past 10 years, this is a normal way of
> doing client/server stuff.
>
> On 30 Apr, Russ Johnson wrote:
> > 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
>
> --
>
> -----------
> Nil Carborundum Illegitimi
> http://andysocial.com
