Subject: Re: altq api for ipf and pf
To: None <current-users@netbsd.org>
From: Miles Nordin <carton@Ivy.NET>
List: current-users
Date: 09/24/2005 21:20:25
--pgp-sign-Multipart_Sat_Sep_24_21:20:25_2005-1
Content-Type: text/plain; charset=US-ASCII
>>>>> "ms" == matthew sporleder <msporleder@gmail.com> writes:
ms> ALTQ API
Here is the status IMHO:
http://mail-index.netbsd.org/port-sparc64/2005/07/25/0004.html
Sorry for the harsh words. I think few people are using ALTQ, on any
BSD, so it's all somewhat understandable. But eventually I just gave
up and switched my main ALTQ box to FreeBSD. It's not as clean, and
loosing NetBSD's cross-build architecture is a harsh blow. But it
works reliably in production with no patches which is a big big plus
with the amount of flak I get if there are problems or
ugrade-of-the-week issues with a box that's routing traffic for lots
of people, which in the end is almost necessarily the whole point of
ALTQ and link-sharing schedulers. :)
--pgp-sign-Multipart_Sat_Sep_24_21:20:25_2005-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)
iQCVAwUAQzX7WYnCBbTaW/4dAQLZxwP+O1H5+GMn90+Vx0su2l2Ld/uUpuKolwn3
Fe049jzgsuwf+vfpFxeajFuvcVBAsoLb0lAqLSHXwzL9O6HkJw7M6Y6m3iwqvmk/
VDOqvFQLV+BzUgppkmtHMdm+FLuHgTDC/AryhLCRsi/aHilrqA9jP4IGPTKvNcFy
z7dX3FOfa8g=
=44Ne
-----END PGP SIGNATURE-----
--pgp-sign-Multipart_Sat_Sep_24_21:20:25_2005-1--