From owner-freebsd-current  Fri Dec  4 18:46:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA25079
          for freebsd-current-outgoing; Fri, 4 Dec 1998 18:46:50 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA25070
          for <current@FreeBSD.ORG>; Fri, 4 Dec 1998 18:46:47 -0800 (PST)
          (envelope-from luigi@labinfo.iet.unipi.it)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id BAA10091; Sat, 5 Dec 1998 01:38:05 +0100
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199812050038.BAA10091@labinfo.iet.unipi.it>
Subject: Re: Dummynet for 3.0?
To: xaa@xaa.iae.nl (Mark Huizer)
Date: Sat, 5 Dec 1998 01:38:04 +0100 (MET)
Cc: current@FreeBSD.ORG
In-Reply-To: <19981205005136.D817@ariel.xaa.iae.nl> from "Mark Huizer" at Dec 5, 98 00:51:18 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > I understand the constraints you were working within.  I believe the
> > correct approach to the problem would have been to leave 2.2 alone and
> > bring DUMMYNET/BRIDGE into -current.  The benefits being:
> 
> Ordinarily good and proper sentiments, but this issue came up after
> code freeze and this option was not open to Luigi.
> 
> Is the option to add dummynet to 3.0 open now?

yes it is, i promise will tackle the problem asap.

	luigi


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message