<?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: Parse ifconfig data with shell scripts</title>
	<atom:link href="http://www.thelinuxblog.com/parse-ifconfig-data-with-shell-scripts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thelinuxblog.com/parse-ifconfig-data-with-shell-scripts/</link>
	<description>The Linux Blog, General Linux, Shell Scripts</description>
	<lastBuildDate>Fri, 17 May 2013 01:16:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: TheLinuxBlog.com</title>
		<link>http://www.thelinuxblog.com/parse-ifconfig-data-with-shell-scripts/comment-page-1/#comment-2047</link>
		<dc:creator>TheLinuxBlog.com</dc:creator>
		<pubDate>Wed, 18 Mar 2009 13:22:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.thelinuxblog.com/parse-ifconfig-data-with-shell-scripts/#comment-2047</guid>
		<description><![CDATA[@SONA Try using cat /proc/net/dev and see if this format is easier to parse. You should be able to count the number of interfaces by subtracting 1, which would account for the header. Hope this helps!]]></description>
		<content:encoded><![CDATA[<p>@SONA Try using cat /proc/net/dev and see if this format is easier to parse. You should be able to count the number of interfaces by subtracting 1, which would account for the header. Hope this helps!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sona</title>
		<link>http://www.thelinuxblog.com/parse-ifconfig-data-with-shell-scripts/comment-page-1/#comment-2034</link>
		<dc:creator>Sona</dc:creator>
		<pubDate>Tue, 17 Mar 2009 07:38:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.thelinuxblog.com/parse-ifconfig-data-with-shell-scripts/#comment-2034</guid>
		<description><![CDATA[Hi, I want to parse the output of ifconfig command to grab number of network cards, and their details.
For ex. Network cards eth0, eth1, and their details.]]></description>
		<content:encoded><![CDATA[<p>Hi, I want to parse the output of ifconfig command to grab number of network cards, and their details.<br />
For ex. Network cards eth0, eth1, and their details.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheLinuxBlog.com</title>
		<link>http://www.thelinuxblog.com/parse-ifconfig-data-with-shell-scripts/comment-page-1/#comment-1268</link>
		<dc:creator>TheLinuxBlog.com</dc:creator>
		<pubDate>Thu, 30 Oct 2008 03:54:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.thelinuxblog.com/parse-ifconfig-data-with-shell-scripts/#comment-1268</guid>
		<description><![CDATA[Hey Kitten, thanks for the tip. For those that get an error running the above, make sure to put an extra space behind the backslash in the cut if you didn&#039;t already figure that out.]]></description>
		<content:encoded><![CDATA[<p>Hey Kitten, thanks for the tip. For those that get an error running the above, make sure to put an extra space behind the backslash in the cut if you didn&#8217;t already figure that out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kitten</title>
		<link>http://www.thelinuxblog.com/parse-ifconfig-data-with-shell-scripts/comment-page-1/#comment-1263</link>
		<dc:creator>kitten</dc:creator>
		<pubDate>Mon, 27 Oct 2008 19:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.thelinuxblog.com/parse-ifconfig-data-with-shell-scripts/#comment-1263</guid>
		<description><![CDATA[This helped me out a lot.  I needed to extract the ip address, so I modified your idea.  Worked great, but then I decided I could use spaces as the delimiter, obviating the need for tr, so I wound up with:

&lt;code&gt;ifconfig eth0 &#124;grep &quot;inet addr&quot; &#124;cut -d \  -f 12 &#124; sed &#039;s/addr://&#039; 
&lt;/code&gt;
Might be a time-saver for some, depending on what they&#039;re trying to do.  Anyway, thanks for the tips -- really got me started.]]></description>
		<content:encoded><![CDATA[<p>This helped me out a lot.  I needed to extract the ip address, so I modified your idea.  Worked great, but then I decided I could use spaces as the delimiter, obviating the need for tr, so I wound up with:</p>
<p><code>ifconfig eth0 |grep "inet addr" |cut -d \  -f 12 | sed 's/addr://'<br />
</code><br />
Might be a time-saver for some, depending on what they&#8217;re trying to do.  Anyway, thanks for the tips &#8212; really got me started.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
