From owner-freebsd-current Mon Dec 7 02:01:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09749 for freebsd-current-outgoing; Mon, 7 Dec 1998 02:01:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA09744 for ; Mon, 7 Dec 1998 02:01:47 -0800 (PST) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id UAA06728; Mon, 7 Dec 1998 20:01:41 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma006726; Mon, 7 Dec 98 20:01:36 +1000 Received: from atlas.dtir.qld.gov.au (atlas.dtir.qld.gov.au [167.123.8.9]) by ogre.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id UAA27965 for ; Mon, 7 Dec 1998 20:01:36 +1000 (EST) Received: from nymph.dtir.qld.gov.au (nymph.dtir.qld.gov.au [167.123.10.10]) by atlas.dtir.qld.gov.au (8.8.5/8.8.5) with ESMTP id UAA08547 for ; Mon, 7 Dec 1998 20:01:35 +1000 (EST) Received: from nymph.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by nymph.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id UAA09667; Mon, 7 Dec 1998 20:01:34 +1000 (EST) (envelope-from syssgm@nymph.dtir.qld.gov.au) Message-Id: <199812071001.UAA09667@nymph.dtir.qld.gov.au> To: freebsd-current@FreeBSD.ORG cc: syssgm@dtir.qld.gov.au Subject: strings - elf vs aout Date: Mon, 07 Dec 1998 20:01:33 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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? Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message