Thanks to all who replied.
>Taso Hatzi wrote:
>> What made you think the distribution was broken?
I installed Mandrake 6.0 on 20 machines, and I could telnet to every one. (Same for
older distributions: RH 4.2, 5.1, and 5.2.)
I installed 3 Mandrake 6.1 machines, and I could not telnet to a single one. After
every attempt, a new line saying "/usr/sbin/in.telnetd not found" was added to
/var/log/messages. Since I chose a rather bloated installation, I concluded that the
telnet package was broken.
Matthew Vanecek wrote:
>Did the package come with a telnetd (as opposed to in.telnetd)? Had you
>the telnet daemon, it doesn't really matter what you name it, as long as
>that name is reflected in inetd.conf (you're not running telnetd all the
>time, are you?). Actually, you'd be better off relegating telnet to the
>back burner and going with something like ssh.
I didn't check, but I will the next time I install MD6.1. It made more sense to me to
simply install the previous version of telnet, since it had worked for me before.
Plus, I was getting really tired of having to walk down to my basement to perform
trivial keyboard input.
That's good advice (about SSL and not leaving [in.]telnetd running), but this is for
my home network so I'm not worried about it.
So is it the new default to NOT have the telnet daemon running? I was quite surprised
at this turn of events. During installation, I was never asked if I wanted to start
that daemon or not, although I was asked if I wanted to start all the "r" daemons.
Doesn't make much sense to me.
Travis Low - [EMAIL PROTECTED]
MindQ Publishing 11490 Commerce Park Drive #400 Reston VA 20191-1532 USA
http://www.mindq.com
+1 703 262 6616 (direct)
+1 703 716 0237 (fax)
"If you do that, he'll really freak off his doodle!" -- Tiernan Low
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
