The future of NetBSD

Constantine A. Murenin mureninc at
Fri Sep 1 00:28:44 UTC 2006

On 31/08/06, Marc G. Fournier <scrappy at> wrote:
> On Thu, 31 Aug 2006, Pedro Martelletto wrote:
> > On Thu, Aug 31, 2006 at 06:50:00PM -0300, Marc G. Fournier wrote:
> >> Even at the kernel level?  Look at device drivers and vendors as one
> >> example ... companies like adaptec have to write *one* device driver, for,
> >> what, 50+ distributions of linux ... for us, they need to write one for
> >> FreeBSD, one for NetBSD, one for OpenBSD, and *now* one for DragonflyBSD
> >> ... if we had *at least* a common API for that sort of stuff, it might be
> >> asier to get support at the vendor level, no?
> >
> > Vendors should release documentation, not write drivers.
>   In a perfect world, they all would ... this is not a perfect world, it is
> one dominated by Linux or Microsoft ... I use Adaptec drivers on 3 of my
> servers, because, in 4.x, they were rock solid ... in 6.x, they have a
> problem ...

Did you ever wonder WHY they don't work in the first place? Does your
fxp(4)-based Ethernet no longer works with 6.x, too?

The driver thing is really simple -- vendors either provide
documentation, and their stuff works forever and everywhere; or they
provide you some rubbish they often name "support", which basically
means that you can only use the purchased hardware for X-number of
years, until some progress in your OS is made, and then you are
EXPECTED to buy a new device.

Complaining that Adaptec doesn't support 6.x is stupid. Didn't they
advertise to you that they support FreeBSD 4.x? So what is the
problem? Either ask them for documentation, or go buy another

More information about the freebsd-chat mailing list