From owner-freebsd-stable  Thu Jun  6 16:52:40 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA22265
          for stable-outgoing; Thu, 6 Jun 1996 16:52:40 -0700 (PDT)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA22253
          for <stable@FreeBSD.ORG>; Thu, 6 Jun 1996 16:52:37 -0700 (PDT)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id RAA27728; Thu, 6 Jun 1996 17:52:26 -0600
Date: Thu, 6 Jun 1996 17:52:26 -0600
From: Nate Williams <nate@sri.MT.net>
Message-Id: <199606062352.RAA27728@rocky.sri.MT.net>
To: nash@mcs.com
Cc: nate@sri.MT.net, stable@FreeBSD.ORG
Subject: Re: IPFW (was Re: miscfs/devfs)
In-Reply-To: <199606062352.SAA04206@zen.nash.org>
References: <199606062352.SAA04206@zen.nash.org>
Sender: owner-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I believe IPFW is synchronized between -stable and -current (minus
> some compiler warning cleanup by Gary). 

Great.  I wasn't sure.

> The documentation on the
> other hand, is either not complete (the ipfw man page), or somewhat
> invalid (the handbook -- Gary's writeup is excellent, but the syntax
> has changed and new features have been added).  
> 
> If there's anyone to blame for this, it would be me.  I've agreed to
> take the ipfw torch from Poul, but I've only just recently gotten
> commit privileges.

I'm glad you've taken the torch.  I was worried that things weren't
going to be documented, and given that -stable is going to be 2.1.5R
soon, I am glad the documentation will be updated.

Thanks for doing this!


Nate