3 This page shall serve as a common place to look if you're in search of a DragonFly related project. It's also the place to check if someone else is already working on it (to prevent project collision) or should be contacted.
10 * Add traffic report, especially to lists requests that cause 404s
11 * Add the mail archive to the search index
12 * Download link right on the main page.
13 * Fix [[RecentChanges]] page to have correct links back to git repo
14 * Fix RSS feed to have correct links
15 * Create layout for http://bugs.dragonflybsd.org that matches the main site.
16 * Create short list of tasks for a new DragonFly user
17 * how to upgrade the operating system
18 * how to get to a working desktop
19 * and where and how to report issues.
21 ### Post papers in the proper locations on the website
22 * Format conversion may be necessary
23 * Aggelos's papers from [http://leaf.dragonflybsd.org/~aggelos/] (http://leaf.dragonflybsd.org/~aggelos/) (netmp-paper.pdf and netmp.pdf) to Presentations
24 * ["A Peek at the vKernel" article](http://cvsweb.dragonflybsd.org/cvsweb/site/data/docs/articles/vkernel/vkernel.shtml?rev=1.3&content-type=text/x-cvsweb-markup) from old site
26 ## Documentation projects
29 * Reorder `/usr/src/UPDATING` to put more relevant information at top; remove data no longer relevant.
30 * Help out in [http://bugs.dragonflybsd.org](http://bugs.dragonflybsd.org) (try to reproduce, diagnose, propose fixes ...)
31 * Organize, contribute to, and finish the C book project.
33 ### Handbook maintenance
34 * Check if the content applies to DragonFly. If not, change it.
35 * Add new content and enhance the previous chapters
36 * Check for syntax error, typos and wiki errors.
37 * Add prev/next buttons to all pages.
42 * Update the [[contributed software|docs/user/ContribSoftware]] which is out-of-date.
43 * Remove `NOINET6` build option
44 * `WARN` corrections to utilities
45 * Bring in code from other *BSDs:
46 * smbfs changes from FreeBSD
47 * Add extended slice support to `fdisk`
48 * Install Coverity and fix the FreeBSD bugs that were uncovered by Coverity, but do not just blindly pull over the FreeBSD patches. Make sure that you first understand what the patch does.
49 * C99 Standards Conformance. The todo list is on [[/docs/developer/StandardsConformanceProject]]
50 * Setup a regression testing machine/system to register and find problems and new improvements..
51 * Networking performance / scalability
52 * [[RegressionTest|/docs/developer/RegressionTest]]
53 * also check [[HowToStressTest|/docs/developer/HowToStressTest]]
54 * Add lwp support to ptrace/gdb/core dumps.
55 * [[/docs/developer/CheckpointFeatures]]
56 * Linuxulator update (FreeBSD did a lot of work in this area. Look [here](http://wiki.freebsd.org/linux-kernel),
57 * Bringing in version 2.0 of the BSD Installer
58 * UTF8 support in the console
60 ### Scalability (algorithmic performance)
61 * [http://bulk.fefe.de/scalability/](http://bulk.fefe.de/scalability/)
62 * [http://bulk.fefe.de/lk2006/talk.pdf](http://bulk.fefe.de/lk2006/talk.pdf)
64 ### Clean our code to make it [style(9)](http://leaf.dragonflybsd.org/cgi/web-man?command#style§ionANY) compatible.
65 * Compile and test your changes.
66 * Verify that the checksum (sha(1)) of the unmodified object matches the checksum of the cleaned object. Check also with strip(1)+sha(1)
68 ### Port BSD-licensed tools (ex: `grep`, `diff` and `sort`)
69 * The OpenBSD guys already did some work related to that.
70 * If you manage to bring the tools to DragonFly, check if everything works as expected (e.g. rc.d scripts, make world runs, ...).
71 * The new tools need to have at least all the features of the old GNU tools.
73 ### Randomize mmap() offsets
74 * [http://www.openbsd.org/papers/ven05-deraadt/index.html](http://www.openbsd.org/papers/ven05-deraadt/index.html)
77 * ptrace/gdb follow-fork-mode support and more (peek at linux)
78 * Change the build to create one libbfd for gdb and binutils
79 * Separate RPC code from NFS into separate library.
81 ### I/O diagnostic utilities
82 * A utility similar to top which displays I/O usage on a per-process basis
85 ### SMART capabilities
86 * Add to natacontrol (see NetBSD's atactl?)
89 ### Disk scheduling rc scripts
90 * Create a rc script to manage the disk/io scheduling system
91 * Perhaps 1 entry to "enable" it, and all disks will have mode set to "auto", in auto mode smart inquiries and other heuristics could attempt to determine the best i/o scheduler
92 * Per-device and device class or similar defaults should be definable in rc.conf also
93 * The bulk of this functionality could be implemented in a resurrected "dschedctl" utility and exposed through the rc interface using just a thin wrapper, allowing hotplug scripts and etc. an easier option to use the same facilities.
95 ### Add usage() to vkernels
96 * Most userspace applications have a (traditionally) usage() routine which prints helpful information when passed -h or -? or any unknown command line argument or incorrect syntax.
97 * Add a usage() to the vkernel's argument parsing.
100 * HAMMER has the capability to expose very rich information to userland through ioctl's.
101 * Currently the hammer(8) utility makes use of this information in an ad-hoc manner.
102 * Port this core functionality into a public libhammer library so that other base and third party utilities may take advantage of it.
107 * Port the BSDL OSS code to DragonFly
108 * Complete Path MTU Discovery by adding a host route to remember the Path MTU and setting a timer to expire old host routes. See netinet/if_ether.c for an example of this mechanism as used by ARP. Periodically increase MTU of hosts that have had its MTU decreased.
109 * Look for places in the kernel that can benefit from Solaris-style caching of preconstructed slab allocator objects. If we can find enough of these uses, we can add this functionality to the kernel memory allocator.
110 * Implement [`sem_open()`](http://www.opengroup.org/onlinepubs/000095399/functions/sem_open.html), [`sem_close()`](http://www.opengroup.org/onlinepubs/000095399/functions/sem_close.html), and [`sem_unlink()`](http://www.opengroup.org/onlinepubs/000095399/functions/sem_unlink.html).
111 * Clean our code to make it [style(9)](http://leaf.dragonflybsd.org/cgi/web-man?command#style§ionANY) compatible. Compile and test your changes. Verify that the checksum (sha(1)) of the unmodified object matches the checksum of the cleaned object. Check also with strip(1)+sha(1)
112 * Setup a regression testing machine/system to register and find problems and new improvements..
113 * Networking performance scalability
114 * fix `APIC_IO` on SMP
115 * Port or update drivers from other systems.
116 * Port NFSv4. [This mail](http://leaf.dragonflybsd.org/mailarchive/kernel/2008-01/msg00065.html) is a good starting point.
117 * clean up buildworld/kernel compilation warnings
118 * Port DragonFly over to Xen.
122 ### Code to port/sync from FreeBSD
123 * PCI code (to take advantage of power saving features)
124 * Bring in support for UFS2, just the changes to extend the width of some fields from 32 bits to 64 bits.
127 ### Code to port/sync from OpenBSD
128 * Add support for the NoExecute bit as described in [http://www.openbsd.org/papers/auug04/index.html](http://www.openbsd.org/papers/auug04/index.html).
129 * After that, make user stacks and data heaps non-executable. (W^X)
130 * hardware drivers, specially wireless.
133 * A scheduler API supporting multiple scheduler implementations already exists
134 * Add a Solaris-like dispatcher framework that can handle more than one installed scheduling policy
137 * A pluggable kernel I/O scheduler already exists
138 * Implement additional disk scheduling policies
140 ### Modify firmware framework
141 * We currently use the firmware(9) FreeBSD also uses
142 * It would be more appropriate to avoid future problems with redistribution problems, etc, to adapt the wifi firmware stuff to use the firmware(9) we used to have before, which was able to load firmware files from userland (/etc/firmware).
143 * See "firmware discussion" thread on kernel@ mailing list, March-May 2010.
144 * Since it's not desired to just add another way of doing it, this project should include getting rid of loading firmwares as modules
146 ### Work relating to LWKT (LightWeightKernelThreading)
147 * Implement lazy IPI cross-processor lwkt message passing.
148 * Add timeout functionality to lwkt_waitmsg().
149 * Write man pages for the lwkt message passing API.
151 ### Filesystem extended attributes
152 * Generic VFS attributes layer
153 * Emulate attributes ala Darwin
154 * Allow filesystems to define their own attribute vop ops
155 * QUESTIONS: Attributes or subfiles? The consensus is that subfiles are better?
158 * Implement something resembling or inspired by POSIX.1e
159 * This implementation could possibly exist in userland and interlock with the kernel via a VFS Journal or HAMMER mirroring ioctl's.
160 * These should be capable of supporting NFSv4 capabilities.
161 * References: [1](http://leaf.dragonflybsd.org/mailarchive/kernel/2006-07/msg00012.html)
163 ### Hardware virtualization extensions
164 * Increase performance of virtual kernels
165 * Make use of hardware virtualization extensions, if supported, to manage vmspaces
166 * Make use of hardware IOMMU support if available
169 * zalloc is a deprecated kernel interface and all current consumers can be ported to objcache, with varying levels of difficulty.
170 * Easier: kqueue, nfs nodes, ufs dirhash, aio, crypto, vm_map_entry
171 * Harder: zlib, pv entries
172 * Once all consumers are ported, zalloc can be removed.
174 ### Document all sysctl's
175 * 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.
176 * Document all undocumented sysctl's
177 * Verify that the description of documented sysctl's is correct.
179 ### Convert kprintf-enabling sysctl's to KTR's
180 * Many sysctl's simply enable one or more kernel kprintf's
181 * This can be very easy, or can be very unwieldy
182 * Convert all of these cases to ktr's, while slightly less easy they are far easier to wield in all cases.
185 For more theoretical projects and project concepts see [[ResearchProjects|/docs/developer/ResearchProjectsPage]]