Re: Design question(s), re: why use of tmp-files or named-pipes(/dev/fd/N) instead of plain pipes?

Path	csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!usenet.stanford.edu!not-for-mail
From	Greg Wooledge <wooledg@eeg.ccf.org>
Newsgroups	gnu.bash.bug
Subject	Re: Design question(s), re: why use of tmp-files or named-pipes(/dev/fd/N) instead of plain pipes?
Date	Mon, 26 Oct 2015 08:27:11 -0400
Lines	11
Approved	bug-bash@gnu.org
Message-ID	<mailman.1069.1445862466.7904.bug-bash@gnu.org> (permalink)
References	<56218DA5.8030501@tlinx.org> <5622CDC8.2030102@case.edu> <5622EB23.6020700@tlinx.org> <20151019122800.GS27325@eeg.ccf.org> <56254945.6020606@tlinx.org> <20151019154705253009402@bob.proulx.com> <56285092.2020701@tlinx.org> <20151023154221971048598@bob.proulx.com>
NNTP-Posting-Host	lists.gnu.org
Mime-Version	1.0
Content-Type	text/plain; charset=us-ascii
X-Trace	usenet.stanford.edu 1445862467 1072 208.118.235.17 (26 Oct 2015 12:27:47 GMT)
X-Complaints-To	action@cs.stanford.edu
To	bug-bash@gnu.org
Envelope-to	bug-bash@gnu.org
Content-Disposition	inline
In-Reply-To	<20151023154221971048598@bob.proulx.com>
User-Agent	Mutt/1.4.2.3i
X-detected-operating-system	by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From	139.137.100.1
X-BeenThere	bug-bash@gnu.org
X-Mailman-Version	2.1.14
Precedence	list
List-Id	Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe	<https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive	<http://lists.gnu.org/archive/html/bug-bash>
List-Post	<mailto:bug-bash@gnu.org>
List-Help	<mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe	<https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
Xref	csiph.com gnu.bash.bug:11764

Show key headers only | View raw

On Fri, Oct 23, 2015 at 04:01:37PM -0600, Bob Proulx wrote:
> The /proc/self/fd/ directory is a kernel construct.  It does not have
> normal file system semantics.

> And really what would be a sane purpose in being able to remove files
> from it?  What would that do?  Would that make any sense at all?  I
> think it wouldn't make any sense.

Well, it *could* conceivably act like close().  But that's a bit
off topic here.

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: Design question(s), re: why use of tmp-files or named-pipes(/dev/fd/N) instead of plain pipes? Greg Wooledge <wooledg@eeg.ccf.org> - 2015-10-26 08:27 -0400

csiph-web