From owner-freebsd-questions@FreeBSD.ORG Fri Oct 21 00:02:58 2005 Return-Path: X-Original-To: freebsd-questions@FreeBSD.org Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0A7D16A41F; Fri, 21 Oct 2005 00:02:58 +0000 (GMT) (envelope-from parv@pair.com) Received: from mta10.adelphia.net (mta10.adelphia.net [68.168.78.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0CFA43D62; Fri, 21 Oct 2005 00:02:57 +0000 (GMT) (envelope-from parv@pair.com) Received: from default.chvlva.adelphia.net ([69.160.76.67]) by mta10.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051021000256.MVMA16334.mta10.adelphia.net@default.chvlva.adelphia.net>; Thu, 20 Oct 2005 20:02:56 -0400 Received: by default.chvlva.adelphia.net (Postfix, from userid 1000) id 320FCB59E; Thu, 20 Oct 2005 20:03:05 -0400 (EDT) Date: Thu, 20 Oct 2005 20:03:05 -0400 From: Parv To: Jung-uk Kim Message-ID: <20051021000305.GA11603@holestein.holy.cow> Mail-Followup-To: Jung-uk Kim , freebsd-stable@FreeBSD.org, f-q , James Long References: <20051020194725.GA10376@ns.museum.rain.com> <20051020205704.GC4000@holestein.holy.cow> <200510201711.49382.jkim@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200510201711.49382.jkim@FreeBSD.org> Cc: James Long , freebsd-stable@FreeBSD.org, f-q Subject: Re: bzegrep behaviour not consistent with egrep? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2005 00:02:58 -0000 in message <200510201711.49382.jkim@FreeBSD.org>, wrote Jung-uk Kim thusly... > > On Thursday 20 October 2005 04:57 pm, Parv wrote: > > in message <20051020194725.GA10376@ns.museum.rain.com>, > > wrote James Long thusly... ... > > > $ bzegrep "38436|41640" /var/log/maillog.0.bz2 | wc -l > > > 0 > > > $ bzcat /var/log/maillog.0.bz2 | egrep "38436|41640" | wc -l > > > 121 ... > > And more fun, try also "egrep -J| wc", which is similar to the > > 2d case above. > > Can you elaborate the fun, please? In short: will you take "bad choice of words" as an explanation? In somewhat long form: i had read once, twice, or more times in past (most likely in comp.unix.*) that "egrep" was exactly not same as "grep -E", and/or "fgrep" not exactly as "grep -F". The OP's finding reminded me of that even if behaviour difference that was due to an actual bug. - Parv --