From owner-freebsd-questions@FreeBSD.ORG Mon Jun 25 20:52:34 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3422B1065673 for ; Mon, 25 Jun 2012 20:52:34 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mx1.freebsd.org (Postfix) with ESMTP id E914A8FC1A for ; Mon, 25 Jun 2012 20:52:33 +0000 (UTC) Received: from r56.edvax.de (port-92-195-102-5.dynamic.qsc.de [92.195.102.5]) by mx01.qsc.de (Postfix) with ESMTP id 24FDA3DD44; Mon, 25 Jun 2012 22:52:27 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id q5PKqQke002972; Mon, 25 Jun 2012 22:52:26 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Mon, 25 Jun 2012 22:52:26 +0200 From: Polytropon To: Fbsd8 Message-Id: <20120625225226.7a5c88db.freebsd@edvax.de> In-Reply-To: <4FE8C72F.4040908@a1poweruser.com> References: <4FE8C72F.4040908@a1poweruser.com> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions Subject: Re: fetch error X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 20:52:34 -0000 On Mon, 25 Jun 2012 16:16:47 -0400, Fbsd8 wrote: > I think I messed up the fetch setting in the envelope. > > Running 9.0 and get this console msg. > > env: usr/bin/fetch: No such file or directory > > When I enter env command to show all values I see nothing about fetch. The "env" command is often used as a "bridge" to explicitely call commands where the actual location is not known or cannot be predicted, e. g. #!/usr/bin/env bash at the start of a bash script instead of #!/bin/bash Linuxism or when statically linked, as opposed to #!/usr/local/bin/bash default location on FreeBSD. In what operation do you receive the message? Maybe some typo in a shell script or Makefile? Examine closely: env: usr/bin/fetch: No such file or directory ^ The leading / is missing, because "usr/bin/fetch" would only exist when $CWD is /, otherwise not; "/usr/bin/fetch" should be correct. % which fetch /usr/bin/fetch ^ Here the correct path is provided. Maybe you ran into some script that calls fetch the "bridge" way improperly? Test: % env usr/bin/fetch env: usr/bin/fetch: No such file or directory And now properly: % env /usr/bin/fetch usage: fetch [-146AadFlMmnPpqRrsUv] ............ It seems that env is used here to "set environment and execute command"; see "man env" for details. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...