<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Controlling Input/Output of Device Drivers</title>
	<link>http://www.linux-mag.com/id/6206/</link>
	<description>Open Source, Open Standards</description>
	<pubDate>Sat, 04 Jul 2009 18:26:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: aholt</title>
		<link>http://www.linux-mag.com/id/6206/#comment-1202</link>
		<pubDate>Thu, 19 Jun 2008 14:46:09 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/6206/#comment-1202</guid>
					<description>Cirnath: I didn't think you were trying to be pedantic - it'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't return down interfaces - if it doesn'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 - 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 - 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>
	<item>
		<title>by: cirnath</title>
		<link>http://www.linux-mag.com/id/6206/#comment-1195</link>
		<pubDate>Wed, 18 Jun 2008 17:14:55 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/6206/#comment-1195</guid>
					<description>Ok.  I didn't know whether ioctl could be used in some other way to obtain the 'down' interfaces as well.  That was more my reason for asking.  I wasn'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-1191</link>
		<pubDate>Mon, 16 Jun 2008 08:03:21 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/6206/#comment-1191</guid>
					<description>Yes you are correct, I probably should have made that clear in the article. I'm just really trying to demonstrate ioctls calls rather write a fully fledged "interface discovery" utility. If I were, I'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-1190</link>
		<pubDate>Sun, 15 Jun 2008 17:28:58 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/6206/#comment-1190</guid>
					<description>Just to be clear... the show_ints code can only see interfaces which are in an 'up' state.

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-1184</link>
		<pubDate>Fri, 13 Jun 2008 08:27:22 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/6206/#comment-1184</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't know why the URL doesn't work, but I've let them know - hopefully it will be fixed soon. However, as an alternative, I'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 - 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: rakesh uv</title>
		<link>http://www.linux-mag.com/id/6206/#comment-1182</link>
		<pubDate>Fri, 13 Jun 2008 04:11:13 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/6206/#comment-1182</guid>
					<description>Hi Alan, 
             That was a wonderful and simple explaination, Keep it UP.
Please Do Post Such Articles frequently.
             There one problem with one of the links provided in the article,http://www.linux-mag.com/code/08.03.ioctl.tar.

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,http://www.linux-mag.com/code/08.03.ioctl.tar.</p>
<p>Thank You
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: mohamedhagag</title>
		<link>http://www.linux-mag.com/id/6206/#comment-1179</link>
		<pubDate>Thu, 12 Jun 2008 16:04:32 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/6206/#comment-1179</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: djeepp</title>
		<link>http://www.linux-mag.com/id/6206/#comment-1174</link>
		<pubDate>Thu, 12 Jun 2008 15:07:18 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/6206/#comment-1174</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>
</channel>
</rss>
