<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns="http://purl.org/rss/1.0/"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
>

  <channel rdf:about="http://lwn.net/headlines/131802/">
    <title>LWN: Comments on "Extending netlink"</title>
    <link>http://lwn.net/Articles/131802/</link>
    <description>
This is a special feed containing comments posted
to the individual LWN article titled &quot;Extending netlink&quot;.

    </description>

    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>2</syn:updateFrequency>
    <items>
      <rdf:Seq>
	<rdf:li resource="http://lwn.net/Articles/132219/rss" />
	<rdf:li resource="http://lwn.net/Articles/132203/rss" />
      
      </rdf:Seq>
    </items>

  </channel>
    <item rdf:about="http://lwn.net/Articles/132219/rss">
      <title>Extending netlink</title>
      <link>http://lwn.net/Articles/132219/rss</link>
      <dc:date>2005-04-14T17:59:18+00:00</dc:date>
      <dc:creator>larryr</dc:creator>
      <description>
      &lt;blockquote&gt;&lt;em&gt;If the netlink interface is too complex, why not make a libnetlink? Keep it in userspace!&lt;/em&gt;&lt;/blockquote&gt;
&lt;p&gt;The purpose is to make the &lt;em&gt;kernel&lt;/em&gt; side easier to implement.&lt;/p&gt;
&lt;p&gt;
Larry
&lt;/p&gt;


      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/132203/rss">
      <title>Extending netlink</title>
      <link>http://lwn.net/Articles/132203/rss</link>
      <dc:date>2005-04-14T16:35:51+00:00</dc:date>
      <dc:creator>bronson</dc:creator>
      <description>
      Erm...  If the netlink interface is too complex, why not make a libnetlink?  Keep it in userspace!  I haven't followed this on lkml so I may be missing something obvious...&lt;br&gt;
      
      </description>
    </item>
</rdf:RDF>

