From owner-freebsd-current Sun Dec 15 11:33:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7990E37B401; Sun, 15 Dec 2002 11:33:22 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15D6343E4A; Sun, 15 Dec 2002 11:33:22 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.5/8.12.5) with ESMTP id gBFJXIOM082013; Sun, 15 Dec 2002 11:33:18 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.5/8.12.5/Submit) id gBFJXINk082012; Sun, 15 Dec 2002 11:33:18 -0800 (PST) (envelope-from dillon) Date: Sun, 15 Dec 2002 11:33:18 -0800 (PST) From: Matthew Dillon Message-Id: <200212151933.gBFJXINk082012@apollo.backplane.com> To: Scott Long Cc: "M. Warner Losh" , sam@errno.com, mux@freebsd.org, obrien@freebsd.org, current@freebsd.org Subject: Re: ipfw userland breaks again. References: <200212150015.gBF0FlbS066547@apollo.backplane.com> <20021215.111441.05985858.imp@bsdimp.com> <200212151826.gBFIQMpo081407@apollo.backplane.com> <20021215.115657.90648628.imp@bsdimp.com> <200212151908.gBFJ811I081774@apollo.backplane.com> <3DFCD553.9080407@btc.adaptec.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Also, fixing the ipfw2 abi is probably a good item to put on the list :for getting 5.x to 5-STABLE. Please don't waste time with band-aids :that will make people forget that ipfw2 needs attention. : :Scott This is a reasonable line of argument but my opinion is that it hasn't been fixed for a long time now and unless someone decides they really want to tackle the issue soon it isn't going to be fixed for a long time to come, and we shouldn't continue to create a major hassle for developers and sysads that hit up against the issue. I mean, hey, if someone asked me to rename the command from 'ipfw unbreak' to 'ipfw somelonggobblygookthatyouhavetocutandpaste' I'm willing to do that too :-) But we need either the API fixed or this hack and, right now, the only person willing to do anything is me and my buddy Hack. If someone stood up and said "I will take on fixing the API but it will take a month" then that's fine with me, I would not feel that I would have to commit this now. But so far nobody has stood up and said that. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message