1 ; $Id: TODO,v 1.4 1994/09/11 20:01:03 phk Exp $
3 ** To skip this preamble, search forward for the pattern `**'.
5 This file contains a list of ideas that people have come up for "good
6 things to do" in FreeBSD 2.0. These aren't necessarily things on the
7 fast-track, and in fact consist mostly of things that the core team is
8 never going to find the time to do so, if most things here are going
9 to happen at all, they'll happen when someone reading this list steps
10 forward and volunteers!
12 That said, a lot of these ideas would be very nice to have and would
13 add substantially to the perceived value of FreeBSD. Some items on
14 this list would add a LOT of value, for that matter, and are by no
15 means trivial. Take and fix an item with a (*) next to it and WC will
16 even send you a free 2.0 CD for your troubles! It's the least they
17 can do for all notable contributors.
19 This is a also good place to look if you're keen for a little
20 assignment, whole project or just something random to do. Many folks
21 often feel intimidated by the sheer size of FreeBSD and think "I'd
22 like to pitch in somehow, but god, what can _I_ do? I can't possibly
23 do any of the things the core team are doing - aiiggh! They'll laugh
24 at my code, I know it! I can't do it!"
25 Trust us, don't worry! Take a dedicated stab at something on this
26 list and most of us will applaud - even if you don't finish, you may
27 stir someone else into picking it up where you left off. Above all,
28 pick something you'll have fun doing!
30 There are small things and large things in this list, and we may
31 periodically reshuffle it to mark things done, outdated or more
32 important. Tasks are tagged with a unique ID number (YYMMDDNNN) for
33 later tracking and are also easily machine-parsable by those seeking
34 to browse them with some home-rolled search program. Some indication
35 of relative difficulty level is also given for each task, though it
36 should be kept in mind that one persons "easy" is anothers
37 "impossible", so take the ratings with a grain of salt! :)
39 If you start working on something from this list, we also suggest that
40 you contact the email-address listed for more information and to
41 provide some central coordination for your effort. If the email
42 address given is simply <foo> then the email address can be presumed
43 to be <foo@freefall.cdrom.com>. If no email address is listed, then
44 simply send to <freebsd-hackers@freefall.cdrom.com>.
48 The FreeBSD core team.
53 TASK: Add interupts to pas.c
54 DETAIL: { You'll need a manual for the ncr-5380 chip and possibly some
55 doc on the PAS16. Linux/NetBSD also have existing drivers to study. }
62 TASK: Add Linux/Crynwr compatible plip mode to lpt.c
63 DETAIL: { Use IF_LLC0 as mode-flag. Look at the crynwr packet-driver
64 plip.asm (ftp::ftp.ftp.com) and the linux driver for reference. }
66 CATS: kernel networking
71 TASK: Add laptop-feature to wd.c
72 DETAIL: { If disk just spun up, do sync when we have it running. Need
73 to detect that disk was turned off, e.g. had a long delay in becomming
81 TASK: Add hot-swap PCMICIA bus and driver support.
82 DETAIL: { Several teams in Linux and one in NetBSD are working on providing
83 hot insertion/removal and autoconfiguration of PCMCIA cards. This task
84 also requires some modification of existing drivers to support being used
85 by PCMCIA cards. This task is both really hard and comparatively easy;
86 hard because it's a big job, easy because others have already gone much of
87 the way and you have their work for reference. }
94 TASK: Salvage seagate.c driver from 1.1.5.1
95 DETAIL: { We've got a seagate driver that could use a little cleanup and
103 TASK: Add bootp/DHCP to the generic ethernet code.
104 DETAIL: { Implement an ioctl(), which will send a bootp on a particular
105 interface and return the data in a usable format. OR make a program which uses
106 existing ioctls to do it. See RFC153[34] for information on DHCP. }
108 CATS: kernel networking
113 TASK: Add bootp/DHCP capability to slip driver.
114 DETAIL: { Cisco's products implement this. Both master and slave side would be
117 CATS: kernel networking
122 TASK: Make a freebsd.com MS-DOS boot program
123 DETAIL: { This program should be able to boot like the boot-blocks, that is
124 find a FreeBSD-partition and load the kernel from there, but it should
125 also be able to load the kernel from an optional MS-DOS file. }
132 TASK: Make iostat find the disks
133 DETAIL: { This is actually mostly a change to the device-drivers to collect
134 the information in the first place. }
141 TASK: Silence "cc -Wall"
142 DETAIL: { Lots of warnings if you try this. You will find this a challenge
143 actually, and it is good training in the C language.}
150 TASK: Add XPG-style message catalogs.
151 DETAIL: { NetBSD has apparently already done the necessary work, so this
152 pretty much comes down to either evaluating their stuff and making any changes
153 necessary, or simply starting from scratch. Not having seen the code in
154 question, I leave it up to the best judgement of the implementor as to how to
155 best accomplish the task. }
162 TASK: Make PAS16 a controller.
163 DETAIL: { Make the ProAudioSpectrum a controller like wdc1 and attach
164 sound and cdrom drivers to it. }
projects / FreeBSD / FreeBSD.git / blob