From owner-freebsd-current Mon Dec 7 06:52:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04554 for freebsd-current-outgoing; Mon, 7 Dec 1998 06:52:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-50-dbn.dial-up.net [196.34.155.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA04508 for ; Mon, 7 Dec 1998 06:52:04 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id QAA26709; Mon, 7 Dec 1998 16:50:38 +0200 (SAT) From: Robert Nordier Message-Id: <199812071450.QAA26709@ceia.nordier.com> Subject: Re: strings - elf vs aout In-Reply-To: <199812071001.UAA09667@nymph.dtir.qld.gov.au> from Stephen McKay at "Dec 7, 98 08:01:33 pm" To: syssgm@dtir.qld.gov.au (Stephen McKay) Date: Mon, 7 Dec 1998 16:50:32 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG, syssgm@dtir.qld.gov.au X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen McKay wrote: > There's an annoying anomaly in the new version of strings. The traditional > version specifically included tabs as valid characters for strings, while > the new one doesn't, leading to: > > $ printf 'My dog has\tno nose' > foo > $ strings -aout foo > My dog has no nose > $ strings -elf foo > My dog has > no nose > $ > > I run "strings" on lots of files (eg frobnoz.doc), not just executables. > This is irritating me specifically in regard to the INCLUDE_CONFIG_FILE > kernel compile option which now requires "strings -aout" to recover the > config file. > > Shall I devise and commit a fix for this behaviour? If you want to do this, I'd suggest making it an option. Current standards, such as the Single UNIX Specification, apparently regard a printable string as 4 or more isprint(3) chars followed by '\n' or '\0'. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message