Date: Mon, 13 Jan 1997 16:56:29 -0500 From: Garrett Wollman <wollman@lcs.mit.edu> To: Lee Crites <adonai@jump.net> Cc: freebsd-hackers@freebsd.org, dg@root.com Subject: Re: bug in setsockopt()... ? Message-ID: <9701132156.AA19128@halloran-eldar.lcs.mit.edu> In-Reply-To: <1.5.4.32.19970113213527.00685734@jump.net> References: <1.5.4.32.19970113213527.00685734@jump.net>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Mon, 13 Jan 1997 15:35:27 -0600, Lee Crites <adonai@jump.net> said: > So now, back to my originally stated requests: > * Can anyone point me to a list of the bugs in the ipc functions? No. Bruce Evans probably has one, but you win a prize if it's anything you actually care about and can understand it in less than ten minutes. Terry Lambert probably has one, but all Terry's bugs can be boiled down to ``I want STREAMS'' so so that's probably not what you're looking for either. > * Who are the people working on them? Generally the people who make the lists, although the particular meaning of ``working'' in this context is debatable. > * What kind of help do they need? Someone else to do the work and submit a patch for review. Lots of money and free time would be helpful, as would a life for some of us, but we don't expect that you can provide that sort of help. > * Can I try to abuse some of the fixes? If you can find them first, sure. Most of the people don't hoard their fixes; if there is a bug, and we have the right fix and it works, then we fix it. > And, some further, while I admit only implied, requests: > * Is there a cental point with a list of the currently identified bugs? There is the GNATS database. See the Web page. Note that it only contains bugs which people bother to file a problem report on. > * How does somone with a vested interest in them get to that list? See the Web page. > * How can someone like me help out? Use the Source. Come up with a solution. Send a patch. If you can't do any of these, at least document the nature of the bug and send a PR if there isn't already one. > * Are there compatibility tests with other os's? No. We define the standard of compatibility. (Only half a smiley.) > If not, why not? Are you waiting for someone to make it? If it > was made, would the results be appreciated or scorned? That would depend on whether being compatible with something else represented an advance or a reversion. We generally have a ranking something like this: 1) Standards (POSIX, ISO C, X/Open when it makes sense, FIPS 151-2, IETF) 2) Other *BSD flavors (NetBSD, OpenBSD, BSD/OS) 3) ``Traditional BSD behavior'' 4) ``Traditional SysV behavior'' 5) ``Traditional SunOS behavior'' Whether (4) or (5) count more or less than the author's own opinion depends on who is doing the writing. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9701132156.AA19128>