From owner-freebsd-current Thu Nov 11 16:29:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcor.twinsun.com (alcor.twinsun.com [198.147.65.9]) by hub.freebsd.org (Postfix) with ESMTP id C9A6F14C0E for ; Thu, 11 Nov 1999 16:29:49 -0800 (PST) (envelope-from eggert@twinsun.com) Received: from red.twinsun.com ([192.54.239.70]) by alcor.twinsun.com (8.9.3/8.9.3) with ESMTP id QAA02911; Thu, 11 Nov 1999 16:29:08 -0800 (PST) Received: from shade.twinsun.com (shade.twinsun.com [192.54.239.27]) by red.twinsun.com (8.8.8+Sun/8.8.8) with ESMTP id QAA03019; Thu, 11 Nov 1999 16:28:54 -0800 (PST) Received: (eggert@localhost) by shade.twinsun.com (8.9.3+Sun/8.9.3) id QAA06638; Thu, 11 Nov 1999 16:28:53 -0800 (PST) Date: Thu, 11 Nov 1999 16:28:53 -0800 (PST) From: Paul Eggert Message-Id: <199911120028.QAA06638@shade.twinsun.com> To: tstromberg@rtci.com Cc: freebsd-current@freebsd.org, bug-gnu-utils@gnu.org In-reply-to: <382B2711.E13A1CC8@rtci.com> (tstromberg@rtci.com) Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? References: <382B2711.E13A1CC8@rtci.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Thu, 11 Nov 1999 15:29:05 -0500 From: Thomas Stromberg I just happened to notice this today. For some reason 'grep' seems to think that 'set' output is binary, not text. Most likely this is because the output of your `set' command contains binary data. In the past, this has been reported by people whose `set' command would output something like this: IFS=' ^@' where the `^@' in my message denotes a single NUL byte (control-@) in the original. If this is what's happening to you, then this is quite possibly a bug in your shell, since environment variables cannot possibly contain NUL bytes in Unix. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message