Thomas Cameron wrote:

On Mon, 2007-01-01 at 01:21 +0800, edwardspl@ita.org.mo wrote:

...

Dear You,

How can we install FC6 with all packages ( everything ) in Text mode ? Eg : there is no any message by using "rpm -qa | grep xinetd.d"...

Edward.

There is no "everything" installation any more. You can come close by right-clicking each group during a graphical mode installation and choosing "install all packages in this group" or some such nonsense.

What I usually do is do a basic installation and then use yum to install anything else I need.

Look at the man page for yum, specifically at the grouplist and groupinstall options.

xinetd will automatically be installed if you install a service which depends on it. You can also just issue the command

yum install telnet-server

That should install the telnet daemon and xinetd.

Thomas

Hello Thomas,

If there is no "Install all packages" function in Text / GUi mode come with FC6, then can we do the following steps ? 1, mount cdrom 2, cd cdrom 3, cp *.rpm /root 4, yum install package-name

PS : There Server machine without connection with Internet.

Edward.

Matt C wrote:

...

If there is no "Install all packages" function in Text / GUi mode come with FC6, then can we do the following steps ? 1, mount cdrom 2, cd cdrom 3, cp *.rpm /root 4, yum install package-name

Yes, just find the rpm files on the CD, and do rpm -i filename

Can't to use yum tool ( instead of rpm ) ?

Matt C wrote:

Yum installs from the Internet, rpm installs from disk.

Yum can be used to install from local files:

yum localinstall /path/to/some.rpm

Todd Zullinger wrote:

Matt C wrote:

...

Yum installs from the Internet, rpm installs from disk.

Yum can be used to install from local files:

yum localinstall /path/to/some.rpm

Sorry, do you meanes ( for sample : command line ) ? yum localinstall ./telnet.rpm

edwardspl@ita.org.mo wrote:

Sorry, do you meanes ( for sample : command line ) ? yum localinstall ./telnet.rpm

Yep. You can leave off the ./ if the rpm is in the current directory if you want.

Tony Nelson wrote:

At 2:28 AM -0600 1/1/07, Matt C wrote:

...

...

Can't to use yum tool ( instead of rpm ) ?

Yum installs from the Internet, rpm installs from disk.

Yum installs from a repository, which may be on the internet or local. See Paul Howarth's http://www.city-fan.org/tips/YumRepoFromImages. Note that "yum localinstall" still resolves any dependencies from the selected repositories, which by default is over the Internet.

Dear All,

Would you mind to help ?

[root@svr1 fc6]# yum localinstall telnet*.rpm Loading "installonlyn" plugin Setting up Local Package Process Examining telnet-0.17-37.i386.rpm: telnet - 1:0.17-37.i386 Examining telnet-server-0.17-37.i386.rpm: telnet-server - 1:0.17-37.i386 Marking telnet-server-0.17-37.i386.rpm to be installed Setting up repositories Could not retrieve mirrorlist http://mirrors.fedoraproject.org/mirrorlist?repo=c ore-6&arch=i386 error was [Errno 4] IOError: <urlopen error (-3, 'Temporary failure in name resolution')> Error: Cannot find a valid baseurl for repo: core [root@svr1 fc6]#

What's problem I had ?

Rick Stevens wrote:

And I'd think long and hard before I'd install telnet since it is completely insecure and one of the easiest protocols to hack. If your machine even BRUSHES up against the Internet, do NOT have telnet installed! You're asking for trouble.

First off, any network daemon that is open to connections is a security problem, simply because it will contain bugs and they may well be exploitable.

That said, an unused telnet daemon is inherently *more* secure than an unused SSH daemon with password logins enabled -- the protocol is much simpler, and there's much less code that has to be run against unauthenticated connections. Less code means there's less places for bugs to hide.

The only -- only -- security advantage that password-based SSH has over telnet is that SSH connections are encrypted and hence can't be eavesdropped. [1] If there are no connections, then there is no advantage to SSH (either over telnet or a machine that doesn't run any un-needed services). If those connections are secured some other way (e.g. a VPN) then a telnet connection is not inherently insecure.

And there are other protocols (e.g. traditional NFS, or rsh) that are a lot more insecure, since they *can* be compromised without password-sniffing.

Having said all *that*, SSH with public key authorisation does have very real security advantages, and SSH can be a good bit more convenient.

The telnet *client* does have uses beyond connecting to telnet servers -- it's very useful when troubleshooting certain sorts of e-mail problems, for example.

My sig-monster's on the ball again...

James.

[1] Please -- this is not an invitation to re-open the NSA thread!