Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 22 Jan 2000 21:01:36 +0100
From:      Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To:        Nick Hibma <n_hibma@webweaving.org>
Cc:        FreeBSD CURRENT Mailing List <current@FreeBSD.ORG>
Subject:   Re: With feature freeze being in place
Message-ID:  <20000122210136.B18600@daemon.ninth-circle.org>
In-Reply-To: <Pine.BSF.4.20.0001212322080.2237-100000@localhost>; from n_hibma@webweaving.org on Fri, Jan 21, 2000 at 11:27:26PM %2B0000
References:  <Pine.BSF.4.20.0001212322080.2237-100000@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help
-On [20000122 15:22], Nick Hibma (n_hibma@webweaving.org) wrote:
>
>	- writing manpages (or send a skeleton of to someone who will
>	finish it)

Damn right! =)

>	- update HARDWARE.TXT
>	- check UPDATING
>	- replace controller with device in all manpages

I think I solved most, if not all, manpages by now, also changed most
disk statements to device.

What needs to be done is making sure our userland tools stop depending
on /dev/r* device nodes, since they aren't needed anymore.

>	- improving manpages in general

Always a good option.

>	- FIXING PRs

Always a good option.  Its saddening to see it alwyas being the same
people taking care of this.  Even if you don't have freebsd.org access
you can easily check what the originator tried on your own system and
submit a follow-up saying your system (uname -a) has the same problem or
not.

I am busy pulling newbus manpages out of my, erhm, head. =)
But I also note a lack of ata/ad manpages.  I offered sos that I'd be
doing them or mdoc if someone wrote the bare text.  But if someone takes
this task from my shoulders, I'd be happy.

Also, are GENERIC and LINT in sync?

Are LINT and GENERIC in sync with the manpages and vice versa?

Are there tools/manpages which need to be removed but were forgotten?

Check the ports tree, there's tidy, libtool, leafnode+, diablo and more
ports which need updating.  Some ARE NOT even the Y2k ready ports yet!!!

Compile world with a memleak package and check for memleaks.

Help the audit project.

Make sure cross compilation works.

Verify the sysinstall.  Alpha support for it greatly improved.  We even
have booting from CD if dfr's and o`brien's stuff works!

wchar support, something we NEED if we want to use OpenJade someday.
Heck, it's part of the SUSv2 and C specs.

Test IPv6 support!  You've all been asking for it, test it.

Given stream.c recent affairs, check boundschecking in code.

See how we can maintain our stack and other relevant subsystems as part
of the best in the world.

I am also working on an up-to-date tasklist which will allow everyone to
look for tasks which measure up to his or her ability and be more active
on the FreeBSD project.  I can't believe that Linux with its ``rabid''
users and less stable source manages to have more enthusiatic supporters
in terms of fixes, additions, documentation and all that.

-- 
Jeroen Ruigrok vd W/Asmodai         asmodai@[wxs.nl|bart.nl|freebsd.org]
Documentation nutter/B-rated Coder BSD: Technical excellence at its best  
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>;
Ain't gonna spend the rest of my Life, quietly fading away...


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000122210136.B18600>