+capabilities + sysctl doc +sysctl ktr

diff --git a/docs/developer/ProjectsPage.mdwn b/docs/developer/ProjectsPage.mdwn
index 9557078..dc3904a 100644 (file)
--- a/docs/developer/ProjectsPage.mdwn
+++ b/docs/developer/ProjectsPage.mdwn
@@ -145,6 +145,12 @@ This page shall serve as a common place to look if you're in search of a DragonF
 * Allow filesystems to define their own attribute vop ops
 * QUESTIONS: Attributes or subfiles? The consensus is that subfiles are better?
 
+### Capabilities
+* Implement something resembling or inspired by POSIX.1e
+* This implementation could possibly exist in userland and interlock with the kernel via a VFS Journal or HAMMER mirroring ioctl's.
+* These should be capable of supporting NFSv4 capabilities.
+* References: [1](http://leaf.dragonflybsd.org/mailarchive/kernel/2006-07/msg00012.html)
+
 ### Hardware virtualization extensions
 * Increase performance of virtual kernels
 * Make use of hardware virtualization extensions, if supported, to manage vmspaces
@@ -156,5 +162,15 @@ This page shall serve as a common place to look if you're in search of a DragonF
 * Harder: zlib, pv entries
 * Once all consumers are ported, zalloc can be removed.
 
+### Document all sysctl's
+* The description of sysctl's can be provided when the sysctl is declared and displayed in userland by passing the -d flag to the sysctl utility.
+* Document all undocumented sysctl's
+* Verify that the description of documented sysctl's is correct.
+
+### Convert kprintf-enabling sysctl's to KTR's
+* Many sysctl's simply enable one or more kernel kprintf's
+* This can be very easy, or can be very unwieldy
+* Convert all of these cases to ktr's, while slightly less easy they are far easier to wield in all cases.
+
 
 For more theoretical projects and project concepts see [[ResearchProjects|/docs/developer/ResearchProjectsPage]]