Projects page link
[ikiwiki.git] / docs / developer / gsocprojectspage / index.mdwn
CommitLineData
90c0b013 1[[!meta title="Google Summer of Code Project List"]]
4114eeff 2
3[[!toc levels=0]]
4
b9ffbe7d 5Have a look at our SoC pages from [[2008|docs/developer/GoogleSoC2008/]], [[2009|docs/developer/gsoc2009]], [[2010|docs/developer/gsoc2010]] and [[2011|docs/developer/gsoc2011]] to get an overview about prior year's projects.
4114eeff 6
7For more details on Google's Summer of Code: [Google's SoC page](http://socghop.appspot.com/)
8
9Note to prospective students: These project proposals are meant to be a first approximation; we're looking forward to your own suggestions (even for completely new directions) and will try to integrate your ideas to make the GSoC project more interesting to all parties. Even when a proposal is very specific about the goals that must be achieved and the path that should be taken, these are always negotiable. Keep in mind that we have tried to limit the proposals on this page to those that (based on our past experience) are appropriate for the GSoC program. This is by no means a comprehensive list, original ideas or proposals based on project ideas found on other pages are very welcome.
10
11Note to everyone else: These proposals are by no means Summer of Code specific, anyone is welcome and encouraged to adopt any of these projects at any time (just please let us know, or make a note on this page).
12
13Legend:
14
15* Prerequisites: knowledge that the student should have before starting the project. It may be possible to acquire the knowledge in the course of the project, but the estimated difficulty would increase substantially. On the bright side, you can expect to have a much deeper understanding of these fields (and gain some real-world experience) after you successfully complete the respective project.
16* Difficulty: Estimated difficulty of the project, taking into account the complexity of the task and the time constraints of the GSoC program.
17* Contact point: The person you should contact for any further information or clarifications. If the primary contact for a project does not respond in a reasonable amount of time (2-3 days), you should contact the appropriate DragonFly BSD mailing list, usually kernel@.
18
19#### Project ideas
20
11f3d975 21---
22
4114eeff 23##### Implement i386 32-bit ABI for x86_64 64-bit kernel
24* Add a 32-bit syscall table which translates 32-bit
25 system calls to 64-bit.
26* Add support for 32 bit compatibility mode operation
27 and ELF binary detection.
28
29The idea here is to support the execution of 32 bit DragonFly binaries in 64 bit DragonFly environments, something numerous other operating systems have done. Several things must be done to support this. First, the appropriate control bits must be set to execute in 32-bit compatibility mode while in usermode instead of 64-bit mode. Second, when a system call is made from 32-bit mode a translation layer is needed to translate the system call into the 64-bit requivalent within the kernel. Third, the signal handler and trampoline code needs to operate on the 32-bit signal frame. Fourth, the 32 and 64 bit ELF loaders both have to be in the kernel at the same time, which may require some messing around with procedure names and include files since originally the source was designed to be one or the other.
30
31There are several hundred system calls which translates to a great deal of 'grunt work' when it comes time to actually do all the translations.
32
33Meta information:
34
35* Prerequisites: C
36* Difficulty: Difficult (lots of moving parts, particularly the trapframes)
37* Contact point: dillon
38
39---
40
41##### Implement ARC algorithm extension for the vnode free list
42* Vnode recycling is LRU and can't efficiently handle data sets which
43 exceed the maxvnode limit. When the maxvnode limit is reached the kernel
44 starts throwing away cached vnodes along with their VM objects (and thus
45 all related cached file data).
46
47* What we would like to do is implement an ARC algorithm for the free
48 vnodes to determine which ones to throw away and potentially combine
49 this with further caching of the related VM object even after the vnode
50 is thrown away by associating it with a mount point and inode number,
51 until memory pressure forces all of its pages out.
52
53* For this project the student can choose to just implement the VM object
54 retention portion and not try to implement an ARC algorithm (which can
55 be considerably more complex).
56
57Meta information:
58
59* Prerequisites: C, OS internals
60* Difficulty: Modest without ARC (Very difficult with ARC)
61* Contact point: dillon
62
63---
64
4114eeff 65##### Make DragonFly NUMA-aware
66
67* Parse related ACPI tables
68* NUMA-aware memory allocation
69* References:
70[ACPI SLIT parser](http://mail-index.netbsd.org/tech-kern/2009/11/23/msg006518.html)
71[ACPI SRAT parser](http://mail-index.netbsd.org/tech-kern/2009/11/23/msg006517.html)
72[NetBSD NUMA diff](http://www.netbsd.org/~cegger/numa2.diff)
73[NetBSD NUMA x86 diff](http://www.netbsd.org/~cegger/numa_x86.diff) (These patches now in NetBSD tree)
74
75Meta information:
76
77* Prerequisites: C, introductory computer architecture
78* Difficulty: Easy
79* Contact point: kernel@crater.dragonflybsd.org
80
81---
82
83
84##### Port valgrind to DragonFlyBSD
85
86Valgrind is a very useful tool on a system like DragonFly that's under heavy development. Since valgrind is very target specific, a student doing the port will have to get acquainted with many low level details of the system libraries and the user<->kernel interface (system calls, signal delivery, threading...). This is a project that should appeal to aspiring systems programmers. Ideally, we would want the port to be usable with vkernel processes, thus enabling complex checking of the core kernel code.
87
88The goal of this project is to port valgrind to the DragonFlyBSD platform so that at least the memcheck tool runs sufficiently well to be useful. This is in itself a challenging task. If time remains, the student should try to get at least a trivial valgrind tool to work on a vkernel process.
89
90Meta information:
91
92* Prerequisites: C, x86 assembly, low-level OS internals
93* Difficulty: Hard
94* Contact point: Aggelos Economopoulos <aoiko@cc.ece.ntua.gr>
95
96---
97
98##### Adapt pkgsrc to create a package system with dependency independence.
99* Create a set of tools that modifies how the pkgsrc packages are installed, allowing for the ability to upgrade individual packages, without stopping applications that depend on said packages from working. One method of achieving this is detailed at http://www.dragonflybsd.org/goals/#packages but other methods may be possible. PC-BSD have written a tool called PBI Builder which modifies FreeBSD ports for their dependency independence PBI system, this could be used as a starting point for the DragonFly BSD tools.
100
101Meta information:
102
103* Prerequisites: C
104* Difficulty: ?
105* Contact point: kernel@crater.dragonflybsd.org
106
107---
108
1e5fd6e2 109##### Implement virtio drivers on DragonFly to speed up DragonFly as a KVM guest (2011 Project)
4114eeff 110
111As virtualization is coming more and more and KVM will be a strong player in that field,
112we want DragonFly to have top-notch support for this virtualization platform. For this
113purpose, we'd like to have a virtio-based implementation of a paravirtualized disk and
114network driver. [virtio](http://www.ibm.com/developerworks/linux/library/l-virtio/index.html)
115is an abstraction to a ring buffer that is shared between the host and the guest. On top of this
116abstraction, one can build a variety of paravirtualized devices, as specified in
117[virtio-spec](http://ozlabs.org/~rusty/virtio-spec/virtio-spec-0.8.6.pdf).
118
119The goal of this project is to create a virtio-ring implementation and then to implement drivers
120for the network and block devices described in the specification linked to above. This is a great
121project for a student who wants to get experience writing (real-world, high-performance) device
122drivers without having to deal with the quirks of real hardware.
123
124Meta information:
125
126* Prerequisites: C, elementary OS internals
2ee12b5f 127* Difficulty: Medium
d745770a 128* Contact point: kernel@crater.dragonflybsd.org
4114eeff 129
130---
131
1e5fd6e2 132##### Make vkernels checkpointable (2011 Project)
4114eeff 133
134* See checkpt(1).
135* Implement save and restore of segment registers so that threaded applications may be checkpointed. The segment registers support TLS. There are potential security concerns here.
136* Teach the checkpt system call how to checkpoint multiple vmspaces.
137* Add code to the vkernel which gets triggered upon reception of a SIGCKPT signal to dump/load e.g. the current state of network drivers.
138* This would allow us to save and restore or even migrate a complete DragonFly operating system running on the vkernel platform.
139This could be especially handy on laptops (if we'd get X11 operating in vkernels).
140* See also: http://www.dragonflybsd.org/docs/developer/CheckpointFeatures/
141
142Meta information:
143
144* Prerequisites: C, OS internals
145* Difficulty: Medium
146* Contact point: Michael Neumann <mneumann@ntecs.de>
147* References: [1](http://leaf.dragonflybsd.org/mailarchive/kernel/2007-02/msg00073.html) [2](http://leaf.dragonflybsd.org/mailarchive/users/2007-02/msg00034.html)
148
149---
150
151##### HAMMER compression
152
153* Compress blocks as they get written to disk.
154* Only file data (rec_type == DATA) should be compressed, not meta-data.
155* the CRC should be that of the uncompressed data.
156* ideally you'd need to associate the uncompressed data with the buffer cache buffer somehow, so that decompression is only performed once.
157* compression could be turned on a per-file or per-pfs basis.
158* gzip compression would be just fine at first.
159
160Doing compression would require flagging the data record as being compressed and also require double-buffering since
161the buffer cache buffer associated with the uncompressed data might have holes in it and otherwise referenced by user
162programs and cannot serve as a buffer for in-place compression or decompression.
163
164The direct read / direct write mechanic would almost certainly have to be disabled for compressed buffers and the
165small-data zone would probably have to be used (the large-data zone is designed only for use with 16K or 64K buffers).
166
167Meta information:
168
169* Prerequisites: C, filesystem internals
170* Difficulty: Difficult
171* Contact point: Michael Neumann <mneumann@ntecs.de>
172
173---
174
175
8b575943 176##### Port FreeBSD's USB stack to DragonFly
177
178This project has been listed for several years under the "USB4BSD" name. Since then that branch was
179brought into FreeBSD 8 on [SVN Revision 184610](http://svnweb.freebsd.org/base?view=revision&revision=184610)
4114eeff 180
8b575943 181* Port the latest FreeBSD USB stack to DragonFly, as our own usb stack is very outdated.
4114eeff 182
183Meta information:
184
185* Prerequisites: C, OS internals
186* Difficulty: Moderate
187* Contact point: kernel@crater.dragonflybsd.org
188
189---
190
191##### Userland System V Shared Memory / Semaphore / Message Queue implementation
192* Implement some or all of these subsystems in their entirety, or as completely as possible in userland using a daemon, mmap and the DragonFly umtx_sleep(2)/umtx_wakeup(2) or other userland facilities.
193* Any security or other major hurdles to this approach that would likely have to be implemented in-kernel should be noted in the students application.
194* Test and benchmark the new facilities with heavy SysV consumers such as PostgreSQL
195* Identify performance tradeoffs made in the userland implementation versus the existing kernel implementation. If time permits identify and apply solutions to these tradeoffs so that the userland implementation performs on par with or better than the kernel implementation.
196
197Meta information:
198
199* Prerequisites: C, x86 assembly
200* Difficulty: Moderate
201* Contact point: Samuel J. Greear <sjg@thesjg.com>
202
203---
204
8e2bdf60 205##### DragonFly history access for Gnome/KDE
5654e978 206* Write a Dolphin (KDE) plugin or Gnome file manager plugin that creates a 'time slider' when working with HAMMER filesystems.
207* If time remains investigate additional features and/or methods of display and possibly a HAMMER configuration utility for managing history retention, etc.
8e2bdf60 208
209Meta information:
210
5654e978 211* Prerequisites: C, Gnome or KDE familiarity
8e2bdf60 212* Difficulty: Hard
213* Contact point: kernel@crater.dragonflybsd.org
214* References: [A similar idea for ZFS](http://blogs.sun.com/erwann/entry/zfs_on_the_desktop_zfs)
215
216---
217
218##### Create a Samba VFS plugin to expose Hammer history
219* Give access to Hammer snapshots/fine-grained history to anyone able to access the Hammer volume over Samba
5654e978 220* This would involve writing a Samba3 VFS module to expose historical versions of files as "shadow copies". VFS module implementations supporting more traditional snapshot hierarchies do already exist.
8e2bdf60 221
222Meta information:
223
5654e978 224* Prerequisites: C
225* Difficulty: Moderate
8e2bdf60 226* Contact point: kernel@crater.dragonflybsd.org
227
228---
229
56ca55df
T
230##### Port Hyper-V Linux Integration components to DragonFly
231* Microsoft released a dual BSD/GPL version of their para-virtualized drivers (SCSI and Networking) for Linux.
232* This work would require porting the Linux VMBus (Microsoft's equivlalent to XenBus) and the corresponding SCSI (StorVSC) and networking (NetVSC) drivers to DragonFly.
233* References: [Sources](http://www.microsoft.com/downloads/en/details.aspx?FamilyID=eee39325-898b-4522-9b4c-f4b5b9b64551) [Architecture Overview](http://port25.technet.com/archive/2009/07/22/introduction-to-the-linux-integration-components.aspx)
8e2bdf60 234
56ca55df
T
235Meta information:
236
237* Prerequisites: C, OS internals
238* Difficulty: Hard
239* Contact point: kernel@crater.dragonflybsd.org
8e2bdf60 240
8cb8502a 241---
242
243##### Implement more dm targets
244* Since we now have dm (device mapper) in DragonFly, it would be nice to make better use of it. Currently we have a relatively small number of useful targets (crypt, linear and striped).
245* Other targets should be implemented, in particular the mirror target would be of interest. Other ideas are welcome, too. Before applying for this please discuss the target of interest on the mailing list or with me directly.
c2cfaa23 246* There is a start of a journalled mirror target, if you want to attack soft mirroring; the problem is a lot more difficult than it seems at first, so talking on the mailing list or on IRC would be definitely worthwhile!
8cb8502a 247
248Meta information:
249
250* Prerequisites: C, OS internals
251* Difficulty: Medium
c2cfaa23 252* Contact point: kernel@crater.dragonflybsd.org , Alex Hornung <alexh@dragonflybsd.org>, Venkatesh Srinivas <vsrinivas@dragonflybsd.org>
8cb8502a 253
3a9e5de8 254---
255
256##### Implement a new unionfs
257* unionfs is a particularly useful pseudo-fs which allows to have an upper and a lower filesystem on a single mountpoint. The upper mountpoint is mostly transparent, so that the lower mountpoint is accessible.
3a9e5de8 258* A typical use case is mounting a tmpfs filesystem as the upper and a read-only FS as the lower mp. This way files can be edited transparently even on a RO filesystem without actually modifying it.
65d9da85 259* The current unionfs is completely broken as it relies on the whiteout VFS technique which is not supported by HAMMER. A new unionfs implementation should not rely on archaic methods such as whiteout.
3a9e5de8 260
261Meta information:
262
263* Prerequisites: C, OS internals, ideally some knowledge of the FreeBSD/DragonFly VFS
264* Difficulty: Medium
265* Contact point: kernel@crater.dragonflybsd.org
8e2bdf60 266
0c47d1e1 267---
268
269##### Improve compatibility of libdevattr with Linux' libudev
270* Our libdevattr has an API which is mostly compatible with Linux' libudev, but it is doubtful that any Linux application making use of libudev would run out of the box on DragonFly with libdevattr.
b515bc2d 271* The aim of this project is to identify the shortcomings of libdevattr and fix them so that some common libudev applications work with our libdevattr.
272* This might involve some kernel hacking to improve our kern_udev and definitely includes some grunt work of "tagging" subsystems with the kern_udev API.
273* Most of the work will be in userland, though, working on udevd and libdevattr.
0c47d1e1 274
275Meta information:
276
277* Prerequisites: C, familiarity with Linux' libudev would be a plus
278* Difficulty: Medium
279* Contact point: kernel@crater.dragonflybsd.org , Alex Hornung <alexh@dragonflybsd.org>
280
281
282
9792e675 283---
284
fc1a3138 285##### Implement further dsched disk scheduling policies (2011 Project: BFQ)
9792e675 286* dsched is a highly flexible disk scheduling framework which greatly minimizes the effort of writing disk scheduling policies.
287* Currently only dsched_fq, a fairly simple fair-queuing policy, and noop policies are implemented.
288* The aim of this project would be to implement at least another useful disk scheduling policy, preferably one that improves interactivity.
289* Other ideas are welcome.
1e4090b0 290* This is a great opportunity for CS students interested in scheduling problems to apply their theoretical knowledge.
9792e675 291
292Meta information:
293
294* Prerequisites: C, OS internals, familiarity with disk scheduling
295* Difficulty: Medium
296* Contact point: kernel@crater.dragonflybsd.org , Alex Hornung <alexh@dragonflybsd.org>
297
82d3efd3 298---
299
692141e4 300##### Implement hardware nested page table support for vkernels
82d3efd3 301* Various modern hardware supports virtualization extensions, including nested pagetables.
302* The DragonFly BSD vmspaces API, used to support vkernels, is effectively a software implementation of nested pagetables.
303* The goal of this project would be to add support for detection of the hardware features on AMD and Intel cpu's and alter the vmspace implementation to use hardware support when available.
304
305Meta information:
9792e675 306
82d3efd3 307* Prerequisites: C, x86 assembly, OS internals
308* Difficulty: Hard
309* Contact point: kernel@crater.dragonflybsd.org
310
8ff76619 311---
312
313##### ATA TRIM and filesystem/swap support
314* Some devices support an ATA command, 'TRIM', which marks disk blocks as 'not in use'; on SSDs, for example, not-in-use blocks can be used to support better wear leveling and to prevent performance degradation over time with fragmentation of the free block set.
315* DFly's BIO system supports BIO_DELETE commands; these commands are not tied to device level TRIM commands, however
316* Once BIO_DELETE commands are possible, it'd be very nice for DragonFly's swap code to generate BIO_DELETE commands for unused swap blocks (batch them!); this would would work well with SSDs and swapcache
317* HAMMER should also send BIO_DELETE commands to mark unused blocks unused. Running HAMMER on an SSD would be more pleasant then.
318* FreeBSD implemented this support on Jan 29th for UFS; it may serve as a good reference.
319
92644e89 320Meta information:
321
8ff76619 322* Prerequisites: C, OS internals, a touch of file systems
71da460d 323* Difficulty: Not too hard
8ff76619 324* Contact point: kernel@crater.dragonflybsd.org
92644e89 325
ec874e8b 326---
327
328##### Access to ktr(4) buffers via shared memory
329Our event tracing system, ktr(4), records interesting events in per-cpu buffers that are printed out with ktrdump(8). Currently, ktrdump uses libkvm to access these buffers, which is suboptimal. One can allow a sufficiently-privileged userspace process to map those buffers read-only and access them directly. For bonus points, design an extensible, discoverable (think reflection) mechanism that provides fast access via shared memory to data structures that the kernel chooses to expose to userland.
330
331Meta information:
332
333* Prerequisites: C, OS internals
334* Difficulty: Medium
335* Contact point: kernel@crater.dragonflybsd.org, Aggelos Economopoulos <aoiko@cc.ece.ntua.gr>
336
82d3efd3 337---
92644e89 338
8b8bd18e 339#####Ability to execute Mach-O (OS X) binaries
340This is a project for a student with something to prove, executing a binary touches a huge number of moving parts of a modern kernel. This project would entail adding or porting support for Mach-O binaries to the DragonFly BSD kernel. It would also involve adding an additional system call vector, like the Linux vector used for linux binary emulation. This is quite a large and complicated task and any proposal will be expected to be well-researched to reflect that. The ability to execute non-GUI binaries that make use of shared libraries should be the minimum to which such a project should aspire. OpenDarwin is available as a reference or to port relevant code from.
341
342Meta information:
343
344* Prerequisites: C, OS internals, binary file formats
345* Difficulty: Hard
346* Contact point: Samuel J. Greear <sjg@thesjg.com>
347
9376443d 348---
349##### nmalloc (libc malloc) measurements and performance work
350
351nmalloc is our libc memory allocator it is a slab-like allocator; it recently had some work done to add per-thread caches, but there is much more work that could be done. A project on this might characterize fragmentation, try out a number of techniques to improve per-thread caching and reduce the number of total syscalls, and see if any are worth applying.
352
353Possible things to work on:
354(thread caches)
355* The per-thread caches are fixed-size; at larger object sizes (say 4K), this can result in a lot of memory tied up. Perhaps they should scale their max size inversely to the object size.
356
357* The per-thread caches are filled one-at-a-time from free(). Perhaps the per-thread caches should be burst-filled.
358
359* Perhaps the per-thread caches should age items out
360
361(slab zone allocation)
362* zone_alloc() currently burst-allocates slab zones with the zone magazine held across a spinlock.
363
364* zone_free() holds the zone magazine lock around bzero()ing a slab zone header
365
366* zone_free() madvise()s one slab at a time; it'd be nice to madvise() runs of contiguous slabs
367
368* zone_free() madvise()s very readily (for every slab freed). Perhaps it should only madvise slabs that are idle for some time
369
370* zone_free() burst-frees slabs. Its not clear whether this is a good idea.
371
372(VMEM):
373* currently allocations > either 4k or 8k are forced directly to mmap(); this means that idle memory from free slabs cannot be used to service those allocations and that we do no caching for allocations > than that size. this is almost certainly a mistake.
374
375* we could use a small (embeddable) data structure that allows:
3761. efficient coalescing of adjacent mmap space for madvise
3772. efficient queries for vmem_alloc() (w/ alignment!)
3783. compact and doesn't use any space in the zone header (dirty/cold!)
3794. allows traversal in address order to fight fragmentation
3805. keep two such data structures (one for dirty pages, one for cold pages)
381
382(Note)
383* These are just ideas; there are many more things possible and many of these things need a lot of measurement to evaluate them. It'd be interesting to see if any of these are appropriate for it.
384
385References:
386* http://www.usenix.org/event/usenix01/bonwick.html
387
388A description of the Sun Solaris work on which the DragonFly allocator is based; use this as an overview, but do not take it as gospel for how the DFly allocator works.
389
390* http://leaf.dragonflybsd.org/~vsrinivas/jemalloc-tech-talk.ogv (Jason Evans tech talk about jemalloc, 1/2011)
391
392jemalloc is FreeBSD's and Firefox's (and NetBSD and GNASH and ...)'s malloc; in this tech talk, Jason Evans reviews how jemalloc works, how it has changed recently, and how it avoid fragmentation.
393
394* http://endeavour.zapto.org/src/malloc-thesis.pdf (Ayelet Wasik's thesis 'Features of a Multi-Threaded Memory Allocator')
395
396This thesis is an excellent overview of many techniques to reduce contention and the effects these techniques have on fragmentation.
397
398* Prerequisites: C, a taste of data structures
399* Difficulty: moderate
400* Contact point: Venkatesh Srinivas <me@endeavour.zapto.org>
401
01b524ba 402---
403
404##### Create a filesystem indexing service
405Currently to locate an arbitrary file on a dragonfly system you would use the locate(1), which(1) or whereis(1) tools. These are a bit clunky, paint in broad strokes and the accuracy of the database is often suspect. The first part of this project would involve implementing the Linux inotify interface in the DragonFly kernel. The second part would be to write a daemon that can (optionally) operate as an indexing service, if the weekly 310.locate periodic job see's that the locate database is being maintained by the daemon, it can skip running locate.updatedb(8). A third part of this project might involve extending the current database to a binary format with information about file types, what bits are set, etc. This could enable the user to have the locate tool paint in narrower strokes by specifying only files of type "ASCII text" or only files that are suid root or have the execute bit set.
406
407Meta information:
408
409* Prerequisites: C, OS internals, binary file formats
410* Difficulty: Easy/Moderate
411* Contact point: Samuel J. Greear <sjg@thesjg.com>
412
4c7e21d4 413---
414
415##### Make DragonFly multiboot capable
416Adjust the DragonFly kernel to be multiboot (the specification) capable. In addition, add necessary code to grub2 to understand our disklabel64 and anything else we need to be able to use grub2 to multiboot DragonFly without any chainloading involved.
417
418Meta information:
419
420* Prerequisites: C, OS internals
421* Difficulty: Easy/Moderate
422* Contact point: Alex Hornung <alexh@dragonflybsd.org>
423
7700f24f 424
425---
426
427##### Add SMT/HT awareness to our scheduler
428Our scheduler (sys/kern/usched_bsd4.c) doesn't know about Simultaneous multithreading/HyperThreads.
429The aim of this project is to add awareness of SMT to it so that scheduling on multithreaded CPUs improves. This involves among other things to first schedule on actual physical cores before populating the hyperthreads. The ground work of adding a generic way of detecting how many threads each core has, etc, also has to be done as part of this project.
430
431See http://lwn.net/Articles/8553/ for what Linux has done in this area.
432
433Meta information:
434
435* Prerequisites: C, OS internals, process scheduling
436* Difficulty: Moderate
437* Contact point: kernel@lists.dragonflybsd.org, Alex Hornung <alexh@dragonflybsd.org>
438
439
2fed452e 440
441
442---
443
444##### Complete installer rewrite
445Completely rewrite the installer to be much simpler to maintain. It will still have to be an ncurses-based installer written in C, unless there is a strong point for using a scripting language. A text interface UI library (e.g. newt [see examples on http://gnewt.sourceforge.net/tutorial-4.html] - which seems very easy and handy) should be used to make the handling of the graphical part as easy as possible.
446
447As part of rewriting the installer, several functions scattered around in other base utils should be factored out into libraries that both the installer and the util it comes from can use, e.g.:
7c6affa1 448
449* partitioning (both GPT and MBR) should be factored out into two libraries, that the fdisk and the gpt tools use, but the installer can make use of, too.
450* disklabel32/64 functionality
451* adduser (and other user/group management)
2fed452e 452
453The new installer should then make use of all these new libraries and other ones that are already available (libcryptsetup, libluks, liblvm, libtcplay) to offer more advanced features.
454
c5845662 455NOTE: The new installer should maintain most if not all of the functionality of the old installer in addition to adding features taking advantage of the aforementioned libraries.
456
2fed452e 457
458
459Meta information:
460
461* Prerequisites: C
462* Difficulty: Moderate
463* Contact point: kernel@lists.dragonflybsd.org, Alex Hornung <alexh@dragonflybsd.org>
464
465
8b8bd18e 466---
4114eeff 467 (please add)