From owner-freebsd-hackers Thu Feb 29 04:36:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA07911 for hackers-outgoing; Thu, 29 Feb 1996 04:36:10 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA07896 for ; Thu, 29 Feb 1996 04:36:06 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id XAA24619; Thu, 29 Feb 1996 23:08:15 +1030 From: Michael Smith Message-Id: <199602291238.XAA24619@genesis.atrad.adelaide.edu.au> Subject: Re: tcpdump changes To: lyndon@orthanc.com (Lyndon Nerenberg VE7TCP) Date: Thu, 29 Feb 1996 23:08:14 +1030 (CST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199602290146.RAA05053@multivac.orthanc.com> from "Lyndon Nerenberg VE7TCP" at Feb 28, 96 05:46:08 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG Precedence: bulk Lyndon Nerenberg VE7TCP stands accused of saying: > > Is there anything out there (expect scripts or the like) that will > break if the output format of -x changes? I would like to avoid adding > another option for ASCII output if at all possible. I like the idea, however perhaps you could activate it by specifying the 'x' option twice. This minimises your incompatabilities, but doesn't pollute the option space any more. ie. -x gives traditional output, but -xx or -x -x gives the new format. > --lyndon -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[