Subject: Re: I'm disapointed with the AMD64 port, and NetBSD in general...
To: None <netbsd-help@netbsd.org, port-amd64@netbsd.org>
From: Dieter <netbsd@sopwith.solgatos.com>
List: port-amd64
Date: 07/27/2005 10:06:33
Wolfgang writes:

> How much should one worry that the undocumented built-in ethernet can't be
> supported when gigabit ethernet pci cards are $25?

Quite a bit if you don't have extra PCI slots.

Robert writes:

> I for one am bothered by the state and pace of which NetBSD is coming along
> (especially when the driver for the BCM5751 has been in NetBSD-current since
> sometime last year)!

Here is one problem that might be fixable.  I also see many things sitting
in -current while release after release come out.  Simple, safe, things that
need little if any testing.

Problem reports with tested fixes included sit around forever and don't even
get checked into -current much less a release, while release after release come out.  
What is the point in submitting a PR with a fix if it never gets checked in?

What is the point of having releases and the time&effort they involve when bugfixes
and new drivers sit around in -current or worse, in an open PR?  Example: a simple
one line fix for a kernel panic was checked in, but didn't make it into 2.0.2.  What
the heck is the criteria for getting into a release if a simple one line fix for a
kernel panic doesn't qualify?