Module Name:    src
Committed By:   pgoyette
Date:           Mon Aug 21 10:38:19 UTC 2017

Modified Files:
        src/doc: TODO.modules

Log Message:
Add previous statement from core@ and add reference to earlier E-mail
discussion.

OK martin@


To generate a diff of this commit:
cvs rdiff -u -r1.12 -r1.13 src/doc/TODO.modules

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

Modified files:

Index: src/doc/TODO.modules
diff -u src/doc/TODO.modules:1.12 src/doc/TODO.modules:1.13
--- src/doc/TODO.modules:1.12	Fri Aug  4 11:55:06 2017
+++ src/doc/TODO.modules	Mon Aug 21 10:38:19 2017
@@ -1,4 +1,4 @@
-/* $NetBSD: TODO.modules,v 1.12 2017/08/04 11:55:06 pgoyette Exp $ */
+/* $NetBSD: TODO.modules,v 1.13 2017/08/21 10:38:19 pgoyette Exp $ */
 
 Some notes on the limitations of our current (as of 7.99.35) module
 subsystem.  This list was triggered by an Email exchange between
@@ -135,6 +135,26 @@ christos and pgoyette.
     loader time, an alternate value for the os-release portion of the
     default module path,  i.e. /stand/$MACHINE/$ALT-RELEASE/modules/
 
+    The following statement regarding this issue was previously issued
+    by the "core" group:
+
+    Date: Fri, 27 Jul 2012 08:02:56 +0200
+    From: <redacted>
+    To: <redacted>
+    Subject: Core statement on directory naming for kernel modules
+
+    The core group would also like to see the following changes in
+    the near future:
+
+       Implementation of the scheme described by Luke Mewburn in
+       <http://mail-index.NetBSD.org/current-users/2009/05/10/msg009372.html>
+       to allow a kernel and its modules to be kept together.
+       Changes to config(1) to extend the existing notion of whether or not
+       an option is built-in to the kernel, to three states: built-in, not
+       built-in but loadable as a module, entirely excluded and not even
+       loadable as a module.
+
+
 15. The existing config(5) framework provides an excellent mechanism
     for managing the content of kernels.  Unfortunately, this mechanism
     does not apply for modules, and instead we need to manually manage

Reply via email to