From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HliRC-00023r-K1
	for qemu-devel@nongnu.org; Wed, 09 May 2007 05:26:22 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HliRA-0001x0-TT
	for qemu-devel@nongnu.org; Wed, 09 May 2007 05:26:21 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HliRA-0001w5-Bq
	for qemu-devel@nongnu.org; Wed, 09 May 2007 05:26:20 -0400
Received: from nz-out-0506.google.com ([64.233.162.239])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <jeff.chua.linux@gmail.com>) id 1HliJy-0007S9-Ee
	for qemu-devel@nongnu.org; Wed, 09 May 2007 05:18:54 -0400
Received: by nz-out-0506.google.com with SMTP id i11so267397nzi
	for <qemu-devel@nongnu.org>; Wed, 09 May 2007 02:18:52 -0700 (PDT)
Message-ID: <b6a2187b0705090218q9650f5bi8d8c5fff8b73c68a@mail.gmail.com>
Date: Wed, 9 May 2007 17:18:51 +0800
From: "Jeff Chua" <jeff.chua.linux@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] configure
In-Reply-To: <200705090851.l498pIUN022707@imap.tools.intra>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <200705090851.l498pIUN022707@imap.tools.intra>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Juergen Keil <jk@tools.de>, qemu-devel@nongnu.org

On 5/9/07, Juergen Keil <jk@tools.de> wrote:

> Isn't the use of "which" wrong, anyway?
>
> "which" belongs to csh/tcsh, and tells you about csh's/tcsh's idea
> about a command or a csh command alias.
>
> IMO, for a /bin/sh (or bash) script, using the "type" command would
> be a better idea.

"which" returns the first path, "type" returns all paths.

# type awk
awk is /bin/awk
awk is /usr/bin/awk
# which awk
/bin/awk
# type foo
-bash: type: foo: not found


Either way would work, but even with "type", it still needs to be
"type foo 2>/dev/null".

Thanks,
Jeff.