From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 24 08:56:45 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A08C91065670 for ; Mon, 24 Nov 2008 08:56:45 +0000 (UTC) (envelope-from stefan@fafoe.narf.at) Received: from viefep25-int.chello.at (viefep25-int.chello.at [62.179.121.45]) by mx1.freebsd.org (Postfix) with ESMTP id E2CBA8FC12 for ; Mon, 24 Nov 2008 08:56:44 +0000 (UTC) (envelope-from stefan@fafoe.narf.at) Received: from edge04.upc.biz ([192.168.13.239]) by viefep16-int.chello.at (InterMail vM.7.08.02.00 201-2186-121-20061213) with ESMTP id <20081124084032.KVFS22909.viefep16-int.chello.at@edge04.upc.biz>; Mon, 24 Nov 2008 09:40:32 +0100 Received: from lizard.fafoe.narf.at ([213.47.85.26]) by edge04.upc.biz with edge id iwgX1a0100a5KZh04wgYT9; Mon, 24 Nov 2008 09:40:32 +0100 X-SourceIP: 213.47.85.26 Received: by lizard.fafoe.narf.at (Postfix, from userid 1001) id 4B959BB5E; Mon, 24 Nov 2008 09:40:17 +0100 (CET) Date: Mon, 24 Nov 2008 09:40:17 +0100 From: Stefan Farfeleder To: Zajcev Evgeny Message-ID: <20081124084016.GA1384@lizard.fafoe.narf.at> Mail-Followup-To: Zajcev Evgeny , freebsd-hackers@freebsd.org References: <87vdueavft.fsf@h1.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87vdueavft.fsf@h1.lan> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-hackers@freebsd.org Subject: Re: `type' built-in command in /bin/sh X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2008 08:56:45 -0000 On Mon, Nov 24, 2008 at 02:12:22AM +0300, Zajcev Evgeny wrote: > > Hello there. I just hit into "problem" that built-in sh command type > outputs to stdout when error occurs. I mean it returns non-0 status, > but outputs to stdout! I think stderr has been made exactly for such > purposes and `type' should use it in case of error .. what do you > think? You're right. I will fix it.