From c26c194513b016d37be676b0f99ede6759866040 Mon Sep 17 00:00:00 2001
From: Sam Leffler <sam@FreeBSD.org>
Date: Sun, 15 Mar 2009 23:27:11 +0000
Subject: [PATCH] remove 2 dead tasks

---
 en/projects/ideas/ideas.xml | 44 +------------------------------------
 1 file changed, 1 insertion(+), 43 deletions(-)

diff --git a/en/projects/ideas/ideas.xml b/en/projects/ideas/ideas.xml
index 0a07230552..2fc7ec17e3 100644
--- a/en/projects/ideas/ideas.xml
+++ b/en/projects/ideas/ideas.xml
@@ -15,7 +15,7 @@ Ideas//EN"
 <ideas>
   <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
     <cvs:keyword name="freebsd">
-      $FreeBSD: www/en/projects/ideas/ideas.xml,v 1.112 2009/03/15 14:13:43 luigi Exp $
+      $FreeBSD: www/en/projects/ideas/ideas.xml,v 1.113 2009/03/15 14:36:31 luigi Exp $
     </cvs:keyword>
   </cvs:keywords>
 
@@ -535,27 +535,6 @@ these buses to be a subclass of this new base class.</p>
 	</desc>
       </idea>
 
-      <idea id="modrefcnt">
-	<title>Dynamic module references</title>
-
-	<desc>
-<p><strong>Technical contact</strong>: <a
-  href="mailto:sam@FreeBSD.org">Sam Leffler</a></p>
-<p>Kernel modules may have dynamic references created during operation.
-  For example net80211 key entries reference functions in the crypto module
-  that implements the key's cipher.  Presently there is no standard mechanism
-  for expressing this dependency so that module unloading is disallowed;
-  instead modules must track references and implement their own semantics.
-  This task is to define and implement a general mechanism for tracking
-  these references and use them in handling module unload requests.</p>
-<p><strong>Requirements</strong>:</p>
-<ul>
-  <li>Good knowledge of C.</li>
-  <li>Kernel awareness.</li>
-</ul>
-	</desc>
-      </idea>
-
     <idea id="kernel-dvb" class="soc">
       <title>Kernel support for linux DVB device drivers</title>
 
@@ -969,27 +948,6 @@ destDir parameter.</li>
        </desc>
       </idea>
 
-      <idea id="wi" class="soc">
-	<title>Update wi</title>
-
-	<desc>
-<p><strong>Technical contact</strong>: <a
-  href="mailto:sam@FreeBSD.org">Sam Leffler</a></p>
-<p>Many new and useful features (e.g. crypto protocols like WPA) of the WLAN
-  infrastructure in the kernel are not used in wi(4).  While wi(4)
-  cards are old and can not compete with recent wireless cards, they are still
-  in use in a lot of places.  The goal of this item is to examine the WLAN
-  infrastructure and other WLAN drivers in the tree for nice features and
-  port/use them in the wi(4) driver.</p>
-<p><strong>Requirements</strong>:</p>
-<ul>
-  <li>Knowledge of C.</li>
-  <li>No fear of undocumented parts of the kernel.</li>
-  <li>One wi(4) card and one other wireless device to test against.</li>
-</ul>
-	</desc>
-      </idea>
-
       <idea id="wpa2preauth" class="soc">
 	<title>WPA2 preauthentication in hostapd</title>