<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: 3 Things in Linux you should NOT Install</title>
	<atom:link href="http://tuxteam.com/2007/05/21/3-things-in-linux-you-should-not-install/feed/" rel="self" type="application/rss+xml" />
	<link>http://tuxteam.com/2007/05/21/3-things-in-linux-you-should-not-install/</link>
	<description>IT Life &#38; Linux Thoughts</description>
	<lastBuildDate>Mon, 02 Aug 2010 12:07:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: drew</title>
		<link>http://tuxteam.com/2007/05/21/3-things-in-linux-you-should-not-install/comment-page-1/#comment-23</link>
		<dc:creator>drew</dc:creator>
		<pubDate>Tue, 22 May 2007 00:41:16 +0000</pubDate>
		<guid isPermaLink="false">http://matir.wordpress.com/2007/05/21/3-things-in-linux-you-should-not-install/#comment-23</guid>
		<description>All absolute things I never run. But then again, a good idea to keep in mind is, if it&#039;s not needed to keep the machine or services you serve to others on the outside world, don&#039;t run them. Some systems by default have samba, telnet, finger and a whole slew of daemons or services by default. Eliminate these if they&#039;re not going to be used.

And as for telnet being a backup, still not a good idea. There&#039;s too many tools available if ssh or any other access isn&#039;t available and the machine is remote. Most colocations and or data centers have on call support and if you&#039;re running a production enterprise environment, there&#039;s no reason to not have some type of console access either via remote kvm, builtin remote management console capability or some third party tool or hardware like Cyclades for console access when ssh, networking or the like is not up.</description>
		<content:encoded><![CDATA[<p>All absolute things I never run. But then again, a good idea to keep in mind is, if it&#8217;s not needed to keep the machine or services you serve to others on the outside world, don&#8217;t run them. Some systems by default have samba, telnet, finger and a whole slew of daemons or services by default. Eliminate these if they&#8217;re not going to be used.</p>
<p>And as for telnet being a backup, still not a good idea. There&#8217;s too many tools available if ssh or any other access isn&#8217;t available and the machine is remote. Most colocations and or data centers have on call support and if you&#8217;re running a production enterprise environment, there&#8217;s no reason to not have some type of console access either via remote kvm, builtin remote management console capability or some third party tool or hardware like Cyclades for console access when ssh, networking or the like is not up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DannyB</title>
		<link>http://tuxteam.com/2007/05/21/3-things-in-linux-you-should-not-install/comment-page-1/#comment-22</link>
		<dc:creator>DannyB</dc:creator>
		<pubDate>Mon, 21 May 2007 18:31:53 +0000</pubDate>
		<guid isPermaLink="false">http://matir.wordpress.com/2007/05/21/3-things-in-linux-you-should-not-install/#comment-22</guid>
		<description>Having a Telnet client can be very handy.  Especially for manually typing, say, the SMTP protocol, POP3, or HTTP.

But I agree you should NEVER even INSTALL, let alone run, the Telnet server.  On both SuSE (which I&#039;ve used for years) and Ubuntu (used about a year), installing SSH is trivial.  Just install it.

Do you use Windows?  Try the nifty drag-drop WinSCP gui to copy files to/from your SSH Linux box.</description>
		<content:encoded><![CDATA[<p>Having a Telnet client can be very handy.  Especially for manually typing, say, the SMTP protocol, POP3, or HTTP.</p>
<p>But I agree you should NEVER even INSTALL, let alone run, the Telnet server.  On both SuSE (which I&#8217;ve used for years) and Ubuntu (used about a year), installing SSH is trivial.  Just install it.</p>
<p>Do you use Windows?  Try the nifty drag-drop WinSCP gui to copy files to/from your SSH Linux box.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jdhore</title>
		<link>http://tuxteam.com/2007/05/21/3-things-in-linux-you-should-not-install/comment-page-1/#comment-21</link>
		<dc:creator>jdhore</dc:creator>
		<pubDate>Mon, 21 May 2007 18:07:04 +0000</pubDate>
		<guid isPermaLink="false">http://matir.wordpress.com/2007/05/21/3-things-in-linux-you-should-not-install/#comment-21</guid>
		<description>#1: I agree...RH is very out of date and if you&#039;re still running it, you REALLY need to migrate to RHEL, CentOS or FC.
#2: I don&#039;t completely agree here because i use 3 or 4 servers that only have telnet access...I would never run a telnet server on any system i run and i avoid using it if possible, it&#039;s good to have a telnet client just in case though.
#3: rsh isn&#039;t really used anymore because unlike telnet, all rsh is is basically an insecure version of SSH.</description>
		<content:encoded><![CDATA[<p>#1: I agree&#8230;RH is very out of date and if you&#8217;re still running it, you REALLY need to migrate to RHEL, CentOS or FC.<br />
#2: I don&#8217;t completely agree here because i use 3 or 4 servers that only have telnet access&#8230;I would never run a telnet server on any system i run and i avoid using it if possible, it&#8217;s good to have a telnet client just in case though.<br />
#3: rsh isn&#8217;t really used anymore because unlike telnet, all rsh is is basically an insecure version of SSH.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeqq.com</title>
		<link>http://tuxteam.com/2007/05/21/3-things-in-linux-you-should-not-install/comment-page-1/#comment-20</link>
		<dc:creator>Jeqq.com</dc:creator>
		<pubDate>Mon, 21 May 2007 17:49:37 +0000</pubDate>
		<guid isPermaLink="false">http://matir.wordpress.com/2007/05/21/3-things-in-linux-you-should-not-install/#comment-20</guid>
		<description>&lt;strong&gt;3 Things in Linux you should NOT Install&lt;/strong&gt;

While Im all for promoting the use of Linux and software on Linux, unless you absolutely know what youre doing, there are certain things you should not install.  Entirely too often, I see people on LinuxQuestions.org asking how to configure one of th...</description>
		<content:encoded><![CDATA[<p><strong>3 Things in Linux you should NOT Install</strong></p>
<p>While Im all for promoting the use of Linux and software on Linux, unless you absolutely know what youre doing, there are certain things you should not install.  Entirely too often, I see people on LinuxQuestions.org asking how to configure one of th&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
