Date: Tue, 11 Mar 2003 07:24:46 +0100 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "Simon 'portlint' Schubert" <corecode@corecode.ath.cx> Cc: Larry Rosenman <ler@lerctr.org>, Conrad Sabatier <conrads@cox.net>, freebsd-current@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: bash2 or devfs problem? Message-ID: <2501.1047363886@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 11 Mar 2003 02:24:23 %2B0100." <20030311022423.53b77f6d.corecode@corecode.ath.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20030311022423.53b77f6d.corecode@corecode.ath.cx>, "Simon 'portlint
' Schubert" writes:
>> 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.
Well, as far as I know we don't need a patch, we just need to mount
fdescfs then.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2501.1047363886>