From owner-freebsd-questions@FreeBSD.ORG Sun Jun 12 20:42:28 2005 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C6A616A41C for ; Sun, 12 Jun 2005 20:42:28 +0000 (GMT) (envelope-from cblack@securecrossing.com) Received: from mail2.securecrossing.com (209-254-39-195.ip.mcleodusa.net [209.254.39.195]) by mx1.FreeBSD.org (Postfix) with SMTP id 23C3C43D49 for ; Sun, 12 Jun 2005 20:42:27 +0000 (GMT) (envelope-from cblack@securecrossing.com) Received: (qmail 52143 invoked by uid 0); 12 Jun 2005 20:42:33 -0000 Received: from unknown (HELO localhost.localdomain) (cblack@securecrossing.com@127.0.0.1) by mail2.securecrossing.com with SMTP; 12 Jun 2005 20:42:33 -0000 From: Christopher Black To: Mike Meyer In-Reply-To: <17067.62149.92183.56827@guru.mired.org> References: <17067.62149.92183.56827@guru.mired.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-BRH8vpG2zTvCYvHHg4ok" Organization: Secure Crossing Date: Sun, 12 Jun 2005 16:42:28 -0400 Message-Id: <1118608948.705.6.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 FreeBSD GNOME Team Port Cc: questions@freebsd.org Subject: Re: Problems with command line scratch files in zsh X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jun 2005 20:42:28 -0000 --=-BRH8vpG2zTvCYvHHg4ok Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Why not just 'cat /etc/motd | wc' ? On Sun, 2005-06-12 at 03:31 -0500, Mike Meyer wrote: > Since going to 5.x with devfd, I've noticed that some of the shell > constructs used by zsh (and other shells - I know zsh didn't invent > this) quit working. To wit: >=20 > guru% wc <(cat /etc/motd) > wc: /dev/fd/11: open: No such file or directory >=20 > The <(...) construct runs the pipe in (), and replaces the <(...) with > the name of the /dev/fd/ entry for the output of that pipe. The file > exists for the shell process doing all this. But when the comm process > tries to open the file to read the data, the file doesn't exist. This > is pretty nasty. >=20 > Anyone got any suggestions on how to fix this? A bug report with a > patch, maybe (I couldn't find any such bug report)? Workarounds? Maybe > this should go to hackers@freebsd.org? >=20 > Thanks, >