DragonFly BSD
DragonFly kernel List (threaded) for 2004-04
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: Begginer

From: Chris Pressey <cpressey@xxxxxxxxxxxxxxx>
Date: Fri, 23 Apr 2004 12:32:06 -0700

On Fri, 23 Apr 2004 01:05:21 +0200
Emiel Kollof <coolvibe@xxxxxxxxxxxxxxxx> wrote:

> On Friday 23 April 2004 00:40, Matias Torchinsky wrote:
> > Hi world !
> > I would like to help. I don't have much experience with kernel
> > source. Anyway, i'm starting looking code. Is there something (easy
> > easy) I could start working on ?
> Well, good way to whet your appetite is by porting freebsd ports that
> don't compile from FreeBSD to DragonFlyBSD by way of an override
> port.. Although that situation might be temporary with the package
> system being planned and made and stuff.
> Other low hanging fruit is found in userland. That is everything
> outside of /usr/src/sys. Chris would love K&R->ANSI cleanups, merges
> from FreeBSD CURRENT userland to DFly is also a possibility. I believe
> Hiten has quite a list of MFC's that need too be brought to our tree.
> Might make a nice TODO list. 

If you're looking for something really really easy easy, you can help
test things... there are two patchsets in particular that I've been
working on that I could use more feedback on:


Synchs our make(1) with FreeBSD-CURRENT's.  Apply it, then buildworld,
then try make'ing as many things as you can think of and see if it
fails.  (I haven't seen it fail yet, except on one odd thing (a stale
dfport) that our make(1) couldn't handle either, so it didn't count.)


Makes our sys/ header files stricter about requiring userland programs
to define _KERNEL_STRUCTURES when accessing the kernel guts.  Apply it,
buildworld, and try installing ports to see which ones fail.  I haven't
found any yet (except lsof, which already fails anyway, so that doesn't
count either :)


[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]