Date: Mon, 21 Apr 2014 22:51:33 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: John Baldwin <jhb@freebsd.org> Cc: ports@freebsd.org, ehaupt@FreeBSD.org, freebsd-amd64@freebsd.org Subject: bash usage of fdescfs [was: Re: amd64/188699: Dev tree] Message-ID: <20140421195133.GO4016@kib.kiev.ua> In-Reply-To: <201404211431.12922.jhb@freebsd.org> References: <201404171850.s3HIo1am064874@freefall.freebsd.org> <201404211431.12922.jhb@freebsd.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Mon, Apr 21, 2014 at 02:31:12PM -0400, John Baldwin wrote: > On Thursday, April 17, 2014 2:50:01 pm Konstantin Belousov wrote: > > The following reply was made to PR amd64/188699; it has been noted by GNATS. > > > > From: Konstantin Belousov <kostikbel@gmail.com> > > To: John Allman <freebsd@hugme.org> > > Cc: freebsd-gnats-submit@FreeBSD.org > > Subject: Re: amd64/188699: Dev tree > > Date: Thu, 17 Apr 2014 21:44:52 +0300 > > > > On Wed, Apr 16, 2014 at 05:32:45PM +0000, John Allman wrote: > > > This is how to reproduce it: > > > > > > Fresh install of 10 on AMD 64 > > > install bash `pkg install bash` > > > Switch to bash `bash` > > > push a here document into a loop: `while true ; do echo; done< <(echo "123")` > > > receive an error: "-su: /dev/fd/62: No such file or directory" > > > > > > I'm sorry I haven't been able to research this any further. I found how while working on some important matters. As I mentioned the above works fine in all > previous versions of FreeBSD up until 10. > > > >How-To-Repeat: > > > Fresh install > > > pkg install bash > > > bash > > > while true; do echo foo done< <(echo "123") > > > > > > -su: /dev/fd/62: No such file or directory > > > > So do you have fdescfs mounted on /dev/fd on the machine where the > > test fails ? It works for me on head, and if unmounted, I get the > > same failure message as yours. I very much doubt that it has anything > > to do with a system version. > > Question I have is why is bash deciding to use /dev/fd/<n> and require > fdescfs? On older releases bash uses named pipes for this instead. The aclocal.m4 contains the test which verifies the presence and usability of /dev/fd/n for n>=3 on the _build_ host. The result of the test is used on the installation host afterward. Such kinds of bugs are endemic in our ports, but apparently upstreams are guilty too. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBAgAGBQJTVXbFAAoJEJDCuSvBvK1BaGkQAKB6E52QI4LNideeL+goVz5y qej61yMDXMv7Ifq6ZH5L2ylbyJqxqhIK/YtrHo0a54ECthOs59UDOfQFi7tdrVj6 SnVlY3+xIuoUor3TO+BGcpD19lX5V6Az/vlweb2k7eGuZyMGI7j20RqiCtpk+K2x CE+kohRQx2nu8eednLEwJggkJy5bcC5uoYGRGsVaIUv/IOAliM1DH52ZkhT2i8Qg ku3SLFAsPaEs637oYHr7mYFSU3Io+bdy/nfC0thEyl7Ft64cewyNl/ezDKBIpT24 2NIVP6Ai2ACiujyeN/cpjFEMOhewoEkgAkvGILa5KSqZpU/fFXgtMcZznZ2Bn1BP IbNRAK4XLBHRSUhIzpMMCNW1cuvEGwL4XDxOI8wlzKWdyDPQ4K+JbyTi04CNx26h lCAFEEcUTNYQETixXtmXPx3YMJxqskOWGhjqde2pfFz9FNvaMKc4Z/WNjkqpR1Y/ FobOSah41QxKtDiHiRDqJ1J9AVyxgXWxMMqmnvKf9K12u45vWcW2FdHEN2TIxVKn dzgiLNwOKEL8IE/Dv07d1y4v0iOqCpnK7XyYjWKjO5bwelf07nPdsJlutCT81SHE Hx2jG+pp2Men7/lr8KkHWBFo48x5AUC0yR+3OnN1ajcZT9lUW6RQDPTin1RNDA0R Um5pRew/En/2hGtxVhBE =TJnt -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140421195133.GO4016>