From owner-freebsd-ports Mon Mar 10 17:24:39 2003 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B987F37B401; Mon, 10 Mar 2003 17:24:35 -0800 (PST) Received: from trafo.fsei.e-technik.tu-muenchen.de (trafo.fsei.e-technik.tu-muenchen.de [129.187.54.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3875D43FBD; Mon, 10 Mar 2003 17:24:34 -0800 (PST) (envelope-from corecode@fs.ei.tum.de) Received: from hydra (hydra.fsei.e-technik.tu-muenchen.de [192.168.113.23]) by trafo.fsei.e-technik.tu-muenchen.de (Postfix) with ESMTP id 362F566DC; Tue, 11 Mar 2003 02:24:28 +0100 (CET) Received: from corecode by hydra with local (Exim 3.35 #1 (Debian)) id 18sYVI-0000lU-00; Tue, 11 Mar 2003 02:24:28 +0100 Date: Tue, 11 Mar 2003 02:24:23 +0100 From: Simon 'portlint' Schubert To: Larry Rosenman Cc: Poul-Henning Kamp , Conrad Sabatier , freebsd-current@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: bash2 or devfs problem? Message-Id: <20030311022423.53b77f6d.corecode@corecode.ath.cx> In-Reply-To: <13630000.1047341994@lerlaptop.iadfw.net> References: <5257.1047339488@critter.freebsd.dk> <13630000.1047341994@lerlaptop.iadfw.net> X-Mailer: Sylpheed version 0.8.10claws105 (GTK+ 1.2.10; i686-pc-linux-gnu) X-Portlint: corecode Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="=.M_NnSk,zI1BVX." Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --=.M_NnSk,zI1BVX. Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Lately Larry Rosenman told: > --On Tuesday, March 11, 2003 00:38:08 +0100 Poul-Henning Kamp > wrote: > > In message , Conrad Sabatier > > writes: > >> Apparently, the nodes for the named pipes are not being created as they > >> should. > >> > >> Is this a bash problem, or something in devfs not working as expected? > > That's a good question... > > > > Has anybody found out what the standards conformant thing is for /dev/fd ? > > > > presently we do only 0,1 & 2, with the std{in,out,err} symlinks. > > > > If we are required to do all filedescriptors, we should do so with > > fdescfs by default. > It is supposed to (based on MY reading of the fd(4) man page on a UnixWare > (SysVr5) system) > be ALL filedescriptors. > > this paragraph seems to be the cogent part: > > These files, conventionally called /dev/fd/0, /dev/fd/1, /dev/fd/2, > and so on, refer to files accessible through file descriptors. If file > descriptor n is open, these two system calls have the same effect: > fd = open("/dev/fd/n",mode); > fd = dup(n); i read that only concerning *open* fds. (you can't dup a closed [non-existant] fd). furthermore i think there was a patch floating around addressing exactly this issue. perhaps it was even committed (i'm too lazy to search for it). solution was to test in configure for additional fds accessible from /dev/fd/* and build without that feature if not. cheers simon -- /"\ http://corecode.ath.cx/#donate \ / \ ASCII Ribbon Campaign / \ Against HTML Mail and News --=.M_NnSk,zI1BVX. Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE+bTrKr5S+dk6z85oRArK3AKCfcXbjf7jzWe5ps+/nFvs922eqLwCgzDJQ s/J2YrboK9YXFDanh3IPcqw= =Jd3G -----END PGP SIGNATURE----- --=.M_NnSk,zI1BVX.-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message