Looks like telnet isn't available as part of the standard install (or
if it is, I can't find it) ... host of other changes to installer &
packages available. I suppose I'll get used to it (after I figure out
where everything is), but at the moment deploying 5.5 is looking
better & better.

I can see many google searches in my future, or maybe even a manual :-(

I imagine telnet has been dropped in favour of ssh.

"Ross Ferris" <rossf (AT) stamina (DOT) com.au> wrote
telnet
at a # prompt shows the telnet client is already loaded.

You're needing a file called something like telnet-server*.rpm
{but not *src.rpm or even *.srpm} from your install dvd media.
If you're very very sure it is not found there, try using the rpm from an
older version of redhat. {I used to use old redhat 9's mc rpm on
rhel3, never had a problem...} {Swiping old rpms doesn't always work,
though; if you hate CUPS printing, you can't use LPRng rpms since
about rhel3 (rhel4?} since it needs library lib.so2}

I've got a whole whitepaper on redhat version-differences "gotcha's";
for example you should also manually install the mc*.rpm after
initial system load, if doing which mc doesn't see that command.
Sadly, general linux post-install tweaks are just horribly off-topic for
this newsgroup, otherwise we
could discuss how to disable all but one of your cpu cores on
motherboard at linux bootup, and junk like that... Or how to
get cups configured so you can administer it from any winbox on the lan...

Oh, even if the telnet-server is loaded,
as in you've done cd /mnt/whatever
then rpm -ivh telnet-server*rpm
you still do not have it enabled. Go vi the file /etc/xinetd.d/telnet
and change the line to say disable=no
then restart xinetd or reboot linux to make the vi changes take effect.

On Oct 28, 1:46*am, "Frank Winans" <fwin... (AT) sbcglobal (DOT) net> wrote:
Thanks.

I think THEY have really stuffed up with this distro (of course, it
"might" be me :-) Even admin tools like the GUI interface to services
doesn't appear to be loaded, so I'm ploughing through as many
"optional" modules as I can to see where all the "stuff" is that we
use from time to time

Change. Gotta love it!

On Oct 27, 6:05*pm, Pete Howell <boredbypolit... (AT) gmail (DOT) com> wrote:
Yes, SSH is available by default

Ross Ferris wrote:
Insecure services and lesser-user apps got moved out to optional
packages. I thought they made these changes Years ago. Where U been?
This reduces the size of the core install and improves performance.
The Linux desktop is virtually dead so it's unusual for people to want
to use the X GUI. The system is usually installed as a server, not a
desktop client, with a web UI for management. As to Telnet, in the
view of many there's absolutely no reason to use a decades-old
protocol that is a known and easy security risk when there are secure
options available and easy to use.

Just wish there wasn't so much of it, eh?

T

"Tony Gravagno" wrote
But many's the time we've gotten a new client that's been using
Microsoft's telnet client to access their d3 server for _years_
and gotten away with it, somehow. After using proper terminal
emulators for years, I really really hate using the d3 full screen
editor from a Microsoft telnet client!

Erm, didn't some countries at least _used_ to forbid using encrypted
protocols like ssh? Hence the PUTTYTEL.EXE on the putty
download page -- is regular PUTTY.EXE but with the ssh stripped out.

"Frank Winans" wrote:

I completely forgot about such things but you're right. OK, when I
say "absolutely no reason", I'm wrong. Change that to "absolutely no
reason for a site in the USA, or other countries not legally
restricted from SSH cryptography".

Since we're on this topic, not long ago I posted a note here asking
about tunneling so that I could do SSH with D3NT and use a telnet
client over a secure pipe. Kevin Powick provided valuable insight and
I've been able to implement this functionality. Except for the
cryptography issue, that put a final nail in the Telnet coffin as far
as I'm concerned.

T