OpenBSD went through a phase of "lets just commit a bunch of stuff to the CVS; if something doesn't work and users complain, just tell them to write a better driver themselves" during early to late 2.x. Around 2.8, I think, stuff like softupdates and various multimedia drivers became much more stable and the crashes stopped. NetBSD had even less manpower back then, and their stuff was always very stable. That's due to the more conservative approach (i.e. it was stable but everything was slightly outdated), and that's one reason why NetBSD release cycles were 15 months long. That's no longer the case however.
On 1/15/06, Jacob Meuser <[EMAIL PROTECTED]> wrote: > btw, most of those "poorly written drivers" came directly from NetBSD. > I suspect your crashes were from poor integration of those drivers > with the changes made in the kernel core, which was due to lack of > manpower to both do the work and properly test. _______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
