From owner-freebsd-security Tue Jan 12 09:42:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16818 for freebsd-security-outgoing; Tue, 12 Jan 1999 09:42:14 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from mired.eh.local (kstreet.interlog.com [198.53.146.171]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16813 for ; Tue, 12 Jan 1999 09:42:12 -0800 (PST) (envelope-from street@iname.com) Received: (from kws@localhost) by mired.eh.local (8.9.1/8.9.1) id MAA00922; Tue, 12 Jan 1999 12:40:00 -0500 (EST) (envelope-from kws) From: Kevin Street MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13979.35056.652849.117334@mired.eh.local> Date: Tue, 12 Jan 1999 12:40:00 -0500 (EST) To: Brook Miles Cc: freebsd-security@FreeBSD.ORG Subject: Re: Quick ipfw question In-Reply-To: References: X-Mailer: VM 6.63 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brook Miles writes: > >Is there some reason that > ipfw /my/file >works but > ipfw -q /my/file >doesn't? > >It gives "ipfw: error: Bad Arguments" > >FreeBSD/i386 3.0-RELEASE It works in 3.0 -current. There were some bug fixes and additional capabilities added around 11/23. One of the comments in CVS says that it fixed a bug with blank lines in the file when using -q. The original support for -q with a file was added around 08/04 according to CVS. -- Kevin Street street@iName.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message