Date: Tue, 06 May 1997 18:07:43 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Jaye Mathisen <mrcpu@cdsnet.net> Cc: dennis <dennis@etinc.com>, Tim Tsai <tim@futuresouth.com>, hackers@FreeBSD.ORG Subject: Re: if_de.c ???? Message-ID: <6125.862967263@time.cdrom.com> In-Reply-To: Your message of "Tue, 06 May 1997 13:35:18 PDT." <Pine.NEB.3.95.970506130427.1963J-100000@mail.cdsnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> It's like FreeBSD is always at this "80%" useful stage. It always seems > to be burning up 10 hours of time a week just kind of keeping the whole OS > all together. Every upgrade seems to break something that worked fine > before. Significant features don't seem to work when really stressed. That's because for the duration of time that 3-4 core members are focused on something, life is good and that something works well. Then, like all developers (not to mention volunteer ones), they turn their attentions to the next challenge, like Intel EtherExpress Pro 100/B support for example, and the focus shifts. If no 2nd-eschelon group moves forward and takes over support in the areas vacated by the front-line troups then yes, of course the quality of life will gradually decline there. Is that the fault of the front-line troups for not simply staying static in one location and ignoring any and all entreaties to advance? No. It is not. It is a breakdown in the formation of this "2nd eschelon" and some of you guys are going to have to get off your asses and address this before it will get a lot better, and no fooling. Since FreeBSD is very close (minus a small fractional percentage) to being volunteer driven, if it's only making it 80% there then somebody isn't pulling his or her 20%. :-) Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6125.862967263>