<?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: Controlling Input/Output of Device Drivers</title>
	<atom:link href="http://www.linux-mag.com/id/6206/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.linux-mag.com/id/6206/</link>
	<description>Open Source, Open Standards</description>
	<lastBuildDate>Fri, 10 Feb 2012 08:31:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: djeepp</title>
		<link>http://www.linux-mag.com/id/6206/#comment-5453</link>
		<dc:creator>djeepp</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/6206/#comment-5453</guid>
		<description>I guess a prerequisite to reading this article would be a basic understanding of coding in c of which I have none of. This stuff is way over my head.</description>
		<content:encoded><![CDATA[<p>I guess a prerequisite to reading this article would be a basic understanding of coding in c of which I have none of. This stuff is way over my head.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mohamedhagag</title>
		<link>http://www.linux-mag.com/id/6206/#comment-5454</link>
		<dc:creator>mohamedhagag</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/6206/#comment-5454</guid>
		<description>nice i hope that we can see more in depth articles like this, Ph. Alan ;) please do it frequently :) .</description>
		<content:encoded><![CDATA[<p>nice i hope that we can see more in depth articles like this, Ph. Alan ;) please do it frequently :) .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rakesh uv</title>
		<link>http://www.linux-mag.com/id/6206/#comment-5455</link>
		<dc:creator>rakesh uv</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/6206/#comment-5455</guid>
		<description>Hi Alan, &lt;br /&gt;
             That was a wonderful and simple explaination, Keep it UP.&lt;br /&gt;
Please Do Post Such Articles frequently.&lt;br /&gt;
             There one problem with one of the links provided in the article,http://www.linux-mag.com/code/08.03.ioctl.tar.&lt;br /&gt;
&lt;br /&gt;
Thank You</description>
		<content:encoded><![CDATA[<p>Hi Alan, <br />
             That was a wonderful and simple explaination, Keep it UP.<br />
Please Do Post Such Articles frequently.<br />
             There one problem with one of the links provided in the article,<a href="http://www.linux-mag.com/code/08.03.ioctl.tar." rel="nofollow">http://www.linux-mag.com/code/08.03.ioctl.tar.</a></p>
<p>Thank You</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aholt</title>
		<link>http://www.linux-mag.com/id/6206/#comment-5456</link>
		<dc:creator>aholt</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/6206/#comment-5456</guid>
		<description>Thanks for the feedback Rakesh. The article appeared in Linux Magazine a couple of months ago, so they are responsible for publishing the article on-line. To save space the editor took the code listings out and put them on the web. I don&#039;t know why the URL doesn&#039;t work, but I&#039;ve let them know - hopefully it will be fixed soon. However, as an alternative, I&#039;ve put the tar file here: http://agholt.googlepages.com/ioctl.tar.gz</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback Rakesh. The article appeared in Linux Magazine a couple of months ago, so they are responsible for publishing the article on-line. To save space the editor took the code listings out and put them on the web. I don&#8217;t know why the URL doesn&#8217;t work, but I&#8217;ve let them know &#8211; hopefully it will be fixed soon. However, as an alternative, I&#8217;ve put the tar file here: <a href="http://agholt.googlepages.com/ioctl.tar.gz" rel="nofollow">http://agholt.googlepages.com/ioctl.tar.gz</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cirnath</title>
		<link>http://www.linux-mag.com/id/6206/#comment-5457</link>
		<dc:creator>cirnath</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/6206/#comment-5457</guid>
		<description>Just to be clear... the show_ints code can only see interfaces which are in an &#039;up&#039; state.&lt;br /&gt;
&lt;br /&gt;
If you were truly doing interface discovery (i.e. for an installer or some such) and no interfaces are in a configured state, what would the code look like to identify the interfaces?</description>
		<content:encoded><![CDATA[<p>Just to be clear&#8230; the show_ints code can only see interfaces which are in an &#8216;up&#8217; state.</p>
<p>If you were truly doing interface discovery (i.e. for an installer or some such) and no interfaces are in a configured state, what would the code look like to identify the interfaces?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aholt</title>
		<link>http://www.linux-mag.com/id/6206/#comment-5458</link>
		<dc:creator>aholt</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/6206/#comment-5458</guid>
		<description>Yes you are correct, I probably should have made that clear in the article. I&#039;m just really trying to demonstrate ioctls calls rather write a fully fledged &quot;interface discovery&quot; utility. If I were, I&#039;d probably just get them out of /proc/net/dev. But thanks for the clarification.</description>
		<content:encoded><![CDATA[<p>Yes you are correct, I probably should have made that clear in the article. I&#8217;m just really trying to demonstrate ioctls calls rather write a fully fledged &#8220;interface discovery&#8221; utility. If I were, I&#8217;d probably just get them out of /proc/net/dev. But thanks for the clarification.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cirnath</title>
		<link>http://www.linux-mag.com/id/6206/#comment-5459</link>
		<dc:creator>cirnath</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/6206/#comment-5459</guid>
		<description>Ok.  I didn&#039;t know whether ioctl could be used in some other way to obtain the &#039;down&#039; interfaces as well.  That was more my reason for asking.  I wasn&#039;t (intentionally) trying to be annoyingly pedantic.</description>
		<content:encoded><![CDATA[<p>Ok.  I didn&#8217;t know whether ioctl could be used in some other way to obtain the &#8216;down&#8217; interfaces as well.  That was more my reason for asking.  I wasn&#8217;t (intentionally) trying to be annoyingly pedantic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aholt</title>
		<link>http://www.linux-mag.com/id/6206/#comment-5460</link>
		<dc:creator>aholt</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/6206/#comment-5460</guid>
		<description>Cirnath: I didn&#039;t think you were trying to be pedantic - it&#039;s a good point. Browsing through the header files SIOCGIFCONF is the only function I see that returns a list of interfaces and, as you correctly point out, it doesn&#039;t return down interfaces - if it doesn&#039;t have an IP address. A down interface with an IP address does show up (how weird is that?) I guess the behaviour of SIOCGIFCONF is down to the whim of the kernel developers.</description>
		<content:encoded><![CDATA[<p>Cirnath: I didn&#8217;t think you were trying to be pedantic &#8211; it&#8217;s a good point. Browsing through the header files SIOCGIFCONF is the only function I see that returns a list of interfaces and, as you correctly point out, it doesn&#8217;t return down interfaces &#8211; if it doesn&#8217;t have an IP address. A down interface with an IP address does show up (how weird is that?) I guess the behaviour of SIOCGIFCONF is down to the whim of the kernel developers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

